Registering After You Already Have Nexus: Handling the Gap Period

If your business discovers that it had sales tax nexus before it registered, treat the time between the nexus start date and the registration or compliance date as a separate “gap period.” Do not assume that registering now automatically resolves earlier obligations. The practical task is to identify the affected states, reconstruct activity for each state, determine whether ordinary late registration or voluntary disclosure is the appropriate route, and address prior returns, tax, interest, and any customer tax already collected.

Sales tax is administered state by state. For liabilities handled through the Multistate Voluntary Disclosure Program (MVDP), each state determines its own lookback period and calculation method. This means a business with the same fact pattern in several states may need a different resolution in each one.

Quick Facts About the Gap Period

Who Needs to Review a Prior Nexus Period?

A gap-period review is appropriate when a business determines that its nexus date may precede its registration date. This can arise after reviewing sales volume, transaction history, employees, inventory, contractors, trade-show activity, or other in-state connections. Start with the underlying trigger rather than the date someone first noticed the issue.

If the nexus date is still uncertain, review Sales Tax Nexus Thresholds: What Triggers Registration and Nexus Explained: When You Owe Sales Tax in Another State. The goal is to create a defensible state-by-state timeline, not to choose one date for the entire business. Handling the gap period is one route among several; for the full set of options when a business is behind, see Behind on Sales Tax: How to Fix Unregistered or Unfiled Back Periods.

Prioritize states where any of the following applies:

• The business appears to have crossed a relevant nexus threshold before registering.
• People, property, inventory, or business activity may have created an in-state connection.
• Invoices show sales tax charged before the business began filing returns.
• The business registered but selected a start date that may not reflect when nexus arose.
• A marketplace, billing platform, or accounting system handled some transactions differently from others.
• The business has potential exposure in multiple states and wants to evaluate a coordinated voluntary disclosure route.

Ordinary late registration and voluntary disclosure should not be treated as interchangeable administrative labels. Before registering, filing, paying, or initiating state contact, decide which route needs to be evaluated. For the MVDP in particular, a taxpayer may be considered for a state and tax type if it has not filed returns or made payments for that tax, is not under audit, and has had no prior state contact concerning the obligation. A premature filing or inquiry can therefore matter to the available strategy. For how disclosure programs work and what relief they offer, see Voluntary Disclosure Agreements: How to Come Forward on Back Sales Tax.

Prepare a State-by-State Gap-Period File

Build one working file for each state rather than combining all sales into a national spreadsheet with a single conclusion. The file should allow someone reviewing it to understand what happened, when it happened, and how the estimated exposure was calculated.

Preparation checklist

• Proposed nexus date: Record the date and the event or activity supporting it. If more than one trigger is possible, preserve each candidate date.
• Registration history: Note whether the business has registered, filed, paid, received correspondence, or communicated with the state about the tax at issue.
• Sales records: Gather transaction-level sales by destination, including taxable, exempt, marketplace, canceled, and refunded transactions.
• Customer tax records: Separate tax actually collected from tax that might have been due but was not charged. Do not combine these figures.
• Exemption support: Organize available resale or exemption documentation by customer and transaction period.
• Marketplace activity: Identify transactions handled through marketplaces and preserve statements showing how those sales were treated.
• Prior-period estimate: Develop a good-faith estimate for each state, with assumptions clearly documented.
• Current operations: Confirm that current invoices, checkout settings, product coding, and filing workflows align with the intended compliance date.

The distinction between collected tax and uncollected potential liability is especially important. In the MVDP, sales or use tax already collected from customers must be remitted in full. It may also carry penalties that cannot be waived or a lookback beginning when collection first occurred. Keeping these amounts separate prevents an estimate based only on uncollected tax from obscuring a more serious collected-tax issue.

Choose and Complete the Appropriate Process

The correct path depends on the state, prior contacts, filing history, audit status, amount involved, and whether the state participates in the MVDP. Use the following sequence to organize the decision without assuming that one route fits every jurisdiction.

1. Confirm the state and tax type. Analyze sales and use tax separately for each state. Also confirm which legal entity made the sales and which entity, if any, registered.
2. Map prior state contact. Record registrations, returns, payments, notices, audits, questionnaires, and communications. This history is relevant when assessing whether voluntary disclosure remains available.
3. Estimate the lookback exposure. Calculate a good-faith state estimate using the relevant transaction records. Under the MVDP, staff will not process an application unless the estimated back-tax liability is at least $500 for each state for the applicable lookback period.
4. Separate participating and nonparticipating states. The National Nexus Program does not handle applications for nonparticipating states. Those states must be approached directly.
5. Submit through the selected channel. A taxpayer or its representative applies for the MVDP online through the Multistate Tax Commission and provides requested information about its activities and estimated liability. A direct-state procedure may be different.
6. Complete registration separately. Participation in the MVDP does not register the business. The taxpayer must follow each state’s prescribed registration procedure.
7. Carry out the final terms. Under an executed MVDP voluntary disclosure agreement, the taxpayer generally files returns and pays past-due tax plus interest for the agreed lookback period. Depending on the agreement, penalties and liabilities before that period may be waived.

State-specific variation can be substantial. Indiana, for example, states that it does not currently participate in MTC programs. Its separate VDA program generally applies a lookback of three full calendar years plus the current period for qualified sales and use tax applicants and accepts Form VDA-1 in writing or online. This example should not be used as a template for another state.

Costs, Timing, and Ongoing Maintenance

There is no useful single dollar amount or completion schedule for resolving a gap period. The amount can depend on the state’s calculation method, the agreed lookback, taxable sales, valid exemptions, tax already collected, interest, and the terms of any voluntary disclosure agreement. Each state determines its own lookback period and calculation method for liabilities addressed through the MVDP.

Once the historical issue is assigned to the appropriate process, create a separate current-compliance workstream. That prevents negotiations or record reconstruction for earlier periods from delaying present obligations.

• Maintain a calendar for each state’s assigned filing frequency and due dates.
• Reconcile returns to sales records, marketplace reports, exemption records, and the general ledger.
• Track tax collected as a separate amount rather than treating it as operating revenue.
• Retain the nexus analysis, application materials, executed agreements, returns, payment confirmations, and supporting calculations together.
• Review new states regularly as sales patterns, personnel, inventory locations, and business activities change.
• Document changes to tax settings, product classifications, exemption treatment, and registration status.

The most important control is a clean handoff from historical remediation to ongoing compliance. The gap period should have a documented resolution path, while current transactions should follow the registrations and procedures applicable to each state. Keeping those workstreams distinct makes it easier to verify what has been corrected, what remains under review, and what must be maintained going forward.