Mandatory E-Invoicing in Europe: What Is Actually Obligatory
E-invoicing in Europe explained: the EU requirements and regulations, when e-invoicing becomes mandatory, and which national law actually obliges your business.
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.
E-invoicing in Europe explained: the EU requirements and regulations, when e-invoicing becomes mandatory, and which national law actually obliges your business.
EN 16931 explained: the European e-invoicing standard's semantic model, its two syntax bindings and its validation rules, and what it deliberately leaves open.
The four-corner and five-corner models are the two architectures of European e-invoicing. How each routes an invoice, who sees it first, and where each one fails.
The ViDA digital reporting requirements explained: what the VAT in the Digital Age directive changes for intra-Community trade, national regimes and the invoice.
Authenticity of origin, integrity of content and legibility: what the VAT Directive requires of every invoice from issue to the end of retention, and how to prove it.
An e-invoicing readiness assessment worked in the order the answers bind: scope, documents, data, systems and the receiving side, ending in a defensible cost range.
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's B2B e-invoicing mandate has applied since 1 January 2026: structured invoices between Belgian businesses over an existing network, with no state platform.
Since 1 January 2026, VAT-registered Croatian businesses issue and receive eRačun and report each one to the Tax Administration. Who is in scope, the deadlines and 2027.
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 EU e-invoicing directive, 2014/55/EU, obliges public bodies to accept invoices built to EN 16931 but obliges no supplier to send one. What it requires, and from when.
France's e-invoicing reform applies from September 2026: licensed platforms carry the invoice, and a separate e-reporting duty catches what invoicing does not.
Germany's B2B e-invoicing mandate: every business has had to receive structured invoices since 2025, issuing follows in stages to 2028, and there is no central platform.
Greek businesses with 2023 revenue up to €1m must e-invoice from 2 November 2026, with a transition to 31 January 2027. What changes, and the route through myDATA.
Italy's SdI exchange system has cleared domestic B2B invoices longer than any system in Europe. How it works, what an SdI code is, and what is still difficult.
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.