For SaaS billing teams, 2026's sales tax picture is this: economic nexus — obligations based on revenue alone, no physical presence — is now the standard across virtually every state with a sales tax, several states adjusted digital-services rules this year, and the most common failure mode is discovering obligations you did not know you had.
General information only — not tax advice. Tax rules are complex and change frequently; consult a qualified tax professional for decisions about your company's obligations.
Economic nexus: the rule that changed everything
Before the U.S. Supreme Court's 2018 decision in South Dakota v. Wayfair, a state generally needed your physical presence — an office, employees, a warehouse — before it could require you to collect sales tax. Wayfair removed that requirement: economic nexus means your revenue volume alone can create a sales tax obligation in a state where you have no office, no employees, and no physical footprint at all.
For SaaS companies, this matters more than for almost any other business type, because SaaS has no warehouses or storefronts to serve as intuitive nexus markers. A SaaS company selling nationally can cross economic nexus thresholds in dozens of states purely through customer revenue — and many founders are surprised to learn how wide their footprint already is. Billing platforms reflect this operationally: Stripe Tax, for example, calculates tax from product type, customer location, and business location, and includes threshold monitoring and registration support — the tooling assumes you track obligations across many jurisdictions at once.
The thresholds themselves are public and vary by state — commonly around $100,000 in annual sales into the state, with some large states setting higher bars. Once you cross a threshold, the obligation begins; the uncomfortable part is that many companies cross thresholds mid-year without noticing, and discover quarters of uncollected tax only later.
Two cautions. First, thresholds and rules change — treat any specific figure as a starting point for verification with a tax professional, not a filing decision. Second, several states have moved away from transaction-count tests toward pure sales thresholds; confirm the current test in each state rather than relying on last year's rules.
Nexus is not the same as taxability
Having nexus in a state means you have a filing obligation there. It does not automatically mean you owe sales tax on your SaaS product. States classify SaaS revenue differently:
- Some states treat SaaS access as a taxable service (often categorized as data processing or an information service).
- Some states exempt SaaS entirely, treating it as a non-taxable service.
- Some states tax it only in specific forms — downloaded software vs. remotely accessed software, prewritten vs. custom, business vs. consumer use.
The practical consequence: a billing team needs two answers per state, not one — (1) do we have nexus here? and (2) is our specific product taxable here, and at what rate? Companies that answer only the first question either over-collect (charging tax where none is owed, which customers notice) or under-collect (the liability stays with the seller — uncollected tax does not disappear, it becomes your debt).
This is also why generic "SaaS is taxable in X states" lists are dangerous without dates and definitions. Classifications shift — several states have updated or expanded their definitions of taxable digital services in the past 12–18 months, explicitly capturing SaaS revenue categories that were previously gray areas. Verify against current sources for your product type.
The SaaS-specific triggers teams miss
Beyond revenue thresholds, practitioners flag several nexus triggers that catch SaaS companies off guard:
- Crossing a threshold mid-year. Fast-growing companies lose track of exactly when they crossed. If nobody monitors revenue by state continuously, obligations can accumulate silently for quarters.
- Remote employees creating physical-presence nexus. A developer, support rep, or salesperson working from home in another state can establish physical-presence nexus there — regardless of revenue in that state. With remote work normalized, this is now one of the most common surprise triggers.
- Contractors and service providers. Third-party implementation partners or onboarding teams performing work on your behalf in a state can create nexus, even for limited engagements.
- Trailing nexus. Some states require continued filing for a period after nexus-creating activity stops. Check each state's rules before assuming obligations end when activity stops.
What changed in 2026
The nexus framework itself is largely settled — the 2026 developments are adjustments at the edges, but edges matter in tax:
- Digital-services definitions keep expanding. The pattern across states is toward explicitly capturing more SaaS and digital-services revenue in taxable categories that were previously gray areas. If your product was borderline non-taxable two years ago, recheck it against current classifications.
- Threshold tests keep evolving. States periodically revise whether transaction counts factor into nexus alongside sales dollars. Confirm the current test in each state where you have customers rather than relying on last year's rules.
- Local-layer taxes add up. State obligations are only one layer — cities and other local jurisdictions can impose their own taxes on software and digital services. Map the local layer wherever you have customer concentration.
- Late discovery keeps getting more expensive. As states refine digital-services rules, the cost of discovering obligations late keeps rising relative to reviewing them proactively.
None of these are DIY filing decisions — each interacts with your product classification, customer locations, and existing registrations. But they are the reasons 2026 is a sensible year for a nexus review if you have not done one recently.
Bundled services and other gray areas
SaaS rarely sells alone — implementation, onboarding, support, and training ride along, sometimes on the same invoice. How you bundle affects taxability: some states tax the entire bundle if any taxable component is included; others let you separate taxable from non-taxable items, but only if your invoicing actually supports the distinction with separate line items and pricing.
This is squarely a billing-operations concern, not just a tax-department one: the invoice structure your billing platform produces determines what separation is defensible. If professional services are always bundled into a single line item with the subscription, you may be foreclosing the separate-treatment option in states that allow it. Worth discussing with your tax adviser before redesigning invoices — not after.
Other gray areas billing teams encounter: free trials that convert (when does the taxable sale occur?), credits and discounts (applied pre- or post-tax?), and multi-year prepayments (which period's rules apply?). None have universal answers; all should be documented positions, not accidents.
What to do if you think you have unaddressed exposure
If the sections above raised uncomfortable questions, practitioners recommend a specific sequence — and the first step is not to simply register and start collecting:
- Run a formal nexus review. Map revenue by state against thresholds, map employee/contractor locations, determine product taxability per state, and establish when each obligation began. Most states require you to declare the nexus start date on registration — and that date determines how far back filing obligations reach.
- Quantify prior-period exposure. If nexus began two years ago, the state may expect back taxes, interest, and penalties from that date. Registering without addressing prior periods does not resolve the exposure and can draw attention to it.
- Consider voluntary disclosure. Many states offer Voluntary Disclosure Agreements (VDAs) that resolve prior periods on better terms — often waiving penalties for companies that come forward proactively. A tax professional can tell you which states offer them and whether you qualify.
- Then register, collect, and file going forward — with monitoring in place so thresholds are caught as they are approached, not after they are crossed. A tax professional can advise on whether centralized multi-state registration options fit your situation.
How billing systems fit in
Billing platforms do not determine your tax obligations — but they are where obligations become operations:
- Revenue-by-state reporting. Your billing system should be able to produce the per-state revenue reports that nexus monitoring requires. If it cannot, that is a reporting gap to close.
- Tax calculation. Platforms offer tax calculation features (Stripe Tax is one published example) that compute tax at checkout or on invoices based on customer location and product tax codes. These automate the arithmetic; they do not replace the nexus and taxability determinations above.
- Exemption handling. B2B customers with exemption certificates, nonprofits, resellers — the billing system needs somewhere to record exemption status and apply it correctly.
- Invoice line-item structure. As noted under bundled services, how invoices itemize affects what tax positions are defensible. Design line items with tax in mind.
- Jurisdiction monitoring. Some tax tools monitor thresholds and flag approaching nexus — useful, but verify what they monitor (revenue only? transactions?) against each state's actual test.
When choosing a billing system, ask vendors specifically about tax calculation coverage, exemption workflows, and nexus-monitoring features — and get the answers in the context of the states where you actually have customers.
- Economic nexus (revenue alone creating obligations, post-Wayfair) is the settled standard — SaaS companies can have obligations in states they have never visited.
- Nexus ≠ taxability: you need both answers per state — do we have an obligation here, and is our product taxable here?
- 2026 developments to note: states keep expanding digital-services definitions, revising threshold tests, and layering local taxes — recheck classifications that were borderline a year or two ago.
- Surprise triggers: remote employees, contractors, mid-year threshold crossings, and trailing nexus after scaling back.
- If you suspect exposure: formal nexus review first, quantify prior periods, consider voluntary disclosure — then register. Consult a tax professional throughout.
- This article is general information, not tax advice.
Frequently asked questions
Does my SaaS company owe sales tax in states where we have no office?
Possibly. Since the 2018 Wayfair decision, physical presence is not required — crossing a state's economic nexus threshold (commonly $100,000 in sales, higher in some large states) can create an obligation on revenue alone. Remote employees can also create physical-presence nexus independently. Consult a tax professional about your specific situation.
If we have nexus in a state, do we definitely owe sales tax on our SaaS?
No. Nexus creates a filing obligation; whether tax applies depends on how that state classifies your product. Some states tax SaaS fully, some partially, some not at all — and classifications change. Both questions need current, state-specific answers.
What changed for SaaS sales tax in 2026?
The framework is settled; the movement is at the edges. States continue to expand digital-services definitions to capture more SaaS revenue, revise whether transaction counts factor into nexus tests, and add local-layer taxes on software. If your product's taxability was borderline a year or two ago, 2026 is a sensible year to recheck it — with a tax professional.
What is trailing nexus?
The obligation to keep filing in a state for a period after you no longer meet its nexus threshold. Rules vary by state — check each state's rules before assuming obligations end when activity stops.
Should we just register in every state to be safe?
Not without a review. Registration typically requires declaring when nexus began, which can trigger back-tax, interest, and penalty expectations for prior periods. A formal nexus review first gives you a documented picture; voluntary disclosure programs may then resolve prior periods on better terms. Get professional advice before registering.
Can our billing platform handle sales tax for us?
Billing platforms and tax tools can automate calculation, collection, and filing workflows — but they implement your tax determinations; they do not make them. You (with a tax professional) decide where you have nexus and how your product is classified; the platform executes. Ensure your system can report revenue by state and structure invoices with tax in mind.
Conclusion
SaaS sales tax in 2026 is a monitoring problem more than a mystery: the thresholds are published, and the failure mode is almost always not looking. Run the review, document your positions, set up threshold monitoring, and keep a tax professional in the loop. For the billing-platform side, see our buyer's checklist and Stripe Billing review.
—
General information only — not tax, legal, or accounting advice. Tax rules change frequently; verify current requirements with a qualified tax professional. Research-based guide; no vendor testing involved.