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]
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. [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]
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]
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 SaaSOver-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]
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]
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]
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]
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]
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]
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]
| Rule/Framework | Key Difference | When to Use |
|---|---|---|
| US SaaS Sales Tax Nexus (this rule) | Covers economic + physical nexus triggers AND SaaS taxability by state | SaaS company selling to customers in multiple US states |
| US Income Tax Nexus | Different thresholds; creates state income/franchise tax obligations, not sales tax collection duties | Determining state corporate income tax filing obligations |
| EU VAT on Digital Services | One-Stop-Shop (OSS) system; VAT applies at customer's EU member state rate; no nexus threshold | SaaS company selling to EU customers |
| Streamlined Sales Tax (SST) | Simplification framework for multi-state registration — subset of 24 states | Registering for sales tax permits across multiple SST member states |
| Marketplace Facilitator Laws | Shifts collection duty from seller to platform for marketplace-facilitated sales | SaaS sold through third-party marketplace platforms |
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.