EN 16931 Explained: The European Standard for E-Invoices
EN 16931 Explained: The European Standard for E-Invoices
Anyone dealing with e-invoicing will quickly come across the designation EN 16931. Behind this standard lies the foundation on which all European e-invoice formats are built. But what exactly does the standard regulate, and why is it so important for German businesses?
What Is EN 16931?
EN 16931 is a European standard that defines a uniform semantic data model for electronic invoices. It was developed on behalf of the European Commission by the European Committee for Standardization (CEN) and published in 2017.
The standard comprises several parts. The two most important (available free of charge from CEN) are:
- EN 16931-1: The semantic data model — defines what information an e-invoice must contain and what each element means.
- CEN/TS 16931-2: The list of compliant syntaxes — specifies that UBL 2.1 and UN/CEFACT CII D16B may be used as syntaxes.
Additional parts include:
- CEN/TS 16931-3 (multiple sub-parts): The actual syntax bindings — describe how the data model is concretely mapped to UBL and CII.
- CEN/TR 16931-4: Guidelines on interoperability at the transmission level.
- CEN/TR 16931-5: Guidelines on the use of sector or country extensions (CIUS and Extensions).
- CEN/TR 16931-6: Test results on practical application.
The Semantic Data Model
At its core, EN 16931 defines a list of Business Terms, each carrying a unique identifier (e.g., BT-1 for the invoice number, BT-31 for the seller's VAT identifier). These Business Terms are organized into Business Groups, such as BG-4 for seller information or BG-25 for invoice line items.
Mandatory and Optional Fields
The standard distinguishes between:
- Mandatory fields: Must be present in every invoice (e.g., invoice number, invoice date, total amount, seller and buyer details).
- Conditional fields: Must be provided under certain circumstances (e.g., VAT identifier for taxable supplies).
- Optional fields: Can be included as needed (e.g., delivery information, payment terms as free text).
Which Formats Build on EN 16931?
The standard itself does not define a file format but rather an abstract model. Concrete formats implement this model:
XRechnung
XRechnung is the German CIUS (Core Invoice Usage Specification) — a national adaptation of EN 16931. It tightens certain rules: for example, the buyer reference (BT-10, in practice the Leitweg-ID) becomes a mandatory field. XRechnung is transmitted as UBL or CII.
ZUGFeRD / Factur-X
ZUGFeRD 2.x is also based on EN 16931 and uses the CII syntax. The "EN 16931" (Comfort) profile maps the European data model exactly, while higher profiles such as Extended allow additional fields.
Peppol BIS Billing 3.0
The Peppol network uses its own CIUS of EN 16931 for cross-border invoice exchange. Here too, the foundation is identical, supplemented by network-specific rules.
How Does Validation Work?
Compliance with EN 16931 is verified through Schematron rules. These rules validate not only the XML structure but also the business logic — for example, whether the total amount matches the sum of the line items, or whether the correct tax ID is provided for certain VAT categories.
Validation typically occurs in two stages:
- Syntax validation: Checks whether the XML file conforms to the schema (UBL or CII).
- Business rule validation: Checks EN 16931 rules and, where applicable, national CIUS rules (e.g., XRechnung-specific checks).
invapi offers a validation API that automatically performs both stages and returns detailed error messages.
Why Is EN 16931 Relevant for Your Business?
Since January 1, 2025, all businesses in Germany must be able to receive e-invoices that comply with EN 16931. From 2027, issuing e-invoices will also become mandatory in stages: initially for businesses with more than 800,000 EUR in prior-year revenue, and from 2028 for all businesses. Small businesses under Section 19 of the German VAT Act (UStG) are permanently exempt from the issuing obligation. The standard therefore affects not just large enterprises or the public sector, but every business operating in the B2B space.
Businesses that align their invoice formats with EN 16931 early on benefit from:
- Legal certainty through demonstrable compliance with the standard
- Interoperability with business partners across Europe
- Future-proofing, since all current and planned e-invoice formats are based on this standard
Conclusion
EN 16931 is more than a technical specification — it is the common language of European e-invoicing. Whether you use XRechnung, ZUGFeRD, or Peppol: the standard ensures that invoice data is uniformly structured, validatable, and interoperable. Anyone who issues or receives e-invoices cannot avoid EN 16931.