EU VAT Rules for Digital Service Providers and Digital Services Taxes After ViDA

EU VAT compliance for digital service providers remains based on one core principle: VAT is generally due where the consumer is located. The VAT in the Digital Age reform, commonly called ViDA, does not replace this rule and does not introduce a new EU-wide digital services tax.

Instead, ViDA modernises the existing VAT system by expanding digital reporting, strengthening platform economy rules, and moving the EU closer to Single VAT Registration.

For businesses selling SaaS, streaming, apps, downloadable software, online subscriptions, gaming content, or automated online courses to EU consumers, the main compliance route remains the One Stop Shop, OSS. OSS allows eligible businesses to register in one EU Member State and report VAT due in multiple Member States through a single quarterly return.

Digital Service Tax (DST) is separate from VAT. They are national taxes adopted by individual countries, generally aimed at large digital groups earning revenue from online advertising, digital intermediation, marketplace activity, or user data monetisation. Compliance with OSS does not remove any DST exposure, and paying DST does not satisfy VAT obligations.

EU VAT and Digital Services

What Counts as a Digital Service?

For VAT purposes, digital services generally include services delivered over the internet or an electronic network with minimal human involvement. Common examples include:

• SaaS and cloud software
• Streaming of music, films, games, or other media
• Downloadable applications and software
• Subscription-based digital content
• Automated online courses and prerecorded training
• Digital templates, files, or tools are delivered automatically after purchase

The key distinction is the level of automation. A live one-to-one consulting session delivered by video call is usually treated differently from an automated subscription platform or a prerecorded online course. The VAT risk increases when a business moves from human-led advisory work into scalable digital delivery.

Destination-Based VAT

For B2C digital services supplied to EU consumers, VAT is generally charged based on the customer’s Member State. This is destination-based VAT.

For example, if a non-EU SaaS provider sells subscriptions to consumers in Germany, France, and Lithuania, the business must apply German VAT to German consumers, French VAT to French consumers, and Lithuanian VAT to Lithuanian consumers.

This requires the supplier to know where the customer is located, apply the correct VAT rate, issue appropriate invoices or receipts where required, and retain transaction records.

EU VAT Versus Digital Services Tax

EU VAT

VAT is a consumption tax charged on supplies of goods and services. For digital service providers, VAT is normally charged to the customer and remitted to tax authorities. VAT compliance focuses on registration, charging the correct rate, filing returns, payment, and record keeping.

Digital Services Tax

Digital Services Tax is different. DST is usually a tax on the gross revenues of large digital businesses. It is normally aimed at specific business models, such as online advertising, digital platforms, marketplaces, or monetisation of user data.

A business can be fully compliant with OSS and still have DST exposure in one or more countries. Equally, a business can be outside DST due to revenue thresholds but still have EU VAT obligations from selling digital services to consumers.

This distinction is important because founders often use the phrase “digital tax” too broadly. EU VAT, DST, corporate income tax, withholding tax, and permanent establishment risk are separate issues and should be analysed separately.

VAT in the Digital Age

ViDA is an EU reform package designed to modernise VAT for the digital economy. It focuses on three broad areas:

• Digital reporting and e-invoicing
• VAT treatment of platform economy activity
• Single VAT Registration across the EU

For digital service providers, ViDA does not remove the need to charge VAT. Instead, it makes the VAT system more digital, more data-driven, and more centralised.

What ViDA Means for Digital Service Providers

The practical direction is clear. The EU wants more cross-border VAT compliance to be handled through centralised schemes such as OSS, reducing the need for multiple local VAT registrations.

For digital service providers, this means:

• OSS remains the main reporting route for cross-border B2C digital services
• VAT rate logic must be based on the customer’s location
• Systems must retain reliable location evidence
• Digital records and audit readiness become more important
• Platform operators may face stronger deemed supplier obligations

Businesses should not wait for future ViDA phases before complying. Existing VAT and OSS obligations continue to apply now.

Who Must Register for EU VAT

An EU-established business selling B2C digital services in its own country usually reports those sales through its domestic VAT return.

If it sells B2C digital services cross-border to consumers in other EU Member States, it may use OSS to report VAT due in those countries. The EUR 10,000 EU-wide threshold is relevant for certain cross-border B2C supplies. Once exceeded, the supplier must apply the VAT rate of the customer’s Member State or use local registrations.

For most EU digital businesses, the practical structure is:

• Domestic VAT registration in the home country
• OSS registration for cross-border B2C digital services
• Local VAT registrations only where activities fall outside OSS

Non-EU businesses selling B2C digital services to EU consumers generally need to address EU VAT from the first sale. They do not usually benefit from the same practical threshold position as small EU-established businesses.

A non-EU digital service provider can usually register under the non-Union OSS scheme in one chosen Member State. This allows it to report eligible B2C digital service sales to consumers across the EU through one OSS return.

For example, a US SaaS company selling subscriptions to private users in Germany, Spain, France, and Italy may choose one Member State for non-Union OSS registration. It then charges VAT based on each customer’s country and reports those sales through one OSS return.

OSS for Digital Services

OSS is designed to simplify cross-border B2C VAT reporting. Instead of registering separately in each EU country where consumers are located, a business can register in one Member State of identification.

Through OSS, the business reports sales by Member State and VAT rate. It makes one payment to the Member State of identification, which then allocates the VAT to the relevant Member States.

For digital service providers, OSS commonly covers B2C digital services such as SaaS subscriptions, apps, streaming services, digital downloads, automated courses, and similar electronically supplied services.

OSS does not cover every situation. A business may still need local VAT registration if it has a fixed establishment, local stock, domestic supplies not covered by OSS, or other activities outside the scope of OSS.

Case example: 

A Canadian SaaS provider sells monthly subscriptions to private customers in Germany, France, and the Netherlands. The company has no EU office and no EU staff.

The company can register under non-Union OSS in one EU Member State. It charges German VAT to German consumers, French VAT to French consumers, and Dutch VAT to Dutch consumers. Each quarter, it reports these sales through the OSS return.

This avoids separate VAT registrations in Germany, France, and the Netherlands, provided the company has no other local activities requiring registration.

Digital Platforms and Deemed Supplier Rules

ViDA strengthens the importance of platform economy VAT rules. In some cases, platforms may be treated as the supplier for VAT purposes. This is known as deemed supplier treatment.

This can affect:

• App stores
• Digital marketplaces
• Online course platforms
• Subscription platforms
• Intermediation platforms
• Marketplaces for digital content

Where deemed supplier rules apply, the platform may be responsible for charging, collecting, reporting, and paying VAT, rather than the underlying seller.

For example, if an app developer sells a digital product through a platform that acts as the deemed supplier, the platform may collect VAT from the consumer and remit it. The developer should then avoid accounting for VAT again on the same sale.

The key compliance point is to map responsibility clearly. A platform and seller should understand which party is liable for VAT, what data is reported, and how transactions are reconciled.

OSS Filing and Record Keeping

OSS returns are generally filed quarterly. The return should show eligible B2C sales by Member State and VAT rate. Payment is made to the Member State of identification.

Digital service providers should reconcile data from:

• Billing systems
• Payment processors
• App stores
• Marketplaces
• Accounting software
• Refund records
• Customer databases

Clean data is essential. If sales are not correctly split by country and VAT rate, OSS reporting becomes unreliable.

Digital service providers should retain records for the required period, commonly 10 years for OSS-related transactions. Records should include invoices or receipts, transaction logs, VAT calculations, customer location evidence, payment confirmations, refunds, and platform reports.

Digital Services Taxes in the EU After ViDA

ViDA is a VAT reform. It does not harmonise or replace national Digital Services Taxes.

DSTs remain country-specific. They are generally aimed at large digital groups with significant global and local revenues. Their scope differs by country but may include online advertising, digital intermediation, sale or use of user data, or platform revenues.

Countries With DST Exposure

Several European countries have implemented or considered DST regimes. France, Italy, Austria, and Spain are commonly cited examples of countries with implemented digital services taxes. Poland has also discussed or proposed work on a digital services tax.

These regimes are politically sensitive and may change depending on domestic policy, OECD developments, and international negotiations. Therefore, businesses should monitor DST separately from VAT.

Practical DST Example

A large online advertising platform earns substantial revenue from users and advertisers in France, Italy, and Spain. Even if the platform correctly charges and reports EU VAT through OSS where required, it may also need to assess whether national DST rules apply in each country.

By contrast, a small SaaS provider selling subscriptions to EU consumers may have VAT obligations through OSS, but may not meet DST revenue thresholds.

Common Compliance Risks

• ViDA does not pause current EU VAT obligations. Digital service providers selling to EU consumers should assess OSS registration now, not wait for later ViDA phases.
• VAT and DST are different taxes with different triggers, taxpayers, reporting processes, and risk profiles.
• A business may incorrectly treat an automated digital service as ordinary consulting or treat a live service as an electronically supplied service. The delivery model should be reviewed carefully.
• If the business cannot prove where the customer is located, it may struggle to justify the VAT rate applied.
• Platforms and sellers may both assume the other party is responsible. This creates either missed VAT or double reporting.

Conclusion

EU VAT rules for digital service providers remain centered on destination-based taxation, OSS registration, accurate VAT rate application, reliable customer location evidence, and strong record keeping. ViDA does not create a new digital services VAT.

 It modernises and expands the existing VAT system, with a gradual move toward more digital reporting, platform accountability, and Single VAT Registration.

Digital Services Taxes are a separate matter. They remain national taxes aimed mainly at large digital businesses and must be reviewed independently from VAT and OSS compliance.

For digital service providers, the practical approach is clear: use OSS where available, configure systems correctly, document customer location, separate B2B and B2C flows, and monitor DST only where the business model and revenue levels make it relevant.

Frequently Asked Questions