What is EN 16931?
EN 16931 is the European standard for the core semantic data model of an electronic invoice. It describes business information and rules so parties can interpret invoice data consistently. It is closely connected to Directive 2014/55/EU on electronic invoicing in public procurement.
The standard does not mean that every invoice in Europe uses one identical file or travels over one network. Implementation involves a syntax binding, validation rules and sometimes a more specific profile or national arrangement.
Semantic model, syntax and delivery are separate
The semantic model answers “what does this information mean?” A syntax answers “how is it encoded?” The European Commission identifies UBL 2.1 Invoice and UN/CEFACT Cross Industry Invoice (CII) as supported XML message syntaxes for carrying the core model. A delivery network or portal answers a different question: how does the message reach the recipient?
| Layer | It determines | It does not determine by itself |
|---|---|---|
| EN 16931 semantic model | Core business terms and their relationships. | A universal transport route. |
| Syntax binding | Where the terms appear in a supported message format. | The recipient address or operational status. |
| Profile or local rules | Additional constraints for a particular use case. | A general obligation for every business transaction. |
| Exchange route | How a file reaches the receiving party. | Whether all invoice content is valid. |
What does the EU public procurement directive require?
The Directive addresses electronic invoicing in public procurement. The European Commission explains that public authorities must be able to receive and process compliant e-invoices for contracts within the Directive's scope. That is a receiver-side requirement in a particular context; it must not be turned into a blanket claim that every supplier or every domestic B2B sale has the same obligation.
For an actual transaction, check the applicable procurement rules, national implementation, buyer instructions and current technical documentation. The B2B and B2G comparison helps keep these contexts separate.
What is a profile or CIUS?
A Core Invoice Usage Specification (CIUS) can constrain use of the core model for a particular community while remaining within the standard's compliance framework. Profiles and country-specific validation may further shape the implementation. The right question is not simply “Does this file say EN 16931?” but “Does it meet the exact specification and recipient rules for this exchange?”
Where does Peppol fit?
Peppol is one possible ecosystem for specifications and exchange. Peppol BIS Billing 3.0 describes a billing profile and its rules; the European standard and a transport network are not interchangeable names. A buyer may specify Peppol, another channel or a national platform. Confirm the actual route and current version with the recipient.
The field and validation guide provides a practical way to map the semantic terms into an implementation.
How to use the standard responsibly
Identify the transaction and recipient, read the relevant standard and profile, obtain accepted test cases, validate both file and business content, then test delivery and rejection handling. Use the European Commission's documentation as a starting point and the appropriate national authority for local obligations. Avoid relying on an old summary for current mandate dates or exceptions.
Related guides
- Invoice data fields and validation — A practical field map and validation framework for structured invoice implementation.
- B2B and B2G invoicing — Understand how buyer type changes e-invoicing research, obligations and implementation choices.
- Structured invoice vs PDF — Compare a human-readable PDF with machine-readable invoice data, including hybrid documents and OCR.
Primary sources and further reading
These official resources support the standards and regulatory context. Check their current versions before implementation.
- European Commission: European legislation on eInvoicing ↗ — Directive 2014/55/EU and the European standard
- European Commission: Compliance with the eInvoicing standard ↗ — Semantic model and UBL/CII syntax bindings
- European Commission: eInvoicing in public procurement ↗ — Public procurement scope and receiver obligations
- European Commission: eInvoicing country factsheets ↗ — Country-level research starting point