US Sales Tax Nexus Rules for SaaS Companies

Summary

Since the 2018 South Dakota v. Wayfair decision, a remote SaaS seller owes sales tax in a state only when TWO things are both true: it has nexus there (economic — typically >$100K in annual in-state sales, with $500K in CA/NY/TX — or physical, from a remote employee, office, or inventory), AND that state actually taxes SaaS (only ~25 of the 45 sales-tax states do). All 45 sales-tax states have economic-nexus laws, but the 200-transaction trigger is being retired fast — 16 states had dropped it by January 1, 2026, with Kentucky (HB 757) following on August 1, 2026, which also newly taxes data brokering services. Build a State x Nexus x SaaS-Taxable matrix; only the intersection requires registration. Non-compliance runs 10-50% penalties plus up to 18% interest over 3-7 year lookbacks. [src1, src2, src3, src9]

Rule

SaaS companies selling to US customers must determine their sales tax collection obligations state by state, based on two independent triggers: economic nexus (exceeding revenue or transaction thresholds in a state) and physical nexus (having employees, offices, or other physical presence). Following the Supreme Court's 2018 South Dakota v. Wayfair decision, all 45 states with a sales tax have enacted economic nexus laws, but only approximately 25 states actually tax SaaS as of 2026. A SaaS company must both establish nexus in a state AND confirm that state taxes SaaS before a collection obligation arises. [src1, src2, src3]

Evidence

The Wayfair decision upheld South Dakota's $100,000 revenue or 200-transaction threshold as constitutionally valid, and this became the de facto standard adopted by most states. [src1] As of 2026, 25 US jurisdictions tax some form of SaaS, though each classifies it differently: as a digital product (Washington, Hawaii), a data processing service (Texas, at 80% of the charge), a communication service (several states), or simply as taxable software (Connecticut, at 1% for business use vs. full rate for personal use). [src3, src8] The trend toward eliminating transaction-count thresholds accelerated in 2025-2026: Alaska (Jan 2025), Utah (Jul 2025), and Illinois (Jan 2026) all dropped their 200-transaction tests, leaving revenue as the sole economic nexus trigger, and by January 1, 2026 at least 16 states had eliminated the transaction count. [src2] Kentucky is the next domino: under House Bill 757, effective August 1, 2026, Kentucky removes its 200-transaction threshold (leaving only the $100,000 gross-sales test) AND begins taxing data brokering services — a reminder that states keep both narrowing nexus tests and broadening the taxable base in the same session. [src9, src2] Maryland's Budget Reconciliation Act of 2025 introduced a 3% tax on SaaS for commercial use and 6% for individual use, effective July 1, 2025, while Maine is adding digital audiovisual and digital audio services to its taxable category in 2026. [src5, src4] Non-compliance penalties are substantial: states typically impose 10-50% of unpaid tax as penalties, with interest rates up to 18% annually and lookback assessment periods of 3-7 years. On average, non-compliant SaaS businesses lose 4.3% of revenue to back-taxes, penalties, and interest combined. [src4]

Key Properties

• Dominant threshold: $100,000 in annual in-state sales (used by ~35 states); California, New York, and Texas use $500,000 [src2]
• Transaction threshold: 200 transactions/year (declining fast — at least 16 states had dropped this test by Jan 1, 2026; Kentucky removes it Aug 1, 2026) [src2, src9]
• SaaS taxability: ~25 of 45 sales-tax states tax SaaS in some form as of 2026 [src3]
• No-sales-tax states: Alaska (no statewide tax, but local SaaS taxes possible under ARSSTC), Delaware, Montana, New Hampshire, Oregon [src3]
• Measurement period: Current or previous calendar year (varies by state; some use rolling 12 months) [src2]
• Marketplace facilitator shift: All taxing states and DC have marketplace facilitator laws that can shift collection duty from seller to platform [src7]

Conditions

• Applies when: A SaaS company sells subscriptions or cloud-based software to customers in multiple US states, whether through direct sales, self-serve signup, or marketplace platforms
• Does NOT apply when: The SaaS company sells exclusively within its home state; sells only to states that do not tax SaaS (e.g., California, Florida); sells only through a marketplace facilitator that handles all tax collection; or sells only to tax-exempt entities (government, nonprofits) with valid exemption certificates
• Confidence degrades when: A state has proposed but not yet enacted SaaS taxation legislation; the company's product straddles multiple tax categories (e.g., part SaaS, part professional service); the company bundles taxable SaaS with nontaxable consulting services

Constraints

• US jurisdiction only — international SaaS tax obligations (EU VAT on digital services, UK Digital Services Tax, India Equalization Levy) operate under entirely different frameworks [src1]
• State-level rules change multiple times per year — Maryland added SaaS taxation in July 2025, Illinois changed thresholds in January 2026, and more states are actively considering SaaS taxation bills [src5, src2]
• Economic nexus does not replace physical nexus — both exist concurrently; a remote employee in a state triggers physical nexus regardless of revenue level [src2]
• SaaS classification varies by state: tangible personal property (New York), data processing service (Texas at 80%), digital product (Washington), not taxed (California, Florida) [src3, src8]
• Exemptions vary: B2B resale exemptions, nonprofit/government exemptions, and state-specific exemptions (e.g., Iowa exempts business-use SaaS but taxes consumer SaaS) require individual analysis per state [src4]

Rationale

The Wayfair decision fundamentally shifted US sales tax from a physical-presence standard (established in Quill Corp. v. North Dakota, 1992) to an economic-activity standard. The Court held that the Commerce Clause does not prohibit states from requiring tax collection by sellers with no physical presence, provided the law has sufficient safeguards (safe harbor thresholds, no retroactive application, single state-level administration). For SaaS companies, this created a patchwork compliance burden because SaaS inherently crosses state lines — a customer in any state can sign up for a cloud subscription without the company ever setting foot there. The resulting obligation is compounded by the lack of federal uniformity: Congress has not passed legislation standardizing digital service taxation, leaving each state to define SaaS taxability differently. [src1, src4]

Framework Selection Decision Tree

START — SaaS company needs US sales tax guidance
├── Do you have customers in multiple US states?
│   ├── NO → Single-state filer: register and collect in home state only
│   └── YES → Continue to nexus analysis
├── For each state with customers, check two questions:
│   ├── Q1: Do you have NEXUS in this state?
│   │   ├── Physical nexus? (employees, offices, inventory in-state)
│   │   │   ├── YES → Nexus established (regardless of revenue)
│   │   │   └── NO → Check economic nexus
│   │   └── Economic nexus? (exceed $100K revenue or 200 txn threshold)
│   │       ├── YES → Nexus established
│   │       └── NO → No collection obligation in this state
│   └── Q2: Does this state TAX SaaS?
│       ├── YES (~25 states) → Must register, collect, and remit
│       ├── NO (CA, FL, etc.) → No collection obligation even with nexus
│       └── UNCLEAR (mixed/partial) → Consult state-specific guidance
│           └── THIS RULE ← YOU ARE HERE
├── Do you sell through a marketplace platform?
│   ├── YES → Check if marketplace facilitator handles tax for that state
│   │   ├── Facilitator collects → No obligation on marketplace sales
│   │   └── Facilitator does not → Seller must collect
│   └── NO → Seller handles all collection
└── Are you already behind on compliance?
    ├── YES → Consider Voluntary Disclosure Agreement (VDA)
    └── NO → Register proactively in nexus states that tax SaaS

Application Checklist

Step 1: Map your nexus footprint

• Inputs needed: Revenue by state (current + prior calendar year), transaction counts by state, list of states where you have employees or physical presence
• Output: A state-by-state nexus determination (physical nexus, economic nexus, both, or neither)
• Constraint: Use the specific threshold for each state — most are $100K, but CA/NY/TX are $500K; some states still count transactions at 200/year while others have dropped this test [src2]

Step 2: Determine SaaS taxability per nexus state

• Inputs needed: List of states where nexus is established, your product's exact classification (pure SaaS, hybrid SaaS+services, bundled)
• Output: Subset of nexus states where SaaS is actually taxable, with applicable tax rate and classification
• Constraint: Do not assume SaaS is taxable in every nexus state — approximately 20 states with sales tax do NOT tax SaaS; classification determines rate (e.g., Texas taxes at 80% of the charge, Connecticut charges 1% for business use) [src3, src8]

Step 3: Register, collect, and remit

• Inputs needed: Final list of states requiring collection, customer billing addresses, tax rates by jurisdiction (state + local)
• Output: Sales tax permits in each required state, tax calculation integrated into billing, remittance schedule established
• Constraint: Use Streamlined Sales Tax (SST) centralized registration where available (24 member states) to simplify multi-state registration; source tax to customer location, not company headquarters [src7, src6]

Step 4: Manage exemptions and ongoing compliance

• Inputs needed: Customer exemption certificates (resale, nonprofit, government), filing calendar, nexus monitoring thresholds
• Output: Exemption certificate database, recurring filing schedule, nexus threshold alerts
• Constraint: Re-evaluate nexus at least quarterly — crossing a threshold mid-year triggers obligations; exemption certificates expire and must be renewed per state rules; keep records for at least 4 years [src4, src6]

Decision Logic

If you have customers in only one US state (your home state)

Skip the multi-state nexus analysis: register and collect in your home state only (if it taxes SaaS), and re-evaluate the moment you cross another state's economic-nexus threshold. [src2]

If you exceed $100K in annual sales into a state but that state does not tax SaaS (e.g., California, Florida, Georgia)

Do NOT register or collect there for SaaS. Economic nexus alone does not create a SaaS collection duty — the state must also classify SaaS as taxable. Over-collecting creates refund liabilities and customer disputes. [src3, src2]

If you have a remote employee, contractor, or any physical presence in a state

Treat that state as having physical nexus regardless of revenue — there is no safe-harbor threshold. If the state also taxes SaaS, you must register and collect from the first dollar of taxable sales. [src2]

If you sell into Kentucky and previously relied on the 200-transaction test (or sell data brokering services there)

Re-check your obligation against the August 1, 2026 change: after that date Kentucky's only economic-nexus trigger is $100,000 in gross sales, and data brokering services become newly taxable. [src9]

If your SaaS is sold partly through a marketplace facilitator and partly direct

Split the analysis: the marketplace generally collects on facilitated sales, but you remain responsible for collecting and remitting on your direct (own-website, sales-team) sales in every state where you have nexus and SaaS is taxable. [src7]

If you are already past nexus thresholds in states where you never registered, and have not received an audit notice

File a Voluntary Disclosure Agreement (VDA) in each applicable state before any state contacts you — VDAs typically cap lookback at 3-4 years and waive or reduce penalties. Once an audit notice arrives, the VDA option is closed. [src4, src6]

If you need how SaaS is taxed OUTSIDE the US, or whether a permanent establishment triggers income tax

Route to the correct unit: VAT/GST on SaaS for non-US destination-based taxes, or Permanent Establishment for income/franchise-tax exposure — neither is governed by US sales-tax economic nexus. [src1]

Anti-Patterns

Wrong: Assuming SaaS is taxable in all 45 sales-tax states

Over-collecting sales tax in states that do not tax SaaS (such as California and Florida) creates refund liabilities and customer disputes. Some companies register in every state and collect everywhere, wasting compliance resources on states that do not require it. [src3]

Correct: Check both nexus AND SaaS taxability per state

Nexus alone does not create a collection obligation — the state must also classify SaaS as taxable. Approximately 20 of the 45 sales-tax states do not tax SaaS at all. Build a matrix: State x Nexus (Y/N) x SaaS Taxable (Y/N). Only the intersection requires registration and collection. [src3, src2]

Wrong: Ignoring physical nexus because you are a remote-first company

A SaaS company with a distributed workforce may have physical nexus in every state where a remote employee lives, regardless of revenue thresholds. A single customer support representative in Florida creates physical nexus in Florida. [src2]

Correct: Audit your physical footprint alongside economic nexus

Map every state where you have employees (full-time, part-time, or contractor), co-working spaces, equipment, or inventory. Physical nexus triggers immediately with no safe harbor threshold. A nexus study should cover both economic and physical triggers. [src2]

Wrong: Using Voluntary Disclosure Agreements after receiving an audit notice

VDAs require that the company has never previously registered with the state and has not received any audit notices. Companies sometimes delay compliance hoping to use a VDA later, only to find they are disqualified after a state contacts them. [src4, src6]

Correct: File VDAs proactively before any state contact

VDAs typically limit lookback to 3-4 years, waive or substantially reduce penalties, and sometimes reduce interest. File VDAs in all applicable states before any state initiates contact. Once an audit notice arrives, the VDA option is closed. [src4]

Counter-Arguments

• Some tax advisors argue that SaaS companies under $100K in total US revenue should ignore nexus analysis entirely, since they fall below all economic nexus thresholds — but this ignores physical nexus from remote employees and the risk of growing past thresholds mid-year. [src2]
• The compliance burden for small SaaS companies is disproportionately high — the Streamlined Sales Tax initiative was designed to simplify this, but only 24 states participate, and the remaining states each require separate registration and filing. [src7]
• Some argue that federal legislation would solve the patchwork problem, but no federal SaaS tax simplification bill has passed as of 2026. [src4]

Common Misconceptions

Misconception: If my SaaS company has no physical presence in a state, I do not need to collect sales tax there.
Reality: Since Wayfair (2018), economic nexus means exceeding revenue or transaction thresholds in a state creates a collection obligation regardless of physical presence. All 45 sales-tax states have economic nexus laws. [src1, src2]

Misconception: SaaS is a service, and services are not subject to sales tax.
Reality: States classify SaaS differently — some treat it as tangible personal property (New York), some as a taxable data processing service (Texas), and some as a digital product (Washington). The "it's a service, not a product" argument does not hold in approximately 25 states. [src3, src8]

Misconception: The $100K/200 transaction threshold is a universal federal standard.
Reality: The Wayfair decision upheld South Dakota's specific threshold as constitutional, but each state sets its own threshold independently. California, New York, and Texas use $500K; some states still include the 200-transaction test while others have eliminated it. [src1, src2]

Misconception: If I sell through a SaaS marketplace or app store, I have no sales tax obligations.
Reality: Marketplace facilitator laws only shift the tax collection responsibility for sales made through the marketplace. If you also sell directly (your own website, sales team), you are responsible for collecting and remitting tax on those direct sales. [src7]

Comparison with Similar Rules

When This Matters

Fetch this rule when a SaaS or cloud software company asks about US sales tax obligations, economic nexus thresholds, which states tax SaaS, or how to handle multi-state sales tax compliance. Also relevant when a SaaS company is expanding to new US states, hiring remote employees, or evaluating whether to register for sales tax collection in specific states.