EU E-Invoicing Mandates 2026: Compliant ≠ Automated

TL;DR: 2026 is the year e-invoicing stops being optional in Europe. Belgium went live in January, Poland in February and April, France requires every business to be able to receive from 1 September. Vendors are selling you compliance: a certified platform, the right XML format, a green checkmark. That gets the invoice into your building in a machine-readable form. It does not code it, match it, approve it, or post it. Compliance removes the typing. The rest of accounts payable is exactly where you left it.

What actually changes in 2026

Four separate national systems, one direction of travel:

Country	Date	What kicks in
Belgium	1 Jan 2026	All VAT-registered businesses issue and receive structured B2B invoices via Peppol. Big-bang, no phasing.
Poland	1 Feb / 1 Apr 2026	KSeF mandatory: large taxpayers (>PLN 200M) in February, everyone else in April. Invoices clear a central government system. Penalties suspended through 2026.
France	1 Sep 2026	Every VAT-registered business must be able to receive. Large and mid-sized businesses must also send. SMEs send from Sep 2027.
Germany	Already / 2027	Receiving mandatory since Jan 2025. Sending phases in from 2027 (>€800k turnover) and 2028 (all).
EU-wide	2030	ViDA: intra-EU B2B on standardised formats with digital reporting.

Two details in that table do most of the damage in planning meetings.

Receiving is mandated before sending. The French date most businesses have circled is 2027, when SMEs must issue e-invoices. But 1 September 2026 applies to everyone — if you're VAT-registered in France, your suppliers may legally send you a structured invoice from that date and you must be able to take it. Your issuing deadline is not your readiness deadline.

Poland's invoices don't exist until the state says so. Under KSeF an invoice acquires legal force when the central system accepts it, not when your supplier sends it. That is a different mental model from Peppol's four-corner exchange, and it changes what "we received the invoice" means in your own records.

The pitch you're being sold

Search any of these mandates and you get the same page from a dozen tax-technology vendors: timeline, formats (UBL, CII, Factur-X, all EN 16931), pick a certified platform, avoid penalties. It's accurate and it's necessary. It is also a remarkably small slice of the problem.

Because here is what the compliance layer delivers on the morning of 1 September: a valid structured invoice, correctly formatted, legally transmitted, sitting in your system.

And then nothing else happens.

What a mandate does not do

Read a supplier invoice and list what your team does with it. Extraction — reading the number off the page — is one step. Here's the rest, and none of it is addressed by any mandate in the table above:

• Coding. Which cost centre, which GL account, which project. The XML tells you the amount; it has no idea it belongs to the Rotterdam warehouse renovation budget.
• Matching. Does this invoice agree with the purchase order and the goods receipt? Structured data makes the comparison easier to execute and does nothing about the 20–40% that don't cleanly match — partial deliveries, unit-of-measure mismatches, price drift.
• Approval routing. Who signs off, at what threshold, and what happens when they're on holiday.
• Duplicate and fraud checks. A perfectly valid Factur-X file is a perfectly valid vehicle for a second copy of an invoice you already paid, or a supplier bank detail that changed last week for reasons nobody verified.
• Exception handling. The part that actually consumes the afternoon.

A mandate converts a PDF into structured data. That is genuinely useful — it's the step that AI document processing existed to solve, handed to you for free by legislation. But if extraction was the only thing standing between you and a touchless AP process, you'd have solved this in 2015 with a decent OCR licence. It wasn't, and you didn't.

The uncomfortable version: mandates will make the rest of your AP workload more visible, not smaller. When the data-entry excuse disappears, what's left is the approval bottleneck.

The dual-channel problem nobody plans for

Here's the operational reality that the compliance pages skip.

Mandates cover domestic B2B transactions in the countries that have them. They do not cover:

• Suppliers outside the EU
• Out-of-scope entities and transactions
• Expense receipts
• Delivery notes, packing slips, pro forma invoices, statements
• Anything from a supplier who is technically compliant but sends the PDF copy to your AP inbox anyway, because that's what they've always done

So from 2026 your AP function runs two channels at once: a structured feed from your certified platform, and the same unstructured mess of emailed PDFs and scans you have today. This lasts years. A business buying from Belgium, Poland, France, the UK, Turkey and China in 2026 is receiving invoices under four different regimes and two different formats simultaneously.

The failure mode is predictable and expensive: you buy an e-invoicing platform for the compliant channel, keep the manual process for everything else, and now you have two AP processes, two sets of rules, two audit trails, and no single view of what you owe. The compliance project reports success. The finance team is doing more work than before.

Whatever handles your invoices needs to sit above both channels — taking structured XML and a photographed receipt to the same coding, matching and approval logic, and reaching the same ledger. That's an AP process design question, not a tax-technology purchase.

What to do before your date

1. Confirm receiving, not just sending. Check the earlier of the two dates for every country you're VAT-registered in. For France that's 1 September 2026, regardless of your size.

2. Map both channels. Which suppliers will arrive structured, which won't, and roughly what share of volume each represents. This number determines how much of your current AP process the mandate actually retires — usually far less than expected.

3. Audit what happens after receipt. Take fifty recent invoices. For each, count the human touches after the data was captured. Every one of those survives the mandate. That list is your real automation backlog.

4. Don't let the compliance vendor scope your AP project. They're solving transmission and format validation, which is their job and which they do well. Coding, matching, approvals and exceptions are a different problem with a different owner.

5. Use the grace periods. Poland has suspended penalties for all of 2026 — that's a full year to get the operational side right while the compliance side can't hurt you.

How OIDO fits

OIDO doesn't replace your certified platform and doesn't want to be your Peppol access point — that's a solved, regulated, commoditised layer. It handles the part that starts after the invoice arrives, from either channel.

The agent picks up invoices from your inbox and from your structured feed, reads whatever format they arrive in, codes them against your chart of accounts, pulls the matching PO and goods receipt from the ERP you already run, resolves routine variances inside tolerance rules you set per supplier, and posts the result back — your ledger stays the source of truth. Genuine exceptions go to a named approver with the discrepancy already explained, which is human-in-the-loop doing what it's for: a person sees the 5% that needs judgment, pre-analysed, instead of the 100% that needs eyes.

The dual-channel point is the practical one. One process, one set of approval rules, one audit trail, whether the invoice came through a certified platform as Factur-X or landed as a phone photo from a supplier who has never heard of EN 16931. See the invoice processing use case for how it runs end to end, or how AI invoice processing works for the pipeline underneath it.

The bottom line

The 2026 mandates are real, the dates are close, and you should absolutely be compliant — the penalties and the inability to transact are not theoretical. But treat compliance as what it is: a format change that hands you clean input data. It's the floor, not the project.

The businesses that get something out of 2026 will be the ones who use the mandate as the trigger to look at what their finance team does after the invoice arrives — because that work was never about reading the document, and no legislature is going to automate it for you.

Sources: European Commission — eInvoicing country factsheets, EY — Poland KSeF timeline, Sovos — E-invoicing in France.