SaaS Sales Tax by State: Which States Tax Software in 2026?

If you sell cloud software anywhere in the United States, you have probably asked yourself the same question a thousand times: do I actually owe sales tax on this? You are not alone, and honestly, you should not feel bad about being confused. SaaS sales tax by state is one of the messiest corners of U.S. tax law, and it gets messier every year as legislatures scramble to catch up with how software is actually sold today.

Here is the short version. Roughly half the states tax SaaS in some form, the other half treat it as an exempt service, and a few states occupy a strange middle ground where taxability depends on who is buying, how they use it, or which city they happen to sit in. Then, just to keep things interesting, California just changed the rules entirely, effective January 1, 2027.

This guide walks through exactly which states tax SaaS in 2026, how those states classify cloud software for tax purposes, what economic nexus means for your business, and where the law is headed next. We will also cover the compliance mistakes that get SaaS companies in trouble and why software alone rarely catches them in time.

Key Takeaways

• As of 2026, roughly 24 states plus Washington, D.C. tax SaaS in some form. The rest treat it as a nontaxable service, at least for now.
• California signed Senate Bill 122 on June 29, 2026, extending sales tax to prewritten software and SaaS starting January 1, 2027. This is the biggest SaaS tax change in years.
• Texas taxes SaaS as a “data processing service,” but only 80% of the charge is subject to tax.
• Connecticut, Iowa, and Maryland tax SaaS differently depending on whether the buyer is a business or an individual consumer.
• Economic nexus, not physical presence, determines most of your collection obligations. The common trigger is $100,000 in annual sales, though several states are dropping the old 200-transaction rule entirely.
• Software can calculate a rate. It cannot always tell you whether your specific product, in your specific state, with your specific bundle of services, is actually taxable. That still takes a human being who reads the statute.

What Is SaaS Sales Tax?

SaaS sales tax is the sales and use tax that some states apply to software accessed remotely over the internet, rather than downloaded or installed on a customer’s own device. Because SaaS involves no physical transfer of a product, states disagree on whether it counts as a taxable good, a taxable service, or something else entirely, which is exactly why SaaS sales tax by state varies so dramatically from one jurisdiction to the next.

There is no federal sales tax and no federal definition of software for tax purposes. Every one of the 45 states with a general sales tax gets to decide this question on its own, using its own definitions, its own court rulings, and its own timeline. That is the root cause of nearly every headache in this article.

Which States Tax SaaS in 2026? A Quick Answer

If you only have thirty seconds, here is the list. These states currently tax SaaS in some form:

Alabama, Arizona, Connecticut, Hawaii, Iowa (consumer use), Kentucky, Louisiana, Maryland, Massachusetts, Minnesota, New Jersey, New Mexico, New York, Ohio, Pennsylvania, Rhode Island, South Carolina, South Dakota, Tennessee, Texas, Utah, Vermont, Washington, West Virginia, and Washington, D.C.

States that generally do not tax SaaS at the state level (for now) include:

• California (until January 1, 2027)
• Florida
• Illinois
• Colorado
• Georgia
• Michigan
• North Carolina
• Nevada
• Wisconsin
• and most of the remaining states, along with the five states that have no general sales tax at all: Alaska, Delaware, Montana, New Hampshire, and Oregon.

That is a useful cheat sheet, but it is also a snapshot. If you take one thing away from this section, let it be this: the map changes constantly, and “not taxable last year” is not the same thing as “not taxable now.”

SaaS Sales Tax by State: Full Comparison Table

Because so much rides on getting this right, here is a fuller picture of how states currently treat cloud software. Always confirm current rules with the relevant Department of Revenue before you finalize a tax position, since several of these are actively in flux.

How Do States Classify SaaS for Tax Purposes?

Why does the same product get taxed in Texas and go completely untaxed in California? It comes down to how each state’s legal definitions were written, often decades before cloud software existed.

Most states fall into one of four camps. Some, like Massachusetts, New Jersey, and Utah, treat SaaS as “prewritten” or “canned” software, meaning it was built once and sold repeatedly rather than custom-made for a single client. Because prewritten software is already taxable tangible personal property in those states, remotely accessing it gets swept into the same bucket.

Others, like Texas and Ohio, classify SaaS as a data processing or automated data processing service. Texas even carved out a partial break here: only 80% of a SaaS charge is taxable, since the state considers the remaining 20% exempt information handling.

Washington created an entirely new category, the “digital automated service,” specifically to capture cloud software. Meanwhile, states like Hawaii and New Mexico do not distinguish software from anything else. Their general excise or gross receipts taxes apply broadly to nearly every business transaction, SaaS included.

And then there are the states that simply ask: is this a service? If professional services are generally exempt in that state, SaaS often rides along as exempt too. That single question explains most of the “yes” and “no” answers on the table above.

SaaS Nexus Requirements: When Do You Actually Have to Collect?

Taxability answers what. Nexus answers where. You only need to collect SaaS sales tax by state in places where your business has established nexus, meaning a legal connection significant enough that the state can require you to register and collect.

Since the Supreme Court’s 2018 decision in South Dakota v. Wayfair, Inc., physical presence is no longer required. Economic nexus lets a state pull you in based purely on sales volume. The most common trigger nationally is $100,000 in annual sales into that state, though a handful of states, including California, Texas, and New York, set the bar at $500,000.

Historically, many states paired that dollar figure with a 200-transaction threshold, so a business selling a high volume of low-dollar subscriptions could trip nexus with barely any revenue. That is changing quickly. Utah dropped its transaction count in mid-2025, Illinois followed on January 1, 2026, and Kentucky removes its own transaction threshold in August 2026. If you have not reviewed your nexus footprint since these changes rolled out, it is worth revisiting, since you may have obligations that shifted without any action on your part. Our economic nexus guide walks through the current thresholds state by state.

California’s New SaaS Tax: What SB 122 Means for 2027

For more than three decades, California was the single biggest exemption in the SaaS sales tax world. That changes on January 1, 2027, when Senate Bill 122 takes effect and applies sales and use tax to prewritten software and SaaS, regardless of how it is delivered.

Governor Gavin Newsom signed SB 122 on June 29, 2026 as part of the state budget, and the numbers behind it are significant: California’s own estimates put the new tax at roughly $900 million in annual General Fund revenue and $1.1 billion in local sales tax revenue once fully phased in. Custom software built specifically for one client stays exempt. Off-the-shelf SaaS sold to many customers does not.

Here is the detail worth sitting with. The law explicitly preserves an exemption for services that “primarily involve human effort” performed after a customer requests them, things like consulting, configuration, and hands-on implementation. In other words, California’s own legislature just drew a line between what a machine delivers automatically and what a person actually has to do, and taxed them differently. That distinction is not just a legal technicality. It is a genuinely useful way to think about your whole compliance strategy, not only in California, but everywhere.

When Should You Charge Sales Tax on SaaS?

Walking through this in order saves a lot of second-guessing later. First, confirm nexus: do you have $100,000 or more in sales (or the relevant state’s threshold) into that state in the current or prior period? Second, confirm classification: does that specific state tax SaaS at all, and does it distinguish business use from personal use? Third, check for bundling: are you selling SaaS alongside implementation, training, or support, and if so, are those charges itemized separately on the invoice?

That last question trips up more companies than any other. When SaaS is sold bundled with other services for one flat price, several states treat the entire bundle as taxable, even the parts that would have been exempt standalone. Itemizing correctly can be the difference between collecting tax on 20% of a contract versus 100% of it.

B2B vs. B2C: How Business Use Changes SaaS Taxability

Should a Fortune 500 company and an individual consumer pay the same SaaS tax rate? A few states clearly say no. Connecticut taxes SaaS sold for personal use at its full 6.35% rate but drops that to just 1% when the buyer is a business. Iowa flips this around entirely: SaaS is taxable for consumers but exempt for a “commercial enterprise” using it exclusively for business purposes. Maryland offers a similar carve-out for software used as part of an “enterprise computer system.”

For SaaS companies selling to a mixed base of individual and business subscribers, this is not a minor footnote. It means the exact same product can carry two different tax treatments depending entirely on who signed the contract, which makes accurate customer classification, not just address data, part of getting SaaS sales tax by state right.

What Happens If You Get SaaS Sales Tax Wrong?

Getting this wrong rarely announces itself immediately. Most SaaS companies discover a problem during due diligence for a funding round or acquisition, or after a state audit letter arrives years after the fact. Because states can typically look back three to seven years, an unaddressed nexus issue does not shrink over time. It compounds.

The good news is that nearly every state offers a Voluntary Disclosure Agreement, a formal process that lets a business come forward proactively, limit the lookback period, and often get penalties reduced or waived entirely. The bad news is that VDAs only work if you find the problem before the state does. Our guide on how to avoid a sales tax audit covers the warning signs worth watching for.

SaaS vs. Downloaded Software vs. Digital Goods: Why the Difference Matters

These three categories sound similar and get taxed completely differently. Downloaded software, code a customer installs on their own device, is taxable in nearly every state that has a sales tax, since most states still treat a download as a transfer of tangible personal property in electronic form. Digital goods, like e-books, music, or streaming video, follow their own separate rules, often under a “specified digital products” definition.

SaaS sits apart from both. Because the customer never takes possession of anything, some states, like California until 2027, exempt it entirely while still taxing a download of the exact same underlying code. This is why a single company selling both a downloadable desktop app and a cloud subscription version of the same product can face two entirely different tax obligations for what looks, to the customer, like one product.

Real-World Examples and Case Studies

Texas, data processing math: A SaaS company bills a Texas customer $10,000 a month. Because Texas taxes SaaS as a data processing service with a 20% exemption, only $8,000 of that charge is subject to the state’s 6.25% rate plus local tax, not the full $10,000.

Connecticut, same product, two rates: A project management platform sells identical subscriptions to a freelance consumer and to a 50-person marketing agency in Connecticut. The consumer’s invoice carries the state’s full 6.35% rate. The agency’s invoice, properly documented as business use, carries just 1%.

Washington, bundled implementation: In a 2026 determination, Washington’s Department of Revenue ruled that professional implementation services and even reimbursed travel costs were taxable when sold exclusively alongside a digital automated service, because they were provided “in connection with” the taxable SaaS rather than as a separate, standalone offering.

California, the countdown: A mid-sized SaaS company with $2 million in annual California revenue currently collects zero California sales tax. Starting January 1, 2027, that same revenue becomes taxable at California’s combined rate, and the company needs registration, updated billing systems, and customer address data in place well before the deadline, not after it.

Common Mistakes SaaS Companies Make with Sales Tax

• Assuming “SaaS is a service” settles the question everywhere. It settles it in some states and is completely irrelevant in others, like Texas or Washington.
• Ignoring nexus because there is no office in the state. Economic nexus does not require a single employee or square foot of office space.
• Selling bundled implementation without itemizing it. An unbundled invoice line can move a project from partially taxable to fully taxable.
• Missing the B2B versus B2C distinction in Connecticut, Iowa, and Maryland, and charging the wrong rate to business customers.
• Overlooking local home-rule taxes, like Chicago’s lease transaction tax, which applies even when the state of Illinois itself does not tax SaaS.
• Relying on a taxability matrix from a year or two ago, when Louisiana, Vermont, Kentucky, and now California have all changed their rules within a few years of each other.

Actionable SaaS Sales Tax Compliance Checklist

1. Map every state where you have customers and identify how each one classifies SaaS: taxable, exempt, or conditional.
2. Track each state’s economic nexus threshold, and flag states that recently dropped their 200-transaction rule.
3. Register for a sales tax permit before you cross a threshold, not after.
4. Itemize implementation, training, and support charges separately from your core SaaS subscription on every invoice.
5. Collect and store valid resale or exemption certificates for every B2B, nonprofit, or government customer claiming an exemption.
6. Calendar known upcoming changes, especially California’s January 1, 2027 effective date under SB 122.
7. Reconcile any marketplace-facilitated sales, such as AWS Marketplace listings, against your own direct-sale nexus footprint.
8. Have a qualified sales tax professional review your setup at least annually, since a rules engine only applies logic someone already programmed into it.

Why Human Expertise Still Beats Automation for SaaS Sales Tax

Automation is genuinely useful here, and we would never tell you otherwise. A good tax engine can calculate a rate in real time, flag an approaching threshold, and file a routine return without anyone lifting a finger. What it cannot do is read a brand-new state statute the week it passes and tell you, with confidence, whether your specific product fits the new definition.

That is worth sitting with for a moment. California’s new law draws its own exemption around work that “primarily involves human effort.” Washington’s rules carve out a similar space. Even state legislatures, when writing tax code for an industry built entirely on automation, keep landing on the same conclusion: some judgment calls genuinely require a person. Interpreting a letter ruling, defending a classification decision during an audit, deciding how to allocate a multi-state enterprise contract, none of that comes out of a software dropdown menu. If you are reselling someone else’s SaaS platform, this gets even more layered; our guide to SaaS resellers and sales tax digs into that specific situation.

This is exactly the gap a firm like ours is built to close. We are not asking you to abandon your billing software. We are saying the software should be one part of a strategy that also includes a human being who has actually read the statute, sat across from an auditor, and knows the difference between what the law says and what it means for your business.

Conclusion

SaaS sales tax by state is not going to simplify itself, and if anything, 2026 and 2027 are shaping up to be two of the most active years this space has seen. California alone is about to reshape the map for every software company doing business there. Add in shifting nexus thresholds, B2B carve-outs in states like Connecticut and Iowa, and local taxes layered on top of state rules, and it becomes clear why so many growing companies eventually decide DIY compliance is not a long-term strategy.

The states that tax SaaS today will not be the same list a year from now. Staying current, staying registered where you should be, and staying protected during an audit takes more than a quarterly glance at a spreadsheet.

Ready for Expert Help?

Need help making sense of your sales tax obligations? The experts at My Sales Tax Firm can help you navigate nexus studies, registrations, filings, audit defense, and ongoing compliance. Contact us today to learn more.