EU e-invoicing mandate: ViDA and EN 16931 explained
How ViDA (VAT in the Digital Age) and the EN 16931 standard harmonise e-invoicing across the EU: timeline to 2035, the UBL and CII syntaxes, and digital reporting.
| ViDA adopted | 11 March 2025 (in force since 14 April 2025) |
|---|---|
| Digital Reporting Requirements (DRR) for cross-border B2B | from 1 July 2030 |
| National systems aligned with ViDA | by 2035 |
| Underlying standard | EN 16931 (UBL 2.1 and UN/CEFACT CII syntaxes) |
The EU VAT in the Digital Age (ViDA) reform was adopted on 11 March 2025 and entered into force on 14 April 2025. It rolls out progressively until 2035 and makes the structured e-invoice based on the European standard EN 16931 the common foundation of every national system.
What ViDA changes
ViDA has three pillars: Digital Reporting Requirements (DRR), platform-economy rules, and single VAT registration. For e-invoicing the DRR pillar is the decisive one: from 1 July 2030, cross-border intra-EU B2B supplies must be issued as a structured e-invoice and reported to tax authorities in near real time. Member states may introduce domestic B2B e-invoicing mandates without prior EU authorisation; pre-existing systems (e.g. Italy, France, Germany, Poland, Romania, Belgium) must align with the ViDA rules by 2035.
EN 16931, UBL and CII
EN 16931 is not a file format — it is a semantic data model of about 170 business terms. It defines what data an invoice must carry, not how it is encoded. Two XML syntaxes are officially bound to EN 16931: UBL 2.1 (OASIS) and CII (UN/CEFACT Cross Industry Invoice). National formats such as XRechnung, Factur-X/ZUGFeRD or Peppol BIS are CIUS — narrower, EN-16931-compliant usage specifications.
| Layer | Example |
|---|---|
| Standard (semantics) | EN 16931 |
| Syntax (XML) | UBL 2.1, UN/CEFACT CII |
| National CIUS | XRechnung (DE), Factur-X (FR), Peppol BIS (EU) |
How invowerk helps
invowerk is the format and field layer of this landscape: a REST API and MCP server that validate UBL and CII invoices against EN 16931, explain every BR/BR-DE error code in plain language (see the error-code pages under /codes) and convert between UBL and CII. That lets you confirm an invoice technically satisfies the format a mandate demands — independent of the channel it later travels over.