If you sell SaaS, software, subscriptions, e-books, streaming access, or similar digital services across borders, the tax point is usually driven by the customer, not by your checkout page. The EU's official OSS guidance says cross-border consumer sales are taxed at the customer's country rate. HMRC says digital services supplied to UK consumers are liable to UK VAT. The real problem is rarely the headline rate. It is the missing evidence, the wrong B2B flag, or the habit of copying one country's rule into every market.
That is why digital indirect tax is not just a bookkeeping topic. Your billing logic, customer-location evidence, VAT ID checks, and country thresholds all need to line up. Corpenza usually looks at this together with tax optimization, broader cross-border structuring through double tax treaties, and payment leakage issues such as withholding tax.
What counts as a digital service for VAT or GST?
A digital service is usually content or software delivered online with minimal human intervention. HMRC's official guide includes e-books, PDFs, online magazines, web hosting, software updates, advertising space on a website, films, music, and games. Using the internet to arrange a physical sale, or emailing a custom piece of advice, does not automatically put the supply into the same bucket.
The practical test is simple. If the customer clicks buy, the system delivers access or content automatically, and the seller's staff do very little after checkout, tax authorities usually treat that as a digital service. A manual consulting engagement can use the same payment tool and still fall under different place-of-supply rules.
Where is VAT or GST due when your customer is abroad?
The first question is not where your company is incorporated. It is where the customer is treated as consuming the service. The EU OSS page describes this as destination-based VAT: you charge the rate of the customer's country. HMRC says supplies of digital services to UK consumers are liable to UK VAT, and sales outside the UK may trigger the customer's local VAT rules instead.
This is where the B2B versus B2C split matters. A customer with a valid business tax number and genuine business status is not the same as a retail buyer paying with a personal card. A business sale may shift into reverse-charge or different place-of-supply treatment. A consumer sale often creates a local VAT or GST issue much faster.
How does the EU OSS system change the workflow?
The EU's One Stop Shop is designed to simplify reporting, not to simplify the rate logic. Your Europe says you can register once, file one VAT return, and make one payment through a single portal while still charging VAT at the customer's country rate. So the rate remains local. The reporting lane becomes centralized.
That changes operations in a useful way. If you sell to consumers in France, Germany, and Spain in the same month, OSS can spare you multiple local VAT registrations. But it does not fix weak data. Your checkout still needs to capture the right country, the right customer type, and the right evidence before the quarterly return ever starts.
What changes in the UK and New Zealand?
The UK and New Zealand are a good reminder that there is no single global threshold. HMRC's digital-services guidance says an overseas business supplying digital services to UK consumers may need to register for UK VAT. New Zealand Inland Revenue says you must register for and charge GST when your total supplies of goods and services to New Zealand customers were, or are expected to be, NZ$60,000 or more over a 12-month period.
That means “we are still a small SaaS company” is not a tax rule. In the UK, the exposure can matter from the first consumer sales. In New Zealand, the threshold matters. Other markets write their own version. The safe operating model is a country-by-country tax matrix, not one generic line in the finance memo.
What records support customer location and business status?
The tax dispute usually starts after the payment has already settled. Your file needs to support customer country, billing country, IP or similar geo-indicators, payment instrument, and any business tax number you relied on. HMRC's place-of-supply guidance also says that if a service is treated as supplied outside the UK, your records should contain enough evidence to support that conclusion.
The expensive mistakes are small on day one. Finance marks a sale as B2B but there is no VAT-ID validation record. The app store is the deemed supplier, yet your own invoice also adds tax. A billing address says Germany while the rest of the evidence says Dubai, and nobody reviews the conflict. These are operating issues, not theory.
Which mistakes create avoidable tax leakage?
The first mistake is treating every digital sale as identical. The second is ignoring the difference between direct sales and marketplace sales. HMRC says that when digital services are supplied via certain third-party platforms or marketplaces, the platform can be responsible for accounting for VAT on the supply. The third mistake is collecting weak country data at checkout and trying to rebuild the evidence later from payment exports.
The quieter mistake is organizational. Teams wait until month-end to think about tax, even though product, finance, and legal have already made decisions that determine the answer. If your subscription business is selling into several markets, it is worth fixing the workflow early. You can start that review through Corpenza's contact page.
Frequently asked questions
Is SaaS always a digital service?
Often yes, but heavy manual onboarding, custom consulting, or project-based human work can create separate supplies that need their own tax analysis.
Do I need separate VAT registrations in every EU country?
Not always. OSS can centralize reporting for eligible B2C sales, but you still apply the customer's country rate and keep usable evidence.
Is there a UK threshold for overseas digital services?
HMRC's guidance says overseas businesses supplying digital services to UK consumers may need UK VAT registration, so this should be checked before you assume there is a comfortable buffer.
What is the New Zealand GST threshold?
Inland Revenue's current page says GST registration is required once supplies to New Zealand customers were or are expected to be NZ$60,000 or more in a 12-month period.
Does the marketplace always leave the tax burden with the seller?
No. In some marketplace structures the platform becomes responsible for VAT accounting, so app stores, aggregators, and direct billing should never be treated as identical.
Corpenza helps founders align checkout data, invoicing rules, country thresholds, and reporting logic before digital revenue starts leaking into tax clean-up work. If you want that mapped properly, start with tax optimization or the contact page.
This is general information, not legal or tax advice; rules change and the answer depends on your facts.
