Europe e-invoicing deadlines in 2026: Germany, France, Belgium and ViDA

Article overview

This article explains Europe e-invoicing deadlines in 2026: Germany, France, Belgium and ViDA as a practical reference for European e-invoicing. It defines the topic in plain language, places it in the compliance context, and connects the explanation to invoice formats such as XRechnung, ZUGFeRD/Factur-X, UBL, and CII.

Europe's e-invoicing calendar is no longer a future problem

If your finance team still relies on PDFs, email attachments and an ERP that was not built for EN 16931, 2026 is the year e-invoicing becomes an operational requirement. The immediate pressure points are clear: Belgium is already in its mandatory phase, France begins its phased rollout on September 1, 2026, and Germany's domestic B2B transition leads to mandatory issuance in 2027 and 2028.

The EU's VAT in the Digital Age (ViDA) package also sets the longer-term legal framework. For companies that cannot justify replacing their ERP, the practical question is no longer whether to prepare, but how to become compliant with minimal disruption.

Europe e-invoicing timeline for 2026

Jurisdiction	Key date	What changes	What it means in practice
Belgium	January 1, 2026	Structured domestic B2B e-invoicing becomes mandatory for most VAT-registered businesses.	Emailing a normal PDF is not enough. You need a structured invoice flow, typically via Peppol BIS Billing 3.0.
France	September 1, 2026	All businesses must be able to receive e-invoices. Large and intermediate companies must also issue.	Buying-side readiness becomes mandatory for everyone first. Sales-side issuance depends on company size.
France	September 1, 2027	SMEs and microenterprises must also issue e-invoices.	If you are a smaller French business, 2026 is your preparation window.
Germany	January 1, 2025	Businesses must be able to receive domestic B2B e-invoices.	Accounts payable and archiving processes already need to handle structured formats.
Germany	January 1, 2027	Businesses with prior-year turnover above €800,000 must generally issue e-invoices from this date.	Larger domestic B2B issuers need a compliant structured output before the transition deadline.
Germany	January 1, 2028	All remaining domestic B2B businesses must issue compliant e-invoices.	The transition period is over. Structured issuance becomes the default.
EU / ViDA	July 1, 2030	Major EU-wide digital reporting and e-invoicing changes begin for cross-border B2B flows.	Country-level mandates still matter now, but the strategic direction is already fixed.

Germany: 2026 is still a transition year, but not a relaxed one

Germany's domestic B2B e-invoicing reform started on January 1, 2025 with a mandatory receiving obligation. The Federal Ministry of Finance FAQ also makes the transition schedule explicit: other invoice formats can still be used in certain cases through December 31, 2026, and smaller issuers with prior-year turnover up to €800,000 can use a longer transition period through December 31, 2027.

The operational takeaway is simple: if you sell into Germany, you should not treat 2026 as a waiting year. It is the year to stabilize your outbound process, decide whether you will issue XRechnung, ZUGFeRD / Factur-X, or another EN 16931-compliant syntax, and make sure validations are part of the workflow instead of an afterthought.

Need a practical bridge? Convert PDF to XRechnung →
Prefer a hybrid PDF + XML flow? Convert PDF to ZUGFeRD / Factur-X →

Belgium: mandatory since January 1, 2026

Belgium is no longer planning e-invoicing. It is already in the mandatory phase. For most domestic B2B transactions between VAT-registered businesses, the expectation is a structured electronic invoice, typically aligned with Peppol BIS Billing 3.0. In practice, that means a plain PDF sent by email does not meet the same compliance objective as a structured invoice that can be processed automatically.

This is exactly where many mid-market teams get stuck: their ERP can generate a readable invoice, but not a compliant structured payload. If that sounds familiar, the right move is usually not a full ERP replacement. It is a controlled compliance layer that can generate, validate, and hand off structured invoices while the core ERP remains in place.

Prepare UBL invoices for Peppol-style workflows →

France: September 1, 2026 is the real preparation deadline

France's reform matters even to businesses whose own sending obligation comes later. Official guidance makes two dates decisive: September 1, 2026 and September 1, 2027. From September 1, 2026, all businesses must be able to receive electronic invoices from suppliers required to issue them, while large and intermediate companies must also issue. SMEs and microenterprises follow on September 1, 2027.

France also officially recognizes structured formats such as UBL, CII, and Factur-X. For businesses that still depend on PDF-heavy processes, 2026 is the window to clean up master data, decide on the target syntax, and test the workflow with your platform and recipients before go-live.

ViDA: why the EU layer still matters in 2026

The VAT in the Digital Age package does not replace national mandates, but it makes the strategic trajectory unmistakable. The Council adopted the package on March 11, 2025. The Commission's ViDA overview then set out phased changes, including a major cross-border digital reporting and e-invoicing stage on July 1, 2030.

For finance and ERP teams, the implication is not “wait until 2030”. It is the opposite. If you solve structured invoice generation, validation, and exception handling now, you build reusable infrastructure for both national mandates and later EU-wide reporting changes.

A low-disruption compliance stack

Most companies do not fail because they do not understand the deadline. They fail because their invoice data lives in inconsistent PDFs, ERP print templates, and email-based approval steps. A practical migration path usually looks like this:

1. Keep the ERP as system of record for commercial data.
2. Extract and normalize invoice fields from the source document or output.
3. Generate the right structured format for the target country and recipient flow.
4. Validate before sending so mandatory fields, totals, tax logic, and profile rules fail early.
5. Route to the recipient channel such as Peppol, a national platform, or a partner network.
6. Keep a human review step for low-quality source documents and edge cases.

This is why converter-and-validator workflows are useful: they can help teams meet the requirements without pausing billing operations for a major ERP program.

2026 checklist for finance and ERP teams

• Map which countries you invoice into and which dates apply to your entity size.
• Decide which structured formats you must support first: XRechnung, ZUGFeRD / Factur-X, UBL, or CII.
• Test whether your outbound data actually covers mandatory EN 16931 fields.
• Make validation part of the process before a customer or platform rejects the invoice.
• Separate “can receive” readiness from “can issue at scale” readiness.
• Document exception handling for incomplete PDFs, missing tax IDs, and master-data gaps.

How Invoice-Converter.com fits into this transition

Invoice-Converter.com is designed for teams that need a low-disruption path to structured invoicing. Instead of promising zero-review magic, the workflow focuses on what actually matters in production: extracting data from heterogeneous invoice inputs, generating compliant structured output, and validating it before it reaches the recipient.

Convert PDF to XRechnung →
Convert PDF to ZUGFeRD / Factur-X →
Convert PDF to UBL →

Official Sources

• Germany: BMF E-Rechnung FAQ
• France: official e-invoicing reform page
• Belgium: official e-invoicing information portal
• European Commission: VAT in the Digital Age

How to use this guide

Use the article as a starting point before changing a finance or ERP workflow: identify the applicable country rule or standard, decide which structured format is expected, validate the generated XML, and keep a documented exception process for invoices that require manual review.