VAT, Sales Tax, and Global Compliance for SaaS: A Founder's Practical Guide

Sales tax is the compliance problem SaaS founders most often discover too late. The product is selling, customers are signing up across states and countries, and then a registration threshold quietly trips — or worse, an auditor or an acquirer's due-diligence team finds years of uncollected tax. By then it's a cleanup project, not a checkbox.

The good news is that the rules, while genuinely complex, are knowable. This guide lays out what actually triggers a SaaS tax obligation in the US and abroad, how VAT and GST differ from US sales tax, where the common traps are, and the two real strategies for handling it: automate the compliance yourself, or offload the obligation entirely. It's written for founders and finance leads who need the practical shape of the problem, not a law review.

A quick note: this is general information, not tax advice. For your specific situation, talk to a qualified tax professional.

Why SaaS tax is uniquely messy

Software sits awkwardly in tax law that was mostly written for physical goods. Is a cloud subscription a "product," a "service," or a "digital good"? The answer changes by jurisdiction — and the obligation depends on where your customer is, not where you are. Stack dozens of US states and a few dozen countries on top of that, each with its own definitions, thresholds, and filing schedules, and you have a compliance surface that grows every time you close a deal in a new place.

Two big systems are in play: US sales tax (state-level) and international VAT/GST (country-level). They work differently, so we'll take them in turn.

US sales tax: it all starts with nexus

In the US there is no federal sales tax and no single rule for SaaS. Each state decides whether cloud software is taxable and at what rate — which is why the same product can be taxable in one state and exempt in the next.

Your obligation to collect in a given state hinges on nexus — a connection significant enough that the state can require you to collect. There are two kinds:

• Physical nexus — the traditional trigger: an office, employees, servers, or inventory in the state.
• Economic nexus — the modern one. Following the 2018 Supreme Court decision in South Dakota v. Wayfair, a state can require you to collect based purely on your sales volume or transaction count there, with no physical presence at all.

Economic nexus is what catches SaaS companies off guard, because you can cross a threshold in a state you've never set foot in simply by selling enough subscriptions to customers located there. Thresholds vary — a common one is $100,000 in sales or 200 transactions in a state per year, but the specifics differ by state and change often. Some cities and counties layer on their own rules.

Is SaaS taxable in every state?

No — and that's the trap. SaaS taxability is genuinely state-dependent. Some states tax cloud software like a product, some treat it as a non-taxable service, and some distinguish between B2B and B2C use. You can't assume your product is taxable or exempt; you have to check each state where you have nexus. The practical first step is a nexus study: review where your employees are, then map your sales volume and transaction counts by state against each state's thresholds.

International: VAT and GST

Once you sell outside the US, you enter a different system. VAT (value-added tax) and GST (goods and services tax) don't exist in the US, and they behave differently from sales tax. The defining principle: tax is generally based on the customer's location, and most countries expect foreign digital-service providers to register and collect even without any local presence.

The single most important distinction abroad is B2B vs. B2C:

• B2C sales are almost always taxable at the point of sale — you charge the local VAT/GST rate and remit it.
• B2B sales often fall under the reverse-charge mechanism, which shifts the VAT obligation to the business buyer, who reports it on their own return. But you must validate the customer's VAT number and keep evidence that they're a genuine business — get that wrong and the liability bounces back to you.

The EU treats SaaS as a digital service taxed by the customer's country, and offers simplification schemes (like VAT OSS) so you can file across member states through a single return rather than registering in each. Other major markets — the UK, Canada, Australia, and many more — apply their own digital-economy rules, frequently requiring foreign providers to register from the first sale or a low threshold.

The compliance lifecycle (what you actually have to do)

Whether domestic or international, staying compliant follows the same loop:

1. Determine taxability — is your product taxable in this jurisdiction, for this customer type?
2. Monitor thresholds — track sales and transactions by state/country so you know when you trip a registration requirement.
3. Register — sign up with the tax authority before you collect. Collecting tax without being registered is itself a problem in many states.
4. Calculate and charge — apply the correct rate at checkout based on customer location and type, and collect valid evidence of that location.
5. Remit and file — pay the collected tax and file returns on each jurisdiction's schedule, which can range from monthly to annually.
6. Keep records — retain location evidence, VAT-number validations, and receipts for audit protection.

What non-compliance actually costs

This is not a theoretical risk. The three costs founders worry about most are real:

• Penalties and interest. Many states impose escalating penalties — a common pattern is 10% once a payment is 30 days late, more at 60 days, compounding monthly, often capped around half the tax due. If you've been under-collecting for years, those stack across periods during an audit.
• Audit exposure. Audits are time-consuming and expensive even when you ultimately owe little.
• M&A friction. Uncollected tax liability is one of the most common issues flagged in due diligence; it can reduce your valuation or hold up a deal while you remediate.

The pattern is always cheaper to prevent than to clean up.

The two ways to handle it

Here's the part most guides skip, because most guides are written by tax-software companies. There are genuinely two strategies, and the right one depends on how much of the obligation you want to keep.

Option 1 — Automate compliance yourself

You remain the entity legally responsible for tax, but you use software to do the heavy lifting: real-time rate calculation at checkout, threshold monitoring and alerts, VAT-number validation, location-evidence capture, and report generation for filing. This keeps you in control and is the right fit if you have finance resources and want to own the relationship with tax authorities. The trade-off: you still register in each jurisdiction, you still file, and you still carry the liability. The software makes it manageable, not invisible.

Option 2 — Offload the obligation with a merchant of record

A merchant of record (MoR) removes the obligation rather than automating it. Because the MoR becomes the legal seller of record, it is the entity that registers, collects, and remits VAT, GST, and sales tax in each jurisdiction — not you. The tax stops being your filing problem and becomes part of the service. (New to the model? See what a merchant of record is and Merchant of Record vs. Payment Service Provider )

This is the cleaner path if you'd rather not build a tax-compliance function at all, especially when you're selling globally and the jurisdiction count is climbing faster than your team. The trade-off is a higher per-transaction cost in exchange for the liability transfer.

A simple way to choose: if your tax footprint is mostly domestic and you have finance capacity, automation often wins. If you're expanding internationally and want the obligation off your books entirely, an MoR usually does. Many companies start with automation and move to an MoR as global complexity outgrows the team — the same inflection we cover for non-US founders selling worldwide

The bottom line

SaaS tax compliance comes down to knowing where you have nexus, whether your product is taxable there, and how to handle the US-vs-international and B2B-vs-B2C splits — then registering, collecting, remitting, and keeping records on time. You can carry that obligation and automate it with software, or you can offload it entirely by selling through a merchant of record. Both are legitimate; the right one depends on your geography and how much compliance you want to own.

If you'd rather have global tax handled as part of your billing instead of running it yourself, talk to the team at Comecero. We build merchant-of-record and billing infrastructure for SaaS and AI companies — with tax, VAT, and compliance handled, and without the complex setup.