Multi-State Sales Tax for Remote Sellers: 2026 Guide

Start with every form of nexus

Nexus is the connection that allows a state to impose a tax obligation on a seller. Economic nexus is only one path. Employees, contractors, offices, inventory, trade shows, installation work, affiliates, or other in-state activity can create physical nexus even when sales remain below an economic threshold.

Build a state inventory that combines operational facts with destination sales. Fulfillment inventory deserves special attention because stock may move between states without appearing in the seller’s ordinary sales reports. Interview operations, HR, logistics, and sales teams rather than relying only on accounting data.

For each activity, capture its start date, end date, frequency, legal entity, and supporting evidence. This timeline matters because registration exposure can begin before the month in which finance first discovers it.

• List employees, contractors, inventory, property, events, and services by state.
• Obtain marketplace and fulfillment inventory-location reports.
• Document the date each activity started and ended.
• Review acquisitions and related entities separately before combining conclusions.

Measure economic nexus correctly

State thresholds are not interchangeable. A state may measure gross sales, retail sales, taxable sales, or a different base; it may use the current or previous calendar year, a rolling period, or a transaction test. Illinois, for example, removed its transaction-count test beginning January 1, 2026 and now applies a $100,000 cumulative gross-receipts test for specified Illinois sales during the applicable lookback period.

Use order-level destination data and preserve marketplace, exempt, wholesale, refunded, and nontaxable sales as separate fields. Whether each category belongs in the threshold numerator depends on the state rule; deleting it early makes the analysis impossible to reproduce.

The monitoring report should show both the amount accumulated and the date the threshold was first met. That date drives the next question: when registration and collection must begin under that state’s rule.

• Create a rule record for amount, sales base, period, transaction test, and effective date.
• Monitor at least monthly and more often near a threshold.
• Set alerts before the threshold so registration work can begin early.
• Preserve the source report used for every register-or-do-not-register decision.

Register before switching on collection

Crossing a threshold does not mean tax should be collected immediately in every state. Confirm the state’s effective date, registration procedure, permit timing, and any Streamlined Sales Tax registration option first. Collecting without authority can create refund and remittance problems.

Registration is the start of an operating obligation. Capture the account number, filing frequency, first return date, zero-return requirement, local registrations, login ownership, and renewal rules in a central calendar.

• Confirm the obligation and effective date.
• Complete registration before checkout activation.
• Add returns, prepayments, and license renewals to the compliance calendar.

Configure sourcing, products, and channels

The correct rate can depend on destination, origin, product type, delivery method, customer exemption, and local jurisdiction boundaries. A state-level headline rate is not enough for checkout or return preparation.

Assign collection responsibility per channel. Marketplaces commonly collect on facilitated orders, while the seller remains responsible for direct website, invoice, phone, or wholesale sales when nexus exists.

• Map products to tax categories and document assumptions.
• Test addresses, discounts, shipping, refunds, and exemptions.
• Keep marketplace-collected and seller-collected tax in separate accounts.

Reconcile and review every filing period

Before filing, reconcile gross sales, taxable sales, exempt sales, marketplace sales, tax collected, refunds, and jurisdiction totals to the general ledger and source systems. Net marketplace deposits are not sales totals because fees and withheld amounts reduce the payout.

After filing, retain the return, payment confirmation, workpapers, source reports, notices, and rule versions used. Repeat the nexus review when products, channels, personnel, inventory locations, or state laws change.

• Explain material differences before submission.
• Track notices and amendments to resolution.
• Review nexus and registrations at least quarterly.

Build a state-by-state implementation plan

Prioritize states using four factors: known physical presence, threshold proximity, historical exposure, and revenue concentration. A business near ten thresholds should not activate all ten states blindly. Validate the data, confirm the legal start date, estimate the operational workload, and sequence registrations so checkout, accounting, and filing are ready together.

Each implementation ticket should name the legal entity, registration account, collection start date, channels, product mappings, sourcing rule, test cases, return owner, and first filing deadline. Include customer-support messaging for invoices or subscriptions whose tax changes after activation.

If the review uncovers past-due obligations, pause before treating a current registration as a complete cure. A qualified adviser can help assess lookback periods, voluntary disclosure programs, penalties, and whether prior customer contracts allow recovery.

• Rank states by exposure and urgency.
• Assign tax, finance, engineering, and support owners.
• Require sign-off before collection goes live.
• Track historical remediation separately from current compliance.

Use a repeatable monthly control cycle

A sustainable multi-state program follows the same cycle every month: import orders, validate destination data, update threshold totals, review physical-presence changes, reconcile marketplace activity, prepare returns, approve payments, and archive evidence. The goal is not more spreadsheets; it is a controlled chain from source transaction to filed return.

Create exception reports for missing ship-to states, unexpected tax rates, tax collected in unregistered states, taxable orders with zero tax, and marketplace tax posted to the seller’s liability account. Exceptions reveal configuration drift earlier than a notice from a revenue department.

Quarterly, refresh the rule matrix and challenge old assumptions. A conclusion that was correct for last year’s product, warehouse footprint, or channel mix may no longer be correct today.

• Close exceptions before the return is filed.
• Compare registered states with tax-enabled states.
• Retain rule versions and approval history.
• Review filing frequencies and zero-return duties after state notices.