E-invoicing mandates across Europe: 2026 tracker

Europe is replacing the paper invoice with a live, structured data feed to tax authorities. The EU’s ViDA package sets 2030 as the horizon for mandatory e-invoicing and digital reporting on cross-border B2B transactions — but several member states aren’t waiting for Brussels.

VeriFactu timeline (updated 6 October 2026). The rule in force, Royal Decree-law 15/2025 of 2 December, sets the adaptation deadline before 1 January 2027 for Corporate Income Tax payers and before 1 July 2027 for everyone else. On 5 October 2026 Spain’s Ministry of Finance announced it will postpone the obligation to October 2028, to align it with mandatory B2B e-invoicing. That postponement has not yet been published in the BOE (Spain’s official gazette).

This is a tracker, not a forecast. It maps what’s confirmed at the EU level, what each major market has announced domestically, and where the exact dates still need checking before you build a deadline around them.

What ViDA actually mandates

ViDA — VAT in the Digital Age — is an EU legislative package adopted on 11 March 2025 (Council Directive (EU) 2025/516 and two accompanying regulations). It sets the path toward mandatory e-invoicing and digital reporting for cross-border B2B transactions across the bloc, applying from 1 July 2030.

Three things worth separating:

• The EU deadline (1 July 2030) covers cross-border B2B. It’s the backstop, not the starting gun — most member states are moving earlier for domestic transactions.
• The common data standard is EN16931. ViDA doesn’t invent a new invoice format from scratch; it builds on the semantic standard already used across EU public procurement e-invoicing.
• Domestic mandates run on their own clocks. Member states are free to require e-invoicing for transactions inside their own borders before the EU-wide deadline lands, and several already do.

That last point is the one that catches businesses off guard. “The EU mandate is 2030” is true and also not the number that matters if you invoice a client in Italy or France next quarter.

The common standard: EN16931

EN16931 is a European semantic standard. It defines what data an invoice must contain — supplier and buyer identification, line items, tax breakdown, totals — not which file format carries it. Both XML-based formats (like UBL) and hybrid formats (like Factur-X) can conform to it.

That semantic layer is what makes automated cross-border validation possible. A tax authority — or a trading partner’s system — can check that an invoice contains everything required, structurally, without a human opening a PDF.

It’s also the layer domestic mandates plug into. Italy’s SdI, Poland’s KSeF, France’s phased rollout, and the network layer described below all reference EN16931-conformant formats, even where the specific technical profile differs country to country.

Country tracker: six markets, six timelines

Status as of July 2026, with dates confirmed against each country’s tax authority or the European Commission. Timelines can still shift — Poland alone has postponed its start more than once — so re-check the official source before locking an internal deadline.

Two patterns hold across all six: receiving structured invoices tends to become mandatory before issuing them, and larger companies get shorter runways than smaller ones. The exact cutoffs are the part that keeps moving — Poland alone has delayed its own start date more than once.

Peppol’s role: the network doing the heavy lifting

Peppol (Pan-European Public Procurement Online) is a network and messaging standard, not a government platform. It uses a four-corner model: your invoicing software sends the invoice to a Peppol access point, which routes it to your buyer’s access point, which delivers it into their system.

Peppol invoices are built on EN16931-conformant formats (the Peppol BIS specifications). That’s the practical reason it keeps coming up across unrelated domestic mandates — a business connected to Peppol once can reuse that connection across multiple countries that recognize the network, instead of building a bespoke integration per country.

It isn’t universal yet. Some domestic mandates (Italy’s SdI, Poland’s KSeF) run their own national platform instead of routing through Peppol by default. Where a country accepts both, Peppol tends to be the path with the least custom integration work.

What this means if you trade across the EU today

There is no single “EU e-invoicing mode” you can switch on. Until 2030, compliance is additive: your own country’s domestic rules, plus every other country’s domestic rules for the transactions that touch them.

Concretely, if you invoice clients in Italy, France, Germany, Poland, or Belgium from Spain, each of those relationships can carry its own format and delivery requirement — independent of what VeriFactu requires for your Spanish-facing invoices.

How to get ahead of it

The pattern across every market on this list is the same: structured, machine-validated data replacing free-form PDFs and paper, moving from “recommended” to “required” one taxpayer category at a time. Where you sit on that curve depends on where your clients are, not just where you are.