Global Revenue and Invoice Compliance for SaaS Businesses

Selling software globally is easier than ever. Complying with revenue and invoicing regulations globally is not.

The moment you charge customers across borders, you step into a web of obligations: sales tax, VAT, GST, e-invoicing mandates, revenue recognition standards, consumer protection regulations, and cross-border reporting requirements. Each jurisdiction has its own rules. Many of those rules have changed significantly in the last five years as governments close the loopholes that let digital businesses operate globally without paying local tax.

This guide explains what applies, where, and how to build billing infrastructure that handles it without creating operational overhead that scales poorly.

Universal Principles: What Applies Everywhere

Before diving into specific regions, there are three principles that apply in virtually every jurisdiction where you sell digital services.

1. Tax Is Based on the Customer's Location, Not Yours

The old model — charge customers wherever you are registered and let other governments figure it out — is dead. Almost every major economy now applies the "destination principle" for digital services: tax is due where the customer is located, regardless of where the seller is incorporated.

This means:

• A US SaaS company selling to German customers may owe German VAT at 19%
• An Indian SaaS company selling to Australian customers may owe Australian GST at 10%
• A UK SaaS company selling to French customers owes French VAT at 20%, not UK VAT

The threshold for triggering these obligations varies by country. Some apply from the first euro of sales. Others have minimum thresholds before registration is required. But the direction is uniform: sell in a market, comply with that market's tax rules.

2. Invoices Are Legal Tax Documents, Not Just Receipts

In every major tax jurisdiction, a compliant invoice must contain specific elements to be valid for tax purposes. An invoice that is missing required fields is not just incomplete — it is invalid, which means the customer cannot claim the tax as an input credit and the tax authority may disallow the deduction.

Required fields in most jurisdictions include:

• Seller's legal name and registered address
• Seller's tax registration number (VAT number, GST number, EIN, etc.)
• Invoice number that is unique and sequential
• Date of issue
• Description of services delivered
• Tax breakdown (rate applied, taxable amount, tax amount)
• Total amount due
• Customer's name and address
• Customer's tax number (for B2B transactions where the customer needs to claim input credit)

Automated billing platforms handle many of these fields by default, but customized pricing, multi-entity billing structures, and usage-based invoices often produce invoices that fail on the description or tax breakdown requirements.

3. Revenue Must Follow the Accounting Standard, Not the Bank Statement

When you receive an annual prepayment of $12,000 on January 1st, you have not earned $12,000. You have a $12,000 liability. You earn $1,000 per month as you deliver the service.

Under ASC 606 (US GAAP) and IFRS 15 (international), revenue is recognised when performance obligations are satisfied — not when cash arrives or invoices are sent. For SaaS companies, this means:

• Annual prepayments create deferred revenue (a liability), not immediate revenue
• Usage-based fees require accrual estimation at period-end
• Bundled deals with multiple components require allocation across each component

Getting this wrong does not just affect your financial statements. It affects how investors value your business, how auditors assess your financial controls, and whether your revenue figures are defensible in a fundraising or M&A context.

United States: Sales Tax and Economic Nexus

The US has no federal VAT. Instead, sales tax is levied at the state level, creating a patchwork of 45 different regimes (five states have no sales tax at all).

The Wayfair Decision Changed Everything

Before 2018, online businesses generally only owed sales tax in states where they had a physical presence. The Supreme Court's 2018 South Dakota v. Wayfair decision changed this: states can now require out-of-state businesses to collect sales tax based on economic nexus — meeting a revenue or transaction threshold in that state, even without any physical presence.

Most states set their economic nexus threshold at $100,000 in sales or 200 transactions per year. Once you cross that threshold in a state, you are required to:

• Register for a sales tax permit in that state
• Collect sales tax from customers in that state at the applicable rate
• File periodic sales tax returns
• Remit the collected tax to the state

For SaaS specifically, taxability varies significantly by state:

• Some states explicitly tax SaaS (Texas, New York, Pennsylvania)
• Some explicitly exempt it (California, Florida)
• Many are ambiguous — the SaaS tax treatment depends on how the product is classified

If you operate in the US at any meaningful scale, you need either a dedicated sales tax solution (Avalara, TaxJar, Vertex) or a Merchant of Record platform that handles this automatically.

Revenue Recognition in the US

Public companies and many private companies in the US follow ASC 606, the five-step revenue recognition model. For SaaS and professional services:

1. Identify the contract — signed agreement with commercial substance
2. Identify performance obligations — distinct services promised
3. Determine the transaction price — including variable consideration
4. Allocate to performance obligations — based on standalone selling prices
5. Recognize when obligations are satisfied — over time or at a point in time

For a detailed breakdown of how this works in practice, including worked examples for agencies and SaaS companies, see ASC 606 Explained in Plain English.

European Union: VAT and Mandatory E-Invoicing

The EU operates under a harmonised VAT system. For digital services, the rules have been tightened progressively since 2015.

VAT for Digital Services Sold B2C

If you sell digital services to consumers (B2C) in the EU, VAT is charged at the rate applicable in the customer's country. There are two ways to handle this:

Register in one EU member state and use the One Stop Shop (OSS). The OSS system lets you file a single quarterly VAT return covering all your EU B2C sales, regardless of which member states your customers are in. You report all sales and pay all VAT through the OSS registration. This is by far the simplest approach for most SaaS companies.

Register in each member state individually. Required if you exceed certain thresholds or for specific transaction types. More complex, rarely necessary for SaaS.

For B2B sales to EU businesses, the customer's VAT registration number triggers a reverse charge mechanism in most cases: the customer accounts for the VAT on their end (you do not charge it). Your invoice must include the customer's VAT number and a reference to the reverse charge mechanism.

E-Invoicing Mandates

This is the area where EU compliance is moving fastest and where most SaaS companies are not prepared.

Italy has operated mandatory B2B e-invoicing since 2019. All invoices must be submitted through the Agenzia delle Entrate's Sistema di Interscambio (SdI) platform in a specific XML format. Paper and PDF invoices are not valid for tax purposes.

France is rolling out mandatory B2B e-invoicing in phases through 2026, with large companies first and SMEs to follow. The French system requires invoices to be transmitted through certified platforms (PDPs) that report transaction data to the French tax authority.

Spain, Belgium, Germany, Poland, and Romania have announced or are implementing similar mandatory e-invoicing systems. The EU is also finalising its VAT in the Digital Age (ViDA) directive, which will require real-time digital reporting across all member states.

What this means practically: if you have significant EU revenue, especially B2B, you need to understand the e-invoicing requirements of your top markets — not just whether VAT applies, but how invoices must be formatted and submitted. A PDF invoice sent by email is legally sufficient today in most EU markets, but that is changing market by market.

United Kingdom: Post-Brexit VAT

After leaving the EU in 2021, the UK operates its own VAT system. For digital services:

• The UK VAT threshold for foreign digital service providers is effectively £nil for B2C sales (you must register as soon as you have UK B2C sales)
• B2B sales to UK VAT-registered businesses use the reverse charge mechanism
• UK VAT registration is separate from EU OSS registration — you need both if you have both EU and UK customers
• The UK is developing its own Making Tax Digital (MTD) programme, which will require digital VAT record-keeping and returns via compatible software

India: GST on Digital Services

India's GST system applies to digital services delivered by foreign providers to Indian consumers and businesses.

For B2C sales: Foreign SaaS companies must register under India's simplified GST registration for overseas suppliers if they exceed INR 20 lakh (approximately $24,000) in annual Indian B2C sales. Once registered, you must:

• Collect GST at 18% on digital services to Indian consumers
• File monthly GSTR-5A returns
• Issue invoices that include your GST registration number and the applicable HSN/SAC code for your service category
• Remit GST collected by the 20th of the following month

For B2B sales: If your Indian customer is a GST-registered business, the reverse charge mechanism typically applies — the customer accounts for GST on their end, and you do not charge it. Your invoice should include the customer's GSTIN.

India's invoicing requirements are specific and enforced. Invoice numbering must be sequential, invoices must use INR or specify the foreign currency with the exchange rate, and the service description must match the HSN/SAC code claimed.

Australia: GST and Digital Services

Australia requires foreign SaaS providers to register for GST if they supply digital services to Australian consumers and exceed AUD $75,000 in annual Australian sales — commonly called the "Netflix Tax" since Netflix was among the first major companies affected.

Once registered:

• Collect 10% GST on digital services to Australian consumers
• File quarterly Business Activity Statements (BAS)
• Remit GST collected
• Issue tax invoices that comply with ATO requirements

For B2B sales to Australian GST-registered businesses, the reverse charge mechanism generally applies. Your invoice should reference the customer's ABN (Australian Business Number).

The Compliance Infrastructure Problem

Here is the operational reality for a SaaS company with customers across these regions:

A single transaction with a German B2C customer requires: charging German VAT at 19%, reporting it through OSS, issuing an invoice with EU VAT compliance fields, recognising revenue ratably over the subscription period per IFRS 15, and if the customer is an enterprise, ensuring your invoice format is compatible with their e-invoicing requirements.

Multiply this across 500 customers in 20 countries, using multiple pricing models, with contract amendments and mid-term changes, and it is clear why "we'll handle this manually" is not a sustainable approach.

The solutions fall into three categories:

MoR platforms (Paddle, Lemon Squeezy): Handle all transaction-level compliance automatically. You become the Seller of Record, they are the Merchant of Record. Simple to implement, limited to standard subscription billing structures. For a detailed breakdown, see Merchant of Record Explained.

Tax automation tools (Avalara, TaxJar, Vertex): You remain the Merchant of Record and the billing remains your system. These tools calculate the correct tax, file returns, and manage registration. More complex to implement, full flexibility on billing structures.

Hybrid architecture: MoR for self-serve consumer/SMB billing, direct billing with tax automation for enterprise customers. The most common approach for growth-stage SaaS companies with both self-serve and enterprise segments.

Common Compliance Gaps

The most common compliance failures we see in SaaS billing infrastructure:

Missing tax registration in key markets. The most direct risk. If you are selling in a market that requires registration and you have not registered, every past transaction is a potential liability.

Incorrect tax rates applied. Reduced rates, zero-rating for B2B transactions, and exemptions for specific service categories are commonly misconfigured. Overcharging tax damages customer relationships. Undercharging creates a liability.

Non-compliant invoice formats. Missing tax registration numbers, incorrect descriptions, non-sequential numbering, missing customer VAT numbers for B2B transactions. These make invoices invalid for tax purposes.

Revenue recognition done on a cash basis. Common in early-stage companies. Annual prepayments recognised immediately instead of ratably. This understates deferred revenue and overstates current period revenue.

No documentation for contract modifications. Mid-term upgrades, downgrades, and amendments affect revenue recognition. Without a documented modification workflow, ASC 606 or IFRS 15 compliance is not maintainable.

Building the right compliance infrastructure from the start is significantly cheaper than retrofitting it under audit pressure. If you want to understand your current compliance exposure and what it would take to close the gaps, get in touch.