European e-Invoicing Standard (EN 16931)

EN 16931 is the European standard at the technical heart of public sector e-Invoicing across Europe. Published by CEN (European Committee for Standardisation) in 2017, it defines precisely what information a compliant electronic invoice must contain and how that information must be structured, ensuring that invoices generated in one country and one accounting system can be automatically processed by a buyer's financial system in any other.

What is the European e-Invoicing Standard (EN 16931)?

EN 16931 specifies a semantic data model: a defined set of data elements (such as invoice date, seller name, buyer reference, line items, tax amounts, and payment terms) with precise definitions and rules governing how they relate to each other. The standard does not mandate a single file format; instead, it defines two permitted syntax bindings that can carry the data model: UBL (Universal Business Language, ISO/IEC 19845) and UN/CEFACT Cross Industry Invoice (CII). Both syntaxes are legally equivalent under EU Directive 2014/55/EU on electronic invoicing in public procurement.

The standard is divided into two main parts:

• EN 16931-1 defines the semantic model itself, the rules, and the core invoice data.
• EN 16931-2 defines the syntax bindings (UBL and CII) that express the semantic model in machine-readable file formats.

Peppol uses EN 16931 as its foundation. The Peppol BIS Billing 3.0 format (the predominant e-Invoice format in Europe) is a constrained profile of EN 16931 using UBL syntax, adding some Peppol-specific rules above the base standard.

EU Directive 2014/55/EU required all contracting authorities in EU member states to be capable of receiving and processing invoices conforming to EN 16931. Central government bodies met this obligation by April 2019; subnational authorities by April 2020. Norway, Iceland, and several other non-EU European countries have adopted equivalent obligations.

The UK adopted EN 16931 as the technical basis for its e-Invoicing programme. UK compliance profiles use the same UBL syntax and data model, enabling cross-border invoice exchange between UK suppliers and EU buyers with minimal format differences.

Why it matters for bidders

EN 16931 compliance is the technical gateway to getting paid electronically by public sector buyers. An invoice that does not conform to the standard (or to a valid national or sector profile derived from it) will be rejected by the buyer's automated invoice processing system. Key implications:

• Your accounting software or e-invoicing service provider must be certified to generate EN 16931-compliant invoices.
• The purchase order reference, buyer routing identifier (such as a Peppol ID or GLN), and contract reference are mandatory fields that must be correctly populated.
• Tax data must be structured according to the standard's rules, not as free-text descriptions.
• Validation tools (including the OpenPeppol Peppol BIS validator) can check compliance before transmission.

The practical entry point for most suppliers is connecting to Peppol through a certified access point provider, which handles the EN 16931 formatting automatically.

Example

An Austrian SME wins a catering contract with a German federal agency. The contract requires invoices in Peppol BIS Billing 3.0 format (EN 16931, UBL syntax). The supplier's accountant uses accounting software certified for Peppol BIS 3.0. When creating the invoice, the software validates the data against the EN 16931 rules (checking that mandatory fields are populated, tax rates are valid, and the buyer's Peppol ID is present) before transmitting through the supplier's Peppol access point to the agency's financial system.

Frequently Asked Questions

What is the difference between EN 16931 and Peppol BIS Billing 3.0?

EN 16931 is the base European standard defining the data model. Peppol BIS Billing 3.0 is a usage profile built on top of EN 16931: it adds Peppol-specific rules (such as requiring a Peppol ID for routing), restricts some optional fields to mandatory, and specifies the UBL syntax. Any invoice conforming to Peppol BIS 3.0 automatically conforms to EN 16931, but the reverse is not always true.

Are national profiles of EN 16931 compatible with each other?

National profiles (such as Italy's FatturaPA, Germany's XRechnung, or France's Factur-X) are all derived from EN 16931 and are technically interoperable at the level of mandatory core data. However, each profile may add nationally required extensions. Cross-border invoicing using a Peppol BIS 3.0 baseline profile is generally safer than relying on national profiles, because Peppol BIS is designed for multi-country use.

Does EN 16931 apply to business-to-business invoicing as well?

EN 16931 was originally designed for public sector (B2G) invoicing. However, several member states are extending e-Invoicing mandates to B2B transactions (Italy has already done so broadly). The EN 16931 data model is technically suitable for B2B use, and several countries are using the same standard for B2B mandates.