E-invoicing mandates: which markets go live in 2025 and 2026

If you run a B2B operation and still send PDFs over email, at least three of your key markets are about to make that non-compliant. E-invoicing mandates are no longer a distant regulatory project. They are live, phased, and arriving on a schedule you can plan around.

Why governments are moving so fast

The motive is straightforward: structured e-invoicing closes VAT gaps. The EU alone estimates a VAT gap of roughly €61 billion a year, much of it from errors and fraud in paper and PDF chains. Mandating machine-readable invoices in real time (or near real time) means tax authorities can cross-check buyer and seller data automatically, before a return is ever filed.

For small businesses, this is a compliance burden that arrives whether you are ready or not. The difference between being ready and scrambling is about six months of lead time.

The 2025 go-live dates you need in your calendar

Germany: phased B2B e-invoicing from January 2025

Germany's e-invoicing obligation under the Growth Opportunities Act (Wachstumschancengesetz) started phasing in on 1 January 2025. From that date, all German B2B businesses must be able to receive structured e-invoices (ZUGFeRD or XRechnung format). The obligation to send them follows in stages: large businesses from 1 January 2027, SMEs from 1 January 2028. If you sell to German buyers right now, your German counterpart is already expecting to receive structured invoices, even if sending is not yet mandatory for you.

France: mandatory for all company sizes by September 2026

France's mandate (via the Portail Public de Facturation) requires all B2B companies to receive e-invoices from 1 September 2026 and to send them on a sliding scale: large enterprises from September 2026, mid-sized from the same date, and SMEs from the same deadline after a 2024 legislative consolidation. If you have French clients, September 2026 is your hard deadline.

Belgium: 2026 for B2B structured invoicing

Belgium confirmed mandatory structured B2B e-invoicing from 1 January 2026, using the Peppol network. If you supply Belgian businesses, you will need Peppol-compatible output by end of 2025 to test in time.

Malaysia: phased since August 2024, now covers SMEs

Malaysia's MyInvois mandate started with large taxpayers in August 2024 and extended to businesses with annual turnover above MYR 25 million from 1 January 2025. SMEs follow from 1 July 2025. If you have customers in Malaysia or operate a regional entity there, the SME phase is live mid-year.

Romania and the wider EU ViDA picture

Romania has been running mandatory B2B e-invoicing (RO e-Factura) since January 2024. The wider EU ViDA (VAT in the Digital Age) reform, formally adopted in 2024, sets 2030 as the outer deadline for all EU member states to mandate domestic structured invoicing. But many are front-running that date, as Germany, France, and Belgium show.

What "structured e-invoice" actually means for your operations

A PDF is not a structured e-invoice. Neither is a Word document saved as PDF. A structured invoice is a machine-readable file (XML-based, typically in formats like UBL, CII, or ZUGFeRD) where each field, seller name, line item, VAT amount, IBAN, is tagged in a defined schema so a buyer's ERP or a tax authority's system can ingest it without human reading.

For a small B2B owner sending 40 to 200 invoices a month, the practical question is not "do I understand the XML spec" but "does my invoicing tool generate compliant output, and does it handle the VAT fields correctly?"

The VAT fields that trip people up

Structured mandates require:

• Tax identification numbers for both seller and buyer on every invoice
• VAT rate and amount per line, not just a footer total
• Reverse-charge notation for cross-border EU B2B (the buyer accounts for VAT, not you)
• Payment terms in a machine-readable field, not a text note

If your current invoicing setup handles these fields loosely, a compliance audit in any of the above markets will surface problems fast.

How to use the phase-in windows without waiting until the last minute

The phased schedules are a gift. Germany's receive-only obligation in 2025 gives you a year to audit your outbound stack before the send mandate hits. France's September 2026 deadline gives you roughly 18 months from now. Use that time in three stages.

Stage 1 (now): audit your client list by country. For each active client, note their country and company size. Flag anyone in Germany, France, Belgium, Malaysia, or Romania. Those relationships need compliant invoices first.

Stage 2 (6 months out): check your VAT fields. Pull three recent invoices. Confirm each one carries: your VAT number, the buyer's VAT number, per-line VAT amounts, a reverse-charge flag where applicable, and a machine-readable due date. Fix the gaps in your template now.

Stage 3 (3 months before deadline): test the output format. If your market requires Peppol or a national portal, confirm your invoicing tool can export to the required format, or that it connects to the portal via API. Compliance is not just about the fields; it is about the delivery channel.

The accounts receivable angle most owners miss

Compliance conversations focus on sending correctly formatted invoices. They rarely mention what happens when your buyer's system rejects a non-compliant invoice: the invoice is simply not processed, and your 30-day clock never starts. That is not a late payment. It is a payment that does not exist yet.

For a small business running recurring invoices to a stable client base, a rejected invoice in January can quietly distort your February cash flow before you notice. The fix is not chasing the buyer harder. It is sending a compliant invoice the first time, so their system accepts it without a human review queue.

Getting the structure right and pairing it with auto-reminders that fire 3 and 7 days after the due date means you are not just compliant: you are also closing the gap between invoice sent and cash received.

The mandate deadlines are fixed. Your preparation timeline is the only variable left.