On this page
- Structure: Two Parts
- Syntax bindings
- CIUS and extensions
- Governance: CEN/TC 434
- EN 16931-1:2026 — The March 2026 Revision (ViDA-Ready)
- Regulatory Mandate
- EU Level: ViDA (VAT in the Digital Age)
- National Mandates (as-of 2026-07-27)
- Relationship to Peppol BIS 3.0 and Peppol BIS 4.0
- ZUGFeRD 2.4 / Factur-X 1.08 (December 2025 Update)
- ERP Implementation
- What practitioners report / SME compliance challenges
- Key terms
- Next frontier concepts (dangling links)
EN 16931 — EU Semantic Data Model for Structured Electronic Invoices
EN 16931 — EU Semantic Data Model for Structured Electronic Invoices
EN 16931 is a European Standard (developed by CEN) that defines a syntax-neutral semantic data model for compliant electronic invoices. It specifies what an invoice must mean — covering 176 business terms for seller/buyer identity, line items, tax breakdowns, payment instructions, allowances, charges, and delivery information — independently of the technical format (UBL or CII XML) used to encode it. Originally mandated for B2G public procurement in 2017, the 2026 revision expands scope to cover B2B and aligns with ViDA (VAT in the Digital Age)'s Digital Reporting Requirements.
Structure: Two Parts
EN 16931 consists of two parts (as-of 2026-03-18):
- EN 16931-1 — the syntax-neutral semantic data model. Defines what information an invoice must carry, expressed as Business Terms (BT) and Business Groups (BG), independent of any encoding format. (Source: seeburger.com, 2026)
- EN 16931-2 — syntax bindings. Specifies how each semantic element maps to a concrete XML syntax (UBL 2.1 or UN/CEFACT CII D22B). (Source: same)
Syntax bindings
Two XML syntaxes are officially bound:
- UBL 2.1 (OASIS Universal Business Language) — ~700 conformance rules (UBL-CR-*) flag any element outside EN 16931 scope.
- UN/CEFACT CII (Cross Industry Invoice) — equivalent CII-SR-* rules; more XML nesting layers, making files larger and mappings more complex.
Conversion between UBL and CII is lossless: every business term has an exact equivalent in both syntaxes. (Source: invoicenavigator.eu, 2026)
CIUS and extensions
Countries and industries may create CIUS (Core Invoice Usage Specification) — constrained subsets of EN 16931 — or extensions for additional data elements, governed by the extension methodology layer in CEN/TC 434 WG5. (Source: rtcsuite.com, 20 Feb 2026)
Examples of CIUS built on EN 16931:
- Peppol BIS Billing 3.0 — the European Peppol implementation profile; adds mandatory CustomizationID, ProfileID, and Peppol participant endpoint identifiers on top of the core model. A valid Peppol BIS 3.0 invoice implies EN 16931 compliance; the reverse is not guaranteed. (Source: complyance.io, 2026)
- XRechnung — Germany's national profile (UBL and CII variants)
- ZUGFeRD / Factur-X — hybrid PDF/A-3 with embedded CII XML; Germany and France
Governance: CEN/TC 434
CEN/TC 434 "Electronic Invoicing" is the CEN technical committee responsible for EN 16931. It has three working groups: (Source: vatupdate.com, 22 May 2025)
- WG1 — Semantic data model (core EN 16931-1 content)
- WG3 — Syntax bindings (EN 16931-2 UBL/CII mapping)
- WG5 — Extension methodology (CIUS and industry extensions)
Working artefacts (validation schematrons, code lists) are published openly at github.com/CenPC434. (Source: same)
Known constraint: CEN's strict IP policies require the published standard text to be purchased from national standardisation bodies, limiting SME access and implementation quality. (Source: same)
Update frequency: No fixed cadence. Original standard 2017; the 2026 revision took approximately three years to develop, triggered primarily by ViDA (VAT in the Digital Age) and B2B expansion requirements.
EN 16931-1:2026 — The March 2026 Revision (ViDA-Ready)
Timeline (as-of 2026-03-18):
- Oct 2025: CEN/TC 434 informal agreement to modernise EN 16931 for B2B and ViDA
- 13 Feb 2026: CEN formal approval — 17 Member State national bodies voted in favour, zero objections
- 18 Mar 2026: Definitive Text published, triggering national publication phases across EU member states
- Subsequent weeks: National bodies (DIN, AFNOR, NBN, BSI, etc.) publish national equivalents
(Source: vatupdate.com, 2 Apr 2026; vatcalc.com, 13 Feb 2026)
New semantic model elements (B2B enrichment) (as-of 2026-03-18):
- Support for multiple purchase orders per invoice, with repeat order references
- Early payment discounts and late-payment charges
- Supplier bank IBAN as a supported/mandatory field (for tax authority tracking of financial flows)
- Explicit triangulation simplification indicator
- Corrective invoice sequential numbering rules
- Foreign currency (FX) handling improvements
- Ability to carry XML attachments in structured flows
- Broader range of exempt supplies and national special VAT schemes (e.g., margin scheme)
- Improved invoice coding and classification
(Source: vatcalc.com, 13 Feb 2026; rtcsuite.com, 20 Feb 2026)
Not backward compatible: New business terms, modified validation rules, and updated syntax bindings for UBL and CII mean existing EN 16931:2017 implementations cannot simply absorb the new traffic without mapping updates. (Source: aigovhub.io, 2026)
The European Commission is expected to publish an official reference to EN 16931-1:2026 in the Official Journal of the EU, along with a transition period for migration (no date confirmed as-of 2026-04-02). (Source: vatupdate.com)
Regulatory Mandate
EU Level: ViDA (VAT in the Digital Age)
- ViDA was formally adopted by the EU Council and entered into force 14 April 2025. It enables member states to introduce mandatory e-invoicing immediately, without prior EU derogation. (Source: ec.europa.eu, 2026)
- Under ViDA's Digital Reporting Requirements (DRR) pillar, from 1 July 2030, electronic invoicing in accordance with EN 16931 is mandatory for intra-Community B2B cross-border transactions. PDFs will not count as valid e-invoices for DRR purposes. (Source: vatcalc.com, 2026)
- The EC projected ViDA's DRR would reduce VAT fraud by up to €11 billion per year and lower compliance costs for EU traders by over €4.1 billion per year over the next decade (as-of 2025 modelling). (Source: ec.europa.eu official projections, cited in multiple industry sources)
[!unverified] NIS2 (Network and Information Security Directive) was listed as a regulatory reference for EN 16931 in the research brief. No web source confirmed this relationship. NIS2 is a cybersecurity directive; ViDA is the correct confirmed regulatory driver. The NIS2 claim is treated as unverified.
National Mandates (as-of 2026-07-27)
| Country | Status | Format | Network |
|---|---|---|---|
| Italy | Full B2B mandate active | FatturaPA (EN 16931-compliant, national schema) | SDI clearance platform |
| Belgium | Mandatory from 1 Jan 2026 (all VAT-registered B2B); 500,000+ businesses onboarded | Peppol BIS Billing 3.0 | Peppol exclusively |
| Germany | Receiving: mandatory from Jan 2025; Sending: Jan 2027 (>€800k turnover), Jan 2028 (all) | XRechnung, ZUGFeRD, Peppol BIS 3.0 | Open; bilateral or Peppol |
| France | Receiving mandatory from Sep 2026; large/mid sending from Sep 2026 | UBL, CII, Factur-X (all EN 16931-compliant) | PPF or PDP accredited platforms |
| Spain | B2B mandate enacted Mar 2026 | TBD | TBD |
| Poland (KSeF) | National mandate rolling out (phased) | KSeF FA_VAT schema | KSeF clearance |
| Romania | National mandate active (RO e-Factura) | — | — |
| Norway | Mandatory B2B e-invoicing from 2027 | Peppol BIS 3.0 | Peppol |
(Source: spscommerce.com, 2026; vatcalc.com, 13 Feb 2026; dynatos.com, Mar 2026; imagetotable.ai, 2026)
Relationship to Peppol BIS 3.0 and Peppol BIS 4.0
Peppol BIS Billing 3.0 is a CIUS (Core Invoice Usage Specification) of EN 16931:
- Every Peppol BIS 3.0 invoice must be EN 16931-compliant
- Not every EN 16931 invoice is automatically Peppol-ready (BIS 3.0 adds CustomizationID, ProfileID, Peppol participant identifiers)
- BIS 3.0 operates as two rule layers: EN 16931 validation rules + BIS 3.0 validation rules
(Source: docs.peppol.eu, Nov 2025 release; invoicenavigator.eu, 2026)
PINT (Peppol International Invoice) and Peppol BIS 4.0 (as-of 2026-07):
- OpenPeppol is developing a next-generation standard that merges European BIS 3.0 with the international PINT model into a single globally applicable e-invoicing standard
- Expected release is 2026, though no specific quarter was confirmed in any source as of July 2026
- BIS 4.0 introduces stricter validation rules for multi-jurisdictional compliance
- Denmark has formally abandoned its national OIOUBL 3.0 initiative and committed to Peppol BIS 4.0 as its single e-invoicing standard
(Source: dynatos.com, Oct 2025; rtcsuite.com, 2026)
ZUGFeRD 2.4 / Factur-X 1.08 (December 2025 Update)
- On 4 December 2025, FeRD (Germany) and FNFE-MPE (France) jointly published ZUGFeRD 2.4 / Factur-X 1.08 — based on UN/CEFACT CII D22B (upgraded from D16B); required for implementation from 15 January 2026. (Source: fnfe-mpe.org press release, 4 Dec 2025)
- ZUGFeRD 2.4 introduces Peppol integration profiles, enabling the hybrid PDF/XML format to be transmitted via Peppol for the first time — closing a gap where ZUGFeRD was previously only exchanged bilaterally or by email. (Source: invoice-portal.de, 2026) (as-of 2026-01-15)
ERP Implementation
SAP S/4HANA — received updated EN 16931 certification in April 2026 covering XRechnung (UBL 2.1 and CII), ZUGFeRD 2.3, FatturaPA, and Factur-X 1.0 profiles. XRechnung 3.0 schema changes included in S/4HANA 2023 FPS02+; Polish KSeF FA_VAT support added June 2026. SAP ECC 6.0 customers have no certified path — a certified middleware layer is required before Germany's 2027 sending mandate. (Source: eu-einvoicing.com, 22 Apr 2026) (as-of 2026-04-22)
Microsoft Dynamics 365 — September 2025 update enabled native Peppol BIS 3.0 sales invoice generation (Finance and Supply Chain Management); prior to this, XRechnung and ZUGFeRD required third-party add-ons. (Source: cegeka.com, citing Microsoft; as-of 2025-09) [stale-risk for specific feature state]
[!unverified] No specific EN 16931 certification announcement for Dynamics 365 or Oracle Fusion was found in sources. Only SAP S/4HANA had a confirmable EN 16931 certification as of April 2026.
DATEV (German SME accounting) — updated XRechnung 3.0 module in 2026 ahead of Germany's 2027 mandate. (Source: eu-einvoicing.com, 2026)
weclapp (cloud ERP, German SME) — added native ZUGFeRD 2.3 and XRechnung 3.0 support in May 2026. (Source: eu-einvoicing.com, 2026)
What practitioners report / SME compliance challenges
- Missing mandatory fields: Incomplete invoices fail validation — one of the most common reported issues. (Source: aigovhub.io, 2026)
- PDF-XML discrepancies in hybrid formats: Particularly in ZUGFeRD — the human-readable PDF does not match embedded XML. (Source: same)
- Non-backward compatibility of EN 16931-1:2026: Existing implementations need new mapping work. (Source: same)
- CEN IP restrictions: Standard text must be purchased, limiting SME implementation quality. (Source: vatupdate.com, 22 May 2025)
- ERP version dependencies: SAP ECC 6.0 requires middleware; mid-market businesses on older ERP versions face the same problem. (Source: eu-einvoicing.com, 22 Apr 2026)
- ERP archiving: German law requires archiving compliant e-invoices for 8 years, creating a data retention obligation alongside format compliance. (Source: eu-einvoicing.com, 2026)
- Guidance gap: CEN was preparing a practical guidance document with implementation examples but it was not yet released as of March 2026. (Source: vatupdate.com, 2 Apr 2026)
Key terms
| Term | Meaning |
|---|---|
| Business Term (BT) | An atomic data element in EN 16931's semantic model (e.g., BT-1 Invoice number) |
| Business Group (BG) | A named cluster of related BTs (e.g., BG-4 Seller) |
| CIUS | Core Invoice Usage Specification — a constrained national/sectoral subset of EN 16931 |
| UBL 2.1 | OASIS Universal Business Language — one of the two official EN 16931 XML serialisations |
| CII | UN/CEFACT Cross Industry Invoice — the other official XML serialisation |
| ZUGFeRD | German/French hybrid PDF+CII format; compliant with EN 16931 |
| Factur-X | French name for ZUGFeRD (same technical spec) |
| XRechnung | Germany's pure-XML national CIUS of EN 16931 (both UBL and CII variants exist) |
| SDI | Italy's Sistema di Interscambio — the national clearance hub for FatturaPA |
| DRR | Digital Reporting Requirements — the ViDA pillar mandating EN 16931 for cross-border B2B from Jul 2030 |
Next frontier concepts (dangling links)
- ViDA (VAT in the Digital Age) — 10+ inbound refs; no standalone page; the primary regulatory driver of EN 16931's B2B expansion
- XRechnung — Germany's national CIUS; 5+ refs across Peppol and EN 16931 pages
- ZUGFeRD — hybrid PDF/XML format; 5+ refs
- CIUS (Core Invoice Usage Specification) — the extensibility mechanism for EN 16931; 3+ refs
- PINT (Peppol International Invoice) — Peppol's global standard converging with BIS 4.0; 2+ refs