The Clearance Model
Mandatory e-invoicing in Europe, read at document level
Independent analysis of mandatory e-invoicing in Europe: the national mandates and their dates, the EN 16931 model, the clearance networks, and what a finance function must change.
One anchor piece for each of the six sections. Each one links down to the analysis underneath it.
There is no single European e-invoicing mandate. There is one directive covering public procurement, a VAT directive that has just changed, and a growing set of national laws that do the real work.
A semantic model, two syntax bindings and a set of validation rules. Understanding what the standard fixes and what it deliberately leaves open is the difference between one integration and twelve.
Every European e-invoicing system is one of two shapes, and the difference decides who tells you an invoice failed, when, and whether you can do anything about it.
Three separate reforms travel under one name, and only one of them touches the invoice. This is what the reporting pillar does to intra-Community transactions and to national regimes.
The VAT Directive requires three properties of an invoice to be assured from issue to the end of retention, and leaves the method to you. What each one asserts is the point.
Scope, documents, data, systems and the receiving side, worked in the order the answers bind. Done properly it produces a cost range you can defend line by line.
The obligation, the model, the network, the reporting, the evidence and the work.
Who has to issue a structured invoice, from what date, to whom, and under which national law.
Open section 02The European semantic model, the two syntaxes that carry it, and the national profiles built on top.
Open section 03Four corners, five corners and the platforms in between: how a document actually gets delivered.
Open section 04Where the invoice data goes after it is issued, and what the tax administration does with it.
Open section 05Authenticity, integrity and legibility over a retention period measured in years, not months.
Open section 06Master data, ERP readiness, supplier onboarding and the cost model that decides the approach.
Open sectionAnalysis across all six sections, from national scope questions to what an exception queue looks like in week three.
Belgium mandated structured invoicing without building a platform, by naming an existing network as the default channel. It is the least original design in Europe and possibly the most sensible.
For a decade, a Member State that wanted to mandate e-invoicing had to ask the Council for permission. That requirement shaped every national mandate in Europe, and it has now been removed.
The first European e-invoicing law obliged public bodies to receive structured invoices and obliged suppliers to send nothing. That asymmetry is why the European standard exists at all.
France did not build one platform. It licensed many, made them the counterparty, and attached a separate reporting obligation that catches transactions the invoicing mandate does not.
Germany obliged every domestic business to be able to receive a structured invoice before obliging anyone to issue one, and it did it without building a central platform.
Italy has run mandatory business-to-business clearance longer than anyone else in Europe. The interesting part is not that it works, but which problems never went away.
Poland routes every domestic business invoice through one state system, which assigns it a number. That number, not your own numbering, is what makes the invoice exist.
Spain legislated a business-to-business e-invoicing obligation and then made it wait for an implementing regulation, while two other obligations arrived in the meantime.
Writes and edits The Clearance Model. Background in administration and finance: reading primary legislation and published technical specifications directly, and modelling what a compliance obligation costs to meet.