US sales tax is a state and local obligation—not one federal tax. A reliable 2026 compliance process connects nexus, registration, sourcing, product taxability, exemptions, marketplace responsibility, filing, and audit evidence at transaction level.
Key takeaways
Test physical and economic nexus separately in every state where you have customers or business activity.
Register with the relevant state before collecting tax; a threshold does not create permission to collect.
Use destination, product-taxability, marketplace, exemption, and filing data together rather than relying on one national rate.
Reconcile returns to orders, refunds, exemptions, and marketplace reports before every filing.
How US sales tax works
States set their own sales and use tax rules, while counties, cities, and special districts may add local rates. The same transaction can therefore produce different results depending on the delivery location, the seller’s nexus, the product classification, and the state’s sourcing rules.
Sales tax is generally charged to the purchaser at checkout and remitted by a registered seller. Use tax commonly complements sales tax when taxable property is used in a state but the seller did not collect the applicable tax. Definitions and taxable categories differ by jurisdiction, so a product decision made for one state should not automatically be copied nationwide.
- Identify the legal seller for each channel.
- Capture the customer’s delivery or consumption location.
- Map each SKU or service to a state-specific tax category.
- Keep the source and effective date behind every rule.
Physical nexus and economic nexus
Physical presence can arise from offices, employees, contractors, inventory, warehouses, events, or other in-state activity. If physical nexus exists, an economic threshold may not protect the seller; state registration obligations can apply regardless of remote-sales volume.
Economic nexus applies to remote sellers after state-defined sales or transaction thresholds are met. Thresholds vary in amount, measurement period, included revenue, treatment of exempt or marketplace sales, and effective date. Several states have removed transaction-count tests, so a static “$100,000 or 200 transactions” rule is not dependable for 2026.
- Monitor current and prior calendar periods where required.
- Separate gross, retail, and taxable sales definitions.
- Track marketplace and direct sales independently.
- Review state guidance whenever a threshold is approached.
Registration, sourcing, and rates
After confirming an obligation, register with the state tax authority before switching on collection. Some states expect registration soon after a threshold is crossed, while others use a specified future effective date. Collecting without a permit can create separate legal and accounting problems.
The correct rate is not always the seller’s local rate. Destination-based states generally source a shipped sale to the customer’s delivery address; origin-based rules and special product rules can change the result. Combined rates may include state, county, city, and district components, and boundary-level accuracy can matter more than a five-digit ZIP code.
- Store registration numbers and effective dates.
- Use full delivery addresses when possible.
- Test shipping, discounts, refunds, and tax-inclusive pricing.
- Document overrides instead of changing rates manually without evidence.
Product taxability, SaaS, and exemptions
Tangible goods are often taxable, but food, clothing, medicine, manufacturing inputs, digital products, and services can receive special treatment. SaaS is especially state-specific: facts such as downloadability, customer control, hosting, bundled support, and the character of the service can affect classification.
A customer’s exempt status does not automatically make every purchase exempt. Sellers should obtain the correct certificate, validate required fields, apply it only to eligible products and jurisdictions, and retain it for the required period. Marketplace-collected sales also need separate records so the seller can show who collected and remitted the tax.
- Maintain a state-by-product taxability matrix.
- Link certificates to customers and covered transactions.
- Track certificate expiration or renewal rules.
- Retain marketplace agreements and tax reports.
Filing, reconciliation, and a 2026 control plan
Registration usually creates a filing obligation even for a period with no taxable sales. Filing frequency is assigned by the state and can change as volume changes. Late or missing zero returns may still trigger notices and penalties.
Before filing, reconcile gross sales, taxable sales, exempt sales, tax collected, refunds, marketplace sales, and payments by jurisdiction. Investigate differences between checkout tax and general-ledger balances rather than forcing the return to match. Keep returns, workpapers, source reports, notices, and rule decisions in a repeatable audit file.
- Run a monthly nexus review.
- Maintain a registration and filing calendar.
- Reconcile each channel and jurisdiction.
- Review notices and rate changes with named owners.
- Escalate uncertain taxability decisions to a qualified adviser.
Build a sales tax implementation roadmap
Start with a fact inventory: legal entities, sales channels, inventory locations, employees, contractors, trade shows, fulfillment partners, customer destinations, and revenue by state. Compare those facts with current state guidance, then rank jurisdictions as registered, registration required, approaching threshold, monitored, or no current exposure. A threshold spreadsheet without physical-presence facts is incomplete.
For each state requiring action, record the authority source, triggering fact, measurement period, registration deadline, collection start date, filing frequency, account credentials owner, and first return. Configure checkout only after the permit and effective date are confirmed. Test representative taxable, exempt, discounted, shipped, refunded, and marketplace orders before release.
- Assign an owner and backup for every state account.
- Set alerts before—not only at—the statutory threshold.
- Keep implementation tickets linked to the legal source and effective date.
- Re-test after channel, inventory, entity, or product changes.
Design an audit-ready transaction data model
A defensible record should show order date, invoice date, legal seller, channel, customer and delivery address, product tax code, taxable amount, rate components, exemption basis, collector, remitter, refund linkage, and the rule version used. Store the original source values as well as normalized values so an auditor can trace the return back to the order.
Close each period by reconciling commerce systems to payment processors, marketplace settlements, the general ledger, tax engine reports, and filed returns. Explain timing, currency, fee, refund, and rounding differences in a signed workpaper. Do not solve a variance by overwriting source data or forcing a return total.
- Preserve address-validation and tax-calculation responses.
- Version product mappings and manual overrides.
- Link exempt sales to approved certificates.
- Retain returns, payments, notices, and reconciliation evidence together.
Frequently asked questions
Is there one US sales tax rate?
No. State and local rates, sourcing rules, and product taxability vary by jurisdiction. A combined rate should be determined for the specific transaction and location.
Does crossing an economic nexus threshold mean I can immediately collect tax?
No. Crossing a threshold can create an obligation, but the seller generally needs to register with the state before collecting tax.
Do marketplace sales eliminate all seller obligations?
No. A facilitator may collect on facilitated sales, while the seller can still have nexus monitoring, direct-channel, registration, reporting, exemption, and reconciliation duties.
How often should a business review US sales tax nexus?
Review it at least monthly and immediately after opening a location, hiring in a state, moving inventory, adding a fulfillment partner, attending events, acquiring a business, or launching a new channel.
What is the safest way to automate US sales tax?
Automate only after legal entities, nexus states, product mappings, sourcing, exemptions, and marketplace responsibility are documented. Then test the integration and reconcile automation outputs to source orders every filing period.
Official sources
Reviewed against the following primary sources on Aug 8, 2026.