Sales Tax for SaaS: the Complete Guide

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

The complexity starts with a question that has no universal answer: is software a taxable good or a service? Jurisdictions disagree, and that disagreement is the root of everything that follows. Some US states tax SaaS outright, others exempt it entirely, and several apply different rules depending on whether the software is downloaded or accessed remotely.

Three concepts structure the entire subject.

Nexus determines where you owe tax in the United States. Since the Wayfair decision, physical presence is no longer required: crossing a revenue or transaction threshold in a state creates an obligation, and those thresholds differ state by state.

Place of supply governs the European approach. Selling digital services into the EU triggers VAT from the first euro based on where your customer resides, with no threshold and no grace period.

Customer status changes everything again. B2B sales frequently shift the liability to the buyer under reverse charge, while B2C sales keep it with you. Collecting and validating VAT numbers is therefore not administrative busywork but a determinant of what you owe.

The operational burden compounds fast. Each jurisdiction means a registration, a filing calendar, threshold monitoring and potentially a fiscal representative with recurring fees.

Inflowpay available at inflowpay.com removes that burden entirely by operating as a full Merchant of Record, becoming the legal seller and 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.

This article is for informational purposes only and does not constitute professional tax advice.

Is SaaS Taxable?

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

The root of the problem is a classification question. Tax codes were written for tangible goods and defined services, and SaaS fits neither category cleanly. Your customer does not receive anything physical, does not own the software, and accesses it remotely. Jurisdictions resolved that ambiguity differently, which produced the patchwork we have today.

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, and the obligation begins with your first European customer.

In the United States, the picture fragments by state. Several states tax SaaS explicitly, others exempt it, and some distinguish between software downloaded versus accessed remotely. A handful treat it differently again depending on whether the customer is a business or a consumer.

The United Kingdom applies VAT similarly to the EU model. 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. B2B sales frequently shift the liability to the buyer under reverse charge mechanisms, meaning you do not collect. B2C sales keep the obligation with you. Validating your customer’s business status is therefore a tax decision, not an administrative detail.

The practical consequence is that “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 Nexus and When Does It Apply?

Nexus is the connection between your business and a US state that creates a legal obligation to collect and remit sales tax there. Without nexus, you owe nothing. With it, you must register, collect at the correct rate and file returns on that state’s schedule.

Understanding how nexus arises is therefore the single most important concept for any SaaS selling into the United States.

Physical nexus

This is the traditional form and the easiest to identify. You create physical nexus by having an office, an employee, a warehouse, inventory or equipment in a state.

For SaaS companies this matters more than founders expect. A single remote employee living in a state typically creates nexus there, which means a distributed team can generate obligations across a dozen states without any deliberate expansion.

Contractors, attendance at trade shows and even server equipment can trigger it in certain states.

Economic nexus

This is the form that changed everything, and it stems from the 2018 Wayfair decision by the US Supreme Court. Before that ruling, physical presence was required. After it, states became free to impose obligations based on sales volume alone.

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. Crossing a threshold is sufficient.

Those thresholds are commonly set around 100,000 dollars in annual revenue or 200 transactions, though the figures and the combinations vary. Some states use revenue only, others use either criterion, and the measurement period differs as well.

Marketplace nexus

If you sell through a marketplace, that platform may be legally required to collect and remit on your behalf under marketplace facilitator laws. This shifts the obligation away from you for those specific sales, though it does not cover your direct sales.

Why nexus is operationally difficult

The concept is simple. Applying it is not.

Thresholds differ by state, which means tracking your revenue and transaction count separately across more than forty jurisdictions, each with its own trigger.

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

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

Rates vary below state level, since many states allow county and municipal additions, which means a single state can contain hundreds of effective rates depending on the customer’s exact address.

And taxability itself varies, because establishing nexus in a state tells you nothing about whether that state taxes SaaS specifically.

The compounding effect

Each new state multiplies the work rather than adding to it. Ten states means ten registrations, ten filing calendars, ten sets of rules on what is taxable and ten opportunities to miss a deadline.

This is why most SaaS companies reach a point where compliance becomes a permanent operational function rather than an occasional task.

Inflowpay available at inflowpay.com removes that entirely by becoming the legal seller as Merchant of Record, carrying registration, collection and filing across all jurisdictions.

How Does VAT Work for SaaS in Europe?

European VAT follows a logic entirely different from US sales tax, and the distinction matters more than founders expect. Here is what governs it.

• Taxable from the first sale, with no threshold and no grace period
• Rate determined by your customer’s country, not your own
• Rates ranging from 17% to 27% depending on the member state
• Reverse charge on B2B sales when the buyer provides a valid VAT number
• Two pieces of evidence required to establish customer location
• OSS filing allowing one quarterly return instead of twenty-seven
• VAT number validation through the VIES system before applying reverse charge
• Invoice requirements varying by member state

Among these, the absence of a threshold is what catches companies off guard. Unlike the United States where you cross a revenue trigger before owing anything, selling a single 20 euro subscription to a customer in Germany creates a German VAT obligation immediately.

That rule applies to electronically supplied services, which covers SaaS without ambiguity.

The customer location rule is the second structural difference. You apply the rate of the country where your customer resides, not where your company operates. A French SaaS selling to a Spanish customer charges Spanish VAT, which means your pricing and your margins vary by market unless you build that into your checkout.

Rate variation compounds this. Hungary applies 27%, Luxembourg 17%, with most member states somewhere between 19% and 25%. On a 100 euro subscription, that spread represents a 10 euro difference in what you remit.

The B2B reverse charge changes the calculation entirely and is worth understanding properly. 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. You must verify the number through the VIES system, and applying reverse charge to an invalid number leaves the liability with you.

The two pieces of evidence requirement is frequently overlooked. To establish your customer’s location you need two non-contradictory indicators, typically the billing address, the IP address, the bank location or the SIM country code. Keeping that evidence is a compliance obligation, not a best practice.

OSS, the One Stop Shop scheme, is the mechanism that 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.

OSS covers B2C sales within the EU. It does not cover your domestic sales, which stay on your national return.

Two further points deserve attention. Invoice requirements differ by member state on content and format, which affects your billing system. And the United Kingdom now operates outside this framework entirely, requiring separate registration and filing.

The operational reality is that European compliance is more centralized than US compliance but begins far earlier, since your first customer creates the obligation.

How Do You Stay Compliant as a SaaS?

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. Keep 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 digital products sell wherever someone finds them.

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 requirement before collecting, and collecting tax without registration 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 pieces of location evidence.

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

The seventh step is to file on each calendar. Deadlines differ by jurisdiction and some require filings even in periods with no sales. Missed returns 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 successful 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.

Conclusion: Build the Function or Transfer It

Sales tax for SaaS comes down to a question most founders postpone until it becomes expensive: do you build a compliance operation, or do you transfer the obligation entirely?

The subject itself is not conceptually difficult. Nexus determines where you owe tax in the United States, and since the Wayfair decision crossing a revenue or transaction threshold is enough to create it without any physical presence. Place of supply governs Europe, where VAT applies from the first sale based on your customer’s country, with no threshold at all. And customer status shifts the liability on B2B sales through reverse charge, provided you validate the VAT number properly.

What makes it hard is the compounding operational load. Each jurisdiction adds a registration, a filing calendar, threshold monitoring, rate configuration and evidence retention. Ten markets does not mean ten times the work on a single process, it means ten separate processes with ten opportunities to miss a deadline.

That load arrives sooner than expected. Digital products sell wherever someone finds them, which means obligations accumulate in markets you never targeted.

Three points deserve particular attention if you handle this internally. Monitor thresholds continuously, since nexus can arise mid-year without warning. Validate VAT numbers through VIES before applying reverse charge, because an invalid number leaves the liability with you. And keep your location evidence, since two non-contradictory indicators are a compliance requirement rather than a precaution.

Budget realistically as well. Tax software, accounting fees, fiscal representatives in jurisdictions that require them and your own time add up to a permanent cost line.

The alternative is structural rather than incremental. A Merchant of Record becomes the legal seller of your product, which moves the obligation off your entity entirely rather than helping you manage it.

Inflowpay available at inflowpay.com operates that way, handling VAT, sales tax, OSS, IOSS and CESOP across all jurisdictions at 4% plus 0.35 dollar all-in, with chargeback liability absorbed and a non custodial model that structurally prevents frozen funds.

Whichever path you choose, choose it deliberately. The expensive outcome is discovering obligations retroactively, with penalties and back taxes on sales you never collected on.

Useful Resources

• Top 6 International Merchants of Record‍
• Top 5 Best Merchants of Record for Shopify‍
• Top 6 Best Shopify-Compatible PSPs‍
• Top 5 Best Payment Gateways of 2026‍
• The Best Stripe Alternatives in 2026‍
• Merchand of Record vs Paypal