Registering online immediately after finding an old exposure may feel responsible, but it can surrender options before the company understands its timeline, amount or remedy. Preserve data, confirm agency-contact status and quantify each state before choosing a path.

1. Lock the activity and agency-contact timeline

Build a monthly state timeline beginning with the first sale, inventory, employee, contractor, trade show and on-site service. Preserve source data from marketplaces, ERP, banking and logistics. Separate direct sales, marketplace-collected sales, wholesale, exempt transactions and nontaxable products. Gross sales alone can materially overstate or understate exposure.

Search registrations, mail, agency notices, service-provider accounts and contacts involving related entities. VDA programs commonly require that the taxpayer has not already been contacted by the state concerning the liability and satisfies state-specific criteria. Verify current eligibility before an ordinary registration or questionnaire response; do not assume one state or tax type controls another.

  • First sales, people, inventory and on-site activity
  • First potential economic-activity trigger
  • Marketplace collection versus company direct sales
  • Notices, questionnaires, audits and registration contacts
  • Tax collected from customers but not remitted

2. Quantify with transaction data, not a top rate

Rebuild the tax base by state, month, channel, product and customer. Remove only nontaxable products, supported resale or exempt transactions and marketplace-collected amounts that current official rules justify. Apply destination, local rate and historical effective-date logic. Missing addresses, refunds, freight and discounts should appear as data exceptions, not silent assumptions.

Show tax, interest, potential penalty, return volume, registration cost and customer-recovery feasibility separately. Sales Tax can be difficult to recover years later, leaving the business with the economic cost. Tax collected but not remitted is more sensitive and may receive different eligibility or relief treatment; escalate it as a distinct category.

3. A VDA defines a process; it does not erase tax

A voluntary disclosure agreement commonly exchanges proactive disclosure for an agreed lookback and specified penalty treatment. The company may still file returns, pay tax and interest and remain compliant prospectively. MTC offers a multistate process, but its official materials show that participating states, covered taxes and procedures differ; not every state or fact pattern is handled through one program.

Before applying, confirm the anonymous phase, identity-disclosure point, eligibility representations, lookback, estimation method, payment deadline, related-entity scope and future filings. Do not copy a prior outcome from another state or promise data that cannot be produced within the proposed agreement timetable.

  • Current eligibility for voluntary disclosure
  • Entities, taxes and periods within scope
  • Returns, tax, interest and penalty treatment
  • Anonymous and named stages of the process
  • Prospective registration and compliance commitments

4. Back filing and prospective registration are not shortcuts

Back filing may be appropriate when VDA is unavailable, the exposure is short, or the state has already made contact. First understand the registration system's start date, historical forms, interest computation and penalty-relief process. Filing only a recent period without analysis can leave earlier periods unexplained and invite a wider inquiry.

Prospective registration does not extinguish historical liability. It is a decision to evaluate only when documented facts and law support no earlier obligation, or governance accepts a quantified residual risk. Record the unresolved periods and reassessment triggers; never present “start now” as the automatic cure for old facts.

5. Convert remediation into sustainable operations

For each state, build a reverse plan covering owner, registration, historical returns, payment, system configuration, customer communication, certificates and the first ordinary return. Historical calculations and the future tax engine must use the same product taxability, address hierarchy and channel definitions or the project will create new differences immediately.

Retain the decision memo, official authority, data version, assumptions, approvals and agency correspondence. Re-run Nexus and account status at least quarterly and whenever a warehouse, employee, channel or product changes. Completion means historical periods are addressed, current invoices work and the filing calendar is sustainable—not merely that an account number exists.

  • State decision memo and governance approval
  • Historical return, payment and agreement milestones
  • Tax-engine, ERP and invoice effective dates
  • Certificates, customer communications and first ordinary return
  • Quarterly monitoring and event-driven review