SaaS Sales Tax: Which States Tax Software Subscriptions and How to Comply

There is no single answer to whether SaaS is taxable. Some states with a general sales tax treat a software subscription as a taxable service or taxable “canned software,” and others don’t tax it at all, and the two groups don’t split along any pattern a founder would guess from population, tax rate, or political lean. Texas, New York, and Pennsylvania all tax SaaS, and Ohio taxes it when it’s bought for business use. California, Florida, and Virginia currently don’t, though that list is shorter than it used to be: California just voted to start taxing SaaS beginning January 1, 2027. A company selling into all 50 states is, by definition, operating in a patchwork, and the compliance burden is real: economic nexus can be triggered without a single employee or server in a state, and getting the taxability call wrong compounds every month a subscription renews.

Which states actually tax SaaS subscriptions?

States get to SaaS taxability through different legal routes, which is part of why the rules feel inconsistent even within states that land on the same answer. Texas, New York, Pennsylvania, and Washington currently tax it, and Ohio taxes it when it’s bought for business use; California (until January 1, 2027), Florida, Virginia, and Michigan generally don’t; Kansas and Wyoming are worth checking with the state directly; in Colorado and Illinois the tax shows up at the local level in certain cities.

• Taxed as a service or as “canned software,” however delivered. Texas taxes SaaS under its data processing services category, but only 80% of the charge is taxable (a statutory 20% exemption applies to data processing services). New York taxes SaaS as the sale of prewritten software, treating remote access as equivalent to a license regardless of whether anything is downloaded. Pennsylvania and Washington reach the same result through similar “software however delivered” language.
• Taxed as a computer or information service. Ohio taxes SaaS as an automatic data processing or computer service when it’s provided for use in business; consumer use isn’t taxed under that rule. Iowa and a handful of others tax it as a defined digital or information service, sometimes with different rules for business versus consumer purchasers.
• Local-only taxation. Colorado and Illinois are notable middle cases: state-level sales tax generally doesn’t reach SaaS, but home-rule cities within those states can and do impose their own local tax on it, so a Colorado-wide “not taxable” answer can still be wrong for a customer in Denver or another home-rule city. In Illinois, Chicago’s lease tax on nonpossessory computer leases is one example.
• Not taxed at all, currently. California (until January 1, 2027), Florida, and Michigan generally don’t tax hosted software because a remotely accessed service isn’t a sale of tangible personal property under their current rules, and Virginia exempts services that provide access over the internet. Kansas guidance is mixed and Wyoming has little published guidance, so check with those states before relying on a no-tax answer.

The practical problem is that this list is not stable and not intuitive. A state’s answer can turn on decades-old statutory language never written with cloud software in mind, on a single Department of Revenue letter ruling, or on a definition of “tangible personal property” that predates SaaS by 40 years. Nothing about a state’s income tax rate, corporate tax climate, or reputation for being business-friendly predicts its SaaS sales tax position.

Why is California about to change its answer?

Because the legislature changed the law in its 2026 budget package. Senate Bill 122, signed in June 2026, extends California sales and use tax to digital prewritten software and SaaS starting January 1, 2027, regardless of delivery method. Custom software built for one customer stays exempt, but the general SaaS exemption California companies have relied on ends on that date.

• Taxability is not a fact a company determines once. It’s a jurisdiction-by-jurisdiction legal position that state legislatures actively revisit as SaaS becomes a larger share of the economy.
• A company that set its tax engine rules in 2022 and never revisited them is running on stale law by definition, and California is proof the list still moves.

How does economic nexus work for a SaaS company?

Nexus is the legal threshold that triggers a state’s authority to require collection, and for SaaS companies it’s almost always economic nexus, not physical presence, that matters. Before the Supreme Court’s 2018 decision in South Dakota v. Wayfair, Inc., a state generally couldn’t require an out-of-state seller to collect its sales tax without a physical footprint there. Wayfair overturned that rule, and states with a sales tax have since adopted economic nexus thresholds based on economic activity alone.

Threshold type	Typical amount	What it means for a SaaS company
Sales dollar threshold	Often $100,000 in sales into the state over a year, though some states set it higher (Texas uses $500,000 over the preceding 12 months)	Crossed the moment cumulative subscription revenue from customers billed to that state passes the number, no matter how many customers
Transaction count threshold	200 separate transactions into the state	Some states don’t use a transaction count at all (Texas doesn’t), but where one applies, such as Ohio’s 200, each renewal or invoice may count, which SaaS billing cycles hit fast
Marketplace exception	N/A	Does not apply; see below

Two details catch SaaS companies off guard. First, the $100,000 threshold is measured on gross sales into the state, not profit, and it typically counts even exempt sales in some states’ calculations, so a company can trip the threshold and trigger a registration and filing obligation in a state where it turns out the product isn’t even taxable, purely because the dollar test looks at revenue, not taxability. Second, once nexus exists, it generally doesn’t reset the moment revenue dips; thresholds are measured over a lookback period (Texas uses the preceding 12 months), so check each state’s rule before closing a registration.

Do marketplace facilitator rules apply to SaaS?

Almost never, and this is one of the more common misconceptions. Marketplace facilitator laws shift the sales tax collection obligation from individual third-party sellers to the platform that facilitates the sale, Amazon, Etsy, and similar marketplaces are the textbook examples. The logic is that the platform controls payment processing and listing, so it’s more efficient to make one entity responsible for collection instead of thousands of individual sellers.

• A SaaS company selling its own subscription directly to its own customers, through its own website and its own billing system, is not selling through a marketplace facilitator in the legal sense, even if it uses a payment processor like Stripe to handle the transaction. Stripe processes payment; it does not list the product, set the price, or facilitate the sale in the way the statutes define, so the collection obligation stays with the SaaS company itself.
• This changes if a SaaS company’s product is distributed and billed through an actual marketplace, an app marketplace like the Salesforce AppExchange or a platform that controls the customer relationship and payment flow for the transaction. Those arrangements need a specific, contract-by-contract look at whether the platform meets the state’s facilitator definition and has assumed collection duty, which some app marketplaces do and some explicitly disclaim in their seller terms.

How do you determine where the customer “uses” the software?

Sourcing, the rule for which jurisdiction’s tax rate and rules apply to a given sale, matters as much as taxability itself, and it’s genuinely unsettled across states for a product with no physical delivery point.

• Billing address is a common practical proxy, because it’s reliably captured at checkout, and some states lean on it directly (Pennsylvania presumes all users are located at a Pennsylvania billing address).
• Primary use location, sometimes required for genuinely multi-state enterprise deals, asks where the substantial use of the software actually occurs, which for a company with offices in three states means the seller theoretically needs to source and potentially apportion the sale across all three, based on employee headcount, seat allocation, or another reasonable method the customer discloses.
• IP address at time of access is rarely the controlling legal test, but it can serve as evidence a company can use (or a state auditor can use against it) when billing address doesn’t reflect reality, for example a company billed in a no-tax state but whose users are demonstrably concentrated in a taxing one.

For a self-serve, single-location small business customer, billing address is almost always a defensible sourcing method. For a large enterprise deal with multiple offices and negotiated terms, the sourcing question deserves a specific conversation with the customer’s own tax or procurement team, because getting sourcing wrong on a large contract creates real exposure in an audit, not just a rounding error.

Is there an exemption for business-use purchases?

Sometimes, and it’s worth checking before assuming a B2B sale is automatically exempt just because the buyer is a business. A few states apply a specific carve-out for software bought for trade-or-business use (Iowa’s commercial enterprise exemption is one), distinct from consumer use. None of this is a blanket “business buyers don’t pay sales tax” rule.

• A handful of states tax SaaS differently depending on whether the end use is business-to-business or business-to-consumer, with the B2B scope sometimes narrower than the consumer one (Iowa) and sometimes broader (Ohio taxes only business use).
• The exemption a B2B SaaS company more often relies on is a resale or manufacturing/processing exemption, though neither usually fits a straightforward subscription purchase.
• Nonprofit status, government purchaser status, and certain data-processing-input uses can qualify for a state-specific exemption certificate, but each requires a valid certificate on file, and the burden of proving one exists at audit time sits with the seller, not the buyer.

What’s a practical compliance approach for SaaS companies?

Start with a nexus study the moment the company crosses roughly $500,000 to $1 million in aggregate revenue, or earlier if growth concentrates in a few taxing states; waiting until nexus is blown in ten states makes cleanup far more expensive than staying ahead of it.

• Sales tax nexus is a separate question from state income tax nexus, covered in our guide to SaaS multi-state income tax; a company can owe one without owing the other.
• Run a taxability matrix specific to the product, not a generic SaaS answer, since a platform with a services or data-processing component can land differently than a pure subscription.
• Automate collection with a dedicated SaaS-aware tax engine rather than a general e-commerce tool, which is frequently wrong on SaaS-specific carve-outs like Texas’s 80% rule or Colorado’s local-only rule.
• Put a recurring reminder on the taxability list itself, not just the nexus thresholds; California’s flip from exempt to taxable proves a list set once in 2023 won’t catch itself.
• Entity structure affects how state tax obligations flow through to the owners; see our guide to SaaS entity structure choices.

What should I do next if I haven’t looked at this yet?

Run the nexus and taxability check before your next state notices you first; states have more ways to spot unregistered sellers than most founders assume, and the two most common cleanup steps both work better done early than after a notice arrives.

• If you already have exposure in a state where you should have been collecting, look into that state’s voluntary disclosure program before an audit letter arrives. Many states offer reduced lookback periods and penalty abatement for a company that comes forward voluntarily.
• Make sure your billing system generates revenue on the schedule your ASC 606 revenue recognition policy actually calls for; a sales tax fix is wasted effort if the underlying invoice data it’s built on is wrong.

This guide is general information, not tax advice for your specific situation. Which points apply, and how, depends on your facts.