SaaS Sales Tax: Economic Nexus and Taxability by State

Post-Wayfair Economic Nexus • SaaS Taxability Varies Dramatically • B2B Exemptions • Marketplace Facilitators
South Dakota v. Wayfair (2018)Streamlined Sales TaxState-by-State
← State & Compliance

Before 2018, a SaaS company could serve customers in all 50 states with no physical presence and collect no sales tax outside its home state. South Dakota v. Wayfair changed that. Every state with a sales tax now imposes economic nexus obligations on out-of-state sellers who cross their threshold - most commonly $100,000 in sales or 200 transactions per year. For SaaS specifically, taxability varies dramatically: some states tax all SaaS, some tax none, some distinguish B2B from B2C, and the definitions shift constantly. Getting this wrong creates audit exposure across multiple states simultaneously.

The Wayfair Framework in 60 Seconds

Pre-Wayfair: Physical nexus required for sales tax collection obligation. A SaaS company with servers and employees only in California owed California sales tax but not New York sales tax, regardless of how many New York customers it had.

Post-Wayfair (June 2018): Economic nexus is sufficient. A SaaS company with $150,000 in annual sales to Texas customers - and no Texas office or employees - has Texas nexus and must register, collect, and remit Texas sales tax if Texas taxes its product category.

Standard threshold (45+ states): $100,000 in sales OR 200 transactions in the state per year. Some states use AND instead of OR. Some states have lower thresholds. All thresholds should be monitored in real time.

The Critical Question: Does Your State Tax SaaS?

Wayfair only creates a collection obligation - it does not determine taxability. If the destination state does not tax SaaS, economic nexus is irrelevant for that state. The taxability question is where SaaS companies spend most of their sales tax analysis time, because state treatment is inconsistent and evolving.

StateSaaS TaxabilityKey Rule
New YorkTaxableSaaS taxed as "information service" and "software service"; very broad interpretation
TexasTaxableSaaS taxed as "data processing service" at 80% of charges (20% exempt)
PennsylvaniaTaxableSaaS taxed as "computer software"; broad coverage
TennesseeTaxableSaaS subject to sales tax as specified digital product
CaliforniaGenerally not taxable (B2B)SaaS not a "sale of tangible personal property"; B2C with data storage may be taxable in limited circumstances
FloridaGenerally not taxableSaaS not taxable unless custom software delivered electronically; ongoing legislative activity - monitor
IllinoisTaxable (B2C); B2B often exemptMyTax Illinois rulings have expanded scope; B2B exemption requires certificate
WashingtonTaxableWashington's B&O tax applies to SaaS revenue separately from sales tax analysis
State taxability rules change without warning and retroactively through administrative rulings and regulation changes. California has narrow but growing SaaS taxability; Texas aggressively audits SaaS companies that underreport the data processing service category; New York has taken the broadest view of any large state. Subscribe to state tax updates or use a compliance provider with real-time rule monitoring. The worst SaaS sales tax audit is one where the company has been non-compliant for three or four years in a high-rate, high-exposure state like Texas or New York.

B2B vs. B2C: Why the Customer Matters

Many states that tax SaaS exempt B2B transactions under a resale exemption or a manufacturing exemption. A SaaS company selling project management software to another business that uses it internally will have different tax treatment than one selling directly to consumers. The mechanism is the resale exemption certificate - if the business customer provides a valid exemption certificate, the SaaS vendor does not collect sales tax on that sale. The SaaS vendor must retain the certificate to support the exempted sale in an audit.

For SaaS platforms that are marketplaces - connecting buyers and sellers on a platform - the marketplace facilitator rules in most states require the platform to collect and remit sales tax on behalf of third-party sellers. If your SaaS product facilitates transactions between your customers and their customers, the marketplace facilitator analysis applies and creates obligations that go beyond your own subscriptions.

Building Compliance: The Practical Framework

The standard approach for a growing SaaS company: (1) Monitor economic nexus exposure in real time - once you cross a threshold in a state, you have 30-60 days to register in most states; (2) Determine taxability in each nexus state before registering - registering in a state where your product is not taxable creates unnecessary compliance costs; (3) Implement automated sales tax calculation (Avalara, TaxJar, Vertex) integrated with your billing system - manual calculation does not scale; (4) Collect and validate exemption certificates for B2B customers; (5) File returns - most states require monthly or quarterly filing depending on revenue volume.

Voluntary disclosure agreements (VDAs) are available in most states for companies that identify prior-year non-compliance before being audited. A VDA typically limits look-back to three or four years, waives penalties, and provides a clean-start path to compliance. For a SaaS company that has been operating for several years without collecting sales tax in Texas or New York, the VDA route is almost always better than waiting for an audit. Many states have online VDA programs.
Authority: South Dakota v. Wayfair, Inc., 585 U.S. 162 (2018) (overturned Quill physical nexus requirement for sales tax; economic nexus sufficient; upheld South Dakota's $100,000/200-transaction threshold as meeting Commerce Clause due process and substantial nexus tests); Complete Auto Transit, Inc. v. Brady, 430 U.S. 274 (1977) (four-part Commerce Clause test for state taxes on interstate commerce: substantial nexus, non-discrimination, fair apportionment, fair relation to services); South Dakota Codified Laws §10-64 (economic nexus statute; $100,000 or 200 transactions threshold; model for post-Wayfair state statutes); New York Tax Law §1105(c)(1) (information services taxable; NY Department of Finance and Taxation Technical Memoranda on SaaS as taxable information service); Texas Tax Code §151.0101 (data processing services taxable; 80%/20% rule; Texas Comptroller Rule 3.330); California Revenue and Taxation Code §6010.9 (software generally not tangible personal property unless custom software delivered on physical medium; SaaS generally not taxable); Streamlined Sales and Use Tax Agreement (SSUTA) - multi-state compact providing uniform definitions for digital products and software including SaaS; 24 member states; sourcing rules for digital products); Marketplace Facilitator Statutes (45+ states enacted marketplace facilitator laws post-Wayfair requiring platforms to collect and remit on behalf of third-party sellers); IRS Publication on State Tax Links (IRS.gov provides links to all state department of revenue websites for direct threshold and taxability verification).
tk.cpa AI Lab
Mission Privacy tk.cpa
Nothing on this page constitutes legal, tax, accounting, or professional advice, and no professional relationship is created by your use of this website. CPA Validated is an educational website for information purposes only. Information should be verified against current primary authority, including the Internal Revenue Code, Treasury regulations, IRS guidance, and applicable state or local law, before being relied upon or acted on. Calculator outputs are estimates only and may be incomplete or inaccurate depending on the facts, assumptions, and inputs used. CPA Inc. and tk.cpa disclaim liability to the fullest extent permitted by law. Full disclaimer: cpavalidated.com/disclaimer.html