6 Reasons SaaS Companies Get Sales Tax Wrong Until It's Expensive

6 Reasons SaaS Companies Get Sales Tax Wrong Until It's Expensive

Most SaaS founders think sales tax is an e-commerce problem. You don't ship boxes. You sell a login. So when does the bill arrive?

Usually about three years after you cross a line you didn't know existed — with penalties, interest, and a back-tax balance that comes out of your own pocket. SaaS sales tax compliance is the quiet liability sitting on most software balance sheets, and it's invisible right up until it's expensive.

Here's the part nobody tells you: the rules genuinely contradict each other from state to state, the obligation can attach without you ever setting foot somewhere, and the people who get burned worst are the ones growing fastest. Below are the six reasons it goes wrong, and what to actually do about each one.

Reason 1: SaaS sales tax compliance starts with a taxability map that keeps changing

There is no federal rule for taxing software. Each state decides on its own, and they don't agree.

Roughly half the states tax SaaS in some form; the rest don't. New York and Texas treat it as taxable. Five states — Alaska, Delaware, Montana, New Hampshire, and Oregon — have no statewide sales tax at all, so the question never comes up there (though some Alaska localities tax it locally).

The trap is that the map moves. A state can reclassify SaaS by statute, regulation, or a single ruling, and your "exempt" product becomes taxable on a date you weren't watching. SaaS taxability by state is a live question, not a settled one — building your compliance on what was true in 2022 is how you end up owing for 2023, 2024, and 2025.

Reason 2: Economic nexus applies to software too — and you cross it without noticing

In 2018, the Supreme Court decided South Dakota v. Wayfair and killed the old rule that you needed physical presence in a state before it could make you collect sales tax. The South Dakota law it upheld kicked in at $100,000 of sales or 200 separate transactions into the state in a year.

Most states copied some version of that threshold. And here's the SaaS-specific kicker: a subscription product blows past 200 transactions almost instantly. Two hundred customers in a state — at $50 a month — is nothing for a growing app. You can trip economic nexus in a state where you have no office, no employee, and no idea you owe anything.

That's the gap. Software sales tax nexus is automatic and silent. Nobody sends you a letter when you cross the line. You find out when the state does.

Reason 3: Sales tax you collected but didn't remit becomes your personal problem

This is the one that should keep founders up at night.

Sales tax isn't your company's money. You're collecting it as a trustee for the state. In most states, unremitted "trust fund" tax can be assessed against the people responsible for the company's finances — personally. The corporate veil that protects you from ordinary business debts often does not protect you here.

So a founder who collected tax through their billing system and let it sit in the operating account — or worse, spent it on payroll — can be on the hook individually for the shortfall, plus penalties and interest. "The LLC owes it" is not the safe answer you think it is.

Reason 4: Calling your product a "service" instead of "software" can flip the tax

The single word you use to describe what you sell can change whether it's taxable.

Several states distinguish between a taxable software product and a non-taxable professional or data-processing service. The exact same platform — billed and described one way — is taxable, and described another way, is exempt. The classification turns on details like whether the customer is buying access to your code or buying an outcome you produce for them.

Founders get this wrong in both directions. Some collect tax they never owed and annoy customers. Others assume "we're a service" and skip collection in a state that would have classified them as taxable software. Either way, the fix is getting the characterization right per state before the audit, not during it.

Reason 5: You assume your billing platform is handling it

Stripe, Chargebee, and the rest can calculate and collect sales tax. They will not register you in a state, file your returns, or decide where you have nexus. Those are your obligations.

The most common failure pattern: a founder flips on "automatic tax" in the billing tool, sees tax appearing on invoices, and assumes the loop is closed. It isn't. Money is being collected without a registration behind it or a return being filed — which is the worst of both worlds. You've created a liability and a paper trail proving you knew.

The tooling is the easy 20%. Knowing where you owe, registering there, and filing on time is the 80% that software doesn't do for you.

Reason 6: You wait until a state finds you instead of disclosing first

The exposure compounds quietly, so the instinct is to keep your head down and hope. That's the most expensive choice available.

Most states offer a voluntary disclosure agreement (VDA): you come forward before they contact you, and in exchange they typically limit the look-back period (often to three or four years instead of "since you started") and frequently waive penalties. It's the cleanest way to cap a runaway back-tax problem.

The catch is in the name. It only works while it's voluntary. The day a state sends you a nexus questionnaire or an audit notice, the VDA door closes — and you're negotiating from the bottom of the hole instead of the top.

What this actually costs: a quick illustrative scenario

Say a SaaS company hits $1.5M in revenue with customers in 12 taxable states, and SaaS is taxable in those states at an average combined rate near 7%. If they should have been collecting and didn't, the uncollected tax base alone is roughly $1.5M × the in-state share. On even $600,000 of that revenue, 7% is about $42,000 in tax — before penalties and interest stack on three years of it.

That number is illustrative, not a quote. But it's the right order of magnitude, and it's why "we'll deal with sales tax later" is one of the most expensive sentences in SaaS.

Find a bookkeeper who actually handles SaaS sales tax compliance

SaaS sales tax compliance is not a problem you solve once. It's a tracking problem — nexus thresholds you monitor, registrations you maintain, returns you file in every state where you've crossed the line. Generalist bookkeepers who do plumbers and dentists are not built for it.

The SaaS Bookkeeper focuses on software companies — exactly the over-$1M tech businesses where economic nexus, software vs. service classification, and multi-state filing all collide. They live in the Stripe-to-state-return workflow that trips up generalists.

If any of these six reasons just described your company, do this before a state does it for you: read The SaaS Bookkeeper's verified reviews on Sam's List and book an intro call. A VDA conversation you start is far cheaper than an audit a state starts for you.