If you sell software in the US, the tax you owe depends on how you deliver it, who’s buying it, and which state you’re selling into. Software-as-a-service (SaaS), downloaded software, and custom-built software each get different tax treatment. And that treatment varies enough by state that two companies that sell functionally identical products can have opposite tax obligations, depending on where their customers are located.
Nearly all states and Washington, DC, collect statewide sales taxes. Below, we’ll explain why software sales tax is so complicated, how states classify SaaS versus downloaded software, what happens when you misclassify a transaction, and how to evaluate your current process for tracking tax obligations as you grow.
Key takeaways
Software tax obligations depend on delivery method, customer type, and state. This means the same product can be taxable in one state and exempt in another.
Downloaded software is taxed more consistently than SaaS. SaaS classification varies by how each state defines a taxable service.
Misclassifying software for sales tax purposes creates compounding exposure since the same error repeats across every transaction.
Why is software sales tax so complex?
Three variables determine your sales tax obligation in any given state: how the software reaches the customer, who the customer is, and which state you’re selling into.
The delivery method matters because states historically taxed physical property. Then, many stretched that definition to cover downloaded software while leaving cloud-based access in a separate category. Customer type matters because several states tax SaaS for business use but exempt personal use and others do the reverse.
State-by-state differences in tax treatment create three kinds of software businesses:
Pure SaaS companies: Businesses that sell access to cloud-hosted software with no download or installation step. Your exposure depends entirely on how each state defines “use” of something you never physically transfer.
Hybrid software companies: Businesses that offer both a downloadable or installed version and a cloud-based version of the same product.
Software-enabled platforms: Businesses that bundle software access with another service (e.g., a platform that charges for both software and a managed component). Bundling can change the whole transaction’s taxability in some states.
A state-by-state breakdown of SaaS taxability
Some states treat SaaS as a taxable service and others treat it as a nontaxable service. Each of the former defines the taxable transaction on its own terms. For example, Texas taxes SaaS as a data processing service, which carries a partial exemption that reduces the portion of the transaction that is taxable.
Other states treat SaaS as narrowly or conditionally taxable. Connecticut taxes B2B SaaS transactions at a reduced rate rather than at its standard rate. Iowa taxes SaaS products for personal use, but not those for business use.
States without statewide sales tax—Alaska, Delaware, Montana, New Hampshire, and Oregon—obviously don’t impose state sales tax on SaaS, although some Alaska municipalities might apply local taxes.
|
State |
Statewide SaaS taxability |
|
Alabama |
Taxable |
|
Alaska |
No state sales tax |
|
Arizona |
Taxable |
|
Arkansas |
Generally not taxable |
|
California |
Generally not taxable (until 2027) |
|
Colorado |
Generally not taxable |
|
Connecticut |
Taxable |
|
Delaware |
No state sales tax |
|
Florida |
Generally not taxable |
|
Georgia |
Generally not taxable |
|
Hawaii |
Taxable |
|
Idaho |
Generally not taxable |
|
Illinois |
Generally not taxable |
|
Indiana |
Generally not taxable |
|
Iowa |
Taxable for personal use, not business use |
|
Kansas |
Generally not taxable |
|
Kentucky |
Taxable |
|
Louisiana |
Taxable |
|
Maine |
Generally not taxable |
|
Maryland |
Taxable |
|
Massachusetts |
Taxable |
|
Michigan |
Generally not taxable |
|
Minnesota |
Generally not taxable |
|
Mississippi |
Generally not taxable |
|
Missouri |
Generally not taxable |
|
Montana |
No state sales tax |
|
Nebraska |
Generally not taxable |
|
Nevada |
Generally not taxable |
|
New Hampshire |
No state sales tax |
|
New Jersey |
Generally not taxable |
|
New Mexico |
Taxable |
|
New York |
Taxable |
|
North Carolina |
Generally not taxable |
|
North Dakota |
Generally not taxable |
|
Ohio |
Taxable for business use, not personal use |
|
Oklahoma |
Generally not taxable |
|
Oregon |
No state sales tax |
|
Pennsylvania |
Taxable |
|
Rhode Island |
Taxable |
|
South Carolina |
Taxable |
|
South Dakota |
Taxable |
|
Tennessee |
Taxable |
|
Texas |
Taxable |
|
Utah |
Taxable |
|
Vermont |
Taxable |
|
Virginia |
Generally not taxable |
|
Washington |
Taxable |
|
West Virginia |
Taxable |
|
Wisconsin |
Generally not taxable |
|
Wyoming |
Generally not taxable |
|
Washington, DC |
Taxable |
These rules are changing, too. For instance, California will begin taxing SaaS products in 2027.
How does sales tax treatment differ for downloaded software vs. SaaS?
States with sales tax generally treat prewritten (“canned”) software delivered by download as taxable. In theory, the buyer is acquiring a copy of something so it’s considered a sale of property and taxed just like a boxed product. Custom software built for a single customer is the main exception: many states exempt it because they see the transaction as a service (the labor of building something bespoke) rather than a product sale. The line between “customized” and “configured” matters here. Heavily modifying a ready-made product can sometimes preserve its taxable status, while software built from zero for a single client typically doesn’t.
With SaaS, nothing transfers to the customer. There’s no download, no installation, and no file that becomes their property. States that tax SaaS do so for one of two reasons: they classify it as a service (e.g., Texas’s data processing service category) or stretch their existing software license definitions to cover access instead of possession. States that don’t tax SaaS generally accept that without a transfer of property, there’s no taxable sale under their statutes as written.
Selling the same product as both a download and a subscription means tracking two tax treatments for the same product. You might owe tax on the download in a state where the subscription is exempt, or vice versa. The determining factor is the version the customer bought, not the product itself.
Which states create high potential audit risk for software companies?
A few states in particular create extra audit exposure for software companies. Compliance can be tricky in the following states.
California
California generally won’t tax SaaS until 2027, but it does tax certain software licenses and software that’s been customized or configured for a specific buyer beyond a basic installation. The line between an exempt SaaS subscription and a taxable software license generally comes down to how much the buyer can modify the software and whether they receive any local processing component alongside it.
Ohio
Ohio taxes SaaS when it’s used by a business within the state, but not when it’s for personal or customer use. Sourcing a transaction by customer type adds a compliance layer traditional retailers don’t typically manage. A SaaS business that does both B2B and B2C sales needs to track how the software is used, not just where the buyer’s billing address is.
Iowa
Like Ohio, Iowa has different tax rules for B2B versus B2C sales. SaaS sales are taxable only when they’re for personal use so you need to know whom you’re selling to.
Texas
Texas taxes SaaS as a data processing service but allows a 20% exemption on the charge so only 80% of the transaction is subject to tax. Missing that exemption or applying it incorrectly creates errors that auditors could flag.
Florida
Florida generally exempts SaaS, but whether a transaction counts as a sale of tangible software or an exempt service depends on contract language and how access is structured. That makes Florida a state where the written agreement matters as much as the product itself.
What are the risks of getting software sales tax wrong?
Getting the classification wrong on software sales tax can have multiple consequences:
Back taxes: If you should’ve been collecting and remitting in a state and weren’t, you generally have to pay the full amount owed plus interest on the unpaid amount.
Penalties: Many states add fines on top of back taxes and interest, which are often calculated as a percentage of the unpaid tax per month.
Compounding exposure: Misclassification grows with your customer base since software companies sell the same product structure to thousands of accounts.
Registration risk: States require registration before you start collecting. Collecting while you’re unregistered can carry penalties, even when the tax treatment itself was correct.
How should software companies evaluate their sales tax compliance approaches?
Several questions can help you determine whether manual sales tax tracking is realistic for your business. Consider the following:
Nexus footprint: If you’re registered, or should be registered, in more than a few states, manually tracking each state’s SaaS classification, exemption percentage, and rate changes can turn into a part-time job for whoever owns this task.
Delivery mix: Companies that sell both downloaded and cloud-based versions of their products might double the classification work.
Product change frequency: Adding a new tier, bundling a managed service with your software, or shifting from a license model to a subscription model can change your tax treatment in some states, even when nothing about the underlying technology changed.
Stripe Tax addresses the classification problem directly with product tax codes built for software and digital products. When you assign a product tax code such as SaaS or downloadable software to your offering, Stripe Tax applies the correct taxability rule for that category in each state automatically, including state-specific exemptions. It also tracks your transaction volume and revenue across states to notify you when you’re approaching an economic nexus threshold so you’re not relying on a manual review to catch the moment you need to register somewhere new.
How Stripe Tax can help
Stripe Tax reduces the complexity of tax compliance so you can focus on growing your business. Stripe Tax helps you monitor your obligations and alerts you when you exceed a sales tax registration threshold based on your Stripe transactions. In addition, it automatically calculates and collects sales tax, value-added tax (VAT), and goods and services tax (GST) on both physical and digital goods and services—in all US states and in more than 100 countries.
Start collecting taxes globally by adding a single line of code to your existing integration, clicking a button in the Dashboard, or using our powerful application programming interface (API).
Stripe Tax can help you:
Understand where to register and collect taxes: See where you need to collect taxes based on your Stripe transactions. After you register, switch on tax collection in a new state or country in seconds. You can start collecting taxes by adding one line of code to your existing Stripe integration or add tax collection with the click of a button in the Stripe Dashboard.
Register to pay tax: Let Stripe manage your global tax registrations and benefit from a simplified process that prefills application details—saving you time and simplifying compliance with local regulations.
Automatically collect tax: Stripe Tax calculates and collects the right amount of tax owed, no matter what or where you sell. It supports hundreds of products and services and is up-to-date on tax rules and rate changes.
Simplify filing: Stripe Tax seamlessly integrates with filing partners, so your global filings are accurate and timely. Let our partners manage your filings so you can focus on growing your business.
Learn more about Stripe Tax, or get started today.
The content in this article is for general information and education purposes only and should not be construed as legal or tax advice. Stripe does not warrant or guarantee the accurateness, completeness, adequacy, or currency of the information in the article. You should seek the advice of a competent attorney or accountant licensed to practice in your jurisdiction for advice on your particular situation.