# Digital Services Tax (DST): A Global Guide for SaaS Sellers

> Digital services tax explained - which countries charge DST, how rates and thresholds differ, and what SaaS sellers need to do to comply across multiple jurisdictions.
- **Author**: Aarthi Poonia
- **Published**: 2026-05-30
- **Category**: Tax, Compliance, SaaS
- **URL**: https://dodopayments.com/blogs/digital-services-tax-global-guide

---

Digital services tax (DST) is a new category of tax that targets the gross revenue large digital businesses earn from users in a country, regardless of whether the business has any physical presence there. It emerged from frustration that traditional corporate income tax rules - based on physical nexus - let global tech companies earn billions in a market while paying minimal tax in that market.

Over the last six years, more than two dozen countries have introduced DSTs or DST-equivalent levies. Rates range from 1.5% to 7.5%. Thresholds vary from $5 million to $750 million in global revenue. Scope varies from advertising revenue only to all digital service revenue. And several major holdouts (most notably the United States, until very recently) have opposed DSTs as discriminatory against US tech companies, creating ongoing political tension.

For SaaS sellers, this matters because DST liability can hit any business serving customers in a DST-enacting country, even if the business has no physical operations there. The compliance overhead is non-trivial, and the penalties for non-compliance are substantial. This guide walks through which countries charge DST, how the rates and thresholds work, and what SaaS sellers need to do to comply.

## What Digital Services Tax Actually Taxes

DST is structured as a tax on gross revenue, not net income. This is the most important conceptual point. Traditional corporate income tax is based on profit (revenue minus deductible expenses) and is paid in the country where the company has nexus. DST is based on gross revenue earned from users in a country, paid regardless of profitability.

The scope of "digital services revenue" varies by country but typically includes:

- Online advertising revenue (the largest DST scope component)
- Marketplace revenue (platform fees on third-party sellers)
- Sale of user data
- Subscription revenue from digital services delivered to local users (in some countries)
- Streaming and digital content revenue (in some countries)

Most DSTs were designed to capture Google, Meta, Amazon, and similar large platforms. But the legislative definitions are typically broad enough to potentially capture SaaS, especially if a SaaS business hits revenue thresholds and earns meaningful revenue from local users.

## Countries With Active DST Regimes

As of 2026, the following countries have implemented or announced DSTs:

| Country | Rate | Threshold | Scope |
| --- | --- | --- | --- |
| France | 3% | Global revenue EUR 750M / France EUR 25M | Online advertising, intermediation services |
| United Kingdom | 2% | Global revenue GBP 500M / UK GBP 25M | Search engines, social media, marketplaces |
| Italy | 3% | Global revenue EUR 750M / Italy EUR 5.5M | Online advertising, digital interface services |
| Spain | 3% | Global revenue EUR 750M / Spain EUR 3M | Online ads, intermediation, data transmission |
| Austria | 5% | Global revenue EUR 750M / Austria EUR 25M | Online advertising only |
| Turkey | 7.5% | Global revenue EUR 750M / Turkey TRY 20M | Broad digital services |
| India | 6% (Equalisation Levy on online advertising, still active); the broader 2% Equalisation Levy on non-resident e-commerce operators was repealed effective August 2024 | None | The 6% levy applies to payments to non-resident online advertising providers; the repealed 2% levy previously covered online sale of goods and services to Indian residents |
| Canada | 3% | Global revenue CAD$1.1B / Canada CAD$20M | Online marketplaces, social media, advertising, user data |
| Kenya | 1.5% | None (applies to all digital service providers) | Broad digital services |

This list is not exhaustive and changes frequently. Several other countries (Brazil, Indonesia, Pakistan, Tanzania, Tunisia) have announced or partially implemented DST-like regimes. The OECD has been working on a multilateral framework (Pillar One) to replace unilateral DSTs, but that framework has not yet been fully implemented, so individual countries continue to enforce their own.

For more on specific jurisdictions, see our [EU digital services tax post](https://dodopayments.com/blogs/eu-digital-services-tax) and the [Canada DST post](https://dodopayments.com/blogs/canada-digital-services-tax-saas).

## DST vs VAT vs Sales Tax: The Differences That Matter

Founders frequently confuse DST with VAT or sales tax. They are structurally different.

**VAT (value-added tax)** and sales tax are consumption taxes. They are charged on the customer (usually shown as a separate line on the invoice) and remitted by the seller to the tax authority. The customer ultimately bears the cost; the seller is just the collector. VAT and sales tax apply to a much broader range of goods and services than DST.

**DST** is a revenue tax on the seller. It is not charged to the customer separately - it is a tax the seller pays out of its own revenue. The customer's invoice does not (typically) show DST as a line item. DST applies only to specifically scoped digital services and only to businesses above the revenue thresholds.

**Corporate income tax** is paid on net profit and requires "nexus" - a physical or legal connection to the country. DST was specifically designed to apply without traditional nexus, capturing revenue from large foreign businesses that had no local entity.

A SaaS business selling into the UK can simultaneously owe:

- UK VAT on the subscription (charged to the customer, remitted to HMRC)
- UK DST on the gross subscription revenue if the business exceeds DST thresholds (paid by the business out of revenue)
- UK corporate income tax on the net profit attributable to UK operations if the business has UK nexus

The three taxes do not offset each other and are owed independently.

## Who DST Applies To

DST regimes are designed to target large multinationals, not small SaaS startups. The global revenue threshold (typically EUR 750M or higher) explicitly excludes most early-stage and growth-stage SaaS. A SaaS company doing $10M ARR is not going to owe DST anywhere - it is well below every threshold.

However, several caveats matter:

**The thresholds apply to consolidated group revenue, not single-entity revenue.** A SaaS that is part of a larger corporate group (parent company, subsidiaries, sister companies) needs to look at total group revenue, not just its own. A small SaaS owned by a large conglomerate could exceed thresholds.

**Some DSTs have lower thresholds for specific scopes.** Kenya's 1.5% DST applies to all digital service providers regardless of size. India's 6% Equalisation Levy on online advertising applies to any non-resident provider receiving advertising revenue from Indian advertisers, regardless of size. (India's broader 2% Equalisation Levy on non-resident e-commerce operators was repealed in August 2024.)

**Thresholds vary year-to-year as countries adjust.** What is a $750M threshold today may be lower next year. Tracking is required for any SaaS that is growing toward DST-relevant revenue levels.

**The OECD Pillar One framework, if implemented, will lower the threshold significantly.** Pillar One targets multinationals with EUR 20B in global revenue but with proposed phase-down to EUR 10B. Lower thresholds increase the population of affected businesses.

For most SaaS founders today, DST is not an immediate compliance concern. But it is worth understanding the framework because thresholds tend to fall over time and the scope tends to expand.

## How DST Is Calculated and Remitted

For SaaS businesses that do hit DST thresholds, the calculation typically works as follows:

1. Identify revenue earned from users located in the DST country during the period (usually a calendar quarter or year)
2. Apply the DST rate to that gross revenue
3. Subtract any allowable deductions (rare; most DSTs have no deductions)
4. Remit the resulting tax via the country's tax authority

The hard part is step 1. "Revenue earned from users located in the DST country" is harder to calculate than it sounds. Different countries use different rules:

- Some use the user's IP address at time of transaction
- Some use the user's billing address
- Some use the user's bank or payment method country
- Some use the user's declared country in their account settings

For SaaS that does not collect this information rigorously, retrofitting attribution can be expensive. Mature compliance setups capture multiple location signals at signup and bill processing time so that DST attribution can be calculated correctly.

The remittance frequency also varies. France, Italy, and Spain require annual filings. The UK requires payment within 9 months of the relevant accounting period end. Turkey requires monthly returns. India's remaining 6% advertising Equalisation Levy requires quarterly returns. Tracking the calendar for each jurisdiction is part of the operational overhead.

## The Cost of DST Beyond the Headline Rate

For a business that earns $50M in revenue from a 3% DST country, the headline DST cost is $1.5M per year. But the true cost includes:

- **Compliance staffing**: Most companies above DST thresholds have dedicated tax counsel and compliance staff for each affected jurisdiction. This is $200K-$500K per year for a multi-jurisdiction operation
- **Software and tooling**: Specialized DST tracking software, geographic attribution analysis, and accounting integrations add $50K-$200K per year
- **Audit risk**: DST audits, where they occur, can take months and require significant management time. Penalties for under-remittance range from 10-50% of the under-remitted amount
- **Legal advice**: Most DSTs have complex scoping questions (what counts as "digital services," what counts as "user location," how to handle bundled offerings) that require ongoing legal review

For SaaS just crossing the threshold, the per-unit cost of compliance is highest because the dedicated headcount and tooling have to be put in place regardless of how much DST is actually owed. The marginal cost of additional DST liability drops sharply once the compliance infrastructure is in place.

A theme we see consistently at Dodo Payments: tax compliance is one of the problems that scales painfully across borders. Each new country adds not just the headline rate but the operational machinery to compute it correctly, file it on time, and defend it under audit. The companies that handle this well are the ones that built the infrastructure - or hand it off to an MoR - before they needed it.

## How the Merchant of Record Model Affects DST Exposure

A [Merchant of Record](https://dodopayments.com/blogs/what-is-a-merchant-of-record) is the named legal seller on transactions. From a tax perspective, this means the MoR - not the underlying SaaS business - is the entity that potentially has DST exposure on transactions it processes.

For most early-stage and mid-market SaaS, this is irrelevant because they would not hit DST thresholds anyway. But for SaaS that operates through an MoR and is approaching DST scale, the MoR structure can substantially simplify the compliance picture:

- The MoR is the named seller in the customer-facing transaction
- The MoR holds the tax registrations and remittance infrastructure
- The MoR's relationship with the underlying SaaS business is typically structured as a service contract, not as a digital service sale to the SaaS business's end users
- The DST exposure of the underlying SaaS business depends on its direct relationship to the end user, which through an MoR may be limited

This is not blanket protection from DST. The specifics depend on the structure of the MoR relationship, the contractual terms, and the country's interpretation of who is the relevant taxpayer. But for SaaS using a Merchant of Record like [Dodo Payments](https://dodopayments.com), the DST compliance complexity is generally lower than for SaaS that sells direct to end users in DST countries.

For our broader treatment of cross-border tax topics, see [global VAT/GST for AI SaaS](https://dodopayments.com/blogs/global-vat-gst-ai-saas) and the [EU VAT SaaS guide](https://dodopayments.com/blogs/eu-vat-saas-guide-2026).

## Recent and Upcoming Changes Worth Tracking

The DST landscape is changing rapidly. Recent and upcoming changes that SaaS founders should know about:

**OECD Pillar One**. The OECD's two-pillar framework was designed to replace unilateral DSTs with a multilateral approach. Pillar One reallocates a portion of large multinationals' profit to market countries based on where users are. As of 2026, Pillar One is partially implemented but has not yet displaced national DSTs in most jurisdictions. Countries have committed to repealing DSTs once Pillar One is fully implemented, but timing is uncertain.

**Canada DST**. Canada implemented its 3% DST in 2024 with retroactive effect to 2022. The retroactivity caused significant political tension with the United States, which threatened tariffs in response. In late 2025, Canada paused enforcement pending negotiations.

**EU Digital Levy proposals**. The EU has been considering an EU-wide digital levy as an alternative to country-by-country DSTs. As of 2026, this has not been enacted but periodic proposals continue.

**India Equalisation Levy contraction**. India repealed the 2% Equalisation Levy on non-resident e-commerce operators effective August 2024, leaving only the 6% levy on online advertising in force. The broader policy direction has shifted toward handling cross-border digital taxation through the GST regime and the OECD Pillar One framework rather than expanding the Equalisation Levy.

**Turkey DST escalation**. Turkey's 7.5% DST is the highest in the world. The country has signaled willingness to raise it further if the OECD Pillar One framework does not deliver expected revenue.

For SaaS approaching DST relevance, working with international tax counsel is essential. The rules change frequently and the penalties for non-compliance are substantial.

## FAQ

### What is digital services tax?

Digital services tax (DST) is a tax on the gross revenue large digital businesses earn from users in a country, regardless of whether the business has physical operations there. Rates typically range from 1.5% to 7.5%. DST applies to specifically scoped revenue (online advertising, marketplace fees, digital services) and only to businesses above thresholds, usually EUR 750 million in global revenue.

### Which countries have digital services tax?

As of 2026, France, United Kingdom, Italy, Spain, Austria, Turkey, India, Canada, and Kenya have active DST or DST-equivalent regimes. Several other countries have announced or are considering DSTs. The OECD Pillar One framework is designed to eventually replace national DSTs with a coordinated multilateral approach, but as of 2026 this has not happened.

### Does DST apply to SaaS companies?

Most SaaS companies do not owe DST because they fall below the revenue thresholds (typically EUR 750M global revenue). Only large multinational SaaS businesses face DST exposure. The scope and thresholds vary by country, and tracking is important for SaaS approaching the relevant revenue levels.

### How is DST different from VAT or sales tax?

DST is a revenue tax paid by the seller on its own revenue. VAT and sales tax are consumption taxes charged to the customer and remitted by the seller. DST applies only to specifically scoped digital services and only to businesses above thresholds. VAT and sales tax apply to a much broader range of goods and services with no minimum threshold for most products.

### When will the OECD Pillar One replace national DSTs?

The OECD Pillar One framework was originally targeted for full implementation by 2024 but has been delayed multiple times. As of 2026, Pillar One is partially in place but has not displaced national DSTs in most jurisdictions. Countries have committed to repealing their DSTs once Pillar One is fully effective, but the timing remains uncertain.

## Conclusion

Digital services tax represents a significant shift in how countries tax digital businesses. By taxing gross revenue rather than profit, and by applying without traditional nexus requirements, DST captures revenue from foreign businesses that would otherwise pay minimal tax in the local market. For SaaS founders, DST is not yet an immediate compliance concern because most SaaS businesses fall below the thresholds. But the trajectory matters: thresholds tend to fall, scope tends to expand, and more countries adopt DSTs each year.

For SaaS approaching DST scale, building the right compliance infrastructure early is far cheaper than retrofitting it under audit pressure. For SaaS operating through a Merchant of Record like [Dodo Payments](https://dodopayments.com), the DST exposure is typically simplified because the MoR is the named seller and handles related tax infrastructure on behalf of the underlying business.

Read the [EU digital services tax guide](https://dodopayments.com/blogs/eu-digital-services-tax) and [Canada DST analysis](https://dodopayments.com/blogs/canada-digital-services-tax-saas) for jurisdiction-specific detail, or compare the MoR cost structure on the [Dodo Payments pricing page](https://dodopayments.com/pricing).
---
- [More Tax articles](https://dodopayments.com/blogs/category/tax)
- [All articles](https://dodopayments.com/blogs)