Imagine you have trained hard for one event, only to arrive at the stadium and discover the organisers have redesigned the entire course. New distances, new rules, new checkpoints. That is precisely what the EU’s ViDA package does to the European VAT system. And if your Indian business exports goods to the EU, runs a tech platform there, or holds stock in multiple European countries, you are already entered in this race whether you registered or not.
ViDA was formally adopted by the EU Council on 11 March 2025. It is a three-pillar reform rolling out in stages until 2035, with the most critical deadlines landing in 2028 and 2030. The whole package is designed to close a compliance gap that has ballooned to staggering proportions. More on that number below.
This post breaks down all three pillars in plain language, corrects the timeline to reflect the final adopted text (some figures circulating online are from older draft proposals that were changed before the vote), explains the key technical standard you will hear mentioned constantly, and gives you a practical training plan.
The Scoreboard: What Is the EU VAT Gap?
Every year, EU governments calculate how much VAT they should collect if every business followed the rules perfectly. Then they look at what actually arrived in the treasury. The difference is called the VAT Gap, and it is the single biggest reason ViDA exists.
To put €128 billion in context: that is more than the entire annual GDP of many individual EU member states. It is not a rounding error. It is a structural haemorrhage.
Why does the gap exist? Four main reasons:
VAT fraud is the most notorious driver. “Missing trader” or carousel fraud involves a company collecting VAT from its customers and then vanishing before paying it to the government. Think of it as a relay runner who takes the baton from their teammate and simply walks out of the stadium. The baton never reaches the finish line.
Bankruptcies are a secondary cause. When a company goes under, any VAT it owes often becomes uncollectable. The government is left holding an empty receipt.
Honest errors pile up across millions of cross-border invoices. One wrong commodity code, one misapplied rate, multiplied across thousands of transactions, adds up very quickly.
Outdated systems are the fourth problem. Many tax offices were working with summary data that was weeks or months old. By the time fraud was spotted, the perpetrators had already moved on.
ViDA is the EU’s answer to all four problems at once. The goal is not to raise VAT rates. The goal is to make evasion structurally impossible by moving to data that arrives in near-real-time.
The Race Calendar: ViDA’s Key Deadlines
Before diving into each pillar, here is the official timeline from the adopted legislation. Bookmark this. The dates in the original 2022 Commission proposal were revised significantly before the final vote in November 2024.
| Date | What Changes | Pillar |
|---|---|---|
| 14 April 2025 | ViDA enters into force. Member states can mandate domestic e-invoicing without EU approval. Buyer consent for e-invoices removed in mandatory schemes. | Pillar 1 (early measures) |
| 1 January 2027 | Minor updates to One-Stop Shop (OSS) and Import One-Stop Shop (IOSS) e-commerce rules. | Pillar 3 |
| 1 July 2028 | Expanded OSS and Single VAT Registration goes live. Platforms may voluntarily adopt the deemed-supplier rule. Reverse charge extended for non-identified suppliers. | Pillars 2 & 3 |
| 1 January 2030 | Deemed-supplier rule becomes mandatory for all ride-sharing and short-term accommodation platforms across all EU member states. | Pillar 2 |
| 1 July 2030 | Digital Reporting Requirements (DRR) and mandatory structured e-invoicing go live for all cross-border B2B transactions within the EU. | Pillar 1 |
| 1 January 2035 | Member states that had domestic digital reporting systems before January 2024 must bring those systems in line with EU-wide ViDA standards. | Pillar 1 (harmonisation) |
Before We Go Further: What Is EN 16931?
You are going to see this term in every ViDA article, every ERP vendor brochure, and every compliance checklist between now and 2030. It sounds like the name of a motorway, but it is actually the technical rulebook that sits at the heart of all three ViDA pillars.
Think of EN 16931 as a shared language that every computer system across all 27 EU countries can read and understand automatically. Right now, if you send an invoice as a PDF to a buyer in Germany, a human being has to open it, read it, and type the numbers into their own system. That process is slow, it introduces errors, and it gives no data to the government in real time.
EN 16931 is the EU’s official standard that defines exactly what a valid electronic invoice must contain and how it must be structured. It specifies which pieces of information are mandatory (buyer name, seller VAT number, commodity codes, tax amount, payment details, and more), what order they appear in, and what file format carries them — so that a computer system in Rome can read an invoice generated in Mumbai and process it instantly, with no human in the middle.
The two file formats that meet this standard are called UBL (Universal Business Language) and CII (Cross Industry Invoice). Both are types of XML — the same structured text format used widely in software and data exchange. Germany also uses a hybrid format called ZUGFeRD, which embeds the structured data inside a PDF so a human can read it visually while the computer reads the data layer underneath.
From 1 July 2030, any cross-border B2B invoice within the EU must comply with EN 16931. A standard PDF, a Word document, or a manually entered order in an accounting system will not qualify. Your invoicing system must be able to generate the structured file and transmit it to the government portal automatically.
The GST equivalent you already know: think of it like the structured JSON data that your system sends to the GSTN portal for GSTR-1 filing. You do not email the GSTN a PDF. You push structured data through an API. EN 16931 is the EU’s version of that API contract — the agreed format that makes automated, real-time tax reporting possible.
If the e-invoicing standard (EN 16931) is the equipment, DRR is the race itself. For decades, businesses reported their cross-border EU sales using European Sales Lists — periodic summaries filed with national tax authorities. These were the equivalent of receiving a match highlights reel three weeks after the final whistle. By then, missing traders had already left the stadium.
From 1 July 2030, those delayed summaries are replaced by something far closer to a live broadcast. Every cross-border B2B transaction within the EU must be reported at the individual invoice level, in near-real-time, automatically.
What the 10-Day Rule Actually Means
Here is what that looks like in practice. Say you sell a consignment of automotive components to a German manufacturer. The goods are delivered on 1 August 2030. Under DRR, you must issue a structured EN 16931 e-invoice by 11 August, and the data on that invoice must have already reached the Indian Revenue Service portal equivalent on the EU side — your national VAT authority’s digital gateway — by the same date. The German buyer then has five days from receiving the invoice to report their side of the same transaction.
The tax authorities on both sides now hold matching records of the same transaction, reported independently, almost in real time. If those records do not match, a flag goes up automatically. No quarterly summary list. No manual reconciliation three months later. Every transaction, every time.
For Indian manufacturers who worked through the CBAM carbon certificate deep-dive, the discipline required here will feel familiar. Just as CBAM demands granular carbon-intensity records per shipment, DRR demands granular invoice data per transaction. The underlying muscle you need to build is identical: your systems must talk directly to government portals, automatically, without any human sitting in the data pipeline manually checking fields.
This also connects directly to the EMEA e-invoicing post, where we covered the infrastructure side of generating EN 16931 files. If you have not yet assessed whether your ERP can produce a structured XML invoice, that post is your starting point. DRR is what happens after the invoice is issued — the reporting obligation that sits on top of the invoicing obligation.
The analogy I keep returning to is the progressive overload principle from the training post. You do not build the capacity to handle heavy loads overnight. Companies that start building EN 16931-compliant invoicing into their ERP workflows today will be well-conditioned by 2030. Companies that wait until 2029 will be trying to deadlift without having learned the basic movement pattern.
This pillar targets digital marketplaces and gig economy platforms. If you operate an Indian tech company that connects European customers with local service providers — short-term apartment rentals, ride-hailing, freelance transport — the entire VAT structure of your business model is about to change.
The Problem This Rule Is Fixing
A traditional hotel charges VAT on every booking. A licensed taxi company charges VAT on every fare. But a driver who lists rides through a platform, or a homeowner who lists their apartment, often falls below the VAT registration threshold in their country. This means those transactions effectively go untaxed. And under current rules, the platform — the company facilitating the booking — is not responsible. It is just the middleman.
This created an unfair competitive advantage. A small driver on a ride-sharing app effectively undercuts a fully licensed taxi firm by the entire VAT rate, simply because the regulatory structure let them. ViDA closes this loophole.
What “Deemed Supplier” Actually Means
Under ViDA, if a platform facilitates a short-term accommodation booking (30 consecutive nights or fewer per customer) or passenger transport by road within the EU, and the service provider who is actually doing the work is not charging VAT, then the EU treats the platform as though it bought and then resold that service itself.
In plain terms: the platform is now the seller in the eyes of the tax authority. It must collect VAT from the end customer at the correct local rate and pay it to the relevant EU government. The actual driver or host is treated as having sold the service to the platform at a VAT-exempt rate.
For an Indian startup scaling into Europe, this is a first-principles redesign of your business logic. Your checkout flow must identify whether a provider is VAT registered. If they are not, your system must calculate the correct local EU VAT rate for that customer’s country, collect it from the customer, and route it to the right tax authority. That is not an add-on feature. That is core product infrastructure.
The voluntary phase begins in July 2028. Platforms can choose to adopt the deemed-supplier model from that date. The mandatory phase applies from January 2030, though individual member states can delay their national implementation until that deadline. Spain has already signalled it may use this deferral option.
The good news: the remittance mechanism is the same expanded One-Stop Shop covered in Pillar 3. You register in one EU country and discharge your VAT obligations across the whole bloc through a single portal. The three pillars genuinely do work together.
The first two pillars add obligations. Pillar 3 removes some of the administrative weight that currently sits on top of them. If ViDA were a cricket innings, this is the over where your team finally gets on the board.
Right now, if an Indian exporter stores goods in a warehouse in the Netherlands and a second warehouse in Poland, they typically need separate VAT registrations in both countries. Add Germany and France to that network and you are managing four national registrations, four sets of local filing deadlines, and correspondence in four different languages.
What the One-Stop Shop Expansion Changes
The existing One-Stop Shop already allows businesses to report B2C cross-border digital sales through one EU registration. From July 2028, ViDA expands this mechanism significantly. Two changes matter most for Indian businesses:
Moving your own stock between EU countries — for example, from a Rotterdam port warehouse to a Berlin fulfilment centre — will no longer automatically require a local VAT registration in the destination country. You report the movement through your single OSS registration instead.
More reverse charge scenarios will apply to cross-border B2B sales, meaning the buyer accounts for VAT in their own country rather than the Indian seller needing to register locally at the point of delivery.
Think of it as moving from 27 separate domestic leagues — each with their own registration, their own filing calendar, and their own local accountant on retainer — into a single unified competition with one central standings table. You still play away games. But you no longer need a separate club membership in every city you visit.
This connects to the efficiency argument running through the GST 2.0 structural rationalisation post. India is rationalising its own rate structure to reduce friction for businesses. The EU is doing the same with registrations. The direction of travel globally is fewer administrative barriers paired with more data transparency. Indian companies that build for both at the same time will carry the lightest compliance load in the long run.
From Invisible to Deemed Supplier in One Regulation Change
Imagine an Indian EdTech company that facilitates in-person workshops in Paris and Berlin. They hire local freelance tutors who are not VAT registered because their individual earnings fall below the French or German threshold. Under current rules, VAT on the workshop fee is effectively lost — the tutor is not registered, so no VAT is collected from the student.
Under Pillar 2 from January 2030, the Indian platform becomes the deemed supplier. It must charge French VAT (currently 20%) or German VAT (19%) to the student at checkout, collect it, and remit it to the relevant EU authority — most likely through the expanded One-Stop Shop under Pillar 3. That remittance must then be backed by a structured EN 16931 e-invoice that meets the DRR reporting requirements under Pillar 1.
All three pillars converge on a single workshop booking. The training plan for this company is not complicated — but it does need to start now, not in 2029. The EMEA e-invoicing post covers the technical standards to target first.
The Data Fields Your System Needs to Capture
For ERP managers and finance leads: here is what EN 16931 actually demands in terms of data. These are not optional fields. They must be present in every structured invoice submitted under DRR from 2030. Think of it as the mandatory information your system must be able to export — automatically and correctly — for every single cross-border B2B transaction.
Buyer Reference: A unique identifier that links the invoice to a specific buyer entity and their VAT registration number in the relevant EU country.
Tax Point Date: The exact moment the VAT becomes chargeable. This is not the invoice date. It is the earliest of: the date of supply, the date of payment, or the date the invoice was issued. Getting this wrong causes a mismatch between your report and the buyer’s report.
Payment Means Code: A standardised code indicating how the transaction was or will be settled — bank transfer, credit card, digital wallet. Where payment is by bank transfer, the buyer’s IBAN must be included.
Commodity Codes: International classification codes that identify the specific goods or services being sold. These are the EN equivalent of HSN codes in Indian GST — different numbering system, same underlying logic of categorising what is being transacted.
If your current system cannot export all of these fields into an XML file automatically, you have identified your gap. The work to close it is primarily an ERP configuration and integration project, not a tax strategy exercise. The tax strategy is already written — it is called ViDA. The execution is a technology decision.
The connection back to the Finance Bill 2026 post on ITC optimisation is worth drawing here. In India, the government tightened invoice-level documentation requirements because that is where the money is — in the detail of individual transactions, not in aggregate summaries. The EU is doing the same thing with DRR, just at a faster reporting cadence. The muscle you build for one helps with the other.
The Training Programme: A Three-Phase Plan for Indian Businesses
In the progressive overload post, the principle is clear: you do not attempt a personal best on day one. You build the movement pattern, add load week by week, and peak at competition day. ViDA compliance works exactly the same way. Here is a structured three-phase approach.
Audit Your Tech Stack and Customer Data
Start with one honest question: can your invoicing system generate a structured XML file containing all the mandatory EN 16931 fields? If the answer is no — or if invoices are still being produced by editing a Word or Excel template — this phase is where you fix that. Engage your ERP or accounting software provider now, while you have four years of runway. The companies that will struggle in 2030 are the ones starting these conversations in late 2029.
In parallel, clean your customer master data. Every EU customer record must have a valid VAT identification number attached to it. Under DRR, an invoice issued to a buyer with no VAT ID is a compliance failure before you have reported anything. Think of it the way GST treats an invoice without a valid GSTIN for input tax credit purposes — incomplete data means you cannot claim the benefit, and in the EU context, incomplete data means an automatic flag.
Map Your EU Footprint and Build Platform Tax Logic
With the expanded One-Stop Shop going live in July 2028, use 2027 to map out how many EU VAT registrations your business currently holds and whether consolidation makes sense. If the India-EU Free Trade Agreement drives new volumes into new member states, building your compliance structure around a single OSS registration from the beginning is far cleaner than accumulating local registrations that you later need to unwind.
For platform businesses: your deemed-supplier VAT logic needs a working prototype by 2027. The voluntary phase opens in July 2028 — use it. Two years of live testing before the mandatory deadline is a genuine competitive advantage. Every platform that waits for January 2030 will be trying to implement complex VAT collection logic at the same time, competing for the same implementation partners and the same technical resources.
Go Live on OSS, Test DRR, and Remove Every Manual Step
The Single VAT Registration expanded OSS is live from July 2028. Register, test the reporting flows, and verify that your accounting system reconciles correctly with the portal output. The period between July 2028 and July 2030 is your live rehearsal for DRR. The underlying data your OSS return requires is structurally close to what DRR will demand — same format, same fields, higher reporting frequency.
By Q1 2030, every step from invoice generation to tax authority reporting must run without manual intervention. The 10-day DRR window leaves no space for a human to sit in the middle of the data pipeline checking whether the commodity code is correct. Automate the generation. Automate the transmission. Audit the output. That is the order of operations.
ViDA is not a compliance sprint. It is a restructuring of the entire stadium. Indian businesses that treat it as a 2029 problem will arrive at the start line having skipped the entire training block.
Quick Reference: Common Questions Answered
Does ViDA apply to Indian businesses without an EU entity?
Yes, in many scenarios. If you make B2B sales of goods to EU buyers that qualify as intra-EU supplies, those transactions fall under DRR. If your platform facilitates services in the EU under the Pillar 2 deemed-supplier rules, the VAT collection and remittance obligations apply regardless of where your company is incorporated. The EU’s position is that the VAT follows the transaction, not the seller’s registered address.
Is ViDA connected to the India-EU Free Trade Agreement?
Indirectly, yes. The FTA is expected to increase the volume of Indian goods and services flowing into the EU. More transactions mean more exposure to ViDA’s reporting requirements. A company that enters the EU market post-FTA without ViDA-compliant invoicing infrastructure will face penalties from day one of trading. The two are not legally linked, but commercially they arrive at the same time for many Indian exporters.
What is the connection between ViDA and CESOP?
ViDA governs what you report about your sales. CESOP — the Central Electronic System of Payment Information — governs what your bank and payment processor report about the money you receive from EU customers. If you receive more than 25 payments per quarter from EU buyers, your payment data is already being reported to EU tax authorities by your payment service providers. The two systems are designed to cross-check each other. Your sales reports and your bank records must tell the same story. That is the subject of the next post in this series.
Does building EN 16931 compliance affect my GST invoicing?
Your GST obligations and EU VAT obligations operate as independent systems and do not directly interact. However, if your ERP generates invoices in EN 16931 XML for EU transactions, you need to ensure your Indian GST fields — GSTIN, HSN codes, place of supply — are also captured correctly in the same system. The cleanest solution is a single invoicing engine that draws from one data source and can output both formats. Keeping them as entirely separate systems creates data mismatches that generate reconciliation problems on both sides.
The Final Score: What ViDA Means for the Tax Athlete
We have covered a lot of ground in this series. Post 1 showed how the EU is taxing the carbon embedded in your exports through CBAM. Post 2 showed how the shift to structured e-invoicing changes your billing infrastructure. Post 3 — this one — shows the full three-pillar VAT reform that underlies both of those changes. They are three separate rules, but they come from the same playbook: give tax authorities better data, in real time, at the transaction level.
The three ViDA pillars are not isolated obligations either. They connect. Your EN 16931 e-invoice feeds the DRR reporting requirement. Your DRR data flows through the same One-Stop Shop portal that handles your Pillar 3 registration. Your deemed-supplier VAT as a platform is remitted through the same OSS system. Build one compliant infrastructure and you cover most of the obligations across all three pillars.
The analogy I keep coming back to: a triathlete does not train three sports in complete isolation. They train transitions. The fastest athletes are the ones who move efficiently between disciplines without losing time at the handover. ViDA demands the same from your compliance setup. Build clean transitions between your invoicing, your reporting, and your registration management. That is where the time is won or lost.
CESOP: The Silent Referee Watching Every Payment You Receive
You now have the equipment (EMEA e-invoicing), and you have trained across all three ViDA disciplines. But there is a silent referee in the booth who is not looking at your invoices at all. They are watching your bank statements. CESOP — the Central Electronic System of Payment Information — requires your payment service providers to report to EU tax authorities every time you receive more than 25 payments in a quarter from EU customers. We will break down exactly what data is being reported, how it cross-checks against your ViDA filings, and how to make sure your sales records and your bank records always tell the same story. A mismatch between the two is the new definition of a red card.
Sources and Further Reading
- European Commission — Official ViDA Adoption Announcement (11 March 2025)
- European Commission — VAT Gap Report Hub (2025 edition, covering 2023 data — €128 billion figure)
- Council of the EU — ViDA Formal Adoption Press Release
- PwC Luxembourg — ViDA Implementation Guide and Business Impact
- VATCalc — ViDA Adopted: Detailed Technical Breakdown (updated March 2026)
- Grant Thornton — ViDA DRR and E-Invoicing: What Businesses Need to Know
- Sovos — ViDA Timeline (detailed milestone tracker)