E-invoicing compliance in Europe: what businesses need to know in 2026
France, Germany, Belgium, and the Netherlands are all rolling out mandatory e-invoicing. Here is what EN 16931, Factur-X, Peppol, and the ViDA directive mean for your business.
Why e-invoicing is becoming mandatory across Europe
The European Union's ViDA directive (VAT in the Digital Age) is reshaping how businesses exchange invoices. Starting in 2026, large enterprises in France must issue e-invoices via the Chorus Pro platform. Germany's E-Rechnungsgesetz requires structured XML invoices for B2G and, progressively, B2B transactions. Belgium and the Netherlands are following suit through Peppol.
The common denominator is the EN 16931 standard — a European semantic data model that defines the mandatory fields for a compliant electronic invoice. Whether you use Factur-X (France/Germany), UBL (Peppol), or XRechnung (Germany), all formats implement EN 16931.
The shift to mandatory e-invoicing is driven by multiple factors: closing the €93 billion annual EU VAT gap through real-time digital reporting, reducing administrative costs (e-invoicing saves an estimated €6.50 per invoice compared to paper processing), and enabling faster cross-border trade. For businesses, this is not optional — non-compliance leads to invoice rejections, delayed payments, and potential penalties.
The EN 16931 standard: the common backbone of European e-invoicing
EN 16931 is not a file format — it is a semantic data model published by CEN (European Committee for Standardization) that specifies which invoice fields are mandatory, conditional, or optional. It was developed under EU Directive 2014/55/EU and defines 162 business terms (BT) organized in 44 business groups (BG). These terms cover everything from invoice identification and seller/buyer details to VAT breakdown, line items, payment terms, and delivery information.
For validation purposes, compliance with EN 16931 means two things: structural validity (the XML or PDF/A-3 file is well-formed and matches the XSD schema) and business rule compliance (amounts add up, VAT rates are valid, mandatory fields are present). The standard defines over 150 business rules, coded as BR-xx and BR-CO-xx, that must be satisfied. ValidateFin checks both for UBL/Peppol invoices and Factur-X files.
EN 16931 recognizes two official syntaxes: UBL 2.1 (ISO/IEC 19845) and UN/CEFACT CII (Cross-Industry Invoice). A Factur-X or ZUGFeRD invoice uses the CII syntax embedded in a PDF/A-3 container, while Peppol BIS Billing 3.0 uses UBL 2.1. Despite different XML structures, both syntaxes carry the same semantic information — an invoice valid in one syntax contains the same business data as one in the other.
Country-by-country overview: e-invoicing mandates in Europe
- France — Mandatory e-invoicing via Chorus Pro and authorized PDP platforms. Large enterprises must issue e-invoices from September 2026; mid-size companies from September 2027; small businesses from September 2028. Preferred format: Factur-X (EN 16931 profile) or UBL via Peppol. All businesses must accept e-invoices from September 2026. The e-reporting obligation requires transmitting transaction data (B2C, international) to the tax administration in real time.
- Germany — E-Rechnungsgesetz mandates structured XML (EN 16931) for B2G since November 2020. B2B e-invoicing obligation: all businesses must be able to receive e-invoices from January 2025; sending obligation starts January 2027 for companies with revenue over €800,000, and January 2028 for all others. Preferred formats: XRechnung (for public sector) and ZUGFeRD 2.x (for private sector). EDI systems may continue until 2028 with buyer consent.
- Belgium — Peppol BIS Billing 3.0 mandatory for B2G (federal suppliers) since 2020. B2B mandatory e-invoicing from January 2026 for all VAT-registered businesses — Belgium is the first EU country to mandate Peppol for B2B. Invoices must be sent via a certified Peppol Access Point. The Belgian tax administration (SPF Finances) uses e-invoicing data for pre-filled VAT returns.
- Netherlands — Peppol BIS Billing 3.0 mandatory for central government since 2017 and for all government entities since 2019. The Netherlands has one of the highest Peppol adoption rates in Europe with over 300,000 registered organizations. B2B mandate expected under ViDA transposition. The Dutch standard SI-UBL is being phased out in favor of Peppol BIS 3.0.
- Italy — Pioneer in European e-invoicing: mandatory B2B and B2C since January 2019 via SDI (Sistema di Interscambio). The Italian format FatturaPA is a national standard (not EN 16931) but cross-border invoices increasingly use Peppol. Italy's experience has been a model for other EU countries — the VAT gap decreased by €3.5 billion since the mandate.
- Poland — KSeF (Krajowy System e-Faktur) — the national e-invoicing platform — becomes mandatory from February 2026 for companies with revenue over PLN 200 million, and from April 2026 for all others. Poland uses a structured XML format based on FA(2) schema. The system provides real-time invoice verification and will eventually replace paper invoices entirely.
- Spain — Ley Crea y Crece mandates B2B e-invoicing for all businesses. The timeline depends on company size: large enterprises from mid-2026, SMEs one year later. Spain uses the FACe platform for B2G and TicketBAI for the Basque Country. The national format Facturae coexists with Peppol BIS for cross-border transactions.
- Portugal — SAF-T (Standard Audit File for Tax) has been mandatory since 2020 for all invoicing data. While not a traditional e-invoicing mandate, Portugal requires real-time invoice reporting to the tax authority (AT) via ATCUD codes. B2G e-invoicing via Peppol is mandatory since 2021. A broader B2B mandate is expected to align with ViDA.
The ViDA directive: what changes for cross-border invoicing
The VAT in the Digital Age (ViDA) directive, adopted by the EU Council in 2024, is the most significant reform of European VAT rules in decades. It introduces three pillars: mandatory digital reporting for intra-EU B2B transactions (starting 2030), a single VAT registration across the EU, and updated rules for the platform economy. For e-invoicing, ViDA means that every cross-border B2B invoice within the EU will need to be issued in a structured electronic format (EN 16931) and reported to the national tax administration within a short timeframe.
The directive establishes a phased timeline. From 2028, member states may impose domestic e-invoicing mandates without needing a derogation from the EU Council — removing a major bureaucratic hurdle that previously slowed adoption. From 2030, all intra-EU B2B transactions must be reported digitally, and structured e-invoicing becomes the default. Member states may opt for real-time reporting (like Italy's SDI model) or periodic batch reporting.
For businesses operating across multiple EU countries, ViDA brings both challenges and simplification. The challenge is adapting to potentially different national systems (France's Chorus Pro, Italy's SDI, Poland's KSeF, Belgium's Peppol mandate). The simplification is that all systems must converge on EN 16931, meaning a single validation logic can check invoices destined for any EU market. Tools like ValidateFin that validate against EN 16931 business rules become essential for ensuring cross-border compliance.
E-invoicing format comparison: which format for which market?
Not all e-invoicing formats are equal. While they all implement EN 16931, they differ in syntax, container format, and regional adoption. The table below compares the five main formats used in Europe today.
| Format | Syntax | Primary markets | Use case |
|---|---|---|---|
| UBL 2.1 (Peppol BIS 3.0) | XML (ISO/IEC 19845) | Belgium, Netherlands, Nordics, UK, Singapore | Cross-border B2B/B2G via Peppol network |
| Factur-X / ZUGFeRD 2.x | PDF/A-3 + CII XML | France, Germany, Austria, Switzerland | Hybrid invoices readable by humans and machines |
| XRechnung | UBL 2.1 or CII XML | Germany (B2G) | German public sector procurement |
| FatturaPA | Custom XML (FPA 1.2.2) | Italy | All domestic B2B and B2C via SDI |
| Facturae | Custom XML (3.2.x) | Spain | Spanish public sector (FACe platform) |
For businesses operating across multiple European markets, UBL 2.1 with Peppol BIS 3.0 offers the broadest interoperability. For the Franco-German corridor, Factur-X / ZUGFeRD is the natural choice as it satisfies both markets with a single file. XRechnung is a subset of UBL/CII specifically tailored for German B2G requirements.
How to prepare your business for e-invoicing compliance
Preparing for e-invoicing is not just a technical project — it impacts your accounting processes, ERP configuration, supplier relationships, and tax reporting. Here are the key steps to ensure a smooth transition:
- Audit your current invoicing process — Map how invoices are created, sent, received, and archived today. Identify manual steps that will need automation. Count your monthly invoice volume to estimate the impact.
- Choose your format and connectivity — Decide whether to use Peppol (via an Access Point), a PDP platform (France), or direct connections. For most European businesses, Peppol BIS 3.0 (UBL 2.1) is the safest long-term bet.
- Update your ERP or accounting software — Ensure your software can generate EN 16931-compliant invoices. Most modern ERP systems (SAP, Oracle, Odoo, Exact, etc.) have e-invoicing modules — check if yours is up to date.
- Validate before you send — Integrate validation into your workflow. A rejected e-invoice costs time and damages supplier relationships. Use ValidateFin to check your files against EN 16931 rules before submission.
- Train your finance team — E-invoicing changes daily workflows. Accountants need to understand the new formats, how to handle rejections, and how to reconcile structured data with existing bookkeeping processes.
- Plan for archiving and compliance — E-invoices must be stored in their original electronic format for the legally required retention period (typically 7-10 years). Ensure your archiving solution supports PDF/A-3, UBL XML, and associated metadata.
Starting early is critical. Companies that wait until the mandate deadline often face rushed implementations, integration bugs, and compliance gaps. A phased approach — starting with B2G invoices, then extending to B2B — allows testing and refinement before the full obligation kicks in.
Penalties and enforcement: what happens if you are not compliant?
E-invoicing mandates come with enforcement mechanisms. In France, failure to issue a compliant e-invoice can result in a fine of €15 per invoice (capped at €15,000 per year for the first offense). In Italy, penalties for missing or incorrect SDI submissions range from 5% to 10% of the invoice value. Germany's penalties for non-compliant B2G invoices include rejection of the invoice by the public buyer, effectively blocking payment.
Beyond direct penalties, non-compliance creates practical problems. A non-compliant invoice submitted to Chorus Pro or a Peppol Access Point will simply be rejected — the buyer never receives it. This delays payment, creates reconciliation issues, and can damage the commercial relationship. For VAT deduction purposes, some countries require that the invoice be in the mandated electronic format.
The enforcement trend is toward real-time verification. Italy's SDI already validates invoices at submission time. France's PDP model and Poland's KSeF will do the same. This means validation errors will be caught immediately, not weeks later during an audit. Pre-validating your invoices with a tool like ValidateFin ensures they pass these checks on the first attempt.
Validate your e-invoices before submission
Submitting a non-compliant invoice can result in rejection by your customer's ERP, the Chorus Pro platform, or a Peppol access point. ValidateFin lets you validate Factur-X / ZUGFeRD PDF invoices and UBL / Peppol XML invoices instantly — 100% in your browser, no data transmitted.
Frequently Asked Questions
What is the ViDA directive and when does it take effect?
ViDA (VAT in the Digital Age) is an EU directive making structured e-invoicing mandatory for intra-EU B2B transactions. It was adopted by the EU Council in 2024 and introduces a phased timeline: from 2028, member states can mandate domestic e-invoicing without EU derogation; from 2030, all cross-border B2B invoices must be issued electronically in EN 16931 format and reported digitally to tax administrations.
Which countries in Europe already require mandatory e-invoicing?
As of 2026: Italy (SDI since 2019 for all B2B/B2C), France (Chorus Pro for B2G since 2020, PDP rollout for B2B from September 2026), Belgium (mandatory B2B via Peppol from January 2026), Germany (mandatory B2B reception from January 2025, sending from 2027), Poland (KSeF from February 2026), and Spain (Ley Crea y Crece from mid-2026 for large enterprises). Several Nordic countries also mandate Peppol for B2G.
What e-invoicing format should I use for European compliance?
For European compliance, use formats conforming to EN 16931. The two main syntaxes are UBL 2.1 (Peppol network, most EU countries) and UN/CEFACT CII (Factur-X/ZUGFeRD). For cross-border Peppol transactions, UBL 2.1 with Peppol BIS 3.0 is recommended. For the French and German domestic markets, Factur-X / ZUGFeRD is preferred as it combines human-readable PDF with machine-readable XML.
What is the difference between Factur-X, ZUGFeRD, and XRechnung?
Factur-X is the French branding and ZUGFeRD is the German branding for the same hybrid PDF/XML invoice format — they are technically identical since ZUGFeRD 2.0. Both embed a CII XML file inside a PDF/A-3. XRechnung is a pure XML format (UBL 2.1 or CII) used specifically for German public sector invoicing — it has no PDF component. All three comply with EN 16931.
How does the Peppol network work for e-invoicing?
Peppol is a decentralized network where businesses connect through certified Access Points (similar to email servers). To send an invoice, your Access Point looks up the receiver's Peppol ID in the SMP (Service Metadata Publisher) directory, establishes a secure connection via the AS4 protocol, and delivers the UBL invoice. The network ensures interoperability — a Belgian company using one Access Point can seamlessly send invoices to a Dutch company using a different Access Point.
What is EN 16931 and why is it important?
EN 16931 is the European standard for the semantic data model of electronic invoices, published by CEN under EU Directive 2014/55/EU. It defines 162 business terms organized in 44 groups, covering all invoice data from identification to payment terms. It also defines over 150 business rules that must be satisfied. EN 16931 is important because it ensures that any compliant e-invoice — regardless of syntax (UBL or CII) — carries the same semantic information and can be validated consistently across all EU member states.
Can I use the same e-invoice format for all European countries?
In theory, any EN 16931-compliant format is accepted across Europe. In practice, each country has preferences: France and Germany prefer Factur-X/ZUGFeRD, Belgium and the Netherlands require Peppol BIS (UBL), Italy uses FatturaPA (a national format), and Spain uses Facturae. For maximum interoperability, UBL 2.1 via Peppol is the broadest choice. Some businesses maintain two formats: Factur-X for domestic and Peppol UBL for cross-border.
What are the penalties for not complying with e-invoicing mandates?
Penalties vary by country. In France, fines are €15 per non-compliant invoice (capped at €15,000/year for first offenses). In Italy, penalties range from 5% to 10% of invoice value for missing or incorrect SDI submissions. In Germany, non-compliant B2G invoices are rejected, blocking payment. Beyond fines, non-compliance means invoices are rejected at the platform level, causing payment delays and reconciliation problems.
Do I need to change my ERP to comply with e-invoicing?
Not necessarily. Most modern ERP systems (SAP, Oracle, Sage, Odoo, Exact, Microsoft Dynamics) have e-invoicing modules or can generate EN 16931-compliant output with configuration updates. You may need a Peppol Access Point subscription or PDP connector. For legacy systems, third-party middleware can convert your existing output to compliant formats. The key requirement is that your system produces valid EN 16931 XML or PDF/A-3 output.
How can I validate my e-invoices before sending them?
Use ValidateFin's free online tools to validate your e-invoices before submission. The UBL / Peppol Validator checks your XML against Peppol BIS 3.0 business rules and EN 16931 requirements. The Factur-X / ZUGFeRD Viewer extracts and validates the XML embedded in your hybrid PDF. All validation happens in your browser — no invoice data is transmitted to any server, ensuring full GDPR compliance for sensitive financial documents.