EU E-Invoicing in Public Procurement: EN 16931, Peppol & Supplier Compliance Guide

The EU E-Invoicing Directive: What It Requires

Directive 2014/55/EU on electronic invoicing in public procurement obliged EU member states to ensure their contracting authorities can receive and process structured electronic invoices complying with the European standard EN 16931. The deadlines were:

• April 2019: Central government contracting authorities must receive EN 16931-compliant e-invoices.
• April 2020: All sub-central contracting authorities (regional, local, health, utilities) must receive EN 16931-compliant e-invoices.

The directive sets a receiving obligation on buyers — every EU public authority must accept a structured e-invoice. Many member states have gone further by mandating that suppliers must send e-invoices, making PDF and paper invoices non-compliant for public contracts.

What Is EN 16931?

EN 16931 is the European standard for a semantic data model for the core elements of an electronic invoice. It defines which data fields are mandatory (seller identity, buyer identity, invoice date, line items, VAT) and how they should be structured so that any compliant system can process the invoice automatically without human rekeying.

EN 16931 can be implemented in two technical syntaxes:

• UBL 2.1 (Universal Business Language): XML-based, most commonly used in Northern and Western Europe and in the Peppol network.
• UN/CEFACT CII (Cross Industry Invoice): XML-based alternative syntax, used in some German and French national implementations.

A PDF invoice — even one generated from accounting software — is not an EN 16931-compliant e-invoice. Only machine-readable structured XML files meeting the standard qualify.

E-Invoicing by Country: Key National Platforms

What Suppliers Need to Do: Practical Compliance Steps

1. Check your contract. Every public contract should specify the e-invoicing format and platform required. If it doesn't, contact the buyer's finance team before submitting your first invoice.
2. Identify the correct platform for the buyer's country. Use the table above as a starting guide. For multi-country contracts, you may need to register on multiple platforms.
3. Register with a Peppol Access Point if your buyers are in Peppol-network countries (most of Northern and Western Europe). Access Point providers include certified software vendors — many accounting platforms have built-in Peppol connectivity.
4. Upgrade your invoicing software. Ensure your accounting or ERP system can generate EN 16931-compliant UBL 2.1 or CII XML files. Major platforms (SAP, Oracle, Microsoft Dynamics, Sage, Xero, QuickBooks) support this via native modules or certified add-ons.
5. Test before your first live invoice. Most national platforms provide test environments. Submit a test invoice before your first real invoice to verify that your buyer can receive and process it.

E-Invoicing and Payment Terms

EU public procurement contracts are subject to the Late Payment Directive (2011/7/EU), which caps public authority payment terms at 30 days (60 days for healthcare authorities). The payment clock typically starts from the receipt of a valid invoice. A non-compliant invoice — including a PDF when structured XML is required — may not start the payment clock, effectively extending payment timelines beyond the legal limit without the authority incurring late payment interest. Ensuring your invoices are in the correct format protects your cash flow as well as your compliance status.

Key Takeaways

• EU Directive 2014/55/EU requires all public sector buyers to accept EN 16931-compliant structured e-invoices — PDF invoices are non-compliant in most EU member states.
• Italy, France, Germany, Denmark, Sweden, Netherlands, Belgium, Spain, Finland, and Austria all have mandatory or near-mandatory B2G e-invoicing requirements.
• Peppol is the dominant network for B2G e-invoicing across Northern and Western Europe — register with a certified Peppol Access Point provider.
• Non-compliant invoices can delay the payment clock — submit structured XML invoices to protect your 30-day payment rights under the Late Payment Directive.
• Check your contract and contact the buyer's finance team before your first invoice to confirm the required format, platform, and reference data fields.