EU e-invoicing requirements: Directive 2014/55/EU, EN 16931 and ViDA

The European Union sets three things for e-invoicing: a definition of what an electronic invoice is, a standard for its content (EN 16931), and two obligations — public bodies must accept compliant e-invoices under Directive 2014/55/EU, and from 1 July 2030 cross-border B2B transactions fall under digital reporting based on e-invoices under the ViDA directive (EU) 2025/516. Everything else — whether domestic B2B invoices must be electronic, in which format, over which network and from when — is decided by each Member State.

What Directive 2014/55/EU requires

Directive 2014/55/EU requires contracting authorities and contracting entities to receive and process electronic invoices that comply with the European standard. It is a B2G (business-to-government) rule for public procurement; it creates no obligation between private businesses.

Its scope follows the procurement directives: invoices issued as a result of contracts under Directive 2014/24/EU (public procurement), 2014/25/EU (utilities), 2014/23/EU (concessions) and 2009/81/EC (defence and security), from the main contractor to the public buyer. Article 2 defines an electronic invoice as one "issued, transmitted and received in a structured electronic format which allows for its automatic and electronic processing". The directive asked the European standardisation bodies to draft a standard that is technologically neutral, compatible with international standards, usable by SMEs and suitable for B2B, and to publish a "limited number of syntaxes" for it.

The dates followed from publication of the standard. Commission Implementing Decision (EU) 2017/1870 of 16 October 2017 published the reference of EN 16931-1:2017 and its syntax list in the Official Journal on 17 October 2017. Member States had to apply the receiving obligation 18 months later for central authorities and could postpone it by up to 30 months for sub-central bodies — hence the commonly cited dates of April 2019 and April 2020. National implementations differ in the details: Germany, for example, added a routing identifier (Leitweg-ID) and the XRechnung specification, and its federal authorities have had to accept Peppol transmission since 27 November 2020 according to the Commission's country sheet. See B2B versus B2G for the practical differences.

What EN 16931 fixes at EU level

EN 16931 fixes the semantic content of an e-invoice — the elements, their meaning, their cardinality and the business rules between them — and lists which syntaxes may carry it. The standard was drafted by CEN/TC 434 under the directive's mandate.

The published family has several parts. Part 1 (EN 16931-1) is the semantic data model; Part 2 (CEN/TS 16931-2) is the list of compliant syntaxes — UBL 2.1 (ISO/IEC 19845:2015) and UN/CEFACT Cross Industry Invoice D16B; Parts 3-1 to 3-4 are the syntax-binding methodology and the bindings for UBL, UN/CEFACT XML and UN/EDIFACT; Part 4 gives transmission-interoperability guidelines; Part 5 describes how countries and sectors may extend the model; Part 6 reports test results. Under a licence agreement between the Commission and CEN, Parts 1 and 2 are available free of charge from national standards bodies; the other parts are sold.

The Commission states that a new edition, EN 16931-1:2026, was published in May 2026 and that the 2017 edition has been formally withdrawn but "will remain compliant during the migration period", with migration plans being developed by Member States and the relevant organisations. The EN 16931 page explains the model, its syntaxes and the CIUS and extension mechanism in detail.

What ViDA adds: the 2025–2035 timeline

ViDA — Council Directive (EU) 2025/516 of 11 March 2025, in force since 14 April 2025 — amends the VAT Directive 2006/112/EC in three areas: digital reporting and e-invoicing, the platform economy, and single VAT registration. For e-invoicing it does two things: it lets Member States mandate domestic e-invoicing without a special authorisation, and it makes structured e-invoices the basis of an EU-wide digital reporting requirement for cross-border B2B transactions from 2030.

The directive's recitals set the tone for the 2030 regime: an electronic invoice must be issued, transmitted and received in a structured electronic format allowing automated processing, aligned with Directive 2014/55/EU (recital 9); invoices for the reported cross-border transactions must be issued no later than 10 days after the chargeable event (recital 10); and pre-existing national reporting systems must converge by 2035 unless the Commission's assessment finds shortcomings (recital 24). The amended Article 218 lets a Member State require taxable persons established in its territory to issue e-invoices for domestic supplies, and the amended Article 232 lets it drop the recipient's consent for such invoices.

What is EU-wide and what is national

EU law fixes the definition, the standard and the two obligations above; the national legislator fixes scope, dates, format choice and transmission.

For a business this means that "EU-compliant" is necessary but never sufficient. An EN 16931 invoice is the right starting point in every Member State that follows the standard, but it still has to carry the national CIUS rules, travel the national channel and meet the national dates. The format guide maps formats to countries; cross-border e-invoicing covers the case where the two parties sit in different Member States.

How KRONENWERK handles this

KRONENWERK implements the EU layer through EN 16931 and the national layer through the format each country expects, generated and validated when the invoice is issued.

• EN 16931 invoices for Germany as XRechnung (UBL or CII) and ZUGFeRD, validated with the KoSIT Schematron rules and cross-checked with the Mustang library — SUPPORTED.
• Factur-X for France (PDF/A-3 with embedded CII) — generation SUPPORTED; transmission through an approved platform NOT YET READY (KRONENWERK is not a plateforme agréée).
• Peppol BIS Billing 3.0 UBL for Belgium — SUPPORTED WITH LIMITATIONS: KRONENWERK sends and receives over Peppol through an accredited access point provider (Storecove) once the company is connected in Settings → Delivery.
• FA(3) for Poland — generation SUPPORTED WITH LIMITATIONS; KSeF transmission NOT YET READY.
• Incoming XRechnung, ZUGFeRD/Factur-X and UBL files are read into bills; the free checker validates a file without storing it — SUPPORTED.

KRONENWERK does not file or transmit any VAT report to a tax authority and does not give tax advice; the 2030 reporting regime will be assessed when its implementing rules exist. Country pages: Germany, France, Belgium, Poland. Back to the Europe hub.