Streamlined guidance keeps remote-seller nexus state-specific
The multistate chart is a useful orientation layer, but its own warning is decisive: thresholds, measurement periods, sales bases, and effective dates remain matters of individual state law and current state guidance.
Editorial figure by Indirect Tax Monitor. Source context: Streamlined Sales Tax remote seller guidance.
One chart does not create one nexus rule
The Streamlined Sales Tax page helps a remote seller see how economic-nexus approaches differ across states. That orientation value is real, but it is not a uniform rule engine. The page itself distinguishes sales-only tests from transaction tests and combined tests, then warns that the underlying sales base may differ. Those dimensions can change which activity enters a threshold calculation before a dollar or transaction count is compared.
A tax platform should therefore model each jurisdiction as a separately versioned authority record. At minimum, the record needs the covered seller type, included sales base, comparison operator, transaction condition if any, measurement period, effective date, source URL, retrieval date, and reviewer. Collapsing those fields into a single national threshold produces a result the source does not support.
Physical presence and economic nexus are different paths
The guidance says a seller with physical presence in a state is not treated as a remote seller for this purpose and may have a registration obligation regardless of remote-sales volume. A remote-seller threshold screen cannot safely become the only nexus test. Property, people, inventory, affiliates, events, marketplace relationships, and other facts may require separate review under the applicable state's current authority.
System design should preserve the path that produced a review outcome. A no-threshold result means only that the configured remote-seller test was not met on the recorded facts and dates. It is not a universal no-nexus conclusion. A physical-presence flag, marketplace-facilitator rule, voluntary registration choice, or state-specific exception needs its own evidence and decision state.
The chart is a discovery layer, not the final authority
The page labels the chart as a summary as of January 11, 2023, while individual rows display later changes. That combination makes row-level dates and linked state records essential. A team should not infer that every row shares one freshness date or that an older summary label invalidates a documented later update. It should open the current state link and retain the exact authority used for the decision.
A defensible workflow captures the chart as the discovery source, the state record as the decision source, and the effective period that governs the seller's facts. If the two disagree, the system should stop automatic treatment, retain both records, and route the difference for qualified review rather than silently choosing the most convenient threshold.
Threshold monitoring needs dated inputs and change control
Remote-seller monitoring is not just a year-to-date revenue counter. The calculation may depend on current or prior periods, destination, sale type, marketplace channel, refunds, exempt or resale activity, and the state definition of receipts or sales. Each input needs a provenance trail so a reviewer can reproduce the population used on the date the threshold was evaluated.
A useful product demonstration should show a rule-version change, a seller moving from below to above a threshold, and a correction to the underlying sales population. The system should preserve the earlier result, identify affected periods, separate registration and collection decisions, and prevent a newly updated rule from rewriting historical conclusions without review.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Indirect Tax Monitor will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.