EN 16931
EN 16931 is the European standard defining the semantic data model—the business terms and rules—for the core elements of an electronic invoice. It describes what invoice information means, not a single file format or delivery network. Syntax bindings map that model into formats such as UBL 2.1 and CII, while national or sector profiles can add controlled requirements.
The 2026 edition is in migration
The European Commission reports that EN 16931-1:2026 was published in May 2026. The 2017 edition has been formally withdrawn but remains compliant during migration while authorities and standards bodies establish their transition plans.
Confirm which edition, syntax and profile the recipient or relevant authority currently requires. This status was reviewed on 3 September 2026 and may change.
Why this matters when you invoice
EN 16931 gives systems a shared meaning for core invoice data such as seller and buyer identifiers, invoice lines, totals, VAT information, dates and payment details. The semantic model helps different software understand the same business concepts even when an accepted syntax carries them differently.
Model, syntax, profile and delivery are separate layers
- Semantic model: EN 16931 defines the meaning and core rules.
- Syntax: a binding represents that meaning in a technical format such as UBL 2.1 or CII.
- Profile: a CIUS or other specification can select or add controlled requirements for a use case.
- Delivery: the sender still needs a route the recipient accepts.
One business meaning, different technical layers
An invoice can express a due date as an EN 16931 business term and carry that value in a UBL XML element. A buyer may also require a particular profile and delivery network. Meeting only the UBL file structure does not establish that every semantic, profile, code-list or delivery requirement has been satisfied.
Common mistakes
- Calling EN 16931 a single XML file format.
- Assuming a syntactically readable file is compliant with all business rules.
- Treating EN 16931, UBL and Peppol as interchangeable names.
- Ignoring a recipient's national profile, identifiers or delivery requirements.
Create or inspect EN 16931-oriented XML
InvoiceCraftly can export an EN 16931 / UBL XML invoice file in beta when the required invoice details are ready. You can also use the XML viewer to inspect supported invoice XML, mapped business fields and deterministic preflight findings.
The export does not by itself establish formal EN 16931, Peppol, national-profile, or recipient compliance. Peppol, EHF, NemHandel, and other network delivery remain separate steps through a compatible service or network.
Official references
- European Commission — European Standard and Specifications
- European Commission — EN 16931 compliance
Sources and terminology reviewed 3 September 2026. Next evidence review: 2 December 2026.
Frequently asked questions
Is EN 16931 an XML format?
No. EN 16931 defines invoice meaning and business rules. Official syntax bindings map that semantic model into formats including UBL 2.1 and CII.
Can the 2017 edition of EN 16931 still be used?
The European Commission reports that EN 16931-1:2017 is formally withdrawn but remains compliant during migration to the 2026 edition. Confirm the applicable timetable with the recipient or relevant authority.
Can InvoiceCraftly export EN 16931 invoice data?
InvoiceCraftly can export an EN 16931 / UBL XML invoice file in beta when the required invoice details are ready. The export does not by itself establish formal compliance, recipient acceptance, or network delivery.