Europe E-Invoicing 2026–2027:
The Timeline Every AP Team Needs

The Map: 12 Countries, 12 Deadlines

Below is the most complete single-page deadline reference available for European e-invoicing mandates in 2026–2027. Each entry includes the relevant legal authority — because when your tax advisor asks "which law says this," a link is better than a paraphrase.

How to read this table: Dates are in DD/MM/YYYY format where possible. "Est." means the date depends on the publication of an implementing ministerial order (Spain, Latvia). Croatia and Denmark confirm B2B scope; Germany and France distinguish between receive and issue obligations. All formats listed are EN 16931-compliant.

The Framework: ViDA and Why 2030 Matters Now

The mandates above are national. Beneath them sits a common EU framework: ViDA — VAT in the Digital Age, formally proposed as COM/2022/701 final on 8 December 2022 and adopted by the ECOFIN Council on 5 November 2024. ViDA contains three pillars, but the one that affects your AP workflow directly is Pillar 3: Digital Reporting Requirements (DRR) based on e-invoicing.

The timeline that matters:

The reason 2030 matters now is simple: businesses that implement country-by-country point solutions for 2026–2027 mandates will face a second integration wave in 2030. Those who choose a platform with multi-country architecture from the start — whether an e-invoicing service provider, an ERP module, or a Peppol Access Point — will absorb the 2030 transition as a configuration change, not a reimplementation.

The Infrastructure: Peppol, 4-Corner vs 5-Corner, and What It Means for Your AP Team

When a German client tells you "we require Peppol," and a French supplier tells you "we use a PDP," and your Polish subsidiary says "everything goes through KSeF" — those are three different things operating at three different layers of the e-invoicing stack. Understanding the difference between a transport network, a transmission model, and a national platform is the single biggest factor in choosing the right compliance approach.

Peppol Is a Transport Network, Not an Invoice Format

Peppol (Pan-European Public Procurement On-Line) is a secure delivery network for business documents. Think of it as the postal service for e-invoices: it routes structured documents from sender to receiver through certified Access Points, but it does not define what the document looks like. The format is EN 16931 (the European e-invoicing standard published by CEN), and Peppol's implementation of it is called Peppol BIS Billing 3.0. Peppol BIS picks UBL 2.1 as its syntax and adds network-specific validation rules. Understanding this distinction — Peppol = how it gets there, EN 16931 = what it contains — prevents months of confusion when your ERP vendor asks "which format do you need."

4-Corner vs 5-Corner: Who's Watching

In a 5-corner model (also called Continuous Transaction Control, or CTC), the government sees the invoice before the buyer does. In France, the PPF (Portail Public de Facturation) acts as this fifth corner: certified platforms called PDPs (Plateformes de Dématérialisation Partenaires) transmit invoice data to the PPF, which forwards it to the buyer's platform. Polish KSeF goes further — the government platform is the single mandatory channel, not one option among several.

What this means for your AP team: in a 5-corner country, your invoice workflow has an additional latency step. If the tax authority's platform is down (and national e-invoicing platforms have experienced outages during early rollouts), invoices stall. Your AP team needs a fallback procedure — typically a PDF copy for payment processing while the structured version waits for clearance. This is a contingency worth building into your SOP before the mandate goes live, not after the first outage.

What This Actually Means: A 3-Phase Preparation Checklist

If your business trades with suppliers or customers in any of the 13 countries with active mandates, you need a plan. Below is a phased approach — not by country, but by what your team should know and do, in order. It is designed for an AP team with existing ERP infrastructure, not a greenfield build.

Phase 1: Information Gathering (Week 1–2)

Phase 2: Technical Assessment (Week 3–6)

Phase 3: Execution (Week 7–12)

The Countries Driving the 2026–2027 Wave

Six economies account for the bulk of AP impact in the 2026–2027 wave. Each has a different architecture, different timing, and different edge cases. Here is what matters for each — with links to our detailed country guides where available.

France — September 2026: The 5-Corner Debut

France's reform — anchored in Article 91 of the Loi de finances 2024 and detailed in Décret n°2024-266 — is the most architecturally complex in Europe. It mandates a 5-corner model: invoices flow through certified partner platforms (PDPs) to the government's PPF, which routes them to the buyer's platform. Three formats are accepted: Factur-X (hybrid PDF/XML), UBL 2.1, and CII. September 2026 requires all businesses to be capable of receiving e-invoices, and large/mid-size companies must issue them. SMEs and TPEs have until September 2027 for issuance. We analyzed the structural tension in this reform — where non-compliant PDFs persist alongside structured mandates — in our earlier article on France's e-invoicing complexity paradox.

Germany — January 2027: The Phased Approach

Germany's mandate, enacted through the Wachstumschancengesetz (Growth Opportunities Act, Bundesrat approval 22 March 2024) which amended §14 UStG, is phased across three stages. Since January 2025, all domestic businesses must be able to receive e-invoices. From January 2027, companies with turnover above €800,000 must issue e-invoices. From January 2028, all companies must issue. Two formats dominate: XRechnung (pure XML, the government standard) and ZUGFeRD 2.x (hybrid PDF/XML, more common in commercial practice). The embedded XML is the legally authoritative document — if PDF and XML conflict, the XML wins. We explored the underlying manual-entry problem this mandate aims to solve in our German invoice manual entry analysis.

Poland — February 2026: The Centralized Model

Poland's KSeF (Krajowy System e-Faktur), established by the Act of 5 August 2025 (signed into law 27 August 2025), is a centralized government platform — unlike France's multi-PDP model. All B2B invoices must pass through KSeF in the proprietary FA(3) XML format. The rollout: large taxpayers (>PLN 200M turnover, ≈€46M) from 1 February 2026; all other VAT-registered businesses from 1 April 2026; micro-entrepreneurs from 1 January 2027. A unique feature: buyer acceptance (explicit or implicit within a statutory period) is a condition of invoice validity. If your Polish subsidiary receives an invoice via KSeF and doesn't acknowledge it, the invoice may not be legally valid.

Belgium — January 2026: Peppol at Scale

Belgium's mandate, effective 1 January 2026 with a three-month tolerance period ending 31 March 2026, requires all VAT-registered Belgian businesses to exchange B2B invoices via the Peppol network using Peppol BIS Billing 3.0. Over 500,000 businesses were onboarded by late 2025, making it the fastest large-scale Peppol deployment in Europe. E-reporting to the Belgian tax authority (FPS Finance) via a 5-corner model is planned for 2028. Belgium is the reference case for "Peppol-first" compliance — if your AP platform handles Belgium, it can likely handle Denmark, Norway, and upcoming Peppol mandates.

Spain — October 2027: The Late Starter with Teeth

Spain's Ley 18/2022 (Crea y Crece), implemented via Royal Decree 238/2026 (approved by the Council of Ministers on 24 March 2026), mandates B2B e-invoicing for all domestic transactions. The phased rollout starts with companies above €8M turnover (estimated October 2027), extending to all businesses and freelancers by October 2028. Spain accepts multiple formats (Facturae, UBL, CII) and allows both public and private platforms. Alongside this, the Verifactu regulation (RD 1007/2023) mandates certified, tamper-proof invoicing software with real-time reporting to AEAT. We covered the Verifactu/TicketBAI compliance landscape in our Spain e-invoicing problem analysis.

Italy — Since 2019: The Blueprint

Italy's Sistema di Interscambio (SdI), established by Legislative Decree 127/2015 and operational since 1 January 2019, is the EU's most mature e-invoicing system. All domestic B2B and B2C transactions flow through SdI in FatturaPA XML format. The results: €12.7 billion in VAT gap reduction by 2021 — the largest single-year drop among all EU-27 member states — and €1.7–2 billion in additional VAT revenue between 2019–2022. Italy's model is the direct inspiration for ViDA's DRR architecture. For businesses operating in Italy, the system is operationally stable but the FatturaPA format is not natively EN 16931-compliant, creating alignment work ahead of the 2035 ViDA harmonization deadline.

Frequently Asked Questions

Do I really need to comply if I only receive 1–2 invoices per month from a mandate country?

Yes. The obligations are based on your tax registration status in the country, not on invoice volume. If your entity is VAT-registered in Belgium, you must be able to receive Peppol e-invoices, even if you receive one per year. The practical answer is often simpler than it sounds: most mandate countries provide a free government portal for low-volume receivers (Belgium's Mercurius, France's PPF, Poland's KSeF web interface). One freelancer on Reddit described the situation bluntly: "I only have 1 or max. 2 invoices each month and were perfectly happy creating them in excel and sending them out in pdfs. Now I'm obligated to switch." The compliance burden for micro-businesses is real, but free-tier government portals are the intended path. Your accountant can likely handle it.

Is a PDF with embedded XML (ZUGFeRD / Factur-X) enough?

In Germany and France, yes — with a critical caveat. ZUGFeRD 2.x and Factur-X are hybrid formats: a human-readable PDF with embedded structured XML. In both countries, the XML is the legally authoritative document. If the PDF displays €10,000 but the embedded XML contains €1,000, the XML value is what the tax authority acts on. This means your AP team cannot simply open the PDF and key the data into your ERP — they must extract from the XML. A workflow that treats a hybrid invoice as "just another PDF" is a workflow that will introduce mismatches.

Can I use the same e-invoicing platform for all EU countries?

Yes, but with a qualification. Global e-invoicing platforms (Tradeshift, Pagero, Basware, Unifiedpost, Sovos) support multiple countries and handle format conversion and network routing. But each country requires separate onboarding: a Peppol ID for Belgium, a SIREN-linked PDP registration for France, a KSeF token for Poland. A multi-country platform consolidates the technical work; it does not eliminate the administrative work. The platform that handles your German XRechnung might not yet support Polish FA(3) — verify country coverage before committing.

What happens if my supplier refuses to send e-invoices?

In most mandate countries, the obligation falls on the issuer, not the receiver. But if you are the issuer and your customer demands an e-invoice (as they are entitled to under most mandates), you must comply. In practice, during the early months of a mandate, enforcement is typically lenient if you can demonstrate good-faith effort. Belgium's three-month tolerance period (January–March 2026) is the model: technical violations were waived if the business showed evidence of working toward compliance. Croatia applied zero financial penalties throughout 2026. Do not rely on tolerance periods as a substitute for preparation — they are a safety net, not a strategy.

Does e-invoicing eliminate the need for document data extraction?

No. E-invoicing reduces the volume of unstructured PDFs in your AP inbox over time, but it does not eliminate them. Three reasons: (1) cross-border invoices from non-EU suppliers still arrive as PDFs; (2) many domestic SMEs will miss their deadlines or use non-compliant formats during transition periods; (3) B2C transactions are exempt from nearly all current mandates. Your AP workflow will operate in a mixed-format environment for years, not months. The practical implication: you need a system that can extract data from both XML e-invoices and scanned PDFs into a common data layer, not two separate processes feeding the same ERP.

What to Do Tomorrow

The deadlines in the table above are fixed. The preparation timeline is not — it shrinks by one day for every day you wait. But the work is finite and structured. Start with Phase 1: map your invoice flows by country, check your VAT registrations, fill in your obligation matrix. That one spreadsheet answers the question every CFO will ask: "What does this actually mean for us?"

If your team is facing a specific country mandate — France in September, Poland already active, Germany in January — our upcoming country guides will break down each one in the same format: timeline by business size, exact legal references, format specifications, and platform options.

Compliance is not a competitive advantage. But getting there without disrupting your AP operations — that is. The difference is whether you start now, or start when the first rejected invoice hits your queue.