ViDA: what actually changes for e-invoicing, and when

Almost every conversation we have about a European roadmap now ends at the same question: "but what about ViDA?" It is a fair question and a badly answered one, because "VAT in the Digital Age" is not a single mandate with a single date. It is one legislative package with three separate pillars, each on its own clock, running from 2025 to 2035. Mix the pillars up — and most summaries do — and you either panic about a 2030 deadline that does not apply to you, or miss a 2025 change that already does.

1. One package, three pillars

ViDA was adopted on 11 March 2025 as Council Directive (EU) 2025/516, together with an amending regulation and implementing regulation. It amends the VAT Directive across three largely independent workstreams:

This article is about the first pillar, because that is the one that touches invoicing systems. But keep the other two in view: they move on different dates, and a stakeholder who has heard "ViDA is 2030" may actually be asking about a 2028 registration change.

2. What already changed (2025)

The most under-reported part of ViDA is the part that is already live. From the directive's entry into force on 14 April 2025, two things changed for e-invoicing at EU level:

• Member States may now mandate domestic e-invoicing without asking the EU for a derogation. Previously a country had to obtain a special Council decision (as Italy and others did). That barrier is gone.
• For those mandated domestic e-invoices, the buyer's consent is no longer required — a supplier can issue a structured invoice without first asking the recipient to accept one.

One thing that does not change yet: the EU-law definition of an "electronic invoice" — the rule that only a structured format counts and a PDF does not — does not take effect until 1 July 2030 (see below). Several national mandates already demand structured formats sooner, but that is national law, not the ViDA definition, and it is exactly the kind of distinction that gets garbled in summaries.

The derogation change is why the map of European mandates has filled in so quickly. Belgium went live in 2026, France and Poland are rolling out, Germany is phasing its issue obligation — none of them now depends on an EU derogation for the domestic leg. If your planning still assumes a country "needs Brussels' permission first", it is out of date. Our mandate tracker shows where each country actually is.

3. The 2030 cliff: intra-EU digital reporting

The date everyone means when they say "ViDA" is 1 July 2030. From that day, intra-Community B2B transactions come under a harmonised Digital Reporting Requirement:

• The EU-law definition of an electronic invoice narrows to a structured format that can be processed automatically — from this date a PDF stops being an electronic invoice for these purposes.
• Structured e-invoicing becomes mandatory for intra-EU B2B supplies, based on the EN 16931 semantic standard.
• A near-real-time, transaction-level report replaces the recapitulative statement (the EC Sales List). Instead of a periodic aggregate, each qualifying transaction is reported to the tax administration around the time it is invoiced.
• The issuing deadline shortens — an intra-EU invoice must be issued within ten days of the chargeable event (down from the current mid-month-following convention, and up from the two working days first proposed).
• Summary invoicing is curtailed for these transactions, and both supplier and customer report their side.

The architectural consequence is the important part. A recapitulative statement is a batch job you run monthly from data you already have. A transaction-level DRR is a second, time-bound data path that has to stay reconciled with the invoice itself — much closer in shape to a clearance obligation than to a VAT return. Teams that treat 2030 as "a bigger EC Sales List" will under-build it.

4. The 2035 convergence deadline

Several countries ran transaction reporting long before ViDA — Italy's SdI clearance, Hungary's real-time invoice reporting, Spain's SII. ViDA does not force them to switch off on day one. Instead it grandfathers pre-existing domestic systems and gives them until 1 January 2035 to converge with the harmonised EU standard.

Two practical implications follow. First, if you operate in one of those countries, you have a second migration on the horizon — the national format you build for today is not the final destination. Italy's FatturaPA is a national XML, not native EN 16931; Hungary's regime is reporting, not invoicing. Both have a convergence step ahead of them. Second, the 2035 date is a ceiling, not a plan: nothing stops a Member State converging earlier, and some will.

5. What ViDA does not decide

ViDA harmonises the cross-border layer and sets a convergence target. It deliberately leaves each Member State a lot of room on the domestic layer, and that is where roadmaps go wrong. ViDA does not tell you:

• Whether your domestic B2B is mandated, or when. That is a national decision — France 2026–27, Germany 2025–28, Belgium 2026, Poland 2026 and so on, each with its own scope and thresholds.
• Which transport or platform your country picks. ViDA points at EN 16931; it does not mandate Peppol, a national portal, or a clearance model. Countries choose.
• How domestic reporting works before 2035. A grandfathered system keeps running on its own rules until it converges.

ViDA sets the destination for cross-border and a deadline for everyone else to arrive. It does not drive your domestic bus — your national mandate does.

So the correct reading of a claim like "Germany is ViDA" is: Germany's domestic mandate is a national scheme that will have to interoperate with the ViDA cross-border layer by 2030 and converge by 2035 — not that ViDA sets Germany's dates. The Germany, France and Italy pages each state where the national scheme meets the ViDA line.

6. Putting it on a roadmap

For a business or a service provider planning the next five years, ViDA resolves into four concrete work items sitting underneath your national obligations:

1. Now: assume any EU country can mandate domestic e-invoicing without warning from Brussels. Track the national dates, not the derogation process.
2. By 2028: check whether the single VAT registration and platform changes shrink your foreign registrations or shift a VAT-accounting responsibility onto a platform you use or operate — noting that a Member State may defer the platform deemed-supplier rule to 1 January 2030.
3. By July 2030: build the intra-EU DRR as a transaction-level, near-real-time data path — reconciled with the invoice, EN 16931-based, ten-day issuance — not as a bigger EC Sales List.
4. Before 2035: if you rely on a grandfathered national system (Italy, Hungary, Spain and others), plan its convergence to the harmonised standard as an explicit migration, not a surprise.

The through-line is the same one that governs every mandate we work on: keep the EN 16931 semantic model as your source of truth, treat each national syntax and transport as an adapter, and the difference between "ViDA-ready" and "rebuild" becomes a matter of configuration rather than a programme.