EN 16931 Explained — The EU Standard Behind E-Invoicing

What Is EN 16931?

EN 16931 is the European Standard for electronic invoicing, published by the European Committee for Standardisation (CEN) in 2017. Its full title is "Electronic invoicing — Part 1: Semantic data model of the core elements of an electronic invoice." It was created in response to EU Directive 2014/55/EU, which required all EU member states to accept electronic invoices for public procurement.

The standard defines a common set of invoice fields — who is the seller, who is the buyer, what was sold, how much tax applies, what is the total amount, and how should it be paid. It specifies around 160 business terms (called "semantic data elements") that together form a complete invoice. These include mandatory fields like invoice number, issue date, and VAT breakdown, as well as optional fields for things like delivery addresses, purchase order references, and payment discounts.

The critical point is that EN 16931 is syntax-independent. It does not prescribe a specific file format. Instead, it defines the meaning and relationships of invoice data elements in abstract terms. The actual encoding — how those elements become an XML file that software can read — is handled by separate syntax specifications.

A Semantic Data Model, Not a Syntax

This distinction trips up many people encountering EU e-invoicing for the first time. EN 16931 tells you what information an invoice must carry. It does not tell you how to write the XML tags. For example, the standard says an invoice must contain a "Seller name" (business term BT-27). But whether that appears in the XML as <cac:AccountingSupplierParty> (UBL) or <ram:SellerTradeParty> (CII) depends on which syntax you choose.

Think of EN 16931 as a blueprint for a house. It says "the house must have a kitchen, a bathroom, and a bedroom." But it does not dictate whether the house is built from brick or timber. The syntaxes are the building materials — different implementations of the same blueprint.

UBL and CII: The Two Approved Syntaxes

EN 16931 recognises exactly two XML syntaxes for encoding its semantic model:

• UBL 2.1 (Universal Business Language), maintained by OASIS. This is the syntax used by Peppol BIS 3.0 and the UBL variant of XRechnung. It is the dominant syntax in Scandinavia, Benelux, and for Peppol network transactions across Europe.
• UN/CEFACT CII (Cross Industry Invoice), maintained by the United Nations. This is the syntax used by ZUGFeRD, Factur-X, and the CII variant of XRechnung. It is the preferred syntax in Germany and France for hybrid PDF/XML invoicing.

Both syntaxes can carry exactly the same EN 16931 data. An invoice encoded in UBL and the same invoice encoded in CII contain identical business information — only the XML tag names and structure differ. EU regulations require member states to accept at least one of these two syntaxes.

CIUS: Country-Specific Adaptations

EN 16931 defines the European baseline, but individual countries often need additional rules. A CIUS (Core Invoice Usage Specification) is a set of country-specific constraints layered on top of EN 16931. A CIUS can make optional EN 16931 fields mandatory, restrict the allowed values of certain fields, or add validation rules — but it cannot remove any mandatory fields or contradict the core standard.

The most prominent examples of CIUS include:

• XRechnung — Germany's CIUS. Requires a routing identifier (Leitweg-ID) for B2G invoices and enforces stricter rules on buyer/seller identification and payment information.
• Peppol BIS 3.0 — While technically a usage specification rather than a country-level CIUS, Peppol BIS 3.0 adds its own business rules on top of EN 16931, such as requiring Peppol participant IDs.
• CIUS-AT — Austria's adaptation, used alongside ebInterface.
• CIUS-IT — Italy's adaptation for use alongside the FatturaPA system.

Any invoice that conforms to a CIUS automatically conforms to EN 16931. The reverse is not always true — a generic EN 16931 invoice may lack fields required by a specific CIUS.

Why EN 16931 Matters for Cross-Border Invoicing

Before EN 16931, every country had its own e-invoicing format with no guarantee of interoperability. A Danish company sending an invoice to a German buyer had to learn a completely different system. EN 16931 changed this by establishing a common semantic foundation that all national formats must respect.

This means that even though Germany uses XRechnung and France uses Factur-X, the underlying data content is the same EN 16931 model. Conversion between formats becomes a syntactic transformation rather than a semantic reinterpretation. A tool that understands EN 16931 can map data between any two compliant formats reliably, because the business terms are standardised.

For businesses operating across the EU, this is transformative. You can maintain a single internal data model based on EN 16931 and generate whichever output format each country or trading partner requires — Peppol BIS 3.0 for Belgium, XRechnung for Germany, Factur-X for France — all from the same source data.

Which Countries Require EN 16931 Compliance?

All EU member states are required to accept EN 16931-compliant invoices for public procurement (B2G). Beyond that, many countries are extending the requirement to B2B transactions:

• Germany: B2B e-invoicing mandate from 2025, requiring EN 16931 compliance (XRechnung or ZUGFeRD EN 16931 profile).
• France: Phased B2B mandate from 2026, accepting Factur-X, UBL, and CII — all EN 16931 compliant.
• Belgium: B2B mandate from January 2026, requiring Peppol BIS 3.0 (EN 16931 compliant).
• Spain: B2B mandate in preparation, expected to require EN 16931 compliance.
• Poland: KSeF platform mandating structured invoicing based on national schema aligned with EN 16931 principles.

The trend is clear: EN 16931 is becoming the universal baseline for e-invoicing across Europe, for both public and private sector transactions.

How InvoicePeppol Helps

InvoicePeppol generates EN 16931-compliant XML from your PDF invoices. Our AI extracts the semantic data — all the business terms defined in the standard — and outputs validated Peppol BIS 3.0 (UBL 2.1) XML. Because the output is EN 16931 compliant, it serves as a reliable foundation for any EU e-invoicing requirement.

Frequently Asked Questions