Home/Research library/Compliance Slows Launches

Guide · Tax and invoicing

Digital Services Taxes

Digital Services Taxes Explained: What International Digital Businesses Need to Know Two tax questions can sound almost identical while asking about entirely different liabilities: What VAT applies to this customer's digital purchase? and: Does this digital business fall within a

Source-imported researchEditorial verification pending

Research draft awaiting independent review. This material was adapted from an existing research library. Provider-specific promotions have been excluded automatically; facts, regulatory requirements, and conclusions must be verified before the page is indexed publicly.

Digital Services Taxes Explained: What International Digital Businesses Need to Know

Two tax questions can sound almost identical while asking about entirely different liabilities:

What VAT applies to this customer's digital purchase?

and:

Does this digital business fall within a country's Digital Services Tax regime?

The first is generally a transaction-level indirect-tax question about a supply to a customer. The second may concern a separate tax imposed on specified categories of digital-business revenue, often subject to substantial global, group-level, and domestic revenue thresholds.

Confusing them can create the wrong tax model before a market even launches.

A Digital Services Tax, or DST, is generally a jurisdiction-specific tax targeting revenue from defined digital activities such as online intermediation, search, social media, targeted advertising, or user-data-related services. It is not another name for VAT or GST on digital products.

Even that definition needs qualification. Countries do not use one standardized DST model. Covered activities, taxpayer definitions, revenue attribution rules, thresholds, rates, filing mechanics, and even the legal characterization of the tax differ. The article brief therefore correctly treats country status, rates, thresholds, suspensions, repeals, and transitions as immediately date-sensitive.

For an international digital business, the practical starting point is not:

“Do we sell something digital?”

It is:

“Does this jurisdiction currently operate a DST-type regime, and does our specific revenue-producing activity fall within it?”

What is a Digital Services Tax?

Digital Services Tax is a label used for taxes designed to capture specified digital activity or revenue that a jurisdiction considers sufficiently connected with users or economic activity in that market.

A typical DST differs from ordinary corporate income tax because it can be calculated by reference to gross revenue from specified digital services rather than net taxable profit. The OECD's 2026 commentary on the global minimum-tax rules describes digital services taxes as generally applying to gross revenues from certain digital services and says they generally are not treated as income taxes for purposes of the GloBE Covered Tax definition.

But there is no universal legal classification. Spain, for example, expressly characterizes its Impuesto sobre Determinados Servicios Digitales as an indirect tax, even though its base is qualifying digital-services revenue rather than a conventional VAT-style charge on each consumer purchase.

That is an important editorial and tax distinction:

“Revenue-based” does not automatically mean every country's DST is legally classified as a direct tax.

Businesses should use the local statutory classification rather than force every DST into one tax-law category.

DST is not VAT or GST on digital services

The name creates the confusion.

A company sells a €20 digital subscription to a consumer. The transaction may be subject to VAT under the applicable place-of-supply, customer-status, registration, and rate rules.

Separately, the company or corporate group might need to determine whether revenue generated by a particular digital-business activity contributes to a DST calculation.

Those are different questions.

Under the EU VAT framework, VAT is applied to taxable transactions such as supplies of goods and services, with the taxable amount generally based on the consideration received for the supply.

DST regimes can instead focus on specified revenue streams and apply only once much larger business or group thresholds have been exceeded.

DST vs VAT: the practical distinction

Dimension

Digital Services Tax

VAT/GST on digital services

Main question

Is this business or group earning revenue from an activity covered by the jurisdiction's DST?

Is this particular supply subject to VAT/GST?

Typical tax base

Defined digital-business revenue, depending on local law

Consideration for a taxable supply

Level of analysis

Often business/group + local attributable revenue

Individual transactions/supplies

Thresholds

Can include substantial global/group and domestic revenue tests

Registration and transaction rules vary by VAT/GST jurisdiction

Customer checkout

Not inherently a VAT-style line-item tax on each purchase

Often affects the tax charged or accounted for on the customer's transaction

Business model

Central to deciding whether revenue is covered

Product/service and customer status also matter

Country rules

Highly jurisdiction-specific

Also jurisdiction-specific despite broader VAT/GST frameworks

The same commercial activity can therefore create multiple tax questions at once.

A digital platform may have VAT obligations connected with customer transactions while also assessing whether platform, advertising, or other qualifying revenue falls within a DST regime.

The brief's core evidence anchor is exactly this distinction: VAT on a digital sale and DST can analyze different taxpayers, tax bases, revenue streams, and activities.

[Internal link opportunity: VAT for Digital Businesses]

Being a “digital business” does not automatically put a company in scope

DST regimes generally define particular activities.

The label on the business is not enough.

A SaaS company is digital.

An ecommerce retailer is digital.

A social network is digital.

An online marketplace is digital.

An advertising platform is digital.

They do not necessarily receive identical DST treatment.

For example, the UK's current DST applies to revenues from defined social-media services, search engines, and online marketplaces linked to UK users. The UK government's 2025 review specifically distinguishes the service provider's revenue from the value of goods or services sold through a marketplace and says the DST was not designed to tax a retailer merely selling directly to consumers through its own digital platform.

France's regime covers specified digital intermediation, targeted online advertising, and certain sales of user data for advertising purposes.

Spain's statute covers defined online advertising, online intermediation, and transmission of certain user-generated data, while expressly excluding some underlying ecommerce sales made by a retailer on its own account.

Austria takes a narrower model: its Digital Tax Act applies to defined online advertising services, including forms such as banner and search-engine advertising, subject to its revenue conditions.

The merchant question is therefore:

Which revenue-producing function are we actually performing?

not:

Are we a technology company?

Marketplaces need to distinguish platform revenue from transaction value

This is especially important for platforms.

Suppose a marketplace facilitates a customer buying a €200 product from an independent seller and earns a €20 fee.

Potential data fields include:

€200 gross merchandise value;

€20 marketplace revenue;

seller revenue;

VAT or other transaction tax;

PSP fees;

refunds.

Those amounts are not interchangeable for DST analysis.

The UK government's 2025 review explicitly says UK DST taxes the relevant service provider's revenue, not the value of the underlying goods or services sold through the marketplace.

Spain similarly defines the taxable base around revenue from the covered digital service rather than automatically treating the underlying transaction value as the digital-services-tax base.

A marketplace that models DST from total payment volume without first understanding the statutory revenue definition can therefore produce a materially wrong estimate.

Revenue thresholds can operate at more than one level

Many DST regimes deliberately target larger businesses.

But “threshold” can refer to several different measurements:

global group revenue

global revenue from covered digital activities

domestic revenue

domestic covered digital-services revenue.

They are not interchangeable.

UK example

The UK's active DST currently applies at 2% and uses group-level threshold conditions of more than £500 million in global digital-services revenues and more than £25 million in UK digital-services revenues. The tax applies to the relevant UK taxable revenue after the statutory £25 million allowance and other rules. The UK government's 2025 statutory review confirmed that the DST continues to operate as an interim measure.

France example

France's Digital Services Tax applies at 3% to qualifying taxable digital-services revenue attributable to France where the relevant taxable-services revenue exceeds €750 million globally and €25 million attributable to France, including relevant group-level application. France's tax administration was collecting the 2025 balance and a 2026 instalment in April 2026, confirming the regime remained operational in 2026.

Spain example

Spain's regime applies a 3% rate where the taxpayer meets both a €750 million prior-year net turnover test and more than €3 million of prior-year revenue from taxable digital services attributable to Spain. Spanish guidance also applies the relevant threshold analysis at group level where entities belong to a group. Spain's 2026 taxpayer calendar continues to provide filing dates for Modelo 490, the return associated with the Digital Services Tax.

Austria example

Austria currently imposes a 5% digital tax on qualifying online advertising revenue. Its current Ministry of Finance guidance specifies a worldwide turnover threshold of at least €750 million and at least €25 million of Austrian online-advertising turnover, with group calculations relevant for multinational groups.

These examples demonstrate why a tax model should never contain a field simply called:

DST threshold

without specifying exactly what the threshold measures.

Why group structure matters

DST analysis is often not confined to the subsidiary that invoices the customer.

Consider a simplified group:

Global Parent

Annual revenue: €2 billion

↓

Digital Platform Group

↓

Local entity

Relevant local revenue: €30 million.

A local team looking only at the subsidiary might conclude:

“This entity is nowhere near a €750 million threshold.”

But if the applicable law tests revenue at group level, that is the wrong unit of measurement.

France's rules can apply threshold tests to qualifying companies belonging to a group, Spain's rules contain group-level threshold treatment, Austria uses group turnover for relevant multinational groups, and the UK's threshold rules are expressly group-based.

For tax operations, the necessary data can therefore sit in two different places:

local finance data

→ local qualifying revenue

and:

group consolidation data

→ global/group threshold.

The business needs both before it can make a reliable determination.

What counts as local revenue?

This may be harder than identifying the customer's billing address.

Different DST regimes use their own mechanisms for connecting digital revenue to a jurisdiction.

Those mechanisms can involve user location, digital-interface use, advertising viewed by local users, marketplace participants, or other statutory factors.

Spain's legislation, for example, uses detailed user-location rules that differ according to whether the activity is online advertising, online intermediation, or data transmission.

Austria's online-advertising regime looks at advertising received on a device with an Austrian IP address together with the service's orientation toward Austrian users.

The correct engineering question is therefore not always:

customer.country

It may be:

user location

covered activity

revenue attribution rule.

That has implications for data collection and tax reporting systems.

Current DST regimes illustrate how different the rules can be

The following examples are deliberately selective rather than an attempted global database.

Last verified: August 20, 2026.

Jurisdiction

Status

Illustrative current design

Key scope point

United Kingdom

Active

2%; >£500m global in-scope revenue and >£25m UK in-scope revenue at group level

Search engines, social media and online marketplaces; provider revenue, not marketplace GMV

France

Active

3%; €750m worldwide qualifying digital-services revenue and €25m attributable to France

Certain digital intermediation, targeted advertising and related data activities

Spain

Active

3%; >€750m prior-year turnover and >€3m Spanish taxable digital-services revenue

Online advertising, online intermediation and specified user-data transmission

Austria

Active

5%; €750m worldwide turnover and €25m Austrian online-advertising turnover

Narrower focus on qualifying online advertising

Canada

Repealed

Former 3% regime was repealed retroactively

Parliament enacted the repeal in March 2026 after the government had halted the measure in 2025

The table should not be interpreted as a complete list of DST jurisdictions.

Its main lesson is more useful than the list itself:

Country name is a configuration dimension, not an afterthought.

Canada's repeal shows why effective status matters

Tax teams frequently work from summaries written when a law was proposed, enacted, or first implemented.

DST is a particularly risky area for that approach.

Canada's Digital Services Tax Act came into force in 2024, but the government announced in June 2025 that it would rescind the tax. Legislation receiving Royal Assent on March 26, 2026 repealed the Digital Services Tax Act retroactively to its original enactment date.

A country spreadsheet last updated in early 2025 could therefore tell an expansion team that Canada has a 3% DST when the current legal position is materially different.

This is why every DST record should carry:

status

effective date

last verified date

primary authority.

The article brief specifically requires distinguishing an announced rule from a current effective rule.

How do international tax developments affect DSTs?

Unilateral DSTs developed partly because existing international corporate-tax rules were considered insufficient to address certain highly digitalized business models operating in markets without conventional physical presence.

The OECD/G20 Inclusive Framework's Pillar One project seeks a coordinated reallocation of some taxing rights to market jurisdictions. Its Multilateral Convention for Amount A was also designed to coordinate the removal of digital services taxes and relevant similar measures.

Implementation is not complete. The OECD's January 2025 update said the Inclusive Framework still needed agreement on the final Pillar One package, and the UK's November 2025 statutory DST review similarly stated that a final agreement had not yet been reached. The UK therefore continues to operate DST while describing it as an interim measure that would be removed once an appropriate global solution is in place.

Pillar Two should not be confused with this process. Pillar Two concerns global minimum taxation for large multinational groups, whereas OECD's 2026 GloBE commentary says DSTs generally tax gross digital-services revenue and generally are not Covered Taxes under those minimum-tax rules.

For a CFO or tax team, this means:

Do not remove an existing DST from the forecast merely because an international tax reform has been announced.

The relevant question is whether the domestic tax has actually been repealed, suspended, replaced, or otherwise changed under current law.

How DST can affect a market launch

DST often does not behave like a checkout tax.

That can lead Product teams to assume it is irrelevant to launch readiness.

It can still create material operational dependencies.

A company may need to determine:

whether its business model is a covered digital activity;

which revenue streams are in scope;

how local attributable revenue is calculated;

whether group-level revenue tests are met;

which entity is the taxpayer;

how covered revenue will be tracked;

whether registration or filing is required;

how Finance will accrue the tax;

which data supports local-user attribution;

who monitors regime changes.

The hardest part can be classification and data, rather than the multiplication required to calculate the tax.

A poor operating model

Country selected

→ payments enabled

→ product launched

→ Finance later discovers a DST regime

→ Tax asks for historical in-scope local revenue

→ Engineering cannot reconstruct the required user/revenue attribution cleanly.

A better operating model

Country selected

→ covered digital activities assessed

→ group/local thresholds reviewed

→ revenue attribution requirements identified

→ reporting data validated

→ filing/payment process assigned

→ launch.

That is how DST connects to Compliance Slows Launches. A technically available payment method does not establish that the tax operating model is ready. The cluster's broader editorial principle is that payment availability and tax readiness are separate questions.

DST Applicability Screen

Before treating DST as relevant—or irrelevant—run this six-question screen.

Does the jurisdiction have an active DST-type regime?

Record:

current status;

effective legislation;

rate;

last-reviewed date.

Do not rely on an old country list.

Is the business activity actually in scope?

Classify revenue by real function:

marketplace/intermediation;

targeted advertising;

social media;

search;

user-data activity;

another specifically covered category.

Do not classify from the company's industry label.

Which revenue is in scope?

Separate:

underlying transaction value

from:

revenue earned for the covered digital service.

For a marketplace, gross merchandise value may not be the relevant DST revenue base.

Do the thresholds apply?

Identify separately:

worldwide group revenue;

worldwide covered-services revenue where applicable;

local revenue;

local covered-services revenue;

relevant measurement period.

Never store one unlabeled “DST threshold.”

Which entity or group is assessed?

Identify:

taxpayer;

legal entity earning revenue;

consolidated group;

local reporting entity;

filing/payment responsibility.

What filing or payment obligation follows?

Determine:

registration if applicable;

return;

payment;

accounting accrual;

records;

data ownership;

review process.

The output should look like:

Jurisdiction

→ active regime?

→ covered activity?

→ covered revenue?

→ thresholds met?

→ responsible group/entity?

→ filing/payment process.

Not:

company is digital = DST.

What data should a digital business maintain?

A scalable DST process may require internal reporting that can produce:

In-scope revenue by jurisdiction

Revenue attributable under each country's applicable rule.

Revenue by covered activity

For example:

marketplace/intermediation;

online advertising;

search;

social-media activity;

other locally defined categories.

Group revenue

Because some thresholds operate at consolidated or multinational-group level.

Jurisdictional status

A centralized register of:

active DST;

pending law;

repeal;

suspension;

transition;

last review.

This data should be owned jointly enough that Tax is not trying to recreate it from PSP settlements.

Payment data may contain useful amounts, currencies, dates, and country indicators, but payment data alone does not determine product tax classification, legal revenue attribution, taxpayer identity, or group threshold status. The master brief expressly requires payment data to be distinguished from full tax determination.

What should digital businesses monitor?

DST is unusually date-sensitive.

A business with meaningful international digital revenue should monitor four things.

First, domestic law. A regime can be amended or repealed.

Second, group thresholds. Growth or acquisition activity can move a group into scope even if the local business itself barely changes.

Third, product functionality. A business can add marketplace, advertising, or user-data monetization functionality that changes the tax analysis without entering a new country.

Fourth, international reform. Pillar One developments may eventually change the future of unilateral DST regimes, but only actual domestic and multilateral implementation should drive compliance changes.

The practical monitoring cycle is:

business model

→ revenue

→ group

→ country status

→ tax obligation

→ repeat.

Key takeaway

Digital Services Tax is not another name for VAT on digital products.

That is the first distinction international businesses should get right.

VAT or GST generally asks how a customer transaction or supply should be taxed.

DST asks a different set of questions:

Does this jurisdiction currently have a DST-type regime?

Does the company's digital activity fall within its statutory scope?

Which revenue is covered?

Are global, group, or domestic thresholds met?

Which entity is responsible?

What reporting and payment process follows?

Current regimes show just how different the answers can be. The UK targets specified marketplace, search, and social-media revenue. France and Spain use their own definitions and thresholds. Austria's regime focuses on online advertising. Canada enacted a DST and later repealed it retroactively.

For market-entry planning, the right sequence is therefore:

jurisdiction

→ current DST status

→ business activity

→ covered revenue

→ group/local thresholds

→ responsible taxpayer

→ reporting/payment infrastructure.

A company should not discover that sequence after launch.

This article provides general information and does not constitute tax, legal, accounting, financial, or regulatory advice. Tax treatment depends on the merchant's circumstances, transaction structure, product or service, customer type, and applicable jurisdictions. Merchants should confirm their obligations with qualified tax and legal advisers and the relevant tax authorities.

FAQ SECTION

Is Digital Services Tax the same as VAT?

No. VAT generally applies to taxable supplies or transactions and is calculated according to the applicable VAT rules for that supply. A Digital Services Tax can instead apply to revenue from specific digital-business activities once defined thresholds and other conditions are met. A business may therefore need to analyze VAT and DST separately.

Who pays Digital Services Tax?

It depends on the jurisdiction. DST regimes generally define the liable business or group and can use substantial global and domestic revenue thresholds. For example, the UK's rules operate at group level, while France, Spain, and Austria also include significant revenue tests under their respective regimes.

Does every SaaS company pay Digital Services Tax?

No. Being a digital company or selling SaaS does not itself establish DST liability. Countries define covered services differently. A company needs to compare its actual revenue-producing activities with the current rules in each jurisdiction.

Are online marketplaces subject to DST?

They can be in some jurisdictions. The UK, France, and Spain all include defined forms of digital intermediation or online-marketplace activity, but their rules differ. Businesses should also distinguish the platform's own revenue from the value of the underlying goods or services sold through it.

Are DST thresholds based on local revenue or global revenue?

Potentially both. Some regimes combine global/group thresholds with a local covered-revenue test. The exact revenue definition and measurement period must be checked in each country's rules.

Can a Digital Services Tax be repealed?

Yes. Canada demonstrates how quickly status can change: its DST was ultimately repealed retroactively through legislation that received Royal Assent on March 26, 2026.

Will OECD Pillar One eliminate Digital Services Taxes?

That is part of the intended international architecture, but businesses should not assume existing domestic DSTs have disappeared. OECD Pillar One negotiations have not yet produced full implementation, and countries such as the UK continue to operate DST while waiting for an appropriate global solution.

🙂 🙂 🙂 🙂 🙂 🙂 🙂 🙂 🙂

END ARTICLE

Digital Services Taxes Explained: What International Digital Businesses Need to Know

META TITLE

Digital Services Taxes Explained | DST vs VAT

META DESCRIPTION

Learn how digital services taxes work, how DST differs from VAT/GST, which digital business models may fall within scope, how revenue and group thresholds work, and why country rules must be checked before launch.

SUGGESTED URL SLUG

/tax-invoicing/digital-services-taxes/

LOCAL MARKET

Qualifying attributable revenue

↓

Does domestic threshold apply?

↓

POTENTIAL DST SCOPE

This helps explain why local-subsidiary revenue alone may not answer the question.

EDITORIAL RECOMMENDATIONS

The strongest editorial framing is already in the brief:

Do not confuse the name of the business activity with the tax mechanism.

I would repeat that principle once near the opening and once in the DST Applicability Screen, but not more often.

I would also preserve the selective country table rather than creating a “Digital Services Tax countries 2026” mega-table. Country tables age quickly, and the controlling brief specifically warns that DST status, rates, thresholds, repeals, suspensions, and transitions require immediate verification.

The most valuable information gain over typical DST explainers is the combination of:

DST vs VAT

revenue versus GMV

group versus local thresholds

active versus announced/repealed rule

operational data requirements.

That makes the page useful to CFO, Tax, Product, Payments, and Expansion teams rather than merely defining the acronym.

SOURCES / RESEARCH REFERENCES

Primary and authoritative research used for this article:

HM Treasury — Digital Services Tax Review, November 2025: current UK status, scope, rate, thresholds, and interim nature.

UK Finance Act 2020: statutory UK threshold and calculation framework.

French tax administration: taxable digital services, 3% rate, €750m/€25m thresholds, and 2026 tax-payment activity.

Spain BOE, Law 4/2020: scope, 3% rate, €750m/€3m thresholds and legal characterization.

Spanish Tax Agency 2026 calendar: continuing Modelo 490 compliance in 2026.

Austrian Federal Ministry of Finance: current online-advertising DST scope, 5% rate, and €750m/€25m thresholds.

Department of Finance Canada: repeal policy and legislation.

Department of Finance Canada, March 2026: Royal Assent for legislation containing the DST repeal.

OECD: Pillar One developments and Amount A/DST relationship.

OECD 2026 GloBE commentary: treatment of DSTs as generally gross-revenue taxes rather than Covered Taxes under GloBE.

European Commission: EU VAT taxable transactions and taxable amount.

None in the current draft.

CLAIMS REQUIRING TAX / LEGAL REVIEW

A qualified international tax reviewer should confirm before publication:

the application of each example regime to particular platform, advertising, SaaS, data, or marketplace business models;

the precise group-aggregation rules for any reader-specific structure;

user/revenue attribution mechanics in each jurisdiction;

treatment of related-party or cross-border revenues where relevant;

how DST deductibility or interaction with other corporate taxes applies to a specific taxpayer;

any conclusion about whether a particular merchant is inside or outside a DST regime.

The brief itself recommends an international corporate-tax or digital-economy tax specialist for this article.

DATE-SENSITIVE CLAIMS TO RE-VERIFY BEFORE PUBLICATION

Immediately recheck:

UK: DST status, 2% rate, £500m and £25m thresholds, and any policy responding to Pillar One.

France: active status, 3% rate, €750m/€25m tests, payment timetable, and any transition agreement.

Spain: active status, 3% rate, €750m/€3m tests, and Modelo 490 filing arrangements.

Austria: active status, 5% rate, €750m/€25m tests, and any amendments.

Canada: continued legal effect of the 2026 repeal.

OECD Pillar One Amount A: final agreement, signature, ratification, entry into force, and resulting DST removal obligations.

Any new unilateral DSTs, repeals, suspensions, or bilateral transition arrangements relevant to markets added to the published article.

For this subject, I would place a visible editorial line near the byline:

Last reviewed: 20 August 2026

and update that date only after the country-status checks have actually been rerun.

Need help narrowing down payment options?

Answer a few questions about your business and compare the capabilities that matter to you.

Explore matching options ↗