EU E-Invoice Mandate Timeline: Country Deadlines 2025–2027

Friday, August 28, 2026

Half of EU member states will require structured e-invoices before the end of 2026 — and the other half are publishing their plans right now. If you sell to businesses anywhere in the bloc, the e-invoice mandate EU country deadlines are no longer a 2030 problem. They are a 2025 problem, and the calendar below is the only one you need to keep cross-border invoicing legal through 2027.

The legal backbone is the EU Directive 2014/55/EU, which makes the EN 16931 European standard for electronic invoicing the baseline every member state must support. VAT in the Digital Age (ViDA) then accelerated the timeline. From 2030 at the latest, every B2B invoice issued between EU-established businesses must be a structured EN 16931 e-invoice, and cross-border exchanges must go through a Peppol-based network. National governments are not waiting for 2030 — they are rolling out mandates now, country by country, on a staggered schedule that runs through 2027. Below is the country-by-country status, what each deadline actually means for a typical SMB, and a 90-day plan to get compliant without buying enterprise document management software.

Where the EU e-invoice mandate stands today (EN 16931 recap)

Before looking at any national deadline, it helps to fix the vocabulary. EN 16931 is the CEN-published European semantic standard for electronic invoices. An EN 16931 e-invoice is a structured file (typically UBL 2.1 or UN/CEFACT XML Cross-Industry Invoice) in which every field — supplier, customer, line items, VAT breakdown, payment terms — is a tagged data element a machine can read without OCR. PDF plus ZUGFeRD, Factur-X, and Peppol BIS Billing 3.0 are all EN 16931-compliant formats.

The ViDA reform package, politically agreed in 2024 and being transposed through 2027–2030, makes the standard mandatory for all B2B invoices inside the EU and introduces digital reporting requirements (DRR) so VAT data is filed almost in real time. The headline milestone is 2030, but ViDA explicitly lets member states run earlier national mandates under the same standard — and most are doing exactly that.

The other shared piece is Peppol, the open network for public procurement e-invoicing that has quietly become the de-facto private-sector transport for cross-border e-invoices in Europe. Each country has a Peppol Authority that accredits Access Point providers; your ERP, accounting tool, or compliance platform speaks to one Access Point and reaches every other. By Q1 2025, 18+ EU member states had a live Peppol infrastructure, and the major mandates below all converge on it.

Three practical implications follow:

Format matters. PDF-only is no longer enough. Germany already requires GoBD-compliant structured archiving, and France mandates a hybrid Factur-X (PDF + XML) under specific schemas.
Routing matters. National platforms (Italy's SDI, France's PPF, Poland's KSeF) plus Peppol Access Points are the legal "pipes." Sending a perfectly valid XML by email is still non-compliant in many of these regimes.
Reporting matters. DRR means tax authorities will receive the invoice data, often within days or hours of issuance. Audits become near-real-time.

That is the floor. Now the ceilings — when each country turns the floor into a hard wall.

Germany B2B e-invoice: what changes in 2025 and 2027

Germany's Growth Opportunities Act (Wachstumschancengesetz) of March 2024 embedded a B2B e-invoice obligation directly into § 14 of the UStG (Umsatzsteuergesetz). There are two deadlines that matter, and they are different in nature.

From 1 January 2025, every German B2B business must be able to receive an EN 16931 e-invoice. It can be a Peppol invoice, a pure XML, or a hybrid (ZUGFeRD 2.x / Factur-X) embedded in a PDF. You can still send paper, PDF, or EDI in 2025; the 2025 change is one-sided.

From 1 January 2027, every B2B invoice between German-established businesses must be issued as an EN 16931 e-ininvoice, with limited exceptions for small amounts (invoices under €250) and certain edge cases (e.g. final consumers, certain transport tickets). Businesses with prior-year turnover under €800,000 get a transitional derogation until the end of 2027, which effectively gives micro-businesses a soft ramp.

In practice this means Germany B2B e-invoice mandatory compliance has two phases for an SMB:

Now → end of 2026: Make sure your accounting inbox and ERP can ingest a ZUGFeRD/Factur-X PDF and a Peppol UBL invoice. Test with at least two suppliers before year-end. Update your incoming-invoice process so structured data lands in your bookkeeping system, not a scanned image.
January 2027: Switch your outgoing invoicing to an EN 16931-compliant format. If your current tool cannot produce ZUGFeRD 2.x or Peppol BIS, you need to migrate before Q4 2026.

Two things to budget for: a Peppol Access Point subscription (often bundled with e-invoicing or ERP SaaS) and a structured archiving workflow that satisfies GoBD. Audit trails must show immutability, timestamping, and a clear chain from receipt to bookkeeping entry.

France 2026 rollout: the PPF, the directories, who is in which wave

France's facture électronique 2026 rollout is the most prescriptive in the EU. The legal base is Article 26 of Loi de finances 2024, building on the earlier 2022 reform. The infrastructure is the Portail Public de Facturation (PPF) — a state hub that connects businesses, the DGFiP tax authority, and certified Plateformes de Dématérialisation Partenaires (PDP). The ANNUAIRE is a public directory of business e-invoicing identifiers used to route invoices to the right PDP, replacing legacy SIRET-only routing.

Three waves, based on company size, are staggered across 2026 and 2027:

1 September 2026: All companies must be able to receive a structured e-invoice. The obligation to issue one applies to large enterprises (more than 5,000 employees, or more than €1.5 bn turnover, or more than €2.2 bn balance sheet).
1 September 2027: Mid-cap issuers (250–5,000 employees, €50m–€1.5 bn turnover or balance sheet €43m–€2.2 bn) must issue e-invoices.
1 September 2027: SMEs, micro-enterprises, and self-employed workers must issue e-invoices. (The 2024 Finance Law collapsed the original two-tier SME wave into a single date.)

A French e-invoice is Factur-X (PDF/A-3 with embedded XML) at the minimum, but the PPF accepts UBL 2.1, UN/CEFACT CII, and Peppol BIS through certified PDPs. Critically, France requires e-reporting alongside: periodic VAT declarations will be replaced or supplemented by transactional reports sent through the PPF, including for B2C transactions and certain cross-border flows.

For an SMB outside France selling into France, this matters because your French customer will demand you send a compliant invoice through their PDP or through a Peppol Access Point that the PPF recognises. If your tool does not speak Factur-X or Peppol, you cannot invoice them.

Practical prep for an SMB:

Choose an accounting or ERP tool with a French PDP integration or a Peppol Access Point that the PPF has approved.
Pre-register your business in the ANNUAIRE once the directory opens for registration (planned from late 2025).
Map your invoice numbering, VAT IDs, and legal entity identifiers to the PPF schema; bad routing means invoices bounce and payment delays pile up.

Italy FatturaPA & SDI: lessons from the first mandatory market

Italy has run Italy e-invoicing SDI FatturaPA since 2018 for B2B and B2G, then 2019 for most B2B. The system is the Sistema di Interscambio (SDI), a state-operated central router that ingests every invoice in FatturaPA XML, validates it, and delivers it to the recipient. The recipient must also receive via SDI; sending a paper invoice to another Italian business is non-compliant.

The lessons for the rest of the EU are concrete:

Format enforcement works. Because SDI rejects malformed XML, the format quickly stabilised. Today there are essentially two compliant flavours: pure FatturaPA XML and FatturaPA hybrid PDFs with embedded XML — both EN 16931-compatible since the 2022 schema update.
Real-time reporting changes behaviour. SDI forwards invoice data to the Agenzia delle Entrate, which uses it to pre-fill VAT returns and to run cross-checks against the esterometro (cross-border ledger). Discrepancies trigger near-immediate assessments.
Public sector uptake drives private adoption. Italian government bodies only pay on SDI-received invoices, so suppliers comply or wait. France's PPF borrows the same logic.
Onboarding costs are front-loaded, then trivial. The first invoice for a new supplier is the hardest because of certification, signature, and PEC or codice destinatario setup. After that, sending is a one-click operation inside most Italian accounting suites.

If you sell into Italy, you must transmit through SDI — directly or via a certified intermediary. Cross-border invoices to Italian customers can use SDI, Peppol, or, until ViDA kicks in, the esterometro ledger, but Peppol-to-SDI interoperability is increasingly the default.

Belgium, Poland (KSeF), Netherlands, Austria: status and dates

The remaining countries on the near-term watchlist are doing different things on different dates, so a country-by-country summary is the cleanest way to plan.

Belgium. A Peppol-first regime. B2G has been mandatory since 2024 (above EU thresholds). B2B e-invoicing is not yet mandatory, but the government has confirmed a Belgium Peppol e-invoice deadline for B2B starting 1 January 2026 for large enterprises and rolling out through 2027 for SMEs, all built on the EN 16931 standard. Belgium does not plan a national SDI-style hub; it relies entirely on Peppol Access Points and a thin federal routing layer.

Poland — KSeF (Krajowy System e-Faktur). The Poland KSeF mandatory e-invoice rollout is the most disruptive outside France. B2B e-invoicing through the central KSeF platform was originally set for February 2026, then deferred to 1 February 2026 for large enterprises (above 200 employees or above PLN 200 m turnover) and 1 April 2026 for SMBs, with the system fully mandatory for all B2B invoices by 2027 in line with the latest ministerial roadmap. KSeF issues sequential invoice numbers and timestamps centrally; you issue the invoice by sending structured XML to the platform and receive it back with a KSeF ID. For non-resident sellers, KSeF integration via certified providers and Peppol interoperability is required.

Netherlands. No hard B2B mandate yet, but the Wet elektronische facturatie track is moving. The government has signalled 2027 for a Peppol-based B2B obligation aligned with ViDA. Until then, B2G e-invoicing is mandatory, and Peppol is the de-facto exchange method through the NLCIUS profile.

Austria. E-Rechnung became mandatory for federal procurement contracts from 2024, with state-level mandates following. Austria uses Peppol BIS Billing 3.0 and the national eRechnung.at profile, both EN 16931-based. A full B2B mandate is not yet in force but is expected to follow the ViDA 2030 timeline unless accelerated.

Other countries worth tracking: Spain is consulting on a 2026 Peppol-based obligation for large enterprises; the Czech Republic runs a Peppol mandate from 2025 for procurement; Sweden, Finland, and Denmark are Peppol-first with progressive B2B obligations; Romania has delayed its RO e-Factura mandate to 2025–2026 in waves; and Hungary has announced an SZAMLAZO KSeF-style platform launching through 2027.

The pattern across all of them: EN 16931 timeline 2025 2026 is essentially a Peppol + national-hub race, with national deadlines clustering between Q1 2026 and Q1 2027.

How to prepare an SMB in 90 days — without buying enterprise DMS

A practical 90-day plan, designed for a 10-to-100-person business with one finance lead and no dedicated IT team. The goal is to be audit-ready on day 1 of every deadline above without buying enterprise document management.

Days 1–15: Map and baseline. Inventory your top 20 customers and top 50 suppliers by invoice volume. Note which are domestic vs cross-border and which country each is in. Capture today: which channels do invoices move over (email PDF, paper, EDI, portals)? Confirm your ERP or accounting tool's current capabilities — most modern suites already support ZUGFeRD, Factur-X, or Peppol via a connector. Document your legal entities, VAT IDs, and any required identifiers (codice destinatario, SIRET, KSeF ID).

Days 16–45: Pick the compliance layer. Decide whether your accounting tool can carry the load alone. If yes, enable its Peppol Access Point add-on or its national integration (PPF PDP, KSeF provider, SDI). If not, layer a dedicated e-invoicing and compliance platform on top of your ERP — typically with a Peppol Access Point, a ZUGFeRD/Factur-X generator, and a structured archive that satisfies GoBD and the equivalent national rules. Make sure the chosen tool can ingest EN 16931 files today, not in 2027.

Days 46–75: Build the pipelines. Configure two flows: outbound (your ERP → e-invoicing layer → Peppol / SDI / KSeF / PPF) and inbound (Access Point inbox → your ERP's structured data fields, not just a PDF). Set up validation rules (VAT IDs, currency, totals, payment terms) so bad invoices never reach bookkeeping. Establish a structured archive: immutable storage, timestamping, hash, and a clear audit trail for every received document.

Days 76–90: Test and train. Run parallel invoicing for the top 10 customers in each regime — Peppol for Belgium and the Netherlands, SDI or Peppol for Italy, KSeF for Poland, PPF PDP or Peppol for France. Confirm invoice receipt on the other side, the KSeF ID, the SDI delivery receipt, or the PPF acknowledgement. Train your finance team on the new exception flow: rejections, failed routing, corrections, and credit notes.

What you do not need: a full DMS replacement, an OCR vendor, or a custom integration layer. The standards and networks are designed so that a Peppol Access Point + an EN 16931-capable accounting tool covers Germany, France, Italy, Belgium, Poland, and the rest of the bloc with the same plumbing.

Frequently asked questions

What is EN 16931 and why does it matter for e-invoicing in the EU? EN 16931 is the European semantic standard for electronic invoices, mandated by EU Directive 2014/55/EU. It defines the data fields every B2B invoice must carry so that any compliant system in any member state can read it. Every country deadline in this article is built on top of EN 16931, which is why one set of formats — UBL 2.1, UN/CEFACT CII, Peppol BIS Billing 3.0, ZUGFeRD, and Factur-X — covers all of them.

When does the EU-wide B2B e-invoice mandate take effect? Under the ViDA reform, the EU-wide EN 16931 mandate for all B2B invoices inside the bloc is set for 1 January 2030, with cross-border exchanges required to use a Peppol-based network. National governments are running earlier mandates from 2025 onward, and the cluster of 2026–2027 deadlines effectively brings most member states onto EN 16931 two to four years early.

Do I need to send Peppol invoices to comply with the German mandate? Not necessarily. Germany accepts any EN 16931-compliant format from 1 January 2027: ZUGFeRD 2.x, Factur-X, pure UBL 2.1, or Peppol BIS. In practice, if you sell cross-border or to public-sector customers, Peppol is the most efficient transport. For purely domestic German B2B, ZUGFeRD embedded in a PDF works.

What happens if I keep sending PDFs after my country's deadline? You risk the invoice being non-deductible for VAT, your customer being unable to pay through compliant channels, and — in regimes like Italy, Poland, and France — your invoice never reaching the buyer because it cannot enter the central platform. In Germany, PDF-only invoices after 2027 are legally non-compliant for B2B; in France, non-issuance triggers the new e-reporting penalties on top of any VAT audit exposure.

Can I use one tool to comply with France, Germany, Italy, and Poland at once? Yes, as long as that tool connects to Peppol or directly to each national platform (PPF, SDI, KSeF) and can produce EN 16931 XML in the required national profile. The Peppol layer covers Belgium, the Netherlands, Austria, Scandinavia, and most cross-border traffic; the national hubs cover France, Italy, and Poland domestically. Most modern e-invoicing platforms bundle both.

How much does SMB compliance cost in 2025? For a 10-to-100-person company, a Peppol-enabled accounting or compliance platform typically costs between €20 and €80 per month per organisation, plus a per-invoice fee that often drops below €0.30 at volume. Compared with the cost of non-deductible VAT, late payment from customers who cannot accept your invoice, or a manual structured-archive build, the ROI is realised in the first quarter.

If you want to see your own compliance posture before any of these deadlines close, the fastest path is to run your invoices through a purpose-built compliance layer. Try Arver free for 14 days and import your existing invoices to see the compliance dashboard in action.