The EU E-Invoicing Mandate: What ViDA Means for You

If your finance team still emails PDF invoices and calls that "electronic invoicing", the next few years are going to feel abrupt. The EU's VAT in the Digital Age package, ViDA, was adopted in March 2025 and is now rolling out country by country. A PDF is a picture of an invoice. What ViDA wants is a structured data file a machine can read, validate and report to a tax authority in near real time. Those are very different things, and the gap between them is where most businesses will get caught.

The headline for planning: cross-border B2B transactions inside the EU move to mandatory structured e-invoicing and digital reporting by July 2030. That sounds far off, but the national deadlines that actually hit your systems arrive much sooner. Belgium started requiring domestic B2B e-invoicing in January 2026, Poland follows in 2026, France's mandate phases in from September 2026, and Germany is on a 2027 to 2028 track. If you trade in more than one member state, you are already inside somebody's timeline.

What ViDA actually changes

ViDA is built on three pillars, and only one of them is the invoice format everyone talks about.

• Digital reporting and e-invoicing. Structured e-invoices become the norm, and their data gets reported to tax authorities close to real time rather than in a periodic return. This is the pillar that touches your ERP, your accounting software and any billing integration you run.
• The platform economy. Online platforms for short-term accommodation and passenger transport take on a "deemed supplier" role for VAT, collecting and remitting it themselves. If you run a marketplace, this is your pillar.
• Single VAT registration. The One Stop Shop expands so you can handle more cross-border obligations under one registration instead of registering in every country you sell into. This is the pillar that actually makes life easier.

The through-line is that VAT reporting stops being a document you file and becomes a data stream you emit. Once you see it that way, the technical work is obvious: your systems have to produce clean, structured transaction data on demand, not reconstruct it from spreadsheets at quarter end.

The timeline that matters to your systems

The EU-level cross-border deadline is July 2030, but you should plan against national mandates because those come first and they are not optional where you operate.

The pattern in every country is the same: the largest companies go first, smaller ones get a grace period, and PDF-based "e-invoicing" is tolerated only until a hard cutoff. Relying on that grace period is a bet that your smallest customers and suppliers will not move faster than you, and plenty of them will, because their other trading partners force them to.

Structured formats, not prettier PDFs

The standard underneath all of this is EN 16931, the European semantic model for an electronic invoice. In practice you will meet it through formats like UBL or CII, often exchanged over the Peppol network. The important shift is conceptual: an e-invoice under ViDA is a dataset with defined fields, buyer and seller identifiers, line items, tax categories, totals, that a machine validates against rules before it is ever accepted.

This is also why the compliance cost is really an integration cost. Generating a valid structured invoice, transmitting it over the right network, receiving structured invoices from suppliers, and feeding the reporting data to the tax authority are all points where your systems have to talk to something outside your walls. Businesses running modern, API-first accounting stacks will bolt this on. Businesses running a patchwork of legacy tools and manual steps will feel it.

Why this is worth doing, not just enduring

It is easy to file ViDA under "regulatory burden", but the economics behind it are genuinely large. The Commission expects e-invoicing and digital reporting to cut VAT fraud by up to 11 billion euros a year and to reduce administrative and compliance costs for EU traders by over 4 billion euros a year across the next decade. That saving is real for you too. Structured invoicing kills a category of manual data entry, cuts the errors that trigger disputes, speeds up reconciliation and shortens the time from invoice to payment.

The businesses that treat this as an accounting-automation project rather than a box-ticking exercise come out ahead. You are going to touch these systems anyway. Touching them once, deliberately, to produce clean structured data end to end is far cheaper than bolting on a compliance patch now and re-doing it when the next national deadline lands.

How to prepare this year

You do not need a 2030 project plan today. You need to know where you stand and remove the obvious blockers.

• Map where you trade. List every EU country you invoice in or receive invoices from, and check each one's national e-invoicing timeline. Your earliest national deadline is your real deadline.
• Audit your invoice flow. Trace an invoice from creation to delivery. If it becomes a PDF at any point and stays one, note that as a gap.
• Check your software's roadmap. Ask your ERP or accounting vendor what they support for EN 16931, Peppol and digital reporting, and when. If the answer is vague, that is a signal.
• Fix the data, not just the format. Structured reporting exposes messy master data instantly. Clean customer tax IDs, product codes and tax categories now, while it is a housekeeping task and not a compliance failure.
• Plan the integrations. The work is in the connections between your billing system, the exchange network and the tax authority. Scope those early.

If you would rather have someone map your invoice flow, check your stack against the national deadlines and build the integrations so structured invoicing just works, that is the kind of project we take on. The deadline that matters is not 2030. It is whichever country you trade in that moves first, and for many businesses that clock has already started.