Sales Tax Economic Nexus for SaaS Founders: 2026 State-by-State Trigger Map

If you crossed $100,000 in annual recurring revenue last year — or you’re closing in on it right now — congratulations. You’ve hit a real milestone. You’ve also, almost certainly without realizing it, crossed the sales-tax economic nexus threshold in a dozen or more states. Sales tax economic nexus for SaaS founders in 2026 is not a VC-funded startup problem. It’s a solo-founder problem that typically surfaces in year two or three, when ARR clears $100K and a finance team is still a fantasy. The retroactive liability clock is already running.

I spent months mapping this compliance landscape after my own SaaS crossed the $100K mark and I realized I had zero systems in place. What follows is the guide I wish I’d had: which states tax SaaS subscriptions, what the 2026 trigger thresholds actually are, how to think about the register-or-automate decision, and how to surface past exposure without getting destroyed by penalties. General information only — consult a qualified sales-tax specialist before registering in any new state.

Physical Nexus vs. Economic Nexus: The Distinction That Changes Everything

Before 2018, sales-tax nexus required a physical presence — an office, warehouse, or employee in the state. As a cloud-native founder shipping no boxes, you were largely invisible to state revenue departments. Then the Supreme Court decided South Dakota v. Wayfair, Inc. (2018) and the entire framework changed. States immediately began enacting economic nexus laws: you trigger a registration obligation simply by generating enough revenue from customers in that state, regardless of where your server sits or where you sleep.

Physical nexus still applies if you have a home office in a state, hire a W-2 employee or 1099 contractor who regularly works there, attend a trade show, or store any equipment. For most solo SaaS founders, the primary exposure in 2026 is purely economic nexus — the dollar threshold your billing platform is quietly crossing month after month.

The 2026 Economic Nexus Threshold Table: $100K Is the Standard, With Three Notable Outliers

Following Wayfair, states rapidly aligned on a common revenue standard. As of 2026, the overwhelming majority of states use $100,000 in annual gross sales as the sole economic nexus trigger. The transaction-count threshold — which used to run alongside the revenue threshold — has been steadily eliminated. Illinois became the most recent state to drop its 200-transaction rule, effective January 1, 2026, leaving revenue as the only test.

Three states still maintain significantly higher revenue thresholds, which matters for your prioritization. The table below covers notable and high-revenue-concentration states; for the full 45-state picture, see the Anrok SaaS taxability index.

Sources: Sales Tax Institute Economic Nexus State Guide; Anrok SaaS Sales Tax Index; TaxCloud: Illinois Eliminates Transaction Threshold 2026; MTC National Nexus Program. General information only — verify with a sales-tax specialist.

The SaaS Taxability Problem: Why This Isn’t Straightforward

Here’s the core complexity that trips up almost every solo founder: economic nexus thresholds are just the registration trigger. Whether you actually owe sales tax on your subscription revenue is a completely separate question that depends on how each state classifies your product. This is the fundamental difference between SaaS and physical goods — with a t-shirt, you know immediately whether the state taxes apparel. With SaaS, you need a state-by-state taxability analysis.

SaaS occupies a legally ambiguous position. Most state sales-tax frameworks were designed for tangible goods. Digital-access products that never transfer a physical object — where the customer uses software via a browser and nothing is downloaded — fall outside the traditional definitions in many states. The result is a patchwork:

• Clearly taxable (25+ states): Arizona, Connecticut, District of Columbia, Hawaii, Kentucky, Louisiana, Massachusetts, Mississippi, Nebraska, New Mexico, New York, Pennsylvania, Rhode Island, South Carolina, South Dakota, Tennessee, Texas, Utah, Vermont, Washington, West Virginia. These states have either amended their code to explicitly include digital services or issued administrative guidance treating SaaS as taxable. Always verify the current effective date of any guidance — Washington’s rules changed materially in 2026 (see below).
• Not taxable at state level: California, Florida, Georgia, North Carolina, Virginia. California is the starkest example — the state has one of the highest economic nexus thresholds ($500,000) and does not tax SaaS. Even if you cross the threshold, you have no SaaS collection obligation there. Note: Virginia has active legislative debate around digital-service taxation — check for updates annually.
• No state sales tax (nexus moot at state level): Oregon, Montana, New Hampshire, Delaware, and Alaska have no state sales tax. For these five states, state-level nexus and taxability questions are irrelevant. Alaska is distinct: it has no state sales tax but home-rule municipalities may impose local sales tax independently. Do not group Alaska with Colorado in your analysis — they are exempt for different structural reasons (Colorado is state-exempt but has a state sales tax framework; Alaska has no state sales tax at all).
• Taxable only at local level (not state-wide): Illinois, Colorado. These require jurisdiction-by-jurisdiction analysis because home-rule cities set their own rules on top of the state framework.
• Conditional on use type (B2B vs. B2C): Connecticut (different rates), Iowa (B2C taxable, B2B exempt), Maryland (same split). If you sell a productivity tool to businesses, you may owe nothing. Sell the same tool to consumers, and you collect tax.

This means the first thing you need to build into your compliance system is not just a threshold monitor, but a taxability matrix: state × customer type × product classification. Tools like Anrok (built specifically for SaaS) and TaxJar maintain these matrices automatically — one of the strongest arguments for using a compliance platform rather than a spreadsheet.

If you’re thinking through how to structure the revenue side of your SaaS, the decisions you make on pricing also affect how states classify your product. Our breakdown of why usage-based pricing can create structural complexity is relevant context here.

2026 State Changes You Need to Know

Illinois: 200-Transaction Rule Eliminated (January 1, 2026) + Amnesty Window Opening August 2026

Illinois Governor JB Pritzker signed HB 2755 on June 16, 2025, effective January 1, 2026. The prior rule required remote sellers to collect tax once they either exceeded $100,000 or completed 200 separate transactions into Illinois. The transaction count is gone. Now it’s a clean $100,000 revenue test against the preceding 12-month period. For a SaaS founder with many small accounts — say, 300 customers at $30/month — this change actually narrows the trigger. You only cross the threshold when cumulative Illinois receipts hit $100,000, not at transaction 201.

Maine: Streaming and Audio Subscriptions Now Taxable (January 1, 2026)

Maine’s supplemental budget (LD 210) expanded digital-service taxability effective January 1, 2026. Digital audiovisual services and digital audio services — think subscription streaming platforms, music services, podcast subscriptions, and audiobook platforms — are now subject to Maine’s 5.5% sales tax per Maine Revenue Services guidance document GIB 115. Critically, pure access-only SaaS (business software accessed via browser with no download) remains exempt in Maine. If your SaaS product has a significant media or content delivery component, you need a careful look at whether Maine’s new rules sweep in part of your offering. Maine’s $100,000 economic nexus threshold, using the prior or current calendar year as the lookback, remains unchanged.

Washington: IT Services and SaaS Now Subject to Retail Sales Tax (April 1, 2026) — Urgent

This is the highest-urgency 2026 change for most SaaS founders, and it is not getting the attention it deserves. Washington ESSB 5814, effective October 1, 2025 for new contracts and April 1, 2026 for existing contracts, newly classifies SaaS and IT services as retail sales subject to Washington retail sales tax — in addition to the existing Business & Operations (B&O) tax framework that already applied.

What this means practically: if you had pre-October 2025 contracts with Washington customers and you did not convert those agreements to collect retail sales tax by April 1, 2026, you are currently out of compliance. The April 1 deadline has passed. If you have Washington customers and were relying solely on the old B&O analysis, your Washington exposure is real and requires immediate attention. The Washington State DOR has issued interim guidance acknowledging active legal challenges to ESSB 5814; check the WA DOR site for current interim guidance and any legislative changes before filing. Do not wait — if you have material Washington revenue, get a specialist to assess your position this month.

The Broader Trend: Simplification Toward Revenue-Only Rules

The Illinois and Maine changes reflect a nationwide direction: states are eliminating transaction-count tests and converging on revenue-only triggers. The practical effect for SaaS founders is that monitoring is simpler — one number per state — but the number of states where you potentially owe tax is larger, because the transaction floor no longer protects businesses with many small subscriptions.

The Register-or-Automate Decision Framework

When I crossed $100K in ARR and started doing this analysis, I had to answer one operational question: do I register and file manually in every state where I have nexus, or do I plug in a compliance tool and let it handle calculation, filing, and remittance? Here’s how I break down the decision:

Register Manually If…

• You have nexus in only 1–2 states and both are clearly taxable for your product category
• Your transaction volume is low enough that per-filing costs are manageable
• You have a CPA with sales-tax expertise already on your team
• And you’ve budgeted 3–5 hours per quarter per state for reconciliation, return preparation, and filing

Use a Compliance Platform If…

• You have nexus in 3+ states or are approaching thresholds in 5+ states
• Your product classification is ambiguous (you’re not sure if a given state taxes your product)
• You use Stripe Billing, Recurly, or Chargebee — most compliance tools integrate directly and handle calculation at checkout
• You don’t want to track threshold proximity manually

Tool cost reference (2026): Anrok is built specifically for SaaS and handles calculations, monitoring, filing, and registration. Pricing is quote-based and varies by transaction volume — visit anrok.com/pricing directly for a current quote rather than relying on figures that change with volume tiers. TaxJar Professional runs approximately $99/month, with AutoFile added at $50–55/filing per state per period. For a solo founder crossing the $100K ARR threshold, compliance tool cost is a rounding error relative to retroactive liability exposure — even a single-state VDA engagement with an advisor can run $2,000–$5,000.

The broader financial architecture question — how to structure yourself as income scales — is something we covered in detail in the OBBBA mid-year tax audit playbook for solo founders, which also covers estimated tax timing that intersects with when you’d owe state sales-tax remittances.

Retroactive Liability and Voluntary Disclosure: The Exposure You Already Have

If you’ve been selling SaaS subscriptions across state lines for more than a year and haven’t registered anywhere, you likely have retroactive nexus exposure. States don’t have a statute of limitations that protects you if you never filed — in most cases, the clock for an audit lookback starts from when you were supposed to register, and penalties plus interest compound.

The structured path forward is a Voluntary Disclosure Agreement (VDA). A VDA is a formal agreement between you and a state tax authority that lets you resolve prior non-compliance under defined terms:

1. Limited lookback period: Most states restrict the audit window to 3–4 years under a VDA, versus potentially unlimited exposure if they discover you first
2. Penalty abatement: States commonly waive all penalties in exchange for voluntary disclosure — you pay tax and interest only
3. Anonymous initial contact: Most states allow you (or your representative) to initiate the process anonymously, assess your liability before committing, and only identify yourself when you’re ready to formalize the agreement

The Multistate Tax Commission (MTC) National Nexus Program lets you file VDAs in multiple states simultaneously, which significantly reduces the administrative overhead of cleaning up exposure across 8–10 states at once.

Building a Minimal-Viable Sales-Tax System

Here’s the operational checklist I use. It’s not glamorous, but it’s the system that makes this manageable for a one-person operation:

1. Run a nexus analysis: Pull the last 12 months of revenue by state from your billing platform. Compare against each state’s threshold. Flag every state where you’re above $100K (or $500K for CA, TX, NY).
2. Check taxability for flagged states: For each state where you have nexus, determine whether your specific product is taxable. The Anrok SaaS taxability index is a solid starting reference, but verify with a specialist for states where the law is ambiguous or recently changed (Washington in particular).
3. Assess retroactive exposure: For states where nexus and taxability both exist, estimate how much tax you should have collected going back to when you crossed the threshold. Multiply prior-period revenue by the applicable rate. This is your VDA conversation starter — do this step only after confirming taxability in step 2, because running the retroactive math in a non-taxable state wastes time.
4. Decide on infrastructure: Register and file manually (1–2 states, clear taxability, existing CPA support), or implement a compliance platform (3+ states, ambiguous classification, no bookkeeper).
5. Set threshold monitoring: Whether manual or automated, you need a monthly flag when any state approaches 80% of the nexus threshold. Economic nexus doesn’t give you a warning letter.

FAQ: Sales Tax Economic Nexus for SaaS Founders

Does economic nexus apply to SaaS the same way it applies to physical goods?

The nexus threshold triggers the same way regardless of what you sell — it’s based on revenue from customers in that state. What changes is whether you actually owe tax once nexus is established. For physical goods, most states impose tax. For SaaS, roughly half of states tax it and half don’t, depending on how their laws define taxable digital services. Crossing the $100,000 threshold in a state where SaaS is exempt means you need to monitor whether you sell any other taxable products, but you have no SaaS collection obligation.

If I use Stripe, does Stripe handle sales-tax collection automatically?

Stripe Tax is a built-in option that handles calculation and collection, but it is not a substitute for a compliance strategy. Stripe Tax calculates and collects tax on transactions, but you are still responsible for registration in each state (you must register before you collect), filing returns, and remitting the collected funds on state-defined schedules. Most solo founders who use Stripe Tax still need either a compliance platform or a CPA to handle the filing and remittance side. Think of Stripe Tax as the front-end calculation layer, not the end-to-end compliance solution.

My SaaS is under $100K in annual revenue — do I need to think about this yet?

Not for economic nexus purposes in most states — you’re below the standard threshold. But use this window to build the monitoring habit and understand which states your customers are concentrated in. A founder who crosses $100K in Year 2 and has a tracking system in place can register prospectively with zero retroactive exposure. The same founder who ignores it until $300K and is operating in 15 states now has a VDA project on their hands. Set a calendar reminder to rerun your state-by-state revenue analysis every quarter as you scale.

What is a voluntary disclosure agreement for sales tax and how do I start one?

A voluntary disclosure agreement (VDA) is a formal settlement between you and a state tax authority that resolves prior non-compliance on defined terms. In exchange for coming forward voluntarily, most states offer a limited lookback period (typically 3–4 years instead of unlimited) and waive all penalties — you pay back tax plus interest only. You can initiate anonymously through a tax advisor or attorney, evaluate your liability, and only identify your business when you’re ready to commit. The MTC National Nexus Program lets you file VDAs across multiple states simultaneously. Start with a sales-tax specialist who handles multi-state VDAs — most complete the process in 60–90 days per state.

What states do not tax SaaS subscriptions?

As of 2026, the major states that do not tax SaaS at the state level include California, Florida, Georgia, North Carolina, and Virginia (though Virginia has pending legislative activity — verify annually). Additionally, Oregon, Montana, New Hampshire, Delaware, and Alaska have no state sales tax whatsoever, making state-level taxability irrelevant there. That said, local jurisdictions in Alaska and Colorado can impose their own sales tax on digital services even where the state does not. Always confirm current status for your specific product with a sales-tax specialist or the Anrok SaaS taxability index — this area changes frequently.

What happens if I get audited for sales tax I never collected?

A sales-tax audit in a state where your SaaS is taxable and you never registered can result in: (1) back tax on all revenue from customers in that state going back to when you first crossed the nexus threshold, (2) interest compounding from the date each remittance was due, and (3) penalties typically ranging from 10–25% of the unpaid tax. For a SaaS generating $150K/year in a taxable state at a 6% rate, a four-year lookback produces approximately $36,000 in back tax before interest and penalties. Filing a VDA before an audit eliminates penalties entirely and caps the lookback at 3–4 years. Once you receive an audit notice, you lose the right to voluntary disclosure in most states — the window closes the moment contact is initiated by the state.

The Bottom Line on Sales Tax Economic Nexus for SaaS Founders in 2026

The system is genuinely complex, but the decision tree is not. As a solo SaaS founder crossing the $100K annual revenue threshold in year two or three: most states want registration at that level, roughly half of those states actually tax your product, three major states (California, Texas, New York) don’t trigger until $500,000, and 2026 changes — particularly Illinois dropping its transaction count and Washington expanding retail sales tax to SaaS — have shifted the compliance landscape materially since 2025.

Your immediate next step is a state-by-state revenue pull from your billing platform and a comparison against the nexus thresholds above. If you find you have exposure, contact a sales-tax specialist about a VDA before a state contacts you. If you have Illinois exposure from prior years, note the amnesty window opening August 1, 2026. If you have Washington customers, assess your ESSB 5814 position now. If you’re approaching thresholds, implement a compliance platform before you cross them. The cost of the infrastructure is predictable; the cost of retroactive liability is not.

This post is general information only and does not constitute tax or legal advice. Sales-tax laws vary significantly by state and product category and change frequently. Consult a qualified sales-tax professional before registering in any new jurisdiction or entering into a voluntary disclosure agreement.