Your SaaS Clients Have a Taxability Problem You're Missing

I work with a lot of software and SaaS clients, and the taxability conversation almost never comes up on its own. Clients assume software is either taxed everywhere or taxed nowhere, pick whichever assumption feels safer, and move on. Neither is close to correct. The gap between what a client is doing and what the rules actually require tends to sit there quietly until an audit, or until a customer's own tax team asks a question nobody at the company can answer.

Why software doesn't follow one rule

Physical goods have a fairly consistent taxability story across states. Software does not. Some states tax software as tangible personal property regardless of how it's delivered. Others tax it only if the customer downloads it, and exempt it when the same product is accessed remotely. A growing number draw a hard line between software a customer installs and software delivered as a hosted service, taxing one and exempting the other. A handful carve out SaaS as its own category with its own rules, separate from how they treat either downloaded software or traditional services.

Roughly half the states now tax SaaS in some form, and that list has been moving rather than settling. The practical effect is that the exact same product, sold the exact same way, can be fully taxable in one state, partially taxable in another, and completely exempt in a third. A client selling nationally is hitting all three outcomes at once, usually without anyone having mapped which states fall into which bucket.

Where subscriptions add another layer

Subscription billing complicates this further. A single tier often bundles several things: hosting, support, occasional professional services, sometimes a downloadable component. When taxable and exempt pieces are sold for one non-itemized price, that's a bundled transaction, and the default outcome in a lot of states is not the favorable one. Many apply a true object test and tax based on what the customer is really buying. Many others take the simpler route: if the taxable and exempt portions aren't separately stated on the invoice, the entire charge gets treated as taxable. A few allow a de minimis carve-out when the taxable piece is small enough.

The consequence is the part I'd want firms focused on. A client billing one flat subscription price with no itemization has no way to reach the better answer even in states that would allow it. The exposure isn't just a wrong rate. It's that the invoice doesn't carry the data needed to defend a better one.

Free trials, tiered plans, and add-on modules raise their own version of the same question, and the answer often turns on invoicing rather than on function. The same capability can land differently depending on whether it's folded into a higher tier or billed as a separately stated add-on. That isn't a quirk. That's the bundling rules doing exactly what they were written to do.

The nexus layer underneath all of this

Taxability is only half the picture. SaaS companies also tend to cross economic nexus thresholds faster than anyone expects, because subscription revenue from a customer base spread across all fifty states adds up quickly even for a relatively small company. A client with a modest customer count but national distribution can be over threshold in several states well before the business feels like it has scaled to the point where sales tax seems relevant. Recurring revenue is the reason. It compounds month over month in a way one-time sales don't.

What this looks like as an advisory conversation

You don't need a formal study to open this up. A few questions get you most of the way:

• How is the product actually delivered? Hosted, downloaded, or some mix depending on the plan?
• In the states where your largest customer segments sit, is SaaS taxed as software, as a service, or as its own defined category?
• Is the invoice structured so taxable and exempt components could be separately stated if a state requires it?
• Has nexus been checked against subscription revenue specifically, since it accumulates differently than one-time sales?

Very few SaaS clients have had this conversation with anyone, including their own finance team. Most are still applying whatever assumption felt reasonable when they set up billing, often years before the business reached its current scale, and nobody has revisited it since.

Why this matters more as products evolve

SaaS companies add capabilities faster than they revisit tax classification. A product that started as pure software access adds professional services, then an API tier, then a marketplace of add-ons built by third parties. Each addition is a taxability question the original setup never anticipated, and the distance between the product today and the classification decided at launch only widens.

For firms serving software clients, this is one of the more overlooked corners of sales tax advisory, mostly because it takes understanding both the tax rules and how the product is actually built and billed. That combination is rare, which is exactly what makes it worth offering.

Sponsored Content: This article is generously brought to you by one of our valued sponsors. Their support enables us to continue delivering expert insights and the latest industry trends to our dedicated community of accounting professionals.