This is a workflow problem before it becomes a filing problem.

Once a threshold may have been crossed, the real questions become: are we already registered, which periods are affected, what data source do we trust, and how quickly can we move from uncertainty to a documented state-by-state filing plan?

What economic nexus actually means.

Economic nexus generally refers to a state rule that creates a sales tax obligation based on remote sales activity rather than physical presence alone. In practice, that usually means a revenue threshold, a transaction-count rule, or both.

It does not automatically mean the filing work is identical in every state. Thresholds can differ, transaction counting methods can differ, and the operational burden after crossing a threshold can differ even more.

Why teams miss nexus thresholds even when the business is growing fast.

Most teams do not miss nexus because they are careless. They miss it because the signal is spread across Shopify, Amazon, Stripe, wholesale orders, marketplaces, and internal reporting. The company may be collecting sales data, but not reviewing it through a nexus lens.

  • Revenue reports may not be grouped cleanly by destination state.
  • Marketplace sales may be mixed with direct-channel sales.
  • Refunds and filing-period cutoffs may distort threshold checks.
  • Finance teams often review accounting reports, not tax-obligation reports.

How states vary in practice.

Some states are widely known for a single revenue threshold. Others historically used transaction-count tests or changed them over time. Some states are easy to watch once the data is clean. Others become annoying because local layering, marketplace treatment, or portal behavior adds friction after registration.

That is why a “state-by-state threshold chart” is useful only as a starting point. The more important operational question is whether your team can tie threshold monitoring to registrations, filing cadence, and approved return data once an obligation exists.

What to review before deciding whether a state needs action.

  • Destination-state sales totals across all channels for the relevant lookback period.
  • Whether marketplace sales should be separated from direct-channel sales for the analysis.
  • Whether any physical presence factors also exist, such as inventory, employees, or events.
  • Whether the state is already registered and active, even if nobody is monitoring it well.
  • Whether the current source data is clean enough to support a filing packet once registration happens.

Think in practical state buckets, not just a giant threshold spreadsheet.

Already active statesThreshold analysis matters less here than keeping the filing workflow timely and clean.
Likely crossed statesThese need a registration review and a plan for first filing periods.
Watchlist statesSales are approaching meaningful levels, so reporting discipline matters now.
Marketplace-heavy statesThese often need cleaner separation of direct sales and facilitator-handled sales.

What to do next if you think nexus may already exist.

Start by cleaning the state sales view, separating channels, and identifying which states are already registered versus unresolved. Then move from threshold theory into operations: registrations, filing calendar setup, source-data validation, and recurring return prep.

Need a cleaner nexus workflow?

AtomicTax helps teams connect state sales data, registration status, filing cadence, and recurring return operations into one clearer system.

Explore nexus monitoring Contact AtomicTax