SaaS Sales Tax by State: The 2026 Taxability Matrix

Why there is no single answer

Sales tax bases were written for physical goods. When software moved to the cloud, no state rewrote its base from scratch — each one reached for the nearest existing category and taxed SaaS by analogy. The analogy a state picked in about 2010 is still what decides your answer today, and different analogies produce genuinely different results for the same product.

This is why "is SaaS taxable?" is the wrong question to ask about a product. The right question is which category does this state's law put my product in — because that is what determines whether an added download, a bundled implementation service or a hardware component moves you across the line.

The full SaaS taxability matrix

Every US jurisdiction, with its classification and the rate that applies where it is taxable. Rates shown are the combined state plus average local rate; the actual rate on an invoice depends on the customer's address¹.

States that tax SaaS (24)

States that do not tax SaaS (22)

States with no general sales tax (5)

The Texas 80/20 rule, worked

Texas classifies SaaS as a data processing service, and Texas law exempts 20% of the charge for data processing². Tax therefore applies to 80% of the subscription price — which quietly makes Texas one of the cheaper taxing states despite a high headline rate.

Charging the full 8.25% on the whole $1,000 would over-collect $16.50 a month per customer. Over-collection is not a safe error: the money belongs to the customer, and Texas expects you to either remit it or refund it.

The B2B and B2C splits that run backwards

Most people assume business customers are more likely to be exempt. For SaaS the assumption is often wrong, and in one state it is exactly inverted.

Two more genuine B2B carve-outs are worth knowing: Iowa exempts SaaS purchased by a commercial enterprise for business purposes, and Maryland carries a substantial enterprise exemption for business software purchases. In both cases the exemption is claimed by the buyer, so you will need an exemption certificate on file — see resale and exemption certificates for how to collect and store them.

The local taxes that survive a state exemption

Two states are listed as exempt above and still cost SaaS sellers money, because the tax is levied below state level.

• Chicago. Illinois exempts SaaS statewide when the licence meets its five-part test, but the City of Chicago levies a Personal Property Lease Transaction Tax on nonpossessory computer leases — which is what a cloud subscription is⁷. This applies to Chicago customers regardless of the state exemption.
• Colorado home-rule cities. Colorado exempts SaaS at state level, but its home-rule municipalities define their own tax base and several, including Denver, tax software as a service. A seller can be correctly exempt with the state and still owe a city.

Home-rule jurisdictions are the single most under-modelled risk in SaaS compliance. The mechanism is covered in home rule sales tax states.

Taxability is not nexus — you need both

The most common structural mistake in SaaS compliance is treating this matrix as a registration list. It is not. Two independent tests have to be satisfied before you owe anything:

You collect only where both are true. A SaaS business doing $2M in California owes nothing on subscriptions there — nexus yes, taxability no. The same business doing $120,000 in New York owes on every dollar. Work through your own numbers with the economic nexus calculator, and read the economic nexus guide for the full state threshold table.

Sourcing: whose rate applies

SaaS is normally sourced to the customer's location rather than yours. For a subscription that usually means the billing address, or the primary place the software is used where those differ.

The hard case is a single enterprise subscription used by staff in a dozen states. Some states expect the charge to be apportioned by user location, and several accept a multiple points of use certificate under which the buyer takes on the apportionment and self-assesses. If you sell enterprise seats, ask for one rather than guessing. The general rules are in origin vs destination sales tax.

How to work out a specific SaaS sale

1. Confirm you have nexus in the state. Taxability is irrelevant until you have an obligation. Check your sales and transaction volume into the state against its economic nexus threshold, and check for any physical presence such as staff or an office.
2. Look up how that state classifies SaaS. Find the state in the matrix on this page. The classification — tangible personal property, data processing, digital automated service, or non-taxable service — is what decides the answer.
3. Check whether the buyer's use changes the answer. Ohio taxes business use and exempts personal use. Connecticut applies a reduced 1% rate to business use. Iowa and Maryland offer enterprise exemptions. Ask what the customer is doing with the product.
4. Source the sale to a specific address. SaaS is generally sourced to the customer's location. Use the billing address or the primary place of use, not your own location, and apportion across states where a subscription is genuinely used in several.
5. Apply the taxable share, then the combined rate. Most states tax the whole charge. Texas taxes 80% of it. Multiply the taxable base by the full combined state and local rate for the customer's address.
6. Check for a local tax the state does not levy. Chicago's lease transaction tax and Colorado's home-rule cities both reach cloud services their states leave alone. A state-level exemption does not always mean zero.

Once you know a sale is taxable, you need the rate for the customer's exact address. Use the calculator below, or the multi-state sales tax calculator to compare several states at once. Full rate tables are on sales tax by state, and the interactive map shows the whole country.

Keeping the matrix current

SaaS taxability moves faster than any other part of the sales tax base. Louisiana brought digital products in for 2025, Maine expanded its definition for 2026, and Kentucky added software access services in 2023. The direction of travel is one-way: states are widening the base, not narrowing it.

Three habits keep you out of trouble:

1. Re-check the states you are exempt in, not the ones you are taxable in. An exempt state turning taxable creates an unbilled liability that grows silently. A taxable state is already in your process.
2. Watch product changes, not just law changes. Adding a downloadable desktop client or a hardware device can make you taxable in states where the cloud-only version was exempt.
3. Track effective dates carefully. Rate and base changes apply from a specific date, and mid-period changes need care — see sales tax rate change effective dates.

If you have discovered exposure in a state you should have been collecting in, do not simply start collecting going forward — read voluntary disclosure agreements and crossed a nexus threshold, what now first. The operational build-out is in the SaaS sales tax compliance playbook.