EN 16931 E-Invoice Standard
CEN (European Committee for Standardization) · Version 1.3.1 (2020)
EN 16931 is the EU's semantic data model for electronic invoices. It defines what information an invoice must contain (the "what") but not how it is represented technically. It is the semantic foundation that XRechnung, Factur-X, Peppol BIS 3.0, and UBL 2.1 all implement.
EN 16931 is the European semantic standard for e-invoicing data. It defines 52 mandatory data elements and a structured taxonomy of invoice information. Rather than specifying a file format, it defines the semantic meaning of each data field. This allows different technical formats — XRechnung, Factur-X, UBL 2.1 — to all be semantically equivalent under EN 16931. It is the backbone of the EU's interoperability framework.
Grounded in official sources listed below. Not a substitute for legal or tax advice.
Quick Answers
- 01 Is EN 16931 a file format?
- No. EN 16931 is a semantic data model — it defines what data an invoice must contain. The actual format can be XML (as in XRechnung), PDF+XML (as in Factur-X), or UBL.
- 02 Which countries require EN 16931?
- All EU countries implementing mandatory e-invoicing under the 2014/55/EU directive are required to accept invoices conforming to EN 16931.
- 03 How does EN 16931 relate to Peppol?
- Peppol BIS 3.0 implements EN 16931 as its semantic model. All Peppol-compliant invoices are EN 16931 compliant.
- 04 How is EN 16931 different from Peppol BIS Billing 3.0?
- EN 16931 defines the semantic invoice data structure — what fields an invoice must contain. Peppol BIS Billing 3.0 takes EN 16931 and adds Peppol-specific XML rules (UBL 2.1), validation constraints, and network routing. Peppol BIS 3 is a more specific implementation of EN 16931.
- 05 What does EN 16931 compliance mean in practice?
- An invoice is EN 16931-compliant when it contains all mandatory data elements (the BT codes) with correct data types. Whether an invoice is "legal" depends on the country — EN 16931 defines the data model; local mandates define what formats and data are required.
Peppol invoice format: BIS 3.0, EN 16931, and UBL explained
Search results for "Peppol format", "Peppol invoice", and "Peppol standard" often surface different terms — sometimes interchangeably. This table clarifies what each query phrase usually means and how it relates to the precise Peppol BIS Billing 3.0 specification.
EN 16931 invoice standard: semantic model, XML structure, examples, and CIUS
EN 16931 defines the European semantic invoice model — it specifies what data an invoice must contain (the "what"), not how it is transmitted or what file format to use. It is not a delivery network or routing specification. Peppol BIS Billing 3.0, XRechnung, Factur-X, and ZUGFeRD each relate to EN 16931 differently: some implement its semantics over UBL XML (Peppol BIS), some over pure XML (XRechnung), and some embed EN 16931-conformant XML inside a PDF (Factur-X, ZUGFeRD). CIUS (Core Invoice Usage Specification) allows countries or sectors to constrain EN 16931 for specific contexts. UBL and CII are the two main XML syntaxes used to represent EN 16931 data, and the examples below show how the model appears in real invoice flows.
Key Data Fields
The following data elements are central to the EN 16931 specification. Mandatory fields are required for compliance; optional fields add detail.
Invoice Header
BT-1 Invoice number Yes BT-2 Invoice issue date Yes BT-3 Invoice due date No BT-5 Invoice total amount with VAT Yes BT-6 Invoice total VAT amount Yes Seller Information
BT-27 Seller name Yes BT-28 Seller VAT identifier Yes BT-29 Seller legal registration identifier No BT-30 Seller trading name No Buyer Information
BT-44 Buyer name Yes BT-45 Buyer VAT identifier Yes BT-46 Buyer legal registration identifier No Invoice Lines
BT-126 Invoice line amount Yes BT-127 Invoice line VAT amount Yes BT-128 Invoice line VAT category code Yes BT-129 Invoice line VAT rate Yes BT-151 Item name Yes BT-152 Item description No Validation Requirements
Invoices using this standard must pass the following validation checks before transmission. Rejections typically occur due to missing mandatory fields or incorrect data types.
- All BT codes must appear with correct data types
- VAT calculation must be consistent (line totals must match header totals)
- Date fields must be valid ISO 8601 dates
- Amount fields must use exactly 2 decimal places
- Currency codes must be valid ISO 4217 codes
Key Advantages
- EU-wide semantic interoperability
- Format-agnostic (works with XML, PDF, UBL)
- Forms the European semantic standard referenced by Directive 2014/55/EU for electronic invoicing in public procurement
- Supported through many ERP platforms, native modules, middleware products, and e-invoicing providers
Implementation Considerations
- Complex with 52 mandatory fields
- Requires understanding of BT code taxonomy
- Validation can be strict — small errors cause rejections
Also Known As
Also searched as: EN16931, en16931, EN 16931, EN 16931 invoice, EN 16931 standard, EN 16931 e-invoice standard, European semantic invoice model, electronic invoice semantic model.
How It Connects
- EN 16931 → European semantic invoice model — defines what data an invoice must contain
- Peppol BIS Billing 3.0 → Peppol network invoice specification built on UBL 2.1 with EN 16931 semantics
- XRechnung → German national format implementing EN 16931 as pure XML
- ZUGFeRD / Factur-X → Hybrid PDF/XML invoice family — embedded XML conforms to EN 16931
- UBL / CII → XML syntax layer used to represent EN 16931 data in structured formats
Official Sources
All information on this page is based on the sources listed below. Always verify current requirements with the issuing authorities.
- EN 16931-1:2017 Product Page Standard Body
Official CEN page for the European e-invoicing standard; access to purchase specification
- EN 16931-1:2017 — Semantic Data Model for Invoices Standard Body
Direct specification for the EU semantic e-invoice data model; BT code taxonomy
- EU Directive 2014/55/EU on E-Invoicing Government
Legal basis requiring EU member states to accept EN 16931-compliant invoices