Skip to main content

The EN 16931 Standard

EN 16931 is the European standard for electronic invoicing. Developed by CEN (European Committee for Standardization) and mandated by EU Directive 2014/55/EU, it provides the semantic data model and business rules that underpin e-invoicing across Europe.

What is EN 16931?​

EN 16931 provides a unified framework for creating, exchanging, and processing electronic invoices across the EU. Rather than leaving invoice structure to each vendor or country, the standard ensures:

  • Semantic consistency: Invoice fields mean the same thing everywhere
  • Technical interoperability: Different systems can understand each other's invoices
  • Legal compliance: Invoices meet requirements across EU member states
  • Business process alignment: Standard processes work regardless of the software used

EN 16931 is sometimes called the "Rosetta Stone" of EU invoicing — it provides a common language that bridges different formats and makes cross-border transactions predictable.

The Standards Development Process​

EN 16931 was developed through a rigorous, multi-year process:

  1. Commission Directive: EU Directive 2014/55/EU called for a European e-invoicing standard
  2. CEN Mandate: The European Committee for Standardization received the mandate to develop it
  3. Multi-stakeholder consultation: Accountants, software vendors, tax authorities, and businesses participated
  4. Technical development: Multiple working groups refined the specification
  5. Harmonisation: The standard was aligned with international e-invoicing efforts
  6. Approval: Adopted as a European Standard in 2017

Core Components of EN 16931​

Semantic Data Model​

The heart of EN 16931 is a data model defining required and optional invoice elements:

Mandatory fields (must be present on every compliant invoice):

  • Invoice identification number
  • Invoice issue date
  • Due date or payment terms
  • Invoice parties (seller and buyer with identification)
  • Total amounts (net, VAT, gross)
  • Line items with descriptions, quantities, and amounts
  • VAT breakdown by category and rate

Optional but recommended:

  • Payment terms and payment means
  • Delivery date and delivery information
  • Discount and allowance/charge information
  • Purchase order and contract references
  • Additional document references

The semantic model is syntax-neutral — it describes what information invoices must contain, not how to encode it technically.

Syntax Bindings​

EN 16931 can be implemented in multiple technical formats (called syntax bindings):

FormatTechnical BasisCommon Usage
UBL 2.1OASIS XML standardWidely used across the EU
CIIUN/CEFACT Cross Industry InvoiceUsed by ZUGFeRD/Factur-X
Peppol BISBuilt on UBLPan-European B2B network

All of these formats express the same semantic information — just in different technical structures. A compliant invoice in one format can be mapped to any other.

ZUGFeRD uses CII

ZUGFeRD/Factur-X uses the CII (Cross Industry Invoice) syntax binding of EN 16931. This is why a ZUGFeRD Comfort invoice is fully EN 16931 compliant — it implements the same semantic model in CII XML.

Business Rules​

EN 16931 defines calculation rules and validation logic that all compliant invoices must follow:

  • VAT calculations: How to compute VAT from line items and aggregate by category
  • Total consistency: Mathematical relationships between net, VAT, and gross amounts
  • Rounding rules: How to handle decimal places in calculations
  • Line item structure: What information must accompany each invoice line
  • Document relationships: How invoices relate to purchase orders and other documents
  • Code lists: Standardised values for currencies, units, VAT categories, and country codes

These rules ensure that any EN 16931-compliant system can validate and process any compliant invoice, regardless of the software that created it.

Mandatory Adoption in Public Sector​

A key aspect of EN 16931 is its mandatory status for public procurement:

  • B2G invoicing: All invoices to EU government agencies must be EN 16931 compliant
  • Implementation: Member states have adopted the standard for public sector invoicing
  • Enforcement: Non-compliant invoices may be rejected or delayed by government entities
  • Broad scope: Applies to all public entities including ministries, regional authorities, municipalities, and state-owned enterprises

This mandate creates downstream pressure — many private companies align with EN 16931 even for B2B transactions because their larger customers expect and sometimes require it.

How EN 16931 Relates to ZUGFeRD​

ZUGFeRD started as a German standard developed in parallel with EN 16931. It was later aligned with the European standard:

  • The ZUGFeRD Comfort profile implements the full EN 16931 semantic model using CII XML
  • Factur-X (the French-German harmonised name) is technically the same specification
  • Both are fully compliant with EN 16931 at the Comfort level and above

This means that when docs101 generates a ZUGFeRD invoice, it is simultaneously producing an EN 16931-compliant electronic invoice.

Impact on Businesses​

For Invoice Senders​

  • Interoperability: Invoices work across systems and countries without manual adaptation
  • Automation support: Customers can process invoices automatically
  • Compliance confidence: Knowing your invoices meet a recognised European standard
  • Competitive advantage: Demonstrating professional, standards-aligned processes

For Invoice Recipients​

  • Automatic processing: Systems can parse and validate invoices reliably
  • Error reduction: Standardised formats reduce interpretation errors
  • Audit trail: Clear structure supports compliance documentation
  • Cost savings: Automation reduces manual invoice processing effort

For the Broader Economy​

  • Reduced barriers to trade: SMEs can more easily sell cross-border
  • Fraud prevention: Standard structure makes anomalies easier to detect
  • Tax compliance: Structured data improves audit capabilities for tax authorities
  • Innovation: A standard foundation enables new business services and integrations

How docs101 Ensures EN 16931 Compliance​

docs101 is built with EN 16931 compliance as a core feature, not an afterthought.

Automatic Compliance​

When you create an invoice in docs101:

  1. The system ensures all required EN 16931 fields are present and correctly populated
  2. Calculations are performed according to EN 16931 business rules (VAT aggregation, totals, rounding)
  3. A VAT Breakdown is materialized — grouping positions by tax treatment and rate with per-group net, VAT, and gross totals, satisfying business rule BR-CO-26
  4. The invoice structure follows the semantic data model
  5. The output is a ZUGFeRD/Factur-X PDF with CII XML that implements EN 16931

KOSiT Validation​

docs101 validates generated invoices using the KOSiT validator — the official validation tool maintained by the Coordination Office for IT Standards of the German federal government:

  • The embedded XML is checked against EN 16931 Schematron rules
  • Business rule violations are caught before the invoice is delivered
  • This ensures every invoice that leaves docs101 is technically compliant
Validated by default

You do not need to run a separate validation step. docs101 validates every invoice automatically as part of the generation process. If validation finds an issue, you are notified so you can correct the data before sending.

What Gets Validated​

  • Required fields are present and correctly formatted
  • VAT calculations are consistent and mathematically correct
  • Total amounts are internally consistent (net + VAT = gross)
  • VAT category codes (derived from the selected tax treatment) are valid for the jurisdiction and transaction type
  • Code list values (currency, unit codes, country codes) are from the approved EN 16931 lists
  • Line item data meets minimum requirements

Learn More​