France's first phase went live on 1 September. Belgium, Poland and Germany are staged around it — and they are not the same obligation. The dividing line is whether a tax authority sits inside your invoice's legal lifecycle or merely reads about it afterwards.
Three days ago, the first phase of France's e-invoicing reform took effect. Every established business in France must now be able to receive a structured electronic invoice, while the obligation to issue one applies to large and mid-sized companies, with smaller businesses following on 1 September 2027.
Most finance organisations with European operations are treating this as one item on a long compliance list — a project, an ERP upgrade, a line in next year's budget. The list framing is where the trouble starts, because the four mandates now live or imminent across Belgium, Poland, France and Germany impose structurally different obligations, and the difference is not cosmetic. It determines who your operational dependency is, what happens when something fails, and which team owns the incident at four o'clock on a Friday.
The distinction that actually matters: clearance versus network
Strip away the country labels and there are two models.
In a clearance model, a government platform is part of the invoice's legal existence. The invoice is transmitted to the tax authority's system, validated, and only then does it count as a legal document. Poland's KSeF 2.0 works this way: centralised government validation is required before an invoice is legally recognised.
In a decentralised network model, the invoice moves between trading parties over an interoperable network — usually Peppol — and the tax authority receives data about it, but the document's legal life does not pause for state approval. Belgium's mandate, which took effect on 1 January 2026, works this way, requiring all Belgian businesses to send and receive B2B e-invoices over Peppol in UBL 2.1. Germany's mandate is similarly decentralised. France sits in between, running a decentralised continuous transaction control with a separate e-reporting obligation alongside.
Under a clearance mandate, the availability of a government platform becomes an operational dependency of your revenue cycle. That is a materially different risk profile from an interoperability requirement, and it belongs on a different register.
Finance teams routinely brief both to their boards as "e-invoicing compliance". They are not comparable. One is a systems integration project. The other is an external single point of failure sitting between you and your ability to issue a valid invoice.
The four mandates, side by side
Visual 1 — Four mandates, compared by what they demand of the ERP
Market | Dates in force | Model | Format | What the ERP must do |
|---|---|---|---|---|
Belgium | 1 January 2026 (live) | Decentralised, Peppol | UBL 2.1 | Send and receive structured invoices over an interoperable network; hold a Peppol access point relationship |
Poland | 1 February 2026, taxpayers above PLN 200m turnover; 1 April 2026, all VAT-registered (live) | Clearance, KSeF 2.0 | FA(3) | Submit to a state platform and handle the returned status; treat validation failure as a blocking revenue event |
France | 1 September 2026, receiving for all + issuing for large and mid-sized; 1 September 2027, issuing for SMEs and micro-businesses | Decentralised CTC with e-reporting | UBL, CII, Factur-X | Receive on day one regardless of size; support three formats; meet a separate transaction-reporting obligation |
Germany | Receipt capability since 1 January 2025; issuing from 1 January 2027 above €800,000 turnover, all businesses from 1 January 2028 | Decentralised, Peppol-capable | Structured formats (EN 16931-conformant) | Accept structured invoices already; build issuing capability against a turnover threshold that will catch mid-market entities in 2027 |
How to read it: The final column is the project scope. Note that in three of the four markets the receiving obligation lands before, or independently of, the issuing obligation — which puts the earliest deadline on accounts payable, not accounts receivable.
The receiving obligation is the one that gets missed
There is a consistent pattern across the timetable, and it runs against how these programmes are usually staffed.
Germany required businesses to be able to accept structured invoices from 1 January 2025, two full years before most of them must issue one. France made receiving universal from 1 September 2026 while staging issuing by company size. Belgium requires both capabilities from the same date. In three of four markets, the obligation that arrives first is the one that lands on accounts payable.
Yet e-invoicing programmes are almost always sponsored by the order-to-cash side, because issuing is where the visible penalties and the customer-facing change sit. AP gets a workstream, usually late, usually under-resourced. The failure mode is quiet and expensive: invoices arriving in a structured format that the AP system cannot parse, being manually re-keyed or rejected, and a supplier ledger that drifts out of agreement with the counterparty's AR ledger — reconciliation debt created by a compliance project.
The second under-scoped item is master data. Structured formats are unforgiving in a way PDFs never were. A missing VAT identifier, an unmapped unit of measure, a tax code that exists in your chart but not in the schema — under a post-audit regime, these produced a query weeks later. Under clearance, they produce a rejection now, and an invoice that legally does not exist.
Questions worth asking before the 2027 wave
Which of our entities fall under a clearance model, and have we put the state platform's availability on the operational risk register? It is a dependency of revenue recognition, not an IT service.
Can accounts payable actually consume a structured invoice today, or does it convert to PDF and re-key? Germany's receipt obligation has been in force since January 2025; the answer is testable now.
Who owns format coverage? France alone accepts UBL, CII and Factur-X. Supporting one is not supporting the mandate.
Where does the German €800,000 turnover threshold place each of our entities as at 1 January 2027, and does that assessment get revisited if turnover moves?
Is master-data cleansing scoped as part of this programme, or has it been assumed away? Under clearance, data quality becomes a revenue control.
What this changes
For finance organisations planning 2027 budgets this quarter, the practical move is to stop treating the mandates as a single compliance line and split them by model. The clearance markets need an availability and exception-handling design, an owner on the risk register, and a documented answer to what happens when the state platform is unavailable during month-end. The network markets need integration and format coverage, which is ordinary systems work with an ordinary systems owner.
Both need accounts payable involved considerably earlier than it usually is. France's phase one is three days old and has already made receiving the universal obligation. Germany's issuing wave lands in sixteen months, and its threshold will catch a large tranche of mid-market entities that have so far treated the mandate as a large-company problem.
Sources and method. A FinancyHub original. Mandate dates, models and formats for Belgium (1 January 2026, decentralised Peppol, UBL 2.1), Poland (KSeF 2.0 clearance; 1 February 2026 for taxpayers above PLN 200 million, 1 April 2026 for all VAT-registered; FA(3)), France (1 September 2026 phase one, 1 September 2027 phase two; decentralised CTC with e-reporting; UBL, CII and Factur-X) and Germany (issuing from 1 January 2027 above €800,000 turnover, all businesses from 1 January 2028; decentralised, Peppol-capable) per Novutech's overview of European mandates 2025–2027. Germany's receipt obligation from 1 January 2025 per ADVISORI. The clearance-versus-network framing, the accounts-payable observation and the diagnostic questions are FinancyHub's own analysis. Mandate timetables have been revised repeatedly across this programme; verify current dates with your tax adviser before acting. Journalism, not procurement or tax advice. Corrections will be made openly on this article.
