SaaS Sales Tax by State: Which States Tax Software and How

Why SaaS Taxability Is So Complicated

Traditional sales tax was designed for tangible personal property, meaning physical goods you can touch. Software delivered on a disk or downloaded to a computer was eventually brought into the tax base in most states as either tangible personal property or a specifically enumerated taxable item. But SaaS, where the software runs on the vendor's servers and the customer accesses it through a web browser, does not fit neatly into either category.

The fundamental question is whether SaaS constitutes the sale of tangible personal property, a taxable service, or something else entirely. States have reached different conclusions, often based on the specific wording of their tax statutes rather than any consistent economic rationale.

Adding to the complexity, some states distinguish between different types of cloud computing. Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS) may each receive different tax treatment within the same state. Some states tax SaaS for businesses but not for personal use. Others tax only SaaS that replaces a product that would have been taxable if delivered on physical media.

For SaaS companies, this patchwork means that a single subscription product can be taxable in one state, exempt in the next, and subject to an unclear or evolving rule in a third. Compliance requires state-by-state analysis of both the legal framework and the specific characteristics of your product.

States That Tax SaaS

Several states clearly and explicitly tax SaaS. These include Connecticut, which taxes computer and data processing services at 1% (not the full 6.35% rate). Hawaii taxes SaaS under its General Excise Tax at 4% (4.5% in Honolulu). New Mexico taxes SaaS under its Gross Receipts Tax, which applies to nearly all services. New York taxes prewritten software regardless of delivery method, including SaaS, at the standard rate (currently 4% state plus local). Ohio taxes SaaS as an "automatic data processing" service, subject to the state sales tax rate of 5.75% plus local rates. Pennsylvania taxes SaaS as the sale of "canned software" regardless of delivery method. South Carolina taxes communication services and has ruled that SaaS falls within that category. Tennessee taxes SaaS explicitly, having amended its sales tax statute to include "specified digital products" and SaaS. Texas taxes SaaS as "data processing services" at 80% of the sale price, resulting in an effective rate of 6.4% (80% of the 8% rate). Utah taxes SaaS under its software definitions. Washington taxes SaaS as a "digital automated service" under its sales tax and B&O tax.

In these states, SaaS companies with economic nexus must register, collect sales tax on subscriptions sold to customers in the state, and file returns.

States That Exempt SaaS

Several states have explicitly determined that SaaS is not subject to sales tax. California does not tax SaaS. The CDTFA has taken the position that SaaS does not constitute the transfer of tangible personal property. However, this position is based on administrative guidance rather than a statutory exemption, and some practitioners consider it potentially subject to change. Colorado does not tax SaaS, though its patchwork of local home-rule jurisdictions (such as Denver and Boulder) may have different rules. Georgia exempts SaaS from sales tax. Idaho does not tax SaaS. Illinois does not tax SaaS at the state level. Indiana does not tax SaaS. Iowa exempts SaaS when accessed remotely. Kansas does not tax SaaS. Maryland does not tax SaaS under its sales tax, but does impose a separate Digital Advertising Tax on certain digital advertising revenues. Michigan does not tax SaaS. Missouri exempts SaaS. Nevada does not tax SaaS. Virginia does not tax SaaS.

For SaaS companies based in or selling into these states, the exemption simplifies compliance. However, the company must still track nexus in states where SaaS is taxable.

Gray Areas and Evolving Rules

Several states have rules that are ambiguous, actively evolving, or dependent on the specific nature of the SaaS product. Arizona has not issued clear guidance on SaaS taxability, and the answer may depend on whether the transaction is characterized as a license or a service. Florida has historically not taxed SaaS, but legislative proposals to expand the sales tax base to include digital services have been introduced in recent sessions. Massachusetts taxes SaaS when it is a substitute for prewritten software that would be taxable if delivered on physical media. This "functional equivalent" test requires analyzing each SaaS product individually. New Jersey treats SaaS as taxable if it constitutes the sale of prewritten software, but its guidance on cloud-based access is not entirely clear. Wisconsin taxes SaaS when the customer has the right to download or use the software.

The broader trend is toward taxing SaaS. States facing budget pressures are looking for ways to expand their tax base, and taxing digital services, including SaaS, is a logical target. Several states that currently exempt SaaS have active legislative proposals or study commissions examining the issue.

SaaS companies should review their state tax exposure annually, not just when they first launch. A state that exempted your product last year may change its rules this year.

Compliance Strategy for SaaS Companies

Given the complexity and variation in SaaS tax rules, we recommend the following compliance strategy. First, categorize your product. Is it purely SaaS (browser-based, no download)? Does it include downloadable components? Does it bundle with tangible goods, professional services, or other elements? The bundling question is critical because a bundle that includes taxable and non-taxable elements may be fully taxable in states with "true object" or "principal purpose" tests.

Second, build a state taxability matrix. For each state where you have nexus (or expect to), determine whether your specific product is taxable, exempt, or unclear. Document the basis for your conclusion, citing specific statutes, regulations, or ruling letters.

Third, consider requesting private letter rulings or advisory opinions from states with ambiguous rules. This provides binding guidance and protects you from retroactive assessments if your good-faith interpretation turns out to be incorrect.

Fourth, implement a tax calculation tool that supports product-level taxability coding. Tools like Avalara, Anrok, and TaxJar allow you to assign tax codes to individual products, so that a taxable SaaS subscription collects tax in applicable states while an exempt professional services engagement does not.

At SpryTax, we specialize in SaaS sales tax compliance. We perform the initial taxability analysis, manage state registrations, configure your billing system for correct tax collection, and handle ongoing filing. Our SaaS clients typically start with a taxability review that maps their product against all 50 states, producing a clear compliance roadmap.