Learn · standards
What is EN 16931?
EN 16931 is the European standard defining the semantic data model for electronic invoices, published by CEN and mandated by EU Directive 2014/55/EU.
TL;DR
EN 16931 works on two levels:
1. Semantic Model (What)
The standard defines 162 business terms that an invoice can contain, organized into groups:
- Invoice identification (number, date, type)
- Seller and buyer information
- Payment details
- Tax information
- Line items
- Totals
2. Technical Syntaxes (How)
The semantic model can be expressed in two XML syntaxes:
- UBL 2.1: Used by Peppol, XRechnung (UBL variant)
- UN/CEFACT CII: Used by ZUGFeRD, Factur-X, XRechnung (CII variant)
CIUS: Country Extensions
Countries can create "Core Invoice Usage Specifications" (CIUS) that add rules without breaking EU compatibility. Examples:
- XRechnung: German CIUS with Leitweg-ID requirement
- Peppol BIS: Peppol's CIUS with network-specific rules
Legal Requirement
EU Directive 2014/55/EU mandates EN 16931 for public procurement. All EU governments must accept EN 16931-compliant invoices.
Cross-Border Interoperability
An EN 16931 invoice from Germany works in France, Italy, or any EU country. The standard ensures data can be understood regardless of the sender's software.
Future Mandate
ViDA (VAT in the Digital Age) will make EN 16931-based e-invoicing mandatory for all EU B2B transactions by 2030. Starting now puts you ahead.
Invoice Navigator’s validation engine checks all EN 16931 business rules plus country-specific CIUS rules in a single API call, returning results in under 500ms.
Step 1: Understand Your Requirements
Check which CIUS applies to your situation. Germany uses XRechnung, Belgium uses Peppol BIS, France uses Factur-X.
Step 2: Choose Your Syntax
UBL for Peppol/international; CII for ZUGFeRD/Factur-X. Both are equally compliant.
Step 3: Validate Compliance
Use validation tools to check both EN 16931 base rules and any CIUS-specific rules.
- What is Peppol?
EU e-invoice network
- What is XRechnung?
German CIUS
- What is ZUGFeRD?
Hybrid format
- UBL vs CII
Syntax comparison
- ViDA
EU e-invoicing mandate
- XRechnung Validator
Validate against EN 16931 + BR-DE rules
Frequently Asked Questions
- Is EN 16931 the same as XRechnung?
- No. EN 16931 is the EU standard; XRechnung is Germany's implementation (CIUS) that adds German-specific rules. XRechnung is EN 16931-compliant plus extra requirements.
- What's the difference between UBL and CII?
- Both are XML syntaxes for expressing EN 16931 invoices. UBL is more common internationally (Peppol), CII is used in ZUGFeRD/Factur-X. Both are equally valid.
- Is EN 16931 mandatory?
- For public procurement (B2G): Yes in all EU countries. For B2B: Varies by country. Germany and Belgium are mandating EN 16931-based formats for B2B.
- What are the 162 business terms?
- They include invoice number, dates, seller/buyer details, line items, VAT, totals, and payment info. Not all are mandatory—core requirements are a subset.
- Can I add custom fields?
- Within limits. CIUS rules can add requirements but not change core elements. Extensions beyond the standard may break interoperability.
More Questions About What is EN 16931?
- What is EN 16931 and why does it matter?
- EN 16931 is the European standard for electronic invoicing, published by CEN (European Committee for Standardization). It defines the semantic data model — the required and optional fields — that all EU e-invoice formats must support. EN 16931 has two syntax bindings: UBL 2.1 and UN/CEFACT CII D16B. Country-specific formats like XRechnung and Factur-X are "CIUS" (Core Invoice Usage Specifications) built on top of EN 16931, adding national rules without breaking the common standard.
Have an e-invoice that came back rejected? Check it here.
Checking is free. The first verified download every 30 days is free. After that €1.90 per invoice, or €9 a month for all of them.