Economic Nexus Thresholds in 2026: What Counts?

Why the familiar threshold shortcut fails

Many early remote-seller laws used $100,000 in sales or 200 transactions, but states have changed their tests over time. Indiana removed its 200-transaction test effective January 1, 2024, and Illinois removed its transaction test for periods beginning January 1, 2026.

A company relying on an old summary can register unnecessarily, miss a true obligation, or choose the wrong collection date. Treat every threshold as a versioned rule.

• Record the state and official source.
• Record the sales amount and transaction test separately.
• Record the effective date of every change.

Determine which sales belong in the numerator

States may count gross receipts, retail sales, taxable sales, or another defined category. Exempt, wholesale, digital, service, and marketplace transactions may be included or excluded differently.

Start from order-level sales rather than tax-return totals. The dataset should preserve destination, channel, product class, exemption status, gross amount, taxable amount, order date, refund date, and customer type.

• Do not remove exempt or marketplace sales before checking the rule.
• Use destination state rather than billing state unless the rule requires otherwise.
• Keep refunds and cancellations traceable to the original order.

Apply the correct measurement period

A threshold may use the current calendar year, previous calendar year, both, or another period. The obligation may begin immediately, after a grace period, or on a future date defined by the state.

Run each state through its own calculation logic. A rolling dashboard can warn the team, but the final determination should be tied to the statutory period and the official state guidance.

• Store current-year and prior-year totals.
• Calculate the threshold date from actual orders.
• Preserve the report used to support the decision.

Monitor physical and economic nexus together

Economic nexus thresholds do not protect a seller that already has physical presence. Inventory, employees, contractors, installations, or events can create an obligation below the remote-seller threshold.

Use two parallel reviews: one for activities and assets, and another for sales thresholds. The earliest valid nexus event should drive the registration analysis.

• Survey operations teams quarterly.
• Review fulfillment locations monthly.
• Include acquired companies and new sales channels.

Create a threshold response playbook

At a warning level, validate data, confirm the current rule, estimate product taxability, and identify registration lead time. After crossing, determine the legal collection date and complete registration before enabling tax.

The playbook should also cover voluntary disclosure or professional advice for historic exposure. Do not silently start collecting today if earlier periods may be involved.

• Alert at 75%, 90%, and 100% of the threshold.
• Assign tax, engineering, finance, and customer-support owners.
• Document both “register” and “no registration” conclusions.

Work through a threshold calculation example

Assume a seller has $120,000 of destination sales into a state: $70,000 taxable direct sales, $20,000 exempt wholesale sales, and $30,000 marketplace sales. If the state uses gross sales including marketplace transactions, the threshold total may be $120,000. If it uses a narrower sales base or excludes facilitated sales, the result can be different.

Now add timing. If the rule tests the previous calendar year, crossing $100,000 in November may create an obligation on a state-defined future date. If it tests a rolling 12-month period quarterly, a different order can become the triggering sale. The same revenue therefore produces different outcomes under different definitions.

A defensible worksheet shows the source transactions, inclusion logic, excluded categories, threshold date, official authority, reviewer, and conclusion. It should be possible for another reviewer to reproduce the answer without asking how the spreadsheet was built.

• Start with complete data, then apply inclusion rules.
• Calculate the amount and trigger date separately.
• Do not treat an internal alert date as the legal collection date.
• Retain the calculation used at registration.

Design a nexus dashboard that stays current

A useful dashboard is a control tool, not a colorful list of totals. For every state it should display physical-presence status, current and prior-period sales, included transaction count, marketplace treatment, threshold rule, percentage reached, registration status, collection start date, and next review date.

Version the underlying rule table. When a state removes a transaction test—as Illinois did beginning January 1, 2026—the old rule must remain available for historical periods while new transactions use the current rule. Overwriting the cell destroys evidence for earlier decisions.

Assign rule maintenance to a named owner and use official state or Streamlined Sales Tax guidance as the primary source. Aggregator charts are helpful for discovery, but the final conclusion should link to the controlling authority.

• Show data freshness and last successful import.
• Flag missing destination or channel data.
• Separate current law from historical rules.
• Require a source URL and effective date for every threshold.