Compliance with Directive 2014/55/EU means sending electronic invoices to EU public-sector buyers in a format that follows the European standard EN 16931, delivered through a channel the buyer accepts, so the invoice can be received and processed without reformatting. The directive was adopted on 16 April 2014 and has been fully in force across the EU since 2020. If you sell to any public authority in the single market above the procurement thresholds, this is the framework you work inside.1European Commission. European Legislation on eInvoicing
Who and Which Contracts Are Covered
The directive governs invoices sent from private suppliers to public-sector buyers. National ministries, regional councils, municipal governments, and utilities in the water, energy, transport, and postal sectors all count as contracting authorities or contracting entities and must be able to accept a compliant electronic invoice. They cannot reject one on format grounds alone.2European Commission. Processing Electronic Invoices
The obligation attaches to contracts that meet or exceed the EU procurement thresholds. For 2026–2027 those are €140,000 for central government supplies and services, €216,000 for the same at sub-central level, and €5,404,000 for public works.3European Commission. Updated Public Procurement Thresholds Apply From 1 January 2026 Contracts below those values fall under national rules, and many member states have extended e-invoicing obligations to smaller procurements on their own.4European Commission. Public Procurement Thresholds
Defence and security contracts under Directive 2009/81/EC are in scope, but a member state can exempt any contract declared secret or requiring special security measures if it determines that its essential security interests cannot be protected through less intrusive means.5EUR-Lex. Directive 2014/55/EU on Electronic Invoicing in Public Procurement
Deadlines Already in Force
Central government contracting authorities had to be able to receive and process EN 16931-compliant invoices by 18 April 2019. Sub-central authorities such as regional and municipal bodies had an optional twelve-month extension, giving them a deadline of 18 April 2020.6European Commission. eInvoicing Compliance Roadmap Every EU member state and EEA country has transposed the directive, so the receiving side is live across the bloc. The remaining compliance work sits with suppliers: producing invoices that meet the standard and getting them into the right channel.
What Makes an Invoice Compliant
EN 16931 is a semantic data model. It defines the meaning of every field an electronic invoice can carry — seller name, tax amount, line item quantity, and so on — and how those fields relate to each other. It does not force a single file format. Different software systems in different countries can interpret the same invoice identically because the meaning is fixed, even when the underlying file format varies.7European Commission. EN 16931 Compliance
The Two Accepted Syntaxes
A contracting authority must accept invoices delivered in either of two XML syntaxes:
- UBL 2.1, the OASIS Universal Business Language invoice and credit note messages, defined in ISO/IEC 19845:2015.
- UN/CEFACT CII, the Cross Industry Invoice XML message based on the SCRDM-CII schemas.
Each syntax has a published binding that maps EN 16931 data elements to specific XML tags. Using a newer version of UBL or CII without an updated binding will break compliance.8European Commission. Required Syntaxes
Hybrid PDF Formats
Where a recipient still needs to read an invoice visually, hybrid formats embed a machine-readable XML file inside a PDF. The most widely used is Factur-X (called ZUGFeRD in Germany), pairing a PDF/A-3 document with a UN/CEFACT CII XML file conforming to EN 16931. The latest release, Factur-X 1.08 / ZUGFeRD 2.4, became applicable on 15 January 2026.9FNFE-MPE. Factur-X EN
Data Fields Your Invoice Must Carry
Automated validation at the receiving end will reject files with missing or malformed fields, so the content matters as much as the syntax. EN 16931’s core business terms cluster into a few groups.
- Identification: a unique invoice number, issue date, document type (invoice or credit note), and a reference to the purchase order or contract where one exists.
- Parties: legal name and postal address for both seller and buyer, with VAT identification numbers where the transaction involves VAT.
- Line items: each product or service on its own line with a description, quantity, unit of measure coded to UN/CEFACT Recommendation 20, unit price, and line-level totals.
- Tax breakdown: a tax summary with the VAT category code for each line. Standard codes include S for standard rate, Z for zero-rated, E for exempt, AE for reverse charge, and K for intra-community supply of goods and services.
- Payment information: the amount due, the payment due date, and payment instructions such as bank account details or credit transfer references.
If the seller uses a tax representative in the buyer’s country, the representative’s details must also appear. An unrecognised code or a missing required field will fail validation before any person in the buyer’s finance team sees the invoice.
How to Deliver the Invoice
Formatting alone is not enough. The file has to reach the buyer through a channel the buyer accepts, and in practice that means one of two routes.
The Peppol Network
Peppol is the most widely used cross-border infrastructure for exchanging e-invoices with EU public entities. It uses a four-corner model: the sender connects to a certified Peppol Access Point, which routes the document through the network to the buyer’s own Access Point. Sender and receiver need no direct technical link; the network handles interoperability.10OpenPeppol. The Future Is Open
To use Peppol you contract with a certified service provider that operates an Access Point. The provider handles the technical connection, validation, and delivery, typically charging you a per-document or monthly subscription fee. The Peppol BIS Billing 3.0 specification governs how invoices are formatted for the network, and is itself a Core Invoice Usage Specification of EN 16931, so any invoice valid under Peppol BIS Billing 3.0 is also valid under the European standard.11OpenPeppol. Peppol BIS Billing 3.0
National Portals
Some member states operate government portals for direct upload. Italy’s Sistema di Interscambio (SDI) validates and routes every invoice to the correct public body using a unique office code.12European Commission. eInvoicing in Italy France uses the Chorus Pro platform for public-sector invoices. These portals give immediate feedback on structural validation, and if a submission fails you get an error message identifying the problem — a wrong tax code, a missing buyer reference, an unsupported syntax version. Correcting and resubmitting is routine.
Whichever channel you use, the receiving system runs an automated check against the EN 16931 data model before the invoice enters the buyer’s accounts payable workflow. A passing check generates a receipt notification; a failure generates a rejection notice explaining which rules were violated.
Payment Clock and What Happens if You Fail Validation
Once a compliant e-invoice clears validation, the public authority’s payment obligation begins. Under Directive 2011/7/EU on combating late payment, public authorities must pay within 30 calendar days of receiving the invoice.13EUR-Lex. Directive 2011/7/EU – Combating Late Payment in Commercial Transactions Two narrow categories can extend to 60 days: public entities carrying out industrial or commercial activities on the market, and public healthcare entities. Outside those, 30 days is the ceiling.
Directive 2014/55/EU sets no EU-wide penalty for suppliers who submit non-compliant invoices. Enforcement is left to member states, and the immediate consequence is operational: an invoice that fails validation does not reach the payment system, and no compliant invoice means no payment. A non-compliant invoice may also fail to support VAT deductibility for the buyer, which gives the buyer its own reason to push back. Several member states have added explicit fines. France imposes a €50 penalty per non-compliant invoice, subject to an annual cap. Italy’s SDI blocks non-compliant files at the gate.
Storing Invoices After Delivery
The EU VAT Directive (2006/112/EC) requires businesses to store invoices but leaves the retention period to each member state. Some countries mandate as few as five years; others require ten. Italy, for example, requires public authorities to store invoices digitally for ten years.12European Commission. eInvoicing in Italy Check the rule in your own country, because getting it wrong can surface years later in a VAT audit.14European Commission. VAT Invoicing Many businesses apply electronic signatures or seals under the eIDAS Regulation (910/2014) to prove data integrity for stored invoices, though the directive itself does not require them.
Where the Rules Are Heading: B2B Mandates and ViDA
Directive 2014/55/EU covers only invoices to public buyers, but several member states have extended electronic invoicing to private business-to-business transactions using the same EN 16931 foundation. If you sell across borders in the EU, these mandates now touch invoices the directive itself does not.
- Italy: VAT-registered businesses have had to issue electronic invoices for B2B and B2C transactions through SDI since January 2019. The earlier turnover-based exemption was removed in January 2024, so the obligation now applies regardless of size.12European Commission. eInvoicing in Italy
- Germany: Under the Growth Opportunities Act, all businesses have had to be able to receive EN 16931-compliant e-invoices since 1 January 2025. The obligation to issue e-invoices applies to businesses with turnover above €800,000 from January 2027, and to all businesses from January 2028.15European Commission. eInvoicing in Germany
- France: Large and medium enterprises must issue e-invoices from 1 September 2026, with reception mandatory for all companies from the same date. Small and micro-enterprises must begin issuing by 1 September 2027.
- Belgium: Mandatory B2B e-invoicing took effect on 1 January 2026, with Peppol BIS as the default interoperability framework. Both parties can agree to use an alternative format, provided it still meets EN 16931.
The wider shift is the VAT in the Digital Age (ViDA) package, adopted on 11 March 2025. On entry into force, member states can introduce mandatory e-invoicing without seeking individual derogations. Digital reporting requirements for cross-border B2B transactions become mandatory from 1 July 2030, and by 1 January 2035 every domestic digital real-time reporting system must align with EU standards.16European Commission. Adoption of the VAT in the Digital Age Package
For businesses already compliant with Directive 2014/55/EU, the technical foundation carries forward. The semantic model, the syntaxes, and the delivery networks are the same. What changes is scope: a public procurement obligation is turning into a VAT compliance obligation that reaches most significant transactions in the single market.