EN 16931 is a European standard that specifies a core semantic model for electronic invoices. It does not dictate a single file format; it defines the meaning of the information an invoice carries, so that different technical syntaxes can express the same content without ambiguity.
National and network formats are built on top of it. XRechnung and ZUGFeRD in Germany, Factur-X in France and Peppol BIS Billing on the Peppol network all implement EN 16931, which is why an invoice created under one can be understood under another. The standard is the reason a European e-invoice is portable at all.
Why It Matters
EN 16931 is the common denominator that stops national e-invoicing mandates fragmenting into incompatible systems. EU legislation points at it as the reference standard for digital reporting later this decade, and existing national systems are expected to converge on it. For a business, the practical significance is that choosing software aligned with EN 16931 is a hedge: it keeps you compatible with whichever national flavour your customers or your regulator eventually require.
Example
A German supplier sends a ZUGFeRD invoice; a Belgian buyer receives it as Peppol BIS Billing. The syntax differs, but both express the same EN 16931 semantic fields — so "total amount including VAT" means the same thing in both, and the buyer’s system maps it without a bespoke integration.
Frequently Asked Questions
Is EN 16931 a file format?
No. It is a semantic model — a definition of what fields an invoice has and what they mean. Formats such as UBL and CII are the syntaxes used to write those fields down, and national specifications narrow the options further.
Does my invoice have to comply with EN 16931?
Only where a mandate or a customer requires structured invoicing under a specification built on it. If you are not subject to an e-invoicing mandate and your customers accept PDFs, it does not currently apply to you.