The e-invoicing rulebook keeps moving — and why “always current” is the point

Electronic invoicing looks, from the outside, like a solved problem: pick a format, embed the XML, done. From the inside it is a moving target. The semantic model, the national usage rules and the legal mandates are all maintained on their own schedules — and they do not pause for your integration. Here is the state of play in mid-2026.

Germany: the mandate is phasing in

Since 1 January 2025 every domestic B2B business in Germany must be able to receive a structured e-invoice — no exceptions, no turnover threshold. The obligation to issue them is phasing in over the following years, with turnover-based thresholds and a transition window for legacy EDI. The practical takeaway: the receiving side is already mandatory, and “we’ll deal with issuing later” has a shrinking runway.

France: a reform on its own timeline

France is rolling out its own reform built around accredited platforms (the Plateformes de Dématérialisation Partenaires). Receiving capability and the first issuing obligations land in 2026, with smaller businesses following later. Same EN 16931 foundation, different national plumbing — which is precisely why Factur-X and the platform model matter there.

EU level: ViDA sets the long arc

VAT in the Digital Age (ViDA) is the EU package that makes structured e-invoicing and near-real-time digital reporting the default for cross-border B2B over the coming years. It is the reason national mandates are converging rather than fragmenting: they are all steering toward the same destination. The dates are far out, but the direction is settled.

The formats themselves keep versioning

Underneath the law, the specifications move too. ZUGFeRD/Factur-X ship new revisions; XRechnung publishes new versions of its CIUS with adjusted rules; the EN 16931 rule set and its validation artefacts get maintenance releases; Peppol tightens its interoperability testing. Each of these can turn a document that validated last quarter into one that a receiver now flags.

Why this is the whole argument for “always current”

Tracking all of that is real, ongoing work: reading changelogs, updating Schematron rule sets, re-testing against the official validators, and re-checking the edge cases — intra-EU supplies, credit notes, exemption codes, early-payment discounts — every time a spec moves. For a single company, that is a distraction from actually running the business.

This is the part eunormia takes off your plate. The validation gate is kept in step with the current PDF/A, EN 16931, XRechnung and country-specific rule sets, and the same updated gate stands behind the web tool, the API and the offline SDK. You integrate once against a stable interface; the moving parts stay on our side. When the rulebook shifts — and it will again — your invoices keep passing, because keeping up is the product.