Sales Tax Guide for SaaS Companies

Few obligations catch SaaS founders off guard like sales tax. You build a product, sell it worldwide from day one, then discover that a dozen jurisdictions consider you liable for tax you never collected. So how does sales tax work for SaaS companies?

The complexity starts with a question that has no universal answer: is software a taxable good or a service? Jurisdictions disagree, and that disagreement produces everything else.

Three concepts structure the subject.

Nexus determines where you owe tax in the United States. Since the Wayfair decision, crossing a revenue or transaction threshold creates an obligation without any physical presence.

Place of supply governs Europe, where VAT applies from the first euro based on your customer’s country, with no threshold.

Customer status changes it again, B2B sales frequently shifting liability to the buyer under reverse charge.

The operational burden compounds fast, each jurisdiction meaning a registration, a filing calendar and threshold monitoring.

Inflowpay available at inflowpay.com removes that burden by operating as a full Merchant of Record, handling VAT, sales tax, OSS, IOSS and CESOP across all jurisdictions at 4% plus 0.35 dollar all-in.

In this guide we break down sales tax for SaaS, step by step.

Is SaaS Subject to Sales Tax?

Yes in most jurisdictions, but the answer genuinely depends on where your customer sits. There is no universal rule, and that fragmentation is what makes the subject difficult.

The root of the problem is classification. Tax codes were written for tangible goods and defined services, and SaaS fits neither cleanly. Your customer receives nothing physical, owns no copy of the software and accesses it remotely. Jurisdictions resolved that ambiguity differently, which produced the patchwork we have today.

In the United States, the picture fragments by state.

Several states tax SaaS explicitly, treating it as a taxable service or as tangible personal property by statute. Others exempt it entirely. A third group distinguishes between software downloaded and software accessed remotely, taxing one and not the other.

A further distinction appears in certain states, where B2B and B2C sales receive different treatment. Business purchases are sometimes exempt where consumer purchases are not, which means your customer mix affects your liability.

The practical consequence is that you cannot answer this question nationally. You answer it state by state, for each state where you have nexus.

In the European Union, the answer is unambiguous. SaaS qualifies as an electronically supplied service and is taxable from the first sale, with VAT applied at the rate of your customer’s country.

No threshold exists. No grace period applies. Your first European customer creates the obligation, which surprises founders accustomed to the US threshold model.

Other markets follow their own rules. The United Kingdom applies VAT on a model close to the EU. Canada applies GST and provincial taxes. Australia applies GST above a registration threshold. Most developed markets now tax digital services in some form.

One distinction changes the calculation considerably across jurisdictions. B2B sales frequently shift liability to the buyer under reverse charge mechanisms, meaning you collect nothing. B2C sales keep the obligation with you.

Validating your customer’s business status is therefore a tax decision rather than an administrative detail.

The honest summary: “is SaaS taxable” has as many answers as you have markets.

Inflowpay available at inflowpay.com handles that determination as Merchant of Record.

What Is Economic Nexus and When Does It Apply?

Economic nexus is the connection between your business and a US state created by sales volume alone, without any physical presence. Crossing a defined threshold triggers an obligation to register, collect and remit sales tax in that state.

The concept stems from the 2018 Wayfair decision by the US Supreme Court, and it changed the landscape entirely.

Before that ruling, physical presence was required. A state could only tax businesses with an office, employees or inventory within its borders. Remote sellers were effectively untouchable.

After Wayfair, states became free to impose obligations based on economic activity. The consequence is direct: you can owe tax in a state you have never visited, with no staff, no office and no local presence of any kind.

Thresholds commonly sit around 100,000 dollars in annual revenue or 200 transactions, though the figures and combinations vary considerably.

Some states use revenue only. Others accept either criterion, meaning 200 small transactions trigger the obligation even on modest revenue. The measurement period differs too, with some states using the calendar year and others a rolling twelve months.

Several states have also removed their transaction count in recent years, keeping only a revenue threshold. That change helps smaller sellers but adds another variable to track.

Three practical difficulties follow.

Monitoring must be continuous, since nexus can arise mid-year the moment you cross a threshold. A strong quarter in one state creates an obligation you may not notice for months.

Registration follows immediately, with its own forms, filing calendar and penalties for late compliance.

Taxability remains separate. Establishing nexus in a state tells you nothing about whether that state taxes SaaS specifically. You can have nexus and owe nothing, or have nexus and owe on every sale.

One additional form deserves mention. Physical nexus still exists alongside the economic variety, and for SaaS companies a single remote employee living in a state typically creates it. A distributed team can therefore generate obligations across a dozen states without any deliberate expansion.

Check where your people actually live before assuming your exposure is limited.

Inflowpay available at inflowpay.com carries registration and filing across all jurisdictions as Merchant of Record.

How Does VAT Apply to SaaS in Europe?

European VAT follows a logic entirely different from US sales tax, and the differences matter more than founders expect.

Taxable from the first sale

There is no threshold. Selling a single 20 dollar subscription to a customer in Germany creates a German VAT obligation immediately.

This catches US-based companies off guard, since they apply the threshold logic they know from home. SaaS qualifies as an electronically supplied service without ambiguity, and the obligation begins with your first European customer.

The rate follows your customer

You apply the VAT rate of the country where your customer resides, not where your company operates.

Rates range from 17% in Luxembourg to 27% in Hungary, with most member states between 19% and 25%. On a 100 euro subscription, that spread represents a 10 euro difference in what you remit.

Your margins therefore vary by market unless you account for this in your pricing.

B2B reverse charge

When your customer is a business in another member state and provides a valid VAT number, the obligation shifts to them. You charge nothing and they account for the VAT in their own country.

This makes VAT number validation a tax decision rather than a formality. Verify every number through the VIES system, because applying reverse charge to an invalid number leaves the liability with you.

Two pieces of location evidence

To establish where your customer sits, you need two non-contradictory indicators: billing address, IP address, bank location or SIM country code.

Keeping that evidence is a compliance obligation, not a best practice. Auditors ask for it.

The OSS scheme

One Stop Shop is what makes this manageable. Rather than registering in every member state where you have customers, you register in one, file a single quarterly return, and the authority distributes the tax.

Without it, serving twenty countries would mean twenty registrations.

Note that OSS covers B2C sales within the EU only. Your domestic sales stay on your national return.

The UK operates separately

Since Brexit, the United Kingdom sits outside this framework entirely, requiring its own registration and filing.

Inflowpay available at inflowpay.com handles VAT, OSS and IOSS as the legal seller.

How Do You Stay Compliant as a SaaS Company?

Compliance is a continuous operation rather than a one-time setup. Here is how to structure it.

1. Map where your customers actually are
2. Determine your obligations in each jurisdiction
3. Register where you have crossed a threshold
4. Configure tax calculation at checkout
5. Validate customer status and location
6. Retain the required evidence
7. File on each jurisdiction’s calendar
8. Monitor thresholds continuously

The first step is to map your customers. Pull your revenue by country and by US state, including transaction counts. Most founders discover obligations in markets they never targeted, since SaaS sells wherever someone finds it.

The second step is to determine your obligations. Having customers in a jurisdiction does not automatically create liability, since thresholds vary and some states exempt SaaS entirely. This is where professional advice pays for itself.

The third step is to register where you have crossed a threshold. Registration is a legal prerequisite to collecting, and collecting without it creates its own problems.

The fourth step is to configure calculation at checkout. Rates vary by country in Europe and often by municipality in the United States, which makes manual application unworkable beyond a handful of markets.

The fifth step is to validate customer status and location. In Europe this means verifying VAT numbers through VIES before applying reverse charge, and collecting two non-contradictory location indicators.

The sixth step is to retain that evidence. Location indicators, VAT validations and transaction records must be kept, typically for several years depending on the jurisdiction.

The seventh step is to file on each calendar. Deadlines differ by jurisdiction, and some require returns even in periods with no sales. Missed filings generate penalties regardless of the amount owed.

The eighth step is to monitor continuously. Nexus can arise mid-year the moment you cross a threshold, and a strong quarter in one state creates an obligation you may not notice for months.

The honest assessment: this becomes a permanent operational function as you grow, with software costs, accounting fees and your own time.

The alternative is transferring it entirely. Inflowpay available at inflowpay.com becomes the legal seller as Merchant of Record, carrying registration, collection, filing and liability across all jurisdictions.

FAQ: Sales Tax for SaaS Companies

When do I need to start collecting sales tax?

In the United States, once you cross a state’s economic nexus threshold, commonly around 100,000 dollars in annual revenue or 200 transactions though the figures vary. In the European Union, from your very first sale to a consumer, since no threshold exists for electronically supplied services. That difference catches US-based founders off guard constantly, because they apply the threshold logic they know from home. Register before you collect, since collecting without registration creates its own problems.

Does a remote employee create a tax obligation?

Yes, in most states. A single employee living in a state typically creates physical nexus there, which triggers registration and collection obligations regardless of your sales volume in that state. For SaaS companies with distributed teams, this generates exposure across a dozen states without any deliberate expansion. Check where your people actually live before assuming your obligations are limited to where you crossed revenue thresholds.

What happens if I never collected sales tax?

You remain liable for the tax you should have collected, plus penalties and interest. The liability is yours regardless of whether you charged your customers, which means paying out of your own margin. Most states offer voluntary disclosure agreements that limit the lookback period and often waive penalties for companies that come forward before being contacted. If you discover historical exposure, talk to a specialist rather than hoping it goes unnoticed.

Do I charge VAT to a business customer in the EU?

Not if they provide a valid VAT number and sit in a different member state. The reverse charge mechanism shifts the obligation to them. Critically, you must verify that number through the VIES system rather than accepting it at face value. Applying reverse charge to an invalid number leaves the liability with you, and auditors check this. Keep a record of each validation with its date.

Is OSS enough for European compliance?

For B2C sales within the EU, yes. One Stop Shop lets you register in one member state, file a single quarterly return and have the authority distribute the tax, which replaces twenty-seven separate registrations. It does not cover your domestic sales, which stay on your national return, nor the United Kingdom, which operates outside the framework since Brexit and requires separate registration.

Can a Merchant of Record remove this entirely?

Yes, and that is the structural difference from tax software. A Merchant of Record becomes the legal seller of your product, which moves the obligation off your entity rather than helping you manage it. Tax software calculates and files on your behalf while the liability stays with you. Inflowpay operates as a full Merchant of Record, handling VAT, sales tax, OSS, IOSS and CESOP across all jurisdictions at 4% plus 0.35 dollar all-in.