SaaS sales tax rates and economic nexus thresholds by state (2026)

Taxable is not the same as registered

Two separate tests decide whether you owe sales tax in a state, and only one of them is about your product.

The first test is taxability: does that state tax what you sell. The second is nexus: have you done enough business there for the state to require you to register and file. Both have to be true before you collect anything. Only the second one decides whether you have a filing obligation at all.

The consequence catches teams off guard. In most states you can cross the registration threshold, register, file a return, and remit nothing because every sale you made there was exempt. The return is still due. The tax on it is $0.

Which sales count toward the threshold varies, and this is what breaks threshold monitoring built on assumptions. Some states measure gross sales, some retail sales, some taxable sales only. California measures gross sales of tangible personal property.

The measurement period varies too. Most states test the current or previous calendar year. Connecticut uses the twelve months ending September 30. New York uses the previous four sales tax quarters. Puerto Rico uses the seller's own accounting year. Monitoring that runs on a rolling twelve months everywhere is wrong in those states.

That is why the measurement period and includable sales columns are in the table: they are the two fields that decide whether an implementation is correct.

Where the rules are changing

Software taxability is moving faster now than at any point since the Wayfair decision. Four jurisdictions matter most if you sell SaaS.

California. Current status: SaaS is exempt unless the software is downloaded or delivered on physical media. What changes: SB 122 is reported to bring remotely accessed prewritten software into the sales tax base on January 1, 2027.

Colorado. Current status: SaaS is exempt from state sales tax, though some home-rule cities tax it locally. What changes: HB 26-1223 is reported to extend sales tax to software regardless of delivery method on January 1, 2027.

Utah. Current status: Seller-hosted prewritten software is taxed on a basis that has been evolving. What changes: SB 162 is reported to codify the treatment of seller-hosted prewritten software, effective July 1, 2026.

Washington. Current status: The tax base was expanded under ESSB 5814. What changes: A later bill is reported to roll back part of that expansion. Bill numbering conflicts across sources and needs a direct check against the state legislature record.

SaaS, digital goods, or a subscription?

The taxability answer depends on which category a state puts your product in, and states do not agree on the categories.

Most states sort software into four buckets: prewritten or canned software, usually taxable when downloaded; custom software built for one customer, usually exempt; SaaS (software accessed remotely without a download), which is the contested one; and specified digital products (e-books, audio, video, and similar), which follow their own rules.

The hard part is the seams: a subscription that bundles software access with a service, a digital download sold alongside a hosted product, or a product that is SaaS under one state's definition and a data processing service under another's (which is what happens in Texas).

Encoding this in your product

If you are building tax logic rather than answering for your own company, four things determine whether a calculation is correct.

• Jurisdiction, not ZIP code. Sales tax boundaries do not follow postal boundaries. A single ZIP code can span multiple taxing jurisdictions with different rates, so two addresses in the same ZIP can owe different amounts.
• Taxability is a product question, not a location question. The rate depends on where the customer is. Whether tax applies at all depends on what you sold and, in some states, who you sold it to. Those are two different lookups, and conflating them is the most common structural mistake.
• Nexus is a running total, not a flag. Registration obligations accrue as sales accumulate, which makes the measurement period and includable sales columns inputs to your monitoring logic, not reference trivia.
• Effective dates belong on every rule. With California and Colorado both changing on January 1, 2027, an invoice dated December 2026 and one dated January 2027 need different answers. Logic that holds a single current value per state will be wrong for backdated invoices, credit notes, and anything an auditor asks about later.

Where Ziptax helps

Rooftop precision. The Ziptax API resolves sales tax rates at the jurisdiction level, from the address or coordinates, not from a postal code. A single ZIP code can span multiple taxing jurisdictions with different rates. Ziptax returns the rate for the specific jurisdiction the address falls in.

Engineered for platforms. Ziptax is built for developers building platforms: niche ERPs, CRMs, SaaS products, and marketplaces that need accurate sales tax rates inside their own checkout and billing workflows. The API ships with documentation and free starter API keys so you can build and test before committing.

Frictionless pricing. Usage-based pricing after the free tier. No enterprise contracts, no minimum commitments. Start building with free starter API keys and pay for what you use.

The TaxCloud runway. Ziptax handles rates. When the business grows and you need registration, filing, and remittance, TaxCloud picks up. Same company, and a Certified Service Provider (CSP) in the SST Program. You do not need a full compliance platform from day one. Providers like Avalara, TaxJar, and Stripe Tax offer broader products that bundle calculation with other compliance services. If your immediate need is getting accurate rates into your product, start with Ziptax and add the compliance services as you need them.

Frequently asked questions

Which states tax SaaS in 2026?

21 US jurisdictions tax SaaS in some form as of 2026, including the District of Columbia. The list spans states that classify SaaS as prewritten software (New York, Pennsylvania, Massachusetts), states that tax it as a digital product or service (Washington, Rhode Island), and states that tax it under their own frameworks (Hawaii's General Excise Tax, New Mexico's Gross Receipts Tax). Three more states tax it conditionally: Ohio and Iowa depending on whether the buyer is a business, and Alaska depending on the local jurisdiction. Colorado exempts SaaS at the state level, but some home-rule cities tax it locally.

The count is not settled. Published figures from other sources range from 21 to 27 because each one draws the line between taxable and conditional differently. The table above lists each state with its specific rule detail so you can see where the line falls for your product.

Do you have to register in a state where your product is exempt?

Often, yes. Registration is triggered by crossing a state's economic nexus threshold, which is a separate test from whether your product is taxable in that state. In most states you can be required to register, file a return, and remit $0 because every sale you made there was exempt. The return is still due.

Which sales count toward the threshold varies by state, and this is what breaks threshold monitoring built on assumptions. Some states measure gross sales, some retail sales, and some taxable sales only. California measures gross sales of tangible personal property.

Which sales count toward an economic nexus threshold?

It depends on the state, and the differences matter for implementation. Some states measure gross sales (all revenue into the state, taxable or not), some measure retail sales, and some measure only taxable sales. The measurement period varies too: most use the current or previous calendar year, but some use a rolling twelve months or a state-specific window like Connecticut's twelve months ending September 30.

For a SaaS company, this means the same revenue stream can count toward the threshold in one state and not in another. If a state measures only taxable sales and your product is exempt there, your sales may never accumulate toward the threshold at all. Both fields (measurement period and includable sales basis) are in the table above for every state.

What is the difference between SaaS and a digital product for sales tax?

SaaS generally means software accessed remotely without a download. Specified digital products generally means e-books, audio, video, and similar content sold electronically. Many states tax these under separate rules, so a company selling both can face two different taxability answers in the same state.

The harder cases are at the seams: a subscription that bundles software access with a service, a digital download sold alongside a hosted product, or a product that qualifies as SaaS under one state's definition and as a data processing service under another's. Texas, for example, treats SaaS as 80% taxable and 20% exempt under its data processing service framework.

How often do these rules change?

Continuously, and faster in the last two years than at any point since the Wayfair decision. Four jurisdictions changed or will change their treatment of software between 2025 and 2027. The two largest shifts land on the same date: California (SB 122) and Colorado (HB 26-1223) both bring SaaS into their tax base on January 1, 2027.

Sources

1. California: California Department of Tax and Fee Administration (CDTFA). cdtfa.ca.gov.
2. Texas: Texas Comptroller of Public Accounts. comptroller.texas.gov.
3. New York: New York State Department of Taxation and Finance. tax.ny.gov.
4. Florida: Florida Department of Revenue. floridarevenue.com.
5. Washington: Washington State Department of Revenue. dor.wa.gov.
6. California SB 122: California State Portal. Senate Bill 122.
7. Colorado HB 26-1223: Colorado General Assembly. House Bill 26-1223.
8. Utah SB 162: Utah Legislature. Senate Bill 162.
9. Washington ESSB 5814: Washington State Legislature. ESSB 5814.