E-Invoicing Mandates: Who Must Switch, Where, and When

Regulators draw a hard line between an invoice that is merely digital and one that is structured. A PDF, a scanned image and a Word file all fail: a human can read them, but software cannot reliably extract the VAT number, the line items and the totals without guesswork. A structured e-invoice carries every field in defined, labelled places, so the buyer’s accounting system can book it automatically and the tax authority can validate it mechanically.

In Europe the reference point is EN 16931, the European standard that defines the semantic model — what fields an invoice has and what they mean. National formats sit on top of it: XRechnung and ZUGFeRD in Germany, Factur-X in France, FA(3) in Poland, Peppol BIS Billing 3.0 across the Peppol network. They differ in syntax but share the standard’s meaning, which is what makes cross-border interoperability possible at all.

One format deserves special mention because it confuses people: hybrid invoices such as Factur-X and ZUGFeRD are a PDF with an XML file embedded inside it. A person opens it and sees a normal invoice; a machine reads the XML. That design exists precisely so businesses can satisfy a structured-data mandate without their customers losing a human-readable document.

Every mandate answers one architectural question: does the tax authority see the invoice before or after it reaches the customer? The answer determines almost everything about how the system feels to use.

Under a clearance (or continuous transaction control) model, the invoice must be submitted to a government platform first. The platform validates it, assigns it an identifier and only then is it considered legally issued. Poland’s KSeF works this way — an invoice without a KSeF identifier is not yet an invoice. The upside is certainty; the downside is that the government platform sits on your critical path, and its downtime is your downtime.

Under a post-audit model, you exchange invoices directly with your customer in an approved structured format, and the authorities inspect later, as they always have. Belgium took this route, requiring structured invoices over the Peppol network without pre-clearance. France sits between the two, with certified private platforms handling exchange while a public portal maintains the directory and feeds data to the tax administration.

The table below summarises the reforms most likely to reach a small business trading in or with Europe. Dates and thresholds move — several of these have already been postponed at least once — so treat this as orientation and confirm against the primary sources at the foot of this page before making decisions.

VAT in the Digital Age, adopted by the Council in March 2025 and in force since that April, is the EU’s attempt to stop national mandates fragmenting into twenty-seven incompatible systems. It does two things that matter here.

First, it removed the requirement for member states to seek Commission approval before mandating domestic e-invoicing. That is the quiet change behind the current wave — countries that once needed a derogation can now simply legislate, which is why the timeline above is suddenly crowded.

Second, it sets a common destination. From July 2030, intra-EU business-to-business transactions fall under digital reporting requirements built on EN 16931, and national systems that predate 2024 have until January 2035 to converge on the same standard. The practical read for a small business is that today’s national quirks are transitional; the long-run direction is one semantic standard across the single market.

The honest answer for most people reading this is: less than the headlines imply, and later. Mandates almost universally phase in by size, and the smallest businesses come last — often a year or more after the large-company deadline. Several regimes also separate the obligation to receive from the obligation to issue, and receiving lands first because it is far easier to satisfy.

That asymmetry is the single most useful thing to understand. Being able to receive a structured invoice is usually a matter of having software or a service that can accept one; being able to issue them means changing how you produce invoices. If you trade domestically in a country with a live mandate, check the receiving obligation first — it is the one most likely to already apply to you.

Purely domestic freelancers outside the mandated countries, and anyone invoicing consumers rather than businesses, are largely untouched for now: these reforms target B2B, and in several cases B2G was already mandatory years earlier. The sensible posture is neither panic nor indifference. Know which country’s rules bind you, know your size bracket, and keep invoice data clean and consistent so that whenever your date arrives, the change is a format conversion rather than an archaeology project.