Most SaaS founders assume tax is straightforward: register in your home country, file once a year, done. That assumption holds until the first international customer pays you. From that moment, you are potentially liable for tax in every jurisdiction where your customers are located — regardless of whether your company has ever set foot there.

This is not a technicality that only affects large companies. Tax authorities in the EU, UK, Singapore, Japan, and Australia have actively pursued small and mid-sized foreign digital service providers for back taxes, regardless of company size.

This guide explains how indirect tax works for SaaS companies, which regimes consistently catch founders off guard, what non-compliance actually costs, and how to structure your payment infrastructure so that tax stops being a recurring operational problem. For the full picture on how MoR infrastructure handles tax, compliance, and liability together, see What Is a Merchant of Record?.

Why SaaS tax works differently from what you expect

Physical goods are taxed at the point of sale or import. Digital services are taxed at the point of consumption — meaning where your customer is located when they access your software.

The practical implication: if a SaaS company incorporated in Singapore sells subscriptions to customers in Germany, France, and Italy, it is potentially liable for VAT in all three countries, not just Singapore. The German customer's payment triggers a German VAT obligation. The French customer's payment triggers a French VAT obligation. Your company's home jurisdiction is irrelevant to these calculations.

This destination-based model is now the global standard for digital services. The OECD framework, adopted by most developed economies, explicitly requires foreign digital service providers to register, collect, and remit tax in the customer's country — either immediately or once any applicable local threshold is crossed.

The tax regimes that catch SaaS founders off guard

European Union VAT

The EU applies VAT to all digital services sold to EU consumers by non-EU businesses, with no minimum revenue threshold for non-EU providers. If you make a single B2C sale to a customer in Germany, you are technically liable for German VAT on that transaction.

Standard VAT rates across EU member states range from 17% to 27%, varying by country. France charges 20%. Germany charges 19%. Hungary charges 27%. The rate that applies is the rate of the customer's country, not a single unified EU rate.

The EU's One Stop Shop (OSS) scheme lets non-EU businesses register in a single member state and file one quarterly return covering all EU sales, rather than registering separately in every country where they have customers. This is the practical compliance path for most SaaS companies operating in the EU. It does not eliminate the obligation; it consolidates the filing.

United Kingdom VAT

Post-Brexit, the United Kingdom operates a separate VAT regime independent of the EU. UK VAT on digital services is 20%. Foreign businesses with UK customers must register for UK VAT separately from any EU OSS registration. A company registered under the EU OSS has no coverage for UK transactions.

United States sales tax

The US applies sales tax at the state level, not the federal level. There are more than 12,000 distinct tax jurisdictions across states, counties, cities, and special districts (Vertex, 2024). Whether SaaS is taxable at all varies by state: some states tax all software-as-a-service, others exempt it, and others tax only specific delivery methods or contract structures.

The post-2018 South Dakota v. Wayfair Supreme Court ruling established economic nexus as the standard for sales tax obligations. A foreign company with no physical US presence can trigger a state obligation based solely on revenue from customers in that state — typically above $100,000 in annual sales or 200 transactions, though thresholds vary by state.

For most early-stage SaaS companies with US customers, the practical risk is low until revenue concentrates significantly in specific states. At scale, the obligation is real and enforcement is active.

Singapore GST

Singapore's Overseas Vendor Registration (OVR) scheme applies 9% GST to foreign digital service providers that meet two simultaneous conditions: annual global turnover exceeding SGD 1,000,000, and digital services supplied to non-GST-registered Singapore customers exceeding SGD 100,000 per year. Once both thresholds are crossed, registration is required within 30 days and GST collection begins from that point forward (Inland Revenue Authority of Singapore).

Japan Consumption Tax

Japan requires foreign businesses selling digital services into Japan to register for 10% Japan Consumption Tax (JCT). Unlike most jurisdictions, Japan also requires non-resident businesses to designate a local tax agent to handle correspondence with the National Tax Agency. These are not alternative options; both registration and a local tax agent are mandatory.

The tax-agent obligation is ongoing, not a one-time setup cost. It adds a recurring administrative and financial cost that does not scale with your revenue in Japan.

Australia GST

Australia applies 10% GST to digital services sold by foreign providers to Australian consumers, with registration required once global turnover reaches A$75,000. The threshold is low enough that most SaaS companies with meaningful traction in the Australian market will cross it.

What non-compliance actually costs

The standard assumption is that non-compliance is a back-tax exposure: you owe the VAT you failed to collect, plus interest. In practice, the full cost is higher and harder to estimate in advance.

• Back taxes plus penalties. Most jurisdictions apply interest on unpaid tax from the date the tax was due, not the date of discovery. For a company that sold into the EU for three years without registering, back taxes cover the full three years, with interest compounding on each period's unpaid balance. Penalties for non-registration are assessed separately from the underlying tax.
• Audit exposure across jurisdictions. A tax audit in one jurisdiction often triggers cross-border information sharing. The EU's administrative cooperation framework lets authorities across member states share taxpayer activity, so a failure discovered in one country can initiate inquiries in others.
• Payment processor risk. Processors operating under regulatory oversight can be required to report merchant activity to tax authorities in certain jurisdictions. Non-compliant merchants identified through these channels face forced remediation, and in some cases account suspension.
• Operational disruption. Resolving multi-jurisdiction back-tax issues typically requires local advisors in each affected country, significant management time, and system changes to collect tax retroactively — an effort that is rarely successful for prior billing periods.

Three ways to handle it

Option 1: Register directly in each jurisdiction. You identify your obligations, register in each country where you have customers, configure your billing system to collect the correct rate, file returns on each jurisdiction's schedule, and maintain the registrations as you grow. This works. It is also a full-time compliance function. At five or more active markets, it requires either a dedicated in-house tax team or external advisors in each jurisdiction, and the cost scales with your geographic footprint.

Option 2: Use a tax calculation tool. Stripe Tax, Avalara, TaxJar, and similar tools automate tax calculation and, in some cases, filing. They reduce the engineering burden of computing the correct rate at checkout and can generate filing-ready reports. The critical limitation: these tools calculate the tax and add it to the checkout total on your behalf — they do not assume liability. Your company is still the seller of record, still responsible for registration, and still subject to audit for any calculation errors. Tax tools are a valuable addition to a PSP setup, but they do not transfer the underlying obligation.

Option 3: Operate under a Merchant of Record. Under an MoR model, the MoR is the legal seller in each transaction. Tax collection, remittance, registration, and audit exposure belong to the MoR, not to you. When the EU audits sales made through the MoR, the audit is the MoR's problem, not yours.

How an MoR removes the tax problem entirely

When Waffo Pancake acts as your Merchant of Record, the tax structure works like this. A customer in France buys a subscription. Pancake is the legal seller on that transaction. Pancake calculates 20% French VAT, collects it from the customer at checkout, and remits it to the French authorities on its filing schedule. You receive net revenue and never incur a VAT liability on that transaction.

This applies across every market where Pancake processes payments. A customer in Singapore, Japan, Australia, the UK, or any US state generates the same structure: Pancake collects and remits the applicable tax; you receive net revenue with no registration or filing obligation in that jurisdiction.

Here is the lifecycle in practice:

1. A customer enters their email, country, and billing details in the first step of Pancake's checkout.
2. Pancake determines the customer's location and applies the correct local rate — for example 19% VAT in Germany, 10% JCT in Japan, or 9% GST in Singapore.
3. Pancake processes the payment as the registered seller of record.
4. Pancake remits the collected tax to the relevant authority on the applicable schedule.
5. You receive clean net revenue — with no filing deadline or audit exposure in the markets Pancake covers.

As your Merchant of Record, Pancake is the registered seller and taxpayer across 173 countries: US sales tax in 45+ states, EU VAT via the OSS scheme, UK VAT, and more. The same integration that handles payment processing handles tax compliance in every covered market. There is no separate tax layer to configure, no additional registrations to maintain, and no jurisdiction-specific advisors to retain. As Pancake puts it: "We're the seller. You focus on building."

Why trust Waffo Pancake as your MoR

Waffo Pancake is built on Waffo's payment platform. Waffo is PCI DSS v4.0 Level 1 certified, backed by HSBC, and built by a founding team from Alipay and Ant Group, with over $30M raised. For context, the industry first-attempt subscription renewal rate averages roughly 57% (Cashfree, 2024); across the Waffo platform, merchants have recorded up to a 45% improvement in payment success rate and recovered about 18% of previously failed orders (based on Waffo platform data).

Pricing: tax compliance included, not an add-on

Unlike a tax calculation tool that bills on top of your processor, Pancake bundles compliance into one transparent rate. There are no monthly fees and no setup costs, and tax compliance in covered markets is included at no extra charge.

The same checkout that collects payment collects the correct tax, and the same flat rate covers the remittance. What you see is what you are charged.

When does an MoR make sense for your tax exposure?

SaaS sales tax is not a problem that resolves itself. Every new market you enter adds a potential registration obligation. Every year you operate without compliance in a jurisdiction with active customers extends your back-tax exposure. The complexity does not diminish as your company grows; it compounds.

The practical options are: build internal compliance infrastructure that scales with your geographic footprint, rely on tax calculation tools that reduce technical work without transferring liability, or shift to an MoR model where the tax obligation belongs to the MoR and your team spends zero time on jurisdiction-specific filings.

A Merchant of Record is likely the right move once you sell into two or more countries, sell B2C into the EU (where the non-EU threshold is zero), or find yourself spending real hours each month tracking registration thresholds. For SaaS companies that plan to grow internationally, the compliance cost of operating without an MoR rarely stays fixed — it grows with every market, every regulatory change, and every year of accumulated exposure.

This article is general information, not tax, legal, or financial advice. Tax rates and rules change; verify current requirements with the relevant authority or a qualified advisor before acting.

Related articles

Global Compliance

Do You Need a Merchant Account? MoR vs. PSP Explained (2026)

Global Compliance

LLC vs. Inc for a SaaS Business: How to Choose (2026 Guide)

Global Compliance

What Is a Merchant of Record (MoR)? The 2026 Guide for Developers and Founders