Sales tax for SaaS: what subscription businesses need to know

This article is educational and general in nature. It is not tax advice, and nothing here should be treated as a rule for any specific state, country, or business. Sales tax treatment of SaaS varies widely, changes often, and depends on your specific facts. Talk to a qualified tax professional or CPA before making any compliance decision.

Most SaaS founders don't think about sales tax until a customer's finance team asks for a tax-inclusive invoice, or until an advisor mentions it during a fundraising due diligence call. By then, the company may have been selling into a dozen states or several countries for a year or more without ever asking whether it owed anything. That's not necessarily a crisis, but it is the kind of gap that gets more expensive to close the longer it sits open.

Sales tax for software is genuinely harder to reason about than sales tax for physical goods, for two reasons that compound each other: taxability and nexus.

Why "is SaaS taxable" doesn't have one answer

When a retailer sells a physical product, most jurisdictions treat it the same way: it's tangible personal property, and it's taxed (or exempt) fairly consistently. Software as a service doesn't get that consistency. Different states and countries have taken different positions on whether a subscription to hosted software is a taxable service, a taxable sale of tangible personal property (treating access to software as equivalent to a license), a nontaxable service, or something that depends on how the product is used or who is buying it.

That variation means a company selling the exact same product can have a taxable transaction in one jurisdiction and a nontaxable one in another, with no changes to the product itself. It also means the answer can shift over time as states update their guidance to catch up with cloud-delivered software, which is part of why this is a poor candidate for a "read one article and you're done" topic. Bloomberg Tax's long-running Survey of State Tax Departments has repeatedly found meaningful disagreement among states on how they classify SaaS and cloud computing for sales tax purposes, and that disagreement alone should be enough to make any subscription business treat this as something to verify jurisdiction by jurisdiction rather than assume.[1]

Economic nexus, in plain terms

The second layer is nexus: the connection a business needs to a jurisdiction before that jurisdiction can require it to collect and remit tax. For decades, nexus was tied to physical presence, an office, employees, or inventory in a state. That changed with the U.S. Supreme Court's 2018 decision in South Dakota v. Wayfair, Inc., which held that a state can require an out-of-state seller to collect sales tax based on the seller's economic activity in that state, such as revenue or transaction volume, even without any physical footprint there.[2]

Every state that adopted economic nexus set its own thresholds and its own rules for what counts toward them. Layer that on top of the taxability question above, and you get a business reality where the same customer relationship can create no obligation at all in one state, a filing obligation once you cross a revenue threshold in another, and something in between in a third. The Streamlined Sales Tax Governing Board, a long-running multistate effort to align sales tax administration and definitions, is a useful example of how much coordination work this kind of alignment actually takes, and digital goods and SaaS often sit outside the parts of that alignment that states have agreed on.[3] Outside the US, value-added tax and goods-and-services tax regimes add their own registration thresholds and rules for digital services sold to consumers versus businesses, which is a separate body of rules again.

None of this means every subscription company needs a tax team on day one. It means that as revenue and geographic reach grow, "which states or countries am I collecting revenue from, and how much" becomes a question finance needs to be able to answer quickly and accurately, because that's the input a tax professional needs to tell you what, if anything, you owe.

Where subscription businesses get tripped up

A few patterns show up repeatedly in SaaS companies that end up scrambling to catch up on sales tax:

Bundled invoices. A single invoice that combines a software subscription with implementation, training, or professional services can have different taxability for each line item, but if the invoicing system doesn't separate them cleanly, the whole invoice gets treated the same way by default, which is often wrong in either direction.

Tiered and regional pricing without matching records. As pricing gets more sophisticated (usage-based add-ons, enterprise bundles, region-specific price points) it becomes harder to answer basic questions like "how much revenue came from customers billed in Texas last quarter" if that information isn't structured consistently at the point of billing.

Exemption certificates that live in someone's inbox. B2B customers claiming resale or nonprofit exemptions typically need to provide certificates, and those certificates need to be tracked against the right customer and jurisdiction, not filed away and forgotten.

Cross-border sales treated as one bucket. A company selling into the US, Canada, the UK, and the Gulf region is really managing several different tax regimes at once, not one global "international" line item.

Why clean subscription data is the real prerequisite

None of the compliance work above starts from a tax rate table. It starts from knowing, with confidence, who your customers are, where they're billed, what they're being charged for, and how that revenue breaks down over time. That's a data problem before it's a tax problem, and it's exactly where a lot of early-stage SaaS companies are weakest, because that information is split across a payments processor, a CRM, and a handful of spreadsheets that don't reconcile with each other.

When subscription and invoicing records live in one place instead of three, finance can see revenue visibility broken down in the ways a tax review actually requires, rather than reconstructing it from exports after the fact. Real-time MRR, ARR, and NRR dashboards paired with AR tracking and CSV or Excel export mean that when a tax advisor asks "show me revenue by billing state for the last four quarters," that's a query, not a project.

The same logic applies on the pricing side. If your company sells across multiple regions with different price points, structuring that through modular pricing that supports regional and tiered rates keeps the underlying data organized by geography from the start, instead of retrofitting that structure after a nexus review flags a gap. And if a tax-driven change means updating how or when certain customers are billed or notified, running that communication through the same automated retention workflows you already use for renewals and dunning is more reliable than a one-off email sent from someone's personal inbox.

A practical starting checklist

This is organizational hygiene, not tax advice, but it's the groundwork that makes tax advice actionable:

When to bring in a professional

Sales tax compliance for SaaS is a specialized area, and the cost of getting it wrong compounds the longer it goes unaddressed. If your company is growing quickly, selling into multiple states or countries, or has never had a nexus review, that's a reasonable trigger to engage a sales tax specialist or CPA, and in many cases to layer in dedicated sales tax automation software once nexus has actually been established somewhere. The role of clean subscription data isn't to replace that expertise, it's to make sure the expert isn't spending the first three weeks of the engagement just trying to reconstruct your revenue history.

Frequently asked questions

Does Revvly calculate or file sales tax for me? No. Revvly is not a tax calculation or filing service. It centralizes subscription, invoicing, and revenue data so that number is accurate and exportable, which makes it easier to hand off to a tax professional or a dedicated tax compliance tool.

What is economic nexus? Economic nexus is a legal basis some states use to require an out-of-state business to collect and remit sales tax once its sales activity in that state crosses a threshold, even without a physical office or employees there. It followed the Supreme Court's 2018 Wayfair decision.

Is SaaS taxed the same way everywhere? No. States and countries differ in whether they treat SaaS as a taxable service, a taxable sale of software, or a nontaxable transaction, and the rules change over time. This is one of the main reasons SaaS sales tax needs jurisdiction-specific review rather than a general rule.

We've never charged sales tax. Does that mean we're fine? Not necessarily, and it's not something to assume either way. It's worth having a tax professional review your nexus footprint, especially if you've grown quickly or expanded into new states or countries, since obligations can exist even if no one has flagged them yet.

How often do these rules change? Regularly enough that a one-time review isn't sufficient on its own. States update thresholds and guidance, and new economic nexus and digital services rules continue to be introduced internationally, which is part of why ongoing access to clean, current revenue data matters more than a single point-in-time audit.

Sources

1. Bloomberg Tax, Survey of State Tax Departments (annual), documenting variation across states in how SaaS and cloud computing transactions are classified for sales tax purposes.
2. South Dakota v. Wayfair, Inc., 585 U.S. 162 (2018), the U.S. Supreme Court decision establishing that states may require sales tax collection based on economic activity rather than physical presence alone.
3. Streamlined Sales Tax Governing Board, streamlinedsalestax.org, a multistate initiative to simplify and align sales tax administration and definitions across member states.

Frequently asked questions