Key takeaways
- EN 16931 is the European standard that defines the semantic model of an e-invoice: the information it contains, not its layout.
- It stems from Directive 2014/55/EU, and its reference was published in the Official Journal of the European Union in 2017.
- The standard is syntax-neutral: two syntaxes are recognised as compliant, UBL 2.1 and UN/CEFACT CII.
- Profiles such as Peppol BIS Billing 3.0 are specialisations of this standard, not competing formats.
The EN 16931 standard, the common ground of the European e-invoice
Behind every structured e-invoice that travels across Europe lies the same reference: the EN 16931 standard. It sets out what an e-invoice must contain so it is understood the same way from one country to another and from one piece of software to another. Understanding this standard means understanding the layer that UBL 2.1, public-procurement invoicing and the Peppol profile used in Belgium all rest upon.
The standard did not emerge from an isolated technical choice. It answers Directive 2014/55/EU, which called for a common European standard on electronic invoicing for public procurement. CEN, the European standardisation body, developed it, and its reference was published in the Official Journal of the European Union in 2017.
This article describes what the standard actually defines, what it leaves open, and how it fits together with the formats you meet day to day.
What the EN 16931 standard actually defines
The core part of the standard, EN 16931-1, describes the semantic model of the core elements of an electronic invoice. In other words, it establishes the ordered list of information an invoice must or may carry: identification of the parties, dates, order references, invoice lines, VAT breakdown, monetary totals and payment terms.
Each piece of information carries a unique, stable identifier. The data is grouped into business groups (BG) and business terms (BT), and a set of business rules (BR) checks their consistency — for example that a total matches the sum of the lines. It is this shared structure that lets two different systems read the same invoice without a prior arrangement.
The three levels to distinguish
The semantic model (EN 16931)
What information the invoice contains and what it means. Neutral with respect to the technology.
The syntax (UBL 2.1 or UN/CEFACT CII)
The XML grammar that expresses that model in a file actually exchanged.
The profile (CIUS, e.g. Peppol BIS Billing 3.0)
A specialisation of the standard for a precise exchange context, with its own rules.
A syntax-neutral standard: UBL 2.1 and CII
The most misunderstood point is that the standard does not fix a single XML format. EN 16931 is syntax-neutral: it describes a model, then points to syntaxes able to express it. Two syntaxes are recognised as compliant: UBL 2.1 and UN/CEFACT CII.
In practice, the same EN 16931-compliant invoice can exist in two different writings while carrying exactly the same information. On the ground, UBL 2.1 dominates invoicing on the Peppol network; the structure of that file is detailed in The UBL 2.1 format explained.
compliant syntaxes
UBL 2.1 and UN/CEFACT CII
reference published in the OJEU
following Directive 2014/55/EU
core part
the semantic model of the core elements
Standard, syntax and profile: who does what
The most common confusion puts the standard, the syntax and the profile on the same footing, when they actually form a stack. The standard defines meaning; the syntax writes it; the profile narrows and completes it for a given use. The table below places each role.
| EN 16931 standard | Profile (Peppol BIS Billing 3.0) | |
|---|---|---|
| Defines the meaning of the invoice information | ||
| Mandates a single syntax (UBL 2.1) | ||
| Adds validation rules for a given network | ||
| Stays neutral with respect to the exchange channel |
This mechanism has a name in the standard: the Core Invoice Usage Specification (CIUS). A profile such as Peppol BIS Billing 3.0 is a CIUS of EN 16931: it invents nothing, it narrows the choices left open and adds its own rules. An invoice compliant with the profile stays, by construction, compliant with the standard.
From the standard to the Belgian mandate
The EN 16931 standard imposes nothing by itself: it is the texts that refer to it that create obligations. Directive 2014/55/EU first required public buyers across the Union to be able to receive and process e-invoices compliant with the standard. The momentum now extends to B2B: in Belgium, the obligation to issue structured e-invoices between businesses rests on this same normative foundation, through the Peppol profile.
For a business, the consequence is simple: the invoice it sends must be compliant with EN 16931, expressed in the expected syntax and validated according to the network's profile. The timeline and scope of that obligation are detailed in Peppol in Belgium: the B2B mandate on 1 January 2026.
EN 16931-compliant invoices, without handling the standard
YouInv structures your invoices according to the EN 16931 model, expresses them in UBL 2.1 and sends them over the Peppol network in a few clicks.
What it changes for your business
You do not have to read the standard or write an XML file. Compliant invoicing software applies the EN 16931 model on your behalf: it structures the data you enter, expresses it in the right syntax and checks the business rules before sending.
What changes is the criterion for choosing your tool. Issuing a PDF has nothing to do with EN 16931: only a structured file compliant with the standard is recognised as an e-invoice in the regulatory sense. When choosing or updating your solution, the first question is therefore whether it produces and receives documents compliant with EN 16931, in the syntax and profile expected on the network.
Further reading
- The UBL 2.1 format explained: the syntax that expresses the EN 16931 model.
- Peppol BIS Billing 3.0: what the format contains: the profile built on the standard.
- Directive 2014/55/EU: e-invoicing in public procurement: the text behind the standard.
The reference source is authoritative: Commission Implementing Decision (EU) 2017/1870, which published the reference of the EN 16931 standard in the Official Journal of the European Union.
What is the EN 16931 standard?
EN 16931 is the European standard for electronic invoicing. It defines the semantic model of the core elements of an invoice, meaning the list of information an e-invoice must or may contain, independently of the technical syntax used to express it.
How does EN 16931 relate to Directive 2014/55/EU?
Directive 2014/55/EU called for a common European standard on electronic invoicing for public procurement. The EN 16931 standard is the result of that request: it was developed by CEN, and its reference was then published in the Official Journal of the European Union in 2017.
Which syntaxes are compliant with EN 16931?
The standard is syntax-neutral: it describes a semantic model, not a single XML format. Two syntaxes are recognised as compliant to express it: UBL 2.1 and UN/CEFACT CII. A compliant invoice uses one of these two syntaxes.
Are EN 16931 and Peppol BIS Billing 3.0 the same thing?
No. EN 16931 is the semantic standard; Peppol BIS Billing 3.0 is a profile (a usage specification, or CIUS) built on that standard. The profile adopts the UBL 2.1 syntax and adds the rules needed to travel over the Peppol network.
Do you need to know EN 16931 to issue an e-invoice?
No. Compliant invoicing software applies the EN 16931 model for you: it structures the data you enter according to the standard and produces a valid file. You never have to read the standard or write the XML.
