What Is Double Taxation? A Guide for Global SaaS and Digital Businesses
Published on: Sun 30-Aug-2026 05:59 AM
In its technical sense, double taxation occurs when the same income is taxed twice by two jurisdictions, on the same taxpayer, for the same period. But for a software or digital business selling across borders, the day-to-day challenge is usually broader than that narrow definition. It is the accumulation of overlapping tax obligations on the same commercial activity – consumption tax in one country, income tax at home, withholding tax on a payment, a digital levy somewhere else – only some of which qualify as true double taxation.
That distinction is not academic. Getting it wrong can lead a business to pursue the wrong type of tax relief such as relying on a treaty for a problem that treaties do not solve or underestimate obligations it actually has. These two issues need to be addressed in different parts of the business: income-tax exposure is primarily a tax-planning question, while transaction-level obligations also require the right billing and payments infrastructure.
This guide explains what double taxation actually is, how it differs from the overlapping obligations digital sellers routinely face, how those obligations work in India, the United States, and other major markets, and the practical steps that can reduce your exposure without slowing your expansion.
Who this is for: CEOs, founders, and finance leaders planning or scaling international sales of SaaS, digital products, or online services. This is an educational guide, not tax advice – confirm specifics with a qualified adviser in each market.
The stakes: demand is up, and so is the compliance drag
The opportunity is enormous. According to research published by tax-compliance firm Avalara, global business-to-business e-commerce is forecast to climb from roughly $32.1 trillion in 2025 to $62.2 trillion by 2030, while global business-to-consumer e-commerce is projected to reach about $16.83 trillion by 2030.
The friction is just as real. In the same research – a survey of more than 900 executives across 17 countries – nearly half (46%) of companies in the $100–500 million revenue band described the international e-commerce environment as "difficult," with much of that difficulty tracing back to the cost and complexity of tax and regulatory compliance.
Understanding exactly which taxes apply and which are genuinely "double" is the difference between expansion that compounds and expansion that leaks margin at every border.
What is double taxation?
Double taxation occurs when comparable taxes are imposed on the same taxpayer's income by two jurisdictions for the same period. For global SaaS businesses, though, tax complexity is broader than that: VAT, GST, sales tax, withholding tax, and digital levies can create overlapping obligations that are not technically double taxation. Telling the two apart is the key to knowing how to respond.
Tax bodies recognise two forms of genuine double taxation:
Juridical double taxation. The OECD, whose Model Tax Convention underpins most of the world's tax treaties, defines international juridical double taxation as comparable taxes imposed in two or more states on the same taxpayer, in respect of the same subject matter, for identical periods. One company, one slice of income, taxed by two countries.
Economic double taxation. In United Nations treaty guidance, this is where the same income is taxed in two countries but treated as belonging to different taxpayers – for example, corporate profit taxed at the company level and again when distributed to shareholders.
Both are about income taxes which is exactly where digital businesses need to be careful.
Is VAT or GST double taxation? Understanding tax overlap
Generally, no. VAT, GST, and sales tax are consumption taxes imposed on transactions, while corporate income tax is imposed on profits. A business can face both on the same commercial activity, but because they are different taxes on different bases, that usually isn't technical double taxation. It's an overlapping obligation. This is the distinction that makes this guide more accurate than most competing content, and one a tax specialist would insist on.
Framed cleanly:
Technical (juridical) double taxation
- Same income
- Same taxpayer
- Two jurisdictions
- Comparable income taxes
Overlapping tax obligations
- Consumption tax (VAT / GST / sales tax) on the transaction
- Corporate income tax on the profit
- Withholding tax on certain payments
- Digital services or gross-revenue taxes in some jurisdictions
Different taxes, different bases, layered onto the same activity – real cost and complexity, but not, in most cases, technically double taxation. Income-tax treaties generally do not provide relief from VAT, GST, or sales taxes, so treating a consumption-tax obligation as "double taxation" points you at the wrong remedy.
Is it technically double taxation?
Situation | Technically double taxation? |
The same income taxed by two countries | Potentially yes (the juridical case) |
Corporate income tax + VAT/GST on the same sale | Generally no – different taxes, different bases |
Corporate income tax + US sales tax on the same sale | Generally no – different taxes, different bases |
Withholding tax + corporate income tax on the same income | Potentially – depends on treaty and foreign-tax-credit treatment |
A digital services tax (DST) + corporate income tax | Depends on the jurisdiction and available relief |
Two different problems, two different fixes
Income-tax side | Indirect / transaction side | |
What's taxed | Your profit / earnings | The individual sale or subscription |
Examples | Corporate tax, withholding tax (TDS) | VAT, GST, US sales tax, DSTs |
True double taxation risk? | Yes, this is where it genuinely arises | Rarely, usually overlapping obligations |
Who fixes it | Tax treaties (DTAAs), foreign tax credits, structuring | Correct registration, place-of-supply logic, collection at the point of sale |
Whose desk it lands on | Your tax adviser / CFO | Your billing, payments, and operations stack |
Key insight
Income-tax double taxation is a planning problem – solved with advisers, treaties, and structure. Overlapping indirect-tax obligations are an infrastructure problem – solved in the system that processes the sale, determines the customer's location, and collects the right tax at the right moment. Founders who treat both as "call the accountant" problems consistently overpay and under-comply on the transaction side.
The transaction side is an infrastructure problem. Solve it like one.
Place-of-supply logic, B2B/B2C classification, and tax collection can live inside your payment flow — not your quarter-end scramble.
Why digital businesses face this more than anyone
A physical exporter has a clear taxable moment – goods cross a border and clear customs. Digital businesses don't. Software crosses no customs post, so "place of supply" becomes a legal construction that each jurisdiction defines differently. That produces overlapping obligations from several directions on the same sale.
Three routes, specifically:
Two countries may both claim your income. You're taxed where you're resident, but the country where your customer sits may also assert a right to tax income arising there – through withholding tax, an economic-presence test, or a permanent-establishment argument. This is where genuine double taxation can occur.
Consumption tax layers on top of income tax. A single subscription can attract VAT, GST, or sales tax in the buyer's jurisdiction and form part of taxable income at home. Different taxes – so no treaty offsets one against the other.
Unilateral digital levies sit outside the treaty system. Some countries taxed digital revenue through levies placed outside their income-tax codes – deliberately beyond treaty relief.
A quick scenario
A SaaS company in Bengaluru sells a $50/month analytics tool. A customer in Germany subscribes, another in Texas, and a third – an unregistered small business – in Mumbai. The German B2C sale generally attracts EU VAT at the customer's local rate; the Texas sale depends on economic nexus and whether Texas taxes SaaS; the Mumbai sale falls under Indian GST rules. Three sales, three tax systems, three answers and none is resolved by an income-tax treaty, because none is income tax.
How it plays out in India, the US, and other markets
The mechanics differ enough by market that no single global rule works. India runs on GST/OIDAR, the US on a state-by-state sales-tax patchwork, and the EU on customer-location VAT. Below is a current-state summary to confirm against the primary sources cited – not settled advice, since these rules change frequently.
India: what SaaS businesses need to know
In India, many automated digital services fall under the OIDAR regime and attract 18% GST, with the collection mechanism depending on whether the customer is a business or a consumer. Here's the breakdown.
1. GST / OIDAR
Many SaaS and automated digital products fall under OIDAR – Online Information and Database Access or Retrieval services, defined under Section 2(17) of the IGST Act, 2017 as internet-delivered services that are essentially automated with minimal human intervention.
Classification isn't automatic: it turns on how automated delivery is, and services with substantial human input can fall outside OIDAR and follow ordinary import-of-service rules. Cloud, streaming, downloadable software, and standardized SaaS are the typical OIDAR cases.
The rate is generally 18% IGST, and the place of supply is the location of the recipient (Section 13(12)). (Under the "GST 2.0" rationalisation effective 22 September 2025, slabs were simplified to broadly 5% / 18% / 40%, with most digital services staying at 18%.)
2. B2B vs. B2C
For B2C (unregistered Indian recipients), a foreign provider must register regardless of turnover (Section 24, CGST Act), via Form GST REG-10, and file GSTR-5A monthly. The Finance Act, 2023 (via CBIC Notifications 28/2023 and 51/2023-Central Tax, effective 1 October 2023) broadened "non-taxable online recipient" to include any unregistered recipient regardless of purpose – widening the B2C net.
For B2B (a GST-registered Indian business), GST is generally payable by the recipient under the reverse charge mechanism – the common treatment, not a universal SaaS rule, and dependent on correct classification and the recipient's status.
3. Withholding tax (TDS)
Separately, cross-border payments for software and services can attract withholding tax in India, depending on how the payment is characterised (royalty vs. business profits) and what the applicable treaty allows. This is an income-tax question – and one a DTAA can reduce or eliminate.
4. Equalisation levy – historical context
India's now-abolished equalisation levy is a useful illustration. The 2% e-commerce levy was withdrawn from 1 August 2024 and the 6% advertising levy abolished from 1 April 2025 (Finance Act, 2025).
Because it sat outside the Income Tax Act, it was not creditable under India's tax treaties – so it created genuine, unrelievable double taxation for non-residents while it existed. The lasting lesson outlives the levy: a tax being charged on digital revenue does not automatically mean treaty-based income-tax relief is available.
United States: no VAT, a sales-tax patchwork, and the Wayfair line
The US has no federal VAT or GST; consumption tax is set state by state, and whether you must collect it turns on "economic nexus." Since the Supreme Court's 2018 decision in South Dakota v. Wayfair (Docket 17-494), a state can require you to collect sales tax based on economic activity alone – no physical presence needed.
Thresholds vary by state. Many states use a sales threshold around $100,000, but dollar amounts, transaction-count tests, measurement periods, and taxable-product rules all differ. The 200-transaction test several states first adopted has since been dropped or modified in a number of them – so treat "$100,000 or 200 transactions" as a common historical example, not a current national standard, and verify each state's current rule before relying on it.
Is SaaS even taxable? This varies significantly by state – some tax SaaS, many don't, and several have changed over time. Two identical sales into neighbouring states can produce opposite outcomes.
The exposure. A non-US seller can find the same revenue in its home income-tax base and subject to US state sales-tax collection – different taxes, no treaty bridge.
European Union: customer location, B2B/B2C, and the One Stop Shop
For B2C electronically supplied services, EU VAT follows the customer's location – so the practical chain is: identify the customer's country, determine B2B or B2C, then let the One Stop Shop simplify filing. That sequence matters more than the fact that each member state sets its own rate.
Customer location drives the obligation. A B2C digital sale is taxed where the customer is, at that country's rate, regardless of where the seller sits.
B2B is different. B2B supplies generally use the reverse charge, with the business customer accounting for VAT – provided you validate their VAT number.
OSS simplifies filing. Since 1 July 2021, the One Stop Shop lets a business file a single quarterly return for B2C sales across the EU; a non-EU seller can use the Non-Union scheme, registering in just one member state. (EU-established micro-sellers get a €10,000 threshold; non-EU sellers generally charge from the first sale.)
Other global developments
Some countries levy digital services taxes (DSTs) on large digital firms; because these usually sit outside income-tax treaties, they carry the same "no relief" property the Indian levy did, though they target only the largest players and their future is politically contested. Separately, the OECD's Pillar Two sets a 15% global minimum tax on groups above €750 million in revenue – out of scope for most digital businesses, but a clear signal that taxing rights are shifting toward where the customer is.
Cross-market comparison
India | United States | European Union | |
Consumption tax | GST (IGST on cross-border) | State/local sales tax (no federal VAT) | VAT |
Rate on digital services | 18% | Varies by state | Varies by member state |
What triggers it | Supplying OIDAR to India; B2C = mandatory registration | Economic nexus (varies; often ~$100k) | Selling to an EU customer (place of supply = customer) |
B2B mechanism | Reverse charge on registered Indian recipient | Buyer's use-tax / exemption certificates | Reverse charge on EU business customer |
Simplified filing | Simplified registration + GSTR-5A | None – register state by state | One Stop Shop (Non-Union scheme for non-EU) |
Income-tax treaty relief? | Yes for income tax/TDS; no for GST | No treaty for state sales tax | No treaty for VAT |
How the framework applies: three SaaS scenarios
To make it concrete, here's the same framework applied to three common cross-border SaaS flows, keeping the transaction tax and the income tax as separate questions.
Indian SaaS → US business customer. The transaction question is US state sales tax, owed only where the company has crossed a state's nexus threshold and that state taxes SaaS; there's no VAT.
Profit is taxed as income in India, with the India–US treaty governing any US income-tax exposure (which generally arises only with a US trade/business or permanent establishment). Sales tax plus Indian income tax is overlapping obligations, not double taxation. Payment settles in USD, so FX conversion affects what lands in INR.
US SaaS → Indian customer. The transaction question is Indian GST/OIDAR: a B2C sale to an unregistered Indian consumer means the US provider must register and charge 18% IGST; a B2B sale to a GST-registered business shifts to reverse charge.
Payments may also attract Indian withholding tax (TDS) depending on royalty-vs-business-profits characterisation – and this income-side overlap with US income tax is where genuine double taxation can arise, relieved by the treaty and foreign tax credits. Profit is taxed as income in the US.
Global SaaS → EU customer. The transaction question is VAT at the customer's location – charged and filed via OSS (Non-Union scheme for a non-EU seller) for B2C, or handled by reverse charge for validated B2B customers. Profit is taxed as income at home. VAT plus home-country income tax is overlapping obligations, not double taxation.
What this means for your margin
A $100 subscription doesn't necessarily mean $100 of revenue reaches the business. Depending on the customer's location and transaction structure, consumption tax may be collected from the customer, withholding tax may reduce the remittance, and payment and FX costs may affect settlement. Crucially, not all of these are double taxation – consumption tax and payment costs are separate from income tax, and only the income-side overlap (e.g., withholding vs. home-country tax) is a candidate for treaty relief.
How to reduce your exposure
Split the problem in two – the whole point of the framework above – and use the right tool for each side. Treaties and credits handle the income side; correct registration and point-of-sale collection handle the transaction side.
On the income-tax side (the treaty toolkit)
Use the relevant tax treaty (DTAA). Treaties allocate taxing rights and typically cap or remove withholding tax on cross-border payments. Rates and definitions differ by corridor – check each.
Claim foreign tax credits. Where tax is correctly paid at source, your home country will often allow a credit, preventing the same income being fully taxed twice.
Understand permanent establishment (PE). Selling into a country is usually fine; people, servers, or a fixed place of business there can create a taxable presence.
Get the characterisation right. Whether a payment is "royalty," "fees for technical services," or "business profits" changes the outcome – where specialist advice pays for itself.
On the indirect / transaction side (the operations toolkit)
Determine the place of supply correctly, every time. Accurate, corroborated customer-location evidence decides which country's tax applies.
Classify B2B vs. B2C reliably. Reverse charge only works if you validate the customer's tax status (a GSTIN in India, a VAT number in the EU).
Register where required – and use simplified schemes. The EU's OSS and India's simplified OIDAR registration exist to reduce the multi-jurisdiction burden.
Collect and remit at the point of sale. Consumption tax is best handled as the sale happens, not reconstructed at quarter-end.
A quick decision framework
Ask, in order:
Is the tax on my profit or on the sale? → income-tax side vs. transaction side.
If on profit: is there a treaty for this corridor, and does a credit apply?
If on the sale: where is the customer, are they B2B or B2C, and have I crossed a registration/nexus threshold there?
Can a simplified regime (OSS, simplified GST registration) or a Merchant-of-Record model carry the obligation for me?
Global SaaS tax compliance checklist before entering a new market
- Is the revenue subject to local indirect tax (VAT/GST/sales tax)?
- Is registration required and from which sale or threshold?
- Is this type of SaaS/digital product taxable in that jurisdiction?
- Does a B2B reverse charge apply, and can we validate customer tax status?
- Is withholding tax applicable to inbound payments?
- Does an income-tax treaty (DTAA) apply to this corridor?
- Can foreign tax credits be claimed for tax paid at source?
- Could local activity (people, servers, presence) create a permanent establishment?
- Who is contractually responsible for collecting and remitting transaction taxes?
- Do we register directly, or use a Merchant of Record?
Entering a new market? Don't rebuild compliance each time.
Let a Merchant-of-Record model carry the registrations, collection, and evidence trail for you.
Where payment infrastructure fits
Most of the transaction-side workflow – determining place of supply, classifying B2B vs. B2C, calculating the tax, collecting it, and keeping the evidence trail – is tied to how the payment is processed. That's why a Merchant of Record (MoR) model can carry much of this burden instead of your team rebuilding it market by market.
Under an MoR arrangement, the provider becomes the legal seller of record, and depending on the jurisdiction and contract, the collection and remittance obligations – plus the registrations and evidence behind them – shift from you to them. Fragmented obligations collapse into a single relationship.
What an MoR won't do: resolve corporate income tax, permanent establishment, transfer pricing, treaty eligibility, or withholding-tax characterisation – those stay with your adviser. And exactly which obligations it does assume depends on the contract, the jurisdiction, and the specific tax.
This is what Transact Bridge is built for. It processes cross-border sales through a single layer engineered for local requirements from the first transaction, across India, the US, and global markets, with support for 100+ local and global payment methods – while the income-tax and structuring questions stay, correctly, with your advisers.
The Final Takeaway
Double taxation isn't simply a matter of being taxed twice. For global digital businesses, the sharper challenge is telling apart the taxes that fall on income – where genuine double taxation arises, and where treaties and credits are the answer – from the overlapping obligations that fall on each transaction, where VAT, GST, and sales tax live and treaties don't help. Name which is which, and every market-entry decision gets clearer.
As you expand across India, the US, and other markets, that transaction-side question becomes inseparable from the payment infrastructure processing each sale – which is why more digital businesses now solve it at the payments layer rather than one registration at a time.
FAQs
What is double taxation in simple terms?
Double taxation is when the same income is taxed twice – by two different countries, on the same taxpayer, for the same period. It commonly affects cross-border businesses, where profit earned in one country can be taxed both there and at home. Different taxes on the same sale, such as VAT plus income tax, are usually not true double taxation.
Can SaaS companies be taxed in two countries?
Yes, SaaS companies often owe tax in more than one country, but usually as different taxes rather than the same tax twice. A subscription can attract consumption tax (VAT, GST, or sales tax) in the customer's country while the revenue is also taxed as income at home. Because these are different taxes, that's overlapping obligations, not technical double taxation.
Is VAT or GST considered double taxation?
Generally, no. VAT and GST are consumption taxes charged on a transaction, while income tax is charged on profit – different taxes on different bases. A business can face both on the same sale without it being double taxation. True double taxation means comparable income taxes imposed on the same taxpayer, for the same income, by two jurisdictions.
Can withholding tax result in double taxation?
Yes, potentially. If one country withholds tax on a cross-border payment and the recipient's home country also taxes that same income, the income is taxed twice. Tax treaties (DTAAs) and foreign tax credits usually provide relief – though the outcome depends on how the payment is characterised and which treaty applies.
Does a Double Taxation Avoidance Agreement (DTAA) protect my digital sales?
A DTAA protects you from the same income being taxed by two countries and can reduce or remove withholding tax on cross-border payments. It does not cover consumption tax – VAT, GST, and sales tax fall outside the treaty system, so those must be handled operationally through correct registration and tax collection, not treaty relief.
How are digital services taxed differently in India, the US, and the EU?
Each market taxes them differently. India applies 18% GST to most digital (OIDAR) services, with foreign B2C providers required to register. The US has no federal VAT – sales tax is set state by state, triggered by economic nexus, and SaaS is taxable in some states but not others. The EU taxes B2C digital services at the customer's local VAT rate, simplified through the One Stop Shop.
How can a digital business avoid double taxation?
"Avoid" here means legally preventing duplicate taxation, not evading tax. Split it in two: for income tax, use the relevant tax treaty, claim foreign tax credits, and manage your permanent-establishment position. For consumption tax (VAT, GST, sales tax), register where required, apply the correct place-of-supply rules, and collect tax at the point of sale – often handled most efficiently through a Merchant of Record.
How does a Merchant of Record handle tax across markets?
A Merchant of Record becomes the legal seller for each transaction, so it can collect and remit consumption taxes (VAT, GST, sales tax) in the markets where it's registered – the exact scope depending on jurisdiction and contract. Transact Bridge operates payment infrastructure on this model, letting a digital business shift much of its transaction-level tax burden onto the payment layer, while income-tax and structuring questions stay with its advisers.