The EU built a single market. It forgot to agree on what a compliant invoice looks like.

Here’s a number worth sitting with: €128 billion.

That’s the EU VAT compliance gap in 2023, the difference between what member states should have collected and what they actually did, according to the European Commission’s Mind the Gap report1 . Not all of it is fraud. A significant chunk is administrative error, system incompatibility, and the quiet chaos of cross-border document flows that nobody designed to work together.

The EU has one currency for most of it, open borders, harmonized trade rules. But ask a finance team processing invoices across Germany, France, Italy, and Poland what “compliant” means in 2026, and you’ll get four different answers. Five if they have a Belgian supplier.

That’s not a minor headache. It’s a structural problem that’s getting more complicated before it gets simpler.

What’s actually happening right now

The e-invoicing mandate wave is real and overdue. The way it’s rolling out is something else, regulatory fragmentation dressed up as harmonization.

Germany requires mandatory e-invoice receiving since January 2025, with mandatory sending phased from 2027, supporting XRechnung and ZUGFeRD formats. France goes live September 2026 with a hybrid Y-model, either through the government’s Portail Public de Facturation or certified private platforms. Belgium went full B2B mandatory on January 1, 2026 via Peppol, no phasing, no grace period. Poland launched KSeF in February 2026, a clearance model where invoices must be validated by the tax authority before they’re legally valid. Italy has been running FatturaPA XML through its SdI state platform for years, and anything arriving in a different format still needs conversion before it’s accepted.2

Each of these is a legitimate national implementation of the EU’s EN 16931 standard. Each of them is also, in practice, subtly incompatible with the others. A structured invoice that’s perfectly compliant in Belgium doesn’t arrive as a valid document in Italy without format conversion. A German ZUGFeRD file and a French Factur-X file are both technically EN 16931 compliant. They are not the same thing.

This is not a future problem finance teams can schedule for later. AP (Account Payable) workflows that were built for one country, ERPs configured before real-time clearance models existed, IT departments still catching up to mandates that went live months ago, that’s the actual situation in most cross-border finance operations right now.

The cost nobody puts in the business case

The compliance conversation tends to focus on fines and deadlines. Belgium has penalties up to €5,000 for repeat non-compliance3 . Poland’s KSeF assigns a unique ID to every validated invoice, no ID means the invoice doesn’t legally exist. Real stakes.

But the cost that never appears in any compliance budget is the operational weight of running parallel document workflows. When an AP team handling invoices from five EU countries routes each one differently, different format, different network, different validation logic, different archiving rule, the manual intervention layer doesn’t go away. It just becomes part of how the team operates. It gets absorbed into headcount and processing time that nobody tracks because nobody formally decided to build it.

That’s where the actual business case for intelligent document processing sits. Not in a compliance deck, but in the quiet accumulation of workaround hours that finance teams are logging without realizing it. The ability to take fragmented, format-inconsistent document inputs and normalize them into something a downstream system can use, regardless of origin country or format, is what the mandate wave is making visible, not creating. Companies like *IRIS have been building this normalization and extraction capability across formats and geographies for years.* The regulatory pressure just made the gap harder to ignore.

The ViDA promise and what it leaves open

The EU’s VAT in the Digital Age initiative (ViDA, adopted in March 2025, is the right long-term answer. It’s designed to replace fragmented national systems with a harmonized real-time reporting framework, with Peppol as the universal exchange standard across all member states by July 20304

Four years away. The mandates going live now aren’t waiting.

And there’s something worth paying attention to underneath the ViDA optimism: harmonization at the transport layer, Peppol as the network, doesn’t automatically solve harmonization at the content layer. Countries still define different mandatory fields, different validation rules, different archiving periods. A Peppol-delivered invoice that fails Italy’s SdI content validation is still a failed invoice, regardless of how cleanly it traveled across the network.

The mandate wave is forcing every AP and finance leader operating cross-border to answer a question they’ve been deferring: is our document infrastructure actually built for this, or are we running 2019 workflows inside 2026 compliance requirements?

Most are finding out it’s the second one…

Such question is high probably live in your organization and you will have to understand what intelligent document processing actually looks like once applied to cross-border compliance flows.

Hence why that conversation starts here with IRIS’ experts.

eInvoicing #VATCompliance #FinanceTransformation #AccountsPayable #DocumentProcessing #DigitalTransformation #Peppol #ViDA #EnterpriseFinance #IDP #IRIS #CrossBorderCompliance #FinanceLeadership

1. European Commission’s Mind the Gap Report. Source: http://taxation-customs.ec.europa.eu
2. Europe’s E-invoicing puzzle: What to know as new mandates go live. Source: http://fiskaly.com/blog/e-invoicing-mandates-in-europe-2026
3. Belgium E-Invoicing: New Penalties for Non-Compliance Effective 2026. Source: https://www.fiscal-requirements.com/news/4211
4. Europe’s shift to digital e-invoicing: What businesses need to know. Source: https://www.columbusglobal.com/insights/articles/e-invoicing-europe/#:~:text=Five%20Key%20Questions,Nordic%20companies%20have%20an%20advantage?