EU E-invoicing Mandates in 2026: What Your Business Needs to Know

2026 is the year European e-invoicing mandates stopped being a future problem. Belgium activated its mandate in January. Poland's KSeF went live in February. France is on the clock for September. If your business issues B2B invoices in any of these countries — or if you're a software vendor whose customers do — this is a compliance sprint, not a planning exercise.

Here's what's live, what's coming, and what you actually need to do.

Belgium: Live Since January 2026

Belgium's structured e-invoicing mandate covers all B2B invoices between VAT-registered businesses. The format is Peppol BIS Billing 3.0, submitted over the Peppol AS4 transport network.

What that means in practice:

• You need a Peppol Access Point to send and receive invoices
• Both sender and receiver must be registered on the Peppol network
• The invoice must be a structured UBL 2.1 XML — a PDF email attachment is no longer compliant for B2B transactions between Belgian VAT numbers

Key details:

• Mandate scope: B2B invoices where both parties are Belgian VAT-registered
• Format: Peppol BIS Billing 3.0 (UBL 2.1)
• Transport: Peppol AS4
• No phased rollout — the mandate applies immediately

If you're using an ERP that hasn't shipped a Peppol connector for Belgium, you're already out of compliance on invoices issued since January. This is a real enforcement risk, not an administrative nuisance. Read the full Belgium e-invoicing guide.

Poland: KSeF Live Since February 2026

Poland's KSeF (Krajowy System e-Faktur) is a centralized government hub model — structurally different from Peppol. Every B2B invoice must be submitted to the KSeF API, receive a unique KSeF number from the government, and only then is it legally valid.

What that means in practice:

• You can't just generate XML and email it — the invoice is not a valid document until KSeF acknowledges it
• The submission flow is asynchronous: you submit, wait for processing, then poll for the KSeF number
• The buyer doesn't receive an email — they retrieve the invoice directly from KSeF using their own access credentials

Key details:

• Mandatory for all VAT-registered Polish taxpayers (B2B)
• Format: FA(2) — Poland's own XML schema, not Peppol
• Transport: KSeF REST API with session token authentication
• Penalties for non-compliance are material and escalate

KSeF is one of the more technically complex mandates in Europe. The session-based auth model, asynchronous status polling, and the government-assigned invoice identifier all require purpose-built integration — bolting an XML generator onto your existing flow is not enough. Read the full Poland KSeF guide.

France: September 2026

France's mandate is the largest in Europe by transaction volume and the most architecturally ambitious. The model splits responsibility between a government platform (PPF — Portail Public de Facturation) and a network of accredited private platforms (PDPs — Plateformes de Dématérialisation Partenaires).

What that means in practice:

• Large businesses (revenue > €800M or > 5,000 employees) must be able to receive e-invoices by September 1, 2026
• SMEs have until September 1, 2027 to comply with the sending obligation
• All invoices must flow through either the PPF or a PDP
• The format supports three options: UBL 2.1, CII (Cross Industry Invoice), or Factur-X (a hybrid PDF/XML)

The important nuance: The September 2026 date is specifically the receiving obligation for large enterprises. If you're selling to large French companies, they need to be able to receive structured invoices from you. That means your submission infrastructure must be in place before then, even if your own sending obligation (as an SME) doesn't kick in until 2027.

France also introduces the concept of "e-reporting" — even for B2C transactions not subject to structured invoicing, businesses must report transaction data to the tax authority. This is separate from the B2B mandate but runs on the same infrastructure. Read the full France e-invoicing guide.

The ViDA Directive: The Longer Game

Beyond the country-specific mandates, the EU's VAT in the Digital Age (ViDA) initiative is reshaping the long-term landscape. ViDA's e-invoicing provisions include:

• From 2028: EU member states can introduce real-time digital reporting requirements without needing individual EU approval (removing the current derogation process)
• From 2030: Cross-border B2B transactions within the EU will require structured digital reporting, moving toward near-real-time
• EN 16931 becomes the baseline: The European e-invoicing standard will be the required format for intra-EU transactions

ViDA means every country that hasn't yet mandated e-invoicing will have a clear runway to do so, without bureaucratic friction. Germany (2025 receiving obligation, with full B2B sending by 2027-2028), Austria, and others are all building toward this.

What You Actually Need to Do

If you're issuing invoices in Belgium right now: You need a Peppol Access Point and your invoice flow needs to generate UBL 2.1 structured XML. If your current process ends with a PDF, it's not compliant.

If you're issuing invoices in Poland: You need KSeF integration. This means a service that can authenticate against KSeF, submit FA(2) XML, and poll for invoice acknowledgment. The KSeF number must appear on any human-readable copy of the invoice.

If you're selling to large French enterprises: You need to be able to deliver structured invoices (UBL 2.1, CII, or Factur-X) via a PPF or PDP before September 2026.

If you're building software used by EU businesses: Your customers are asking about this. The businesses that engage with compliance early avoid the last-minute sprint. The ones that don't are already non-compliant in Belgium and Poland.

The Practical Answer

Clearvo covers all three of these mandates — Belgium (Peppol), Poland (KSeF), and France (PDP model) — through a single API. You send a structured invoice object. We handle format generation, submission, and status normalization. One integration, three mandates, and the rest of the 14-country network when you need it.

Compliance in 2026 isn't optional. The question is how much integration work you want to own.