Sales Tax Compliance for SaaS: Nexus, Exemptions & Penalties

SaaS sales tax compliance means figuring out which states treat your subscription as taxable, watching your revenue against each state’s economic nexus threshold, registering and filing where you cross it, charging the right rate at the customer’s location, keeping exemption certificates on file, and cleaning up any past gaps through a voluntary disclosure agreement before a state finds you first. Roughly half the states tax SaaS, and a company selling nationwide can easily owe tax in 20 or more jurisdictions, each with its own rules, rates, and filing calendar.

Where Your Subscription Is Taxable

No two states define cloud software the same way. Some treat SaaS as tangible personal property because the user can perceive and interact with it on a screen. New York taxes prewritten software regardless of whether it arrives on a disc or through a browser. Other states classify the same subscription as an intangible service and exempt it. A smaller group taxes SaaS only under specific conditions, such as whether the sale is business-to-business or business-to-consumer, or whether the software was custom-built for the buyer.

As of early 2026, roughly 20 to 25 states tax SaaS at the state level. Five states have no general sales tax at all. Among the rest, the split between taxing and non-taxing states is close to even. A handful of states add local taxes even when the state itself doesn’t impose one, so a subscription can be taxable in one city and not in the rest of the state.

The custom-versus-prewritten line matters. Many states exempt software designed and developed to the specifications of a single buyer while taxing off-the-shelf products, including SaaS. A standardized platform used by thousands of subscribers reads as prewritten in most taxing states. Bespoke work built for one client may qualify for exemption in some of those same states. The gray zone is a standard platform heavily configured for each customer, and that’s where most disputes start.

Economic Nexus: When You Have to Start Collecting

Before 2018, a state could only require you to collect sales tax if you had a physical presence there. The Supreme Court ended that rule in South Dakota v. Wayfair, holding that states can require collection from remote sellers with a significant economic connection to the jurisdiction.1Supreme Court of the United States. South Dakota v. Wayfair, Inc. Every state with a sales tax now has economic nexus rules for remote sellers.

The common threshold is $100,000 in annual sales into the state. Many states originally paired this with an alternative trigger of 200 separate transactions, but that second prong is disappearing. As of 2026, at least 14 states have dropped the transaction count entirely, including South Dakota itself, Illinois, Indiana, and Washington. Some states still keep both, so a high-volume, low-price subscription can trip nexus on transactions alone in those places.

Watch whether a state measures gross sales or only taxable sales. In a gross-sales state, every dollar you earn there counts, even if SaaS itself is exempt in that state. You can end up with a registration obligation in a state where your core product isn’t taxable, simply because your total revenue there is high enough.

Crossing the threshold does not make earlier sales retroactively taxable. The obligation is prospective. Most states give a grace period of roughly 30 to 60 days to register and start collecting; the transaction that pushes you over doesn’t itself have to be taxed. That window is for getting set up, not for deciding whether to comply.

Marketplace Sales

If you sell through a third-party platform, the platform may handle the tax. All states with a sales tax now require marketplace facilitators to collect and remit on behalf of third-party sellers.2Amazon Web Services. AWS Marketplace – Tax Help for Sellers You still need to track your own nexus and handle direct sales, but revenue flowing through a facilitator largely takes care of itself.

Charging the Right Rate

Even after you know your product is taxable in a state, you have to pick a rate. Most states use destination-based sourcing: you charge the rate where the customer uses the software. About ten states use origin-based sourcing for in-state sales, taxing at the seller’s location. For remote sellers the distinction mostly collapses, since origin states generally apply destination sourcing to out-of-state sellers. A SaaS company based in Texas selling to a customer in Pennsylvania charges the Pennsylvania rate.

The operational problem is pinpointing the customer’s location, because county and municipal rates vary. Billing address works for most SaaS transactions. Some states want the primary location where the software is actually used, which is difficult for a product accessed from anywhere.

Bundled Subscriptions

Most SaaS companies don’t sell pure software access. Subscriptions often bundle implementation, training, consulting, data storage, or API access into a single price. When taxable software and non-taxable services share one line, the whole transaction is at risk.

The general rule: a bundled transaction sold for a single, non-itemized price can be fully taxable if any component is taxable. Many states apply a “true object” test, sometimes called “dominant purpose.” The question is what the customer actually wanted to buy. If the software was the point and the consulting was incidental, the whole bundle is taxable. If the software was a minor add-on to a large consulting engagement, the bundle may be exempt.

Itemize invoices. When each component has its own line and price, most states evaluate each line on its own merits instead of applying one taxability determination to the whole invoice. A single line reading “Annual Platform Subscription + Implementation” invites the state to tax the full amount. Two separate lines usually let the non-taxable piece stay non-taxable. Invoice structure is one of the simplest levers you have, and it’s the one most companies ignore until an audit.

Exemption Certificates

Not every sale to a customer in a taxable state actually requires collection. Resale buyers, manufacturers, government entities, and nonprofits may all qualify for exemption. The burden of proving it is on you as the seller. If you don’t have a valid certificate on file when an auditor asks why you didn’t collect, you owe the tax plus interest and penalties, whether or not the customer was genuinely exempt.

A valid certificate needs the buyer’s name, address, state tax identification number, and the specific reason for the exemption. Most certificates last one to three years; some states allow indefinite certificates as long as the buyer’s circumstances don’t change. Build a process that flags exempt buyers at the point of sale, collects the certificate before the first invoice, and tracks expirations. Retrofitting certificates after an audit notice is expensive, and often impossible: customers who left two years ago will not fill out paperwork for you.

Registering and Filing

Once you know where you have nexus and where your product is taxable, register with each state’s revenue department before you start collecting. Most states register online, and the fee is small or zero. You’ll provide your federal EIN, business structure, and officer information, along with an expected date of first taxable sale.

Streamlined Sales Tax

Registering individually across 20 or more states is tedious. The Streamlined Sales Tax program offers one centralized registration that covers all 24 member states.3Streamlined Sales Tax. Streamlined Sales Tax – Home The program also connects qualifying businesses with certified service providers that handle tax calculation and reporting at no cost. Not every state participates. California, New York, and Texas are among the non-members, so you’ll still register directly with those states if you have obligations there.

Filing Frequency and Zero Returns

After approval, each state assigns you a filing frequency, usually based on expected volume: monthly, quarterly, or annually. The filing itself reports gross sales, subtracts exempt sales, applies the correct rate, and remits payment, typically by electronic funds transfer. Even in a period with no sales, file a zero return. Skipping zero returns is one of the most common compliance mistakes; states treat non-filing as non-compliance, which can trigger estimated assessments, penalties, and permit suspension.

Cleaning Up Past Gaps

If your company has been selling into states where it had nexus but never registered, the standard remedy is a voluntary disclosure agreement. A VDA is a deal: you come forward, register, file back returns for a limited lookback period (typically three to four years), and pay the tax owed during that window plus interest. In exchange, the state waives penalties and does not pursue liability for periods before the lookback.

The Multistate Tax Commission runs a centralized program that lets you negotiate VDAs with multiple states through one process.4Multistate Tax Commission. Multistate Voluntary Disclosure Program You can initiate anonymously; the state doesn’t learn your identity until you’ve agreed to terms and signed. This matters because once a state contacts you first through an audit notice or inquiry, you’re generally disqualified from that state’s VDA program for that tax type. The voluntary window closes the moment the state knows you exist.

The math usually favors a VDA. Without one, a state can audit back to the date you first had nexus, which could be your launch date. With one, exposure is capped at three or four years of back tax plus interest, with penalties waived. The longer you wait, the more back tax accumulates outside the eventual lookback window, so the correction only gets more expensive.

Penalties and Personal Liability

Sales tax you collect from customers is not your money. States classify it as a trust fund tax: funds held temporarily on behalf of the government. If your company collects and fails to remit, the liability doesn’t stop at the corporate level. Officers, owners, and anyone classified as a “responsible person” for the company’s tax obligations can be held personally liable. In many states, personal liability does not require a finding of intent. Being the person in charge of finances can be enough.

Late-filing and late-payment penalties vary but typically run between 5% and 25% of tax due, sometimes with a minimum dollar amount regardless of the balance. Interest accrues on top. For businesses that never registered, the audit lookback can stretch to the date nexus first arose, exposing years of uncollected tax. States that find non-compliance through their own enforcement are far less generous than those that receive a voluntary disclosure.

The most overlooked risk is permit revocation. Stop filing returns, even zero returns, and states can suspend or revoke your permit after notice. Making taxable sales without a valid permit can convert a civil penalty situation into one with criminal exposure, depending on the jurisdiction and the amounts.

Running the Process

Ongoing compliance comes down to five recurring tasks: tracking where you have nexus, determining taxability in each jurisdiction, registering where required, collecting the right amount on each transaction, and filing returns on schedule. Each has to be repeated as your customer base shifts, as states change their rules, and as your revenue crosses new thresholds.

Automation software from providers such as Avalara, Anrok, or TaxJar handles rate calculation and return filing across multiple states. With nexus in a handful of states, manual compliance is feasible if someone owns the process. Once you’re registered in ten or more jurisdictions with monthly filings, the volume of returns and rate lookups makes automation close to unavoidable. The cost of the software is predictable. The cost of getting it wrong shows up as back tax assessments, penalties, and interest that dwarf the subscription fee.