Three of the six 2026 e-invoicing mandates are already live as you read this. By the end of the year, every business doing cross-border B2B inside the EU will be sending or receiving structured invoices in at least one national system. The patchwork is real, but so is the through-line: EN 16931.
The one-line thesis
2026 is when EU e-invoicing stops being a slide in a tax-advisor's deck and starts being a deadline on your VAT calendar. Six member states are switching on mandatory structured B2B e-invoicing in this calendar year, each through its own national platform, each with its own grace period — and all of them sharing the same European semantic standard underneath. If your invoicing tool can speak EN 16931 today, you are positioned for the rest of the decade. If it cannot, 2026 is the year that becomes an expensive problem.
How we got here
For years, mandatory e-invoicing inside the EU required each member state to ask the Council for a derogation under Article 395 of the VAT Directive. Italy got the first one in 2018 and used it to build SdI / FatturaPA. France, Poland, Romania and Germany followed with their own derogation requests, each on a different timeline.
That changed in April 2025. The "VAT in the Digital Age" (ViDA) package entered into force on 14 April 2025, and one of its most immediate effects was to remove the derogation requirement entirely. Member states are now free to impose mandatory domestic e-invoicing without asking permission first. The reason 2026 looks like a wave is that several countries had already lined up their domestic mandates and were waiting for the political green light. (We cover the ViDA umbrella in detail in ViDA one year on.)
The result is a year in which six member states activate B2B mandates, each pointing at the same destination (cross-border digital reporting in 2030) but taking different roads to get there.
The 2026 calendar, in order
1 January 2026 — Belgium goes Peppol-mandatory
Belgium switched on mandatory structured B2B e-invoicing via Peppol BIS 3.0 on 1 January 2026. All VAT-registered Belgian businesses are in scope. The Belgian tax authority published a three-month tolerance window: no penalties before April 2026, giving businesses time to migrate their billing pipelines onto a Peppol Access Point.
The format is the standard one: Peppol BIS 3.0, which is itself a CIUS (Core Invoice Usage Specification) of EN 16931. If your tool already emits EN-compliant XML you are about one Access Point away from compliance.
Belgium B2B e-invoicing mandate
Live: 1 January 2026
Tolerance window: until 1 April 2026 (no penalties)
Format: Peppol BIS 3.0 (EN 16931 CIUS)
Channel: Peppol four-corner network
1 January 2026 — Spain's VeriFactu obligation
Spain activated VeriFactu on the same day. VeriFactu is not quite the same animal as the others on this list — it is a certified-invoicing-software obligation under Royal Decree 1007/2023, requiring billing software to produce a tamper-evident chain of invoice records and (optionally) submit them in real time to the AEAT (Spanish tax authority). Large companies are first; SMEs phase in across 2026.
The full B2B e-invoicing track under Spain's Crea y Crece law is a separate, later step (2027/2028). VeriFactu is the structural precondition: get the billing software certified, then the e-invoicing mandate clips on top.
1 February 2026 — Poland's KSeF Phase 1
On 1 February 2026, Poland's Krajowy System e-Faktur (KSeF) went live for large taxpayers — businesses with annual sales turnover above PLN 200 million. Roughly 4,200 entities are in scope for Phase 1.
KSeF is centralised: every in-scope invoice has to be issued through a single national platform. The Polish Ministry of Finance also published a phased rollout for everyone else:
- 1 February 2026 — large taxpayers (turnover > PLN 200 m)
- 1 April 2026 — all other VAT taxpayers, including foreign businesses registered for Polish VAT
- 1 January 2027 — micro-entrepreneurs
2026 is an enforcement grace year for KSeF — full penalties land in 2027. But the structural obligation to route invoices through the system applies from each go-live date.
1 April 2026 — Poland's KSeF Phase 2
Phase 2 is the one that catches most readers of this article. From 1 April 2026 every Polish VAT taxpayer plus every foreign business that holds a Polish VAT registration has to issue B2B invoices through KSeF.
If you are an Amsterdam consultancy that registered for Polish VAT in 2024 because you crossed the OSS threshold for selling into Poland, you are in scope from 1 April 2026 onward. Your invoicing tool either talks to KSeF or it doesn't — there is no middle ground.
1 July 2026 — Romania's RO e-Factura SME deadline
Romania has been running RO e-Factura B2B mandatorily for large taxpayers for some time. The remaining exemption for SMEs with turnover below EUR 500,000 ends on 1 July 2026. From that date forward every B2B invoice between Romanian-VAT-registered parties has to be submitted via the ANAF (Romanian tax authority) platform.
The format is XML-based with Romania's own CIUS over EN 16931. Romania has also been one of the more aggressive members on sanctions: the e-Factura fines for non-compliance are non-trivial, especially for VAT deduction on the buyer side.
1 September 2026 — France's Phase 1
France was supposed to launch its e-invoicing + e-reporting mandate in 2024. It slipped to 2026. In April 2025, the French National Assembly rejected a further proposed postponement of one year, and the 2026 budget law confirmed the schedule. As of May 2026, the calendar is:
- 1 September 2026 — every French business must be able to receive structured e-invoices; large and mid-size companies must issue them through a Plateforme Agréée (PA).
- 1 September 2027 — small and micro-enterprises must also issue.
A small terminology note: the certified intermediaries that route invoices and submit e-reporting data to the DGFiP used to be called "Plateforme de Dématérialisation Partenaire" (PDP). They are now officially called Plateforme Agréée (PA). It is the same role, the name changed in the 2025 legislative redrafting.
The French model is hybrid: domestic B2B invoices go through a PA (which routes them to the recipient and the DGFiP), while the supplementary "e-reporting" stream covers B2C and cross-border transactions that are out of scope for the structured-invoice flow but still need to be reported to the tax authority.
Background — Germany's receipt obligation already lives, issuance lands later
Germany is the outlier on this list because its mandate is staged across 2025, 2027 and 2028 rather than triggering inside 2026. Under the Wachstumschancengesetz:
- 1 January 2025 — every German business must be able to receive EN 16931-compliant e-invoices. This is already the reality.
- 1 January 2027 — businesses with previous-year turnover above EUR 800,000 must issue EN-compliant e-invoices.
- 1 January 2028 — the issuance obligation applies to all businesses.
Accepted German formats are XRechnung (the national CIUS) and ZUGFeRD 2.1 (hybrid PDF+XML). Both are EN 16931-compliant.
The 2025 receipt obligation is why a Berlin freelancer who has a French client suddenly cares about the September 2026 French mandate: from that date, the invoice arriving in their inbox from a French SaaS vendor will be a structured XML attached to a PDF, not just a PDF.
Background — Italy is the long-standing baseline
Italy's SdI / FatturaPA has been mandatory for B2B and B2G since 2019. The remaining carve-out — the flat-rate regime (regime forfettario, turnover up to EUR 85,000) — was pulled in in 2024 without a threshold. As of 2026, every Italian VAT number must invoice through SdI. The Italian system is the longest-running national e-invoicing platform in the EU and the practical reference design that the rest of this list is converging towards.
The through-line: EN 16931
Six countries, six platforms — but only one underlying standard. EN 16931 is the European semantic standard for the structured electronic invoice, published by CEN in 2017. Every member-state-specific format on this list (Peppol BIS 3.0, FatturaPA, XRechnung, ZUGFeRD 2.1, the French Factur-X via PA, RO e-Factura's XML schema) is either EN 16931 directly or a CIUS — a Core Invoice Usage Specification — that constrains EN 16931 to local needs.
That matters because ViDA's 2030 cross-border digital reporting requirements are written around EN 16931 directly. If your invoicing tool emits EN-compliant structured invoices today, you are pre-adapted for:
- the 2026 wave of national mandates (each accepting its EN-CIUS variant);
- the 2030 cross-border B2B real-time reporting that ViDA will require for intra-EU B2B; and
- the 2035 alignment of domestic reporting systems on the EU model.
If your tool only emits PDF, every one of those deadlines is a re-implementation problem.
What it looks like from four desks
These four scenarios use realistic 2026 facts. They are illustrative — your own VAT-registration footprint dictates which mandates actually bind you.
A Berlin freelancer with a French SaaS client
From 1 September 2026, the French SaaS vendor must issue its invoice as a structured EN-compliant document through a Plateforme Agréée. The freelancer will receive a Factur-X file (PDF with embedded XML) attached to an email. Their German receipt obligation has been in force since 1 January 2025, so their tooling needs to ingest the XML side, not just file the PDF. Inbound is already the case in TaxItEasy® — invoices arrive by email, get classified, OCR runs against PDF, structured XML data is parsed where present.
An Amsterdam consultancy invoicing into France
The Dutch side does not have a domestic e-invoicing mandate yet. But the moment the Amsterdam consultancy issues an invoice into France for a French-VAT-registered client, the French Phase 1 rule applies to the recipient flow — the French client must be able to receive a structured invoice, and the consultancy's PA selection determines whether the invoice is legally valid in the French e-reporting system. For invoices on French B2B from September 2026, the issuer needs a Plateforme Agréée connection.
A Warsaw-based SMB selling B2B inside Poland
From 1 April 2026, the SMB must issue every domestic B2B invoice through KSeF. There is no PDF-via-email alternative; KSeF is a centralised state platform. The grace year through end-2026 means non-compliance is not yet penalised — but the structural obligation to use the platform is in force from day one.
A Lisbon freelancer with a Spanish client
VeriFactu has been in force in Spain since 1 January 2026. The Lisbon freelancer is on the receiving end: incoming Spanish invoices will increasingly carry a VeriFactu identifier and QR code that lets the buyer (or the buyer's tooling) verify the invoice was issued through certified software. The freelancer's own outbound invoices to Spain are not yet bound by Spain's full B2B e-invoicing mandate — that lands in 2027/2028 under Crea y Crece.
Practical implications
If you operate cross-border inside the EU, the action items for 2026 are unusually concrete:
- Know which VAT registrations bind you to which mandate. A foreign VAT registration in Poland makes you in-scope for KSeF Phase 2 on 1 April 2026, no matter where your company is incorporated. Same for Romania (1 July 2026) and France (1 September 2026, on the issuance side, for any business mid-size or above with a French VAT footprint).
- Ask your invoicing tool one specific question: does it emit EN 16931-compliant structured invoices today, in at least one of the national CIUS variants (Peppol BIS 3.0, XRechnung, Factur-X)? Not "can it generate a PDF that looks like one" — does the output validate against the EN 16931 XSD.
- Verify your inbound side. Every business in scope of any of these mandates needs to be able to receive structured invoices, not just send them. PDF-only inbound is no longer a complete solution for any business with EU cross-border exposure.
- Reconcile VAT IDs proactively. Each platform validates the buyer's and seller's VAT IDs. A VAT ID that fails VIES validation at the moment of invoice submission means the invoice is rejected at the platform level — not just flagged on the buyer's VAT return.
What TaxItEasy already does
TaxItEasy is positioned on the inbound side of this transition. We process incoming invoices — PDF, ZUGFeRD/Factur-X, image scans, email attachments — through OCR + structured-data extraction, and we surface the resulting records for year-end export. We support multi-currency invoicing with live ECB rates, and the VAT aggregation view summarises VAT by country for cross-border reconciliation. We do not currently issue outbound e-invoices into national platforms — that is a different category of tooling (the supplier-side platform connection), and not what we ship today.
If you are an EU-VAT-registered business buyer, the most relevant fact is that any structured invoice you receive in 2026 — Peppol, FatturaPA, KSeF XML, Factur-X — is just an inbound document we can ingest. The mandates change how your suppliers' tooling works; they do not change how your inbox needs to handle the document.
Sources
- VAT in the Digital Age — DG TAXUD — official EC overview confirming member-state mandates are now permitted without derogation since ViDA entry into force on 14 April 2025.
- Poland announces new timeline for mandatory e-invoicing — EY — authoritative timeline for KSeF Phase 1 (1 February 2026), Phase 2 (1 April 2026) and micro-entrepreneurs (1 January 2027).
- France revises schedule for adopting e-invoicing reform — EY — confirms the 1 September 2026 + 1 September 2027 dates, the PDP-to-PA rename, and the National Assembly's rejection of the proposed postponement.
- eInvoicing in Germany — European Commission — Commission country page; XRechnung + ZUGFeRD 2.1 as accepted formats, EUR 800,000 turnover threshold for 1 January 2027.
- Poland's KSeF — recent changes effective February 2026 — VATupdate — confirms the ~4,200 large-taxpayer Phase 1 scope.