EN 16931 Explained: Europe's Core e-Invoice Standard

Q: What is EN 16931?

**EN 16931** is the European standard for electronic invoicing, developed by **CEN/TC 434** - a technical committee with around 25 active members drawn from EU national standardisation bodies. It defines a semantic data model (the "core invoice") that specifies every business term an e-invoice can carry: who is selling, who is buying, what was sold, how much is owed, and when payment is due. First published in 2017, EN 16931 is not a file format. It is a language-neutral blueprint of invoice data. The standard tells you **what** information an invoice must contain and how those data elements relate to each other, but it does not prescribe a specific XML schema or file structure. That separation between meaning and encoding is what makes it possible for different technical formats to interoperate. The standard is split into multiple parts. Part 1 defines the semantic model itself. Part 2 lists the conformant syntaxes. Parts 3 through 6 provide the detailed mapping between the semantic model and specific syntax implementations. Parts 1 and 2 are freely available from CEN; Parts 3 through 6 must be purchased from national standards bodies.

Q: Why was it created?

The genesis was **EU Directive 2014/55/EU**, adopted in 2014, which required all public administrations across EU member states to accept e-invoices in a common format for business-to-government (B2G) transactions. Before the directive, each country had its own specifications - or none at all - making cross-border public procurement a headache of format conversions and manual rekeying. The European Commission tasked CEN (the European Committee for Standardisation) with developing a single specification that all member states could adopt. CEN/TC 434 was formed, and the result was EN 16931, published in 2017. Member states had until April 2019 (central authorities) and April 2020 (sub-central authorities) to ensure their procurement systems could receive compliant invoices. The directive targeted interoperability, not uniformity. Countries were free to add their own national requirements on top of the core - which is exactly what happened, through CIUS profiles like XRechnung in Germany and CIUS-PT in Portugal.

Q: How do businesses comply?

An important distinction: Directive 2014/55/EU targets **member states**, not individual businesses. Each EU country is responsible for implementing national regulations that specify which formats and channels are acceptable for B2G (and increasingly B2B) invoicing. Businesses comply by meeting their national requirements, which are built on top of EN 16931. For example, the [Netherlands](/country/NL) requires Peppol BIS 3.0 for B2G invoicing - a CIUS of EN 16931 transmitted via the Peppol network. Germany requires XRechnung for federal B2G, with different states setting their own timelines. France is building a platform-based system where accredited providers must support Factur-X and Peppol BIS. The common thread is EN 16931 underneath, but the practical requirements differ country by country. For most businesses, compliance means working with an ERP vendor, e-invoicing service provider, or Peppol access point that already supports the relevant national specification. The [Germany e-invoicing guide](/guides/germany-e-invoicing) walks through the practical steps for that market. The key is knowing which CIUS or Extension your trading partners and tax authority expect - EN 16931 handles the rest.

Q: What does the future hold for EN 16931?

The revised **EN 16931-1:2025** was approved by CEN/TC 434 on 23 October 2025, passed its formal CEN vote on 13 February 2026, and is expected to be published by May 2026. This is the first major revision since 2017 and brings practical additions: support for **multiple purchase orders per invoice**, **early payment discounts**, **late-payment charges**, **margin schemes**, dedicated **IBAN fields**, and **triangulation indicators** for three-party transactions. The revision was driven by [ViDA (VAT in the Digital Age)](/blog/what-is-vida), the EU regulatory package that will make EN 16931-based e-invoicing mandatory for intra-EU B2B trade from 2030. The revised standard explicitly adds support for ViDA's Digital Reporting Requirements, ensuring the technical foundation is ready before the regulatory deadlines hit. For businesses and vendors, the signal is clear: EN 16931 is no longer just a B2G procurement standard. It is becoming the foundation for all structured invoicing across Europe. The [country comparison page](/compare) tracks each member state's progress toward these deadlines.

What is EN 16931?

EN 16931 is the European standard for electronic invoicing, developed by CEN/TC 434 - a technical committee with around 25 active members drawn from EU national standardisation bodies. It defines a semantic data model (the "core invoice") that specifies every business term an e-invoice can carry: who is selling, who is buying, what was sold, how much is owed, and when payment is due.

First published in 2017, EN 16931 is not a file format. It is a language-neutral blueprint of invoice data. The standard tells you what information an invoice must contain and how those data elements relate to each other, but it does not prescribe a specific XML schema or file structure. That separation between meaning and encoding is what makes it possible for different technical formats to interoperate.

The standard is split into multiple parts. Part 1 defines the semantic model itself. Part 2 lists the conformant syntaxes. Parts 3 through 6 provide the detailed mapping between the semantic model and specific syntax implementations. Parts 1 and 2 are freely available from CEN; Parts 3 through 6 must be purchased from national standards bodies.

Why was it created?

EN 16931 is the backbone of e-invoicing interoperability across Europe.

The genesis was EU Directive 2014/55/EU, adopted in 2014, which required all public administrations across EU member states to accept e-invoices in a common format for business-to-government (B2G) transactions. Before the directive, each country had its own specifications - or none at all - making cross-border public procurement a headache of format conversions and manual rekeying.

The European Commission tasked CEN (the European Committee for Standardisation) with developing a single specification that all member states could adopt. CEN/TC 434 was formed, and the result was EN 16931, published in 2017. Member states had until April 2019 (central authorities) and April 2020 (sub-central authorities) to ensure their procurement systems could receive compliant invoices.

The directive targeted interoperability, not uniformity. Countries were free to add their own national requirements on top of the core - which is exactly what happened, through CIUS profiles like XRechnung in Germany and CIUS-PT in Portugal.

What goes into the core invoice?

The core invoice model defines over 160 business terms grouped into logical clusters. At the document level: invoice number, invoice date, currency code, and document type (invoice, credit note, etc.). For the parties involved: supplier name and address, buyer name and address, VAT identification numbers, and optional registration details.

Line items carry the transactional detail: item description, quantity, unit of measure, unit price, and line-level allowances or charges. Each line links to a tax category (standard rate, reduced rate, exempt, reverse charge, and so on), which rolls up into the document-level tax summary.

The totals section brings it together: sum of line net amounts, total allowances and charges, tax-exclusive amount, total VAT, tax-inclusive amount, and amount due for payment. Payment terms, delivery information, and references to contracts or purchase orders round out the model. Every field has a defined cardinality (mandatory, optional, or conditional) and a set of validation rules.

What are UBL and CII?

EN 16931 maps its semantic model to two official XML syntaxes. UBL (Universal Business Language), maintained by OASIS, is the more widely adopted of the two. It is the basis for Peppol BIS Billing 3.0 and is used by most cross-border and public-sector e-invoicing implementations in Europe and beyond.

CII (Cross-Industry Invoice), maintained by UN/CEFACT, has its roots in the manufacturing and logistics sectors. It is the syntax behind ZuGFeRD (Germany) and Factur-X (France) - hybrid formats that embed a CII XML stream inside a PDF/A-3 file, giving both human-readable and machine-readable content in a single document.

Under Directive 2014/55/EU, public administrations must accept invoices in both syntaxes. In practice, most organisations standardise on one - typically UBL for Peppol-connected systems and CII for supply-chain-heavy industries - but the mapping rules in EN 16931 Parts 3 through 6 ensure that a valid UBL invoice and a valid CII invoice carrying the same data are semantically equivalent.

What is a CIUS and what is an Extension?

Countries and networks adapt EN 16931 to local needs through two mechanisms. A CIUS (Core Invoice Usage Specification) restricts the core - making optional fields mandatory or narrowing code values - without adding new data. An Extension does the opposite: it adds fields beyond what the core defines. The e-invoicing glossary covers both concepts in detail.

The most widely used CIUS profiles are Peppol BIS 3.0 (40+ countries), XRechnung (Germany), and CIUS-PT (Portugal). On the Extension side, ZuGFeRD and Factur-X embed CII XML inside a PDF, giving both human-readable and machine-readable content in one file. The European Commission maintains an official registry of known CIUS and Extension specifications.

How do businesses comply?

An important distinction: Directive 2014/55/EU targets member states, not individual businesses. Each EU country is responsible for implementing national regulations that specify which formats and channels are acceptable for B2G (and increasingly B2B) invoicing. Businesses comply by meeting their national requirements, which are built on top of EN 16931.

For example, the Netherlands requires Peppol BIS 3.0 for B2G invoicing - a CIUS of EN 16931 transmitted via the Peppol network. Germany requires XRechnung for federal B2G, with different states setting their own timelines. France is building a platform-based system where accredited providers must support Factur-X and Peppol BIS. The common thread is EN 16931 underneath, but the practical requirements differ country by country.

For most businesses, compliance means working with an ERP vendor, e-invoicing service provider, or Peppol access point that already supports the relevant national specification. The Germany e-invoicing guide walks through the practical steps for that market. The key is knowing which CIUS or Extension your trading partners and tax authority expect - EN 16931 handles the rest.

What does the future hold for EN 16931?

The revised EN 16931-1:2025 was approved by CEN/TC 434 on 23 October 2025, passed its formal CEN vote on 13 February 2026, and is expected to be published by May 2026. This is the first major revision since 2017 and brings practical additions: support for multiple purchase orders per invoice, early payment discounts, late-payment charges, margin schemes, dedicated IBAN fields, and triangulation indicators for three-party transactions.

The revision was driven by ViDA (VAT in the Digital Age), the EU regulatory package that will make EN 16931-based e-invoicing mandatory for intra-EU B2B trade from 2030. The revised standard explicitly adds support for ViDA's Digital Reporting Requirements, ensuring the technical foundation is ready before the regulatory deadlines hit.

For businesses and vendors, the signal is clear: EN 16931 is no longer just a B2G procurement standard. It is becoming the foundation for all structured invoicing across Europe. The country comparison page tracks each member state's progress toward these deadlines.