ViDA · Strategy

ViDA 2027–2035: what does it mean for your organisation.

The timeline is long enough to plan sensibly, but too short to keep waiting for a perfect moment. The value lies in an early impact assessment and a measured route forward.

3 March 2026 Alexander Breekpot ViDA

ViDA is no longer a topic for later. The package was definitively adopted by the Council of the EU on 11 March 2025. The rollout runs in phases through to 1 January 2035. For organisations, that does not mean everything must change today, but it does mean that data, invoicing and VAT reporting can increasingly less be arranged independently of one another.

Treat ViDA therefore not as an isolated compliance project. The question is whether your current process, data and governance can grow towards ViDA requirements without a great deal of remediation work. Organisations that investigate this too late usually discover that the biggest challenge is not in e-invoicing itself, but in source data, exceptions and fragmented responsibilities.

Timeline overview

The change comes in stages, not all at once

In broad terms, ViDA moves along three blocks. From 2027 and 2028, parts of the single VAT registration and platform rules will change, among other things. From 1 July 2030, digital reporting obligations for intra-EU B2B transactions become more prominent and e-invoicing comes more clearly into view. By 1 January 2035 at the latest, existing national domestic reporting systems must align with the European standard. The precise impact in each case depends on your transaction flows, countries and existing systems.

Use 2026 and 2027 to map your impact. These years are meant for assessing where your biggest gap lies. Some organisations primarily have a data and master data problem. Others mainly struggle with local exceptions, ERP customisation or a filing process that no longer matches how transactions actually flow through the organisation.

ViDA does not necessarily require a large multi-year programme. It does require a sober inventory of what is currently too fragile to keep running under digital reporting.

What this affects

The impact sits mainly in the chain around VAT data

Many organisations look at ViDA first through the lens of invoice formats or local reporting requirements. That is logical, but too narrow. In practice, the real impact begins much earlier: in master data, document flows, tax codes, transaction types, references between source and output data, and the question of whether your organisation spots errors early enough. Digital reporting does not make those weak points larger, but it does make them more visible and less forgiving.

A workable ViDA approach is therefore usually multidisciplinary. Tax, finance, ERP, reporting and business operations need to share the same understanding of what a transaction is, which data is mandatory and where the control takes place. Without that foundation, there is a risk that teams work in parallel: a technical project here, a tax review there, and a local workaround as soon as the deadline draws near.

A good roadmap does not need to be complicated. It mainly needs to make clear which countries or flows you look at first, which minimum dataset you need and where you consciously opt for a proof-of-concept before rolling out further. That lowers risk and prevents ViDA from turning into a collection of disconnected initiatives.

Practical route

Start with an impact assessment that is usable in practice

The best first step is usually not a target architecture, but a short impact assessment across countries, data and processes. Which intra-EU B2B flows are material? Which source data is currently not stable enough? Where are there manual intermediate steps between transaction, invoice and reporting? Once that picture is in place, you can decide much more effectively whether to clean up data first, run a pilot in one country or strengthen your governance.

Practical tips

To approach ViDA in a manageable way, these steps help:

  • Work with a limited set of priority countries or transaction flows rather than trying to complete an EU-wide inventory straight away.
  • For each priority flow, map which data is currently missing, unreliable or available too late.
  • Record which teams own source data, invoicing, VAT review and final reporting, so that gaps become visible.
  • Choose one proof-of-concept that genuinely touches both tax and ERP; otherwise ViDA remains a paper roadmap.
  • Reassess the timeline periodically, because national implementation and local obligations may run alongside the European main line.

Want to make your ViDA impact concrete?

We help you determine where the pressure in your landscape is greatest and which route makes sense for data, controls and reporting.

Schedule a ViDA session