How a SaaS Company Found It Had Been Charging Sales Tax in the Wrong States

How a SaaS Company Found It Had Been Charging Sales Tax in the Wrong States

This case study is an illustrative, anonymized composite based on patterns common in software sales tax cleanup. It is not a description of a specific client engagement, and no outcome described here is promised or guaranteed.

SaaS sales tax by state has two wrong answers, and this company had managed to hit both at once.

It was a Series A workflow platform, roughly $6 million in annual recurring revenue, selling a monthly subscription to customers in about thirty states. It had done the responsible thing eighteen months earlier: registered where its revenue thresholds were crossed, connected an automated tax engine to its billing system, and moved on.

The engine was working correctly. The inputs were wrong.

The Discovery Was a Data Room, Not a Notice

An acquirer's diligence team asked for the sales tax registrations, the returns, and the taxability determination behind them.

The first two existed. The third did not. Nobody had ever written down why the product was being taxed the way it was, because nobody had ever decided. The product had been mapped to a generic "software" category in the tax engine on setup day, and that single dropdown had been quietly governing thirty state answers ever since.

That is how this almost always surfaces. Not from a state, which has no idea you exist until you register or get flagged, but from a buyer's advisor who reads the file as one document and notices there is no reasoning in it.

Two Errors, Pointing in Opposite Directions

The reconstruction produced an uncomfortable table.

Category	What the engine did	What the state actually does
A state that does not tax remotely accessed software	Collected and remitted	No tax due on the subscription
A state that taxes it as a data processing service	Collected at the full rate	Only 80% of the price is taxable
Two states that tax it as prewritten software	Collected nothing, product mapped as a service	Tax due on the subscription

Over-collection in one place. Under-collection in another. A third where the rate was structurally wrong. Same product, same invoice template, same engine.

The instinct is to treat these as one problem with one fix. They are two problems with opposite fixes, and conflating them is how a cleanup goes sideways.

Why SaaS Sales Tax Genuinely Differs by State

There is no federal answer to whether SaaS is taxable, and the states did not converge. They reached for whichever existing category was closest, and they reached for different ones.

New York taxes it as software. Prewritten computer software is taxable as tangible personal property regardless of how it is conveyed to the purchaser, and application service provider fees for website functionality are treated as receipts from the sale of prewritten software. The subscription is taxable. There is a carve-out for a genuine service bundled with the software, but only where the charge for that service is reasonable and separately stated on the invoice, which is an invoicing decision more than a tax decision.

Texas taxes it as a data processing service. Cloud software is treated as data processing, and 80% of the sales price is subject to tax with the remaining 20% exempt. So the correct answer in Texas is neither taxable nor exempt, it is 80% taxable, and an engine set to full-rate taxable is over-collecting by a fifth. Texas also amended its data processing rule effective April 2, 2025 and brought certain marketplace provider services into the definition effective October 1, 2025, which is a reminder that the answer moves.

California generally does not tax it. Canned programs delivered electronically or accessed remotely are generally not subject to tax, because nothing tangible changes hands. The trap is small and specific: provide the customer a backup copy on physical media and the entire transaction becomes taxable. A helpful support engineer mailing a USB drive can change the tax treatment of an entire contract.

Three states, three completely different frameworks, one product.

The Over-Collection Problem Is the Awkward One

Founders assume under-collection is the emergency. In practice, over-collection was the harder conversation.

Money collected from customers as tax is not revenue. It was collected in a state where nothing was due, which means it should not have been charged, and the company was holding customer money it had labeled as a tax. Unwinding that means identifying every affected customer, deciding whether to refund them or leave it with the state, amending returns, and explaining to a hundred and forty customers why an invoice line item from two years ago was wrong.

None of that is a large dollar amount. All of it is contact with customers, in the middle of a diligence process, on a subject that erodes confidence. That is the actual cost.

The under-collection side was more money and less friction. The company had never charged the tax, so no customer had an incorrect invoice. The exposure sat with the company: uncollected tax plus interest, and the practical question of whether to approach the states through a voluntary disclosure program or wait. That is a decision made with counsel, not a bookkeeping entry.

What the Cleanup Fixed

Three things, in order.

A written taxability determination, product by product and state by state, with the authority cited for each answer and the date it was checked. That document is the deliverable. The engine configuration is downstream of it.

An invoice template that separately states the components that can be separately stated, so that a state permitting a service carve-out can actually be given one. The old template bundled everything into a single subscription line, which foreclosed the argument before it started.

A calendar. Taxability rules moved twice in eighteen months in one state alone, so the determination has a review date rather than being a one-time artifact.

What It Did Not Fix

The honest ledger.

The historical exposure did not disappear. A cleanup establishes what is owed and to whom. It does not erase it, and voluntary disclosure programs vary widely by state in what they waive and what look-back period they require.

The diligence timeline slipped. The buyer did not walk, but the tax issue moved to the escrow conversation, and escrow is a price adjustment wearing a different name.

And the underlying ambiguity is still there. Several states have no clear published position on cloud software at all, and reasonable practitioners reach different conclusions in them. The company's new determination documents its position and its reasoning, which is the point. It does not make the position certain, and a future audit can disagree with a well-documented position.

If nexus itself is the open question rather than taxability, start with How Sales Tax Nexus Works for Online Sellers and 5 Sales Tax Nexus Triggers Every Online Seller Should Know. Registration and taxability are separate questions, and getting the first right does nothing for the second.

Who Does SaaS Sales Tax Cleanup Work

The skill is not exotic. It is knowing that "is SaaS taxable" is thirty questions rather than one, and being willing to write the answers down with citations.

The SaaS Bookkeeper is an Austin, Texas accounting and bookkeeping firm founded in 2017, nine years in business with a team of 21, serving clients nationwide and holding CPA and Enrolled Agent credentials. Its profile reports that 100% of the industries it serves is technology and software, and its published service lines include bookkeeping, business and individual tax preparation, sales tax, international tax services, and tax resolution and IRS representation.

The single-vertical focus is the relevant detail here. A firm that works only with software companies has already had the New York prewritten software argument, already knows the Texas 80% figure without looking it up, and already knows which invoice fields matter. A generalist can get to the same answers, but not from memory, and not before the diligence deadline.

Being in Texas is a small practical advantage on this particular question, since the data processing framework is one of the more idiosyncratic ones and it changed twice recently.

The honest constraints, and they are worth stating plainly. The firm's Sam's List profile shows a single client review, which is too few to tell you anything, so we are not citing a count or drawing any comparison from it. Published pricing runs $650 to $5,000 a month, which sets a floor on engagement size. And a bookkeeping-led firm can build the determination and clean up the configuration, but a multi-state voluntary disclosure is usually a separate engagement, often involving counsel. Ask where that line sits before you start.

To compare firms, browse the Sam's List accountant directory and read what actual clients wrote before you get on a call.

Frequently Asked Questions

Is SaaS taxable in Texas? Generally yes, as a data processing service, with 80% of the sales price subject to sales tax and the remaining 20% exempt. That means the correct treatment is neither fully taxable nor exempt, and a tax engine configured to tax the full price is over-collecting. Texas amended its data processing rule effective April 2, 2025, so confirm the current position rather than relying on older guidance.

Is SaaS taxable in New York? Generally yes. New York treats prewritten computer software as taxable tangible personal property regardless of how it is delivered, and application service provider fees for website functionality are treated as receipts from the sale of prewritten software. A charge for an otherwise exempt service bundled with the software is exempt only if it is reasonable and separately stated on the invoice.

Is SaaS taxable in California? Generally no. Canned software delivered electronically or accessed remotely is generally not subject to California sales tax, because there is no transfer of tangible personal property. Providing the customer a backup copy on physical media, however, can make the entire transaction taxable, so shipping media to a customer is a decision with tax consequences.

What happens if we collected sales tax in a state where it was not due? The amounts collected are generally not yours to keep. Resolving it typically involves identifying affected customers, deciding between refunding them and remitting to the state, and amending the affected returns. It is often a smaller dollar figure than under-collection but a larger operational and customer-communication problem, and the right sequence depends on the state.

---

About the author: Kimberly Green is the cofounder of Sam's List, where business owners and high earners find vetted CPAs, financial advisors, and fractional CFOs. She's met one-on-one with 400+ financial professionals and writes from the real data behind thousands of client-advisor matches. Ask her anything about finding an accountant - she's heard it all, including the questions people are afraid to ask.