# Europe E-Invoicing Deadlines 2026: Germany, France, Belgium and ViDA - Date: 2026-04-15 - Reading time: 11 min read Updated April 2026: compare Europe’s key e-invoicing deadlines for Germany, France and Belgium, and see what the EU ViDA package means for ERP teams and compliance planning. ## 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 never built for EN 16931, 2026 is the year e-invoicing becomes operational instead of theoretical. The immediate pressure points are clear: **Belgium is already live**, **France starts its phased rollout on September 1, 2026**, and **Germany's domestic B2B transition is moving toward mandatory issuance in 2027 and 2028**. At the same time, the EU's **VAT in the Digital Age (ViDA)** package has turned the long-term direction of travel into law. For companies that cannot justify replacing their ERP, the practical question is no longer *whether* to prepare, but *how to get compliant with minimal disruption*. ### Key 2026 Dates At A Glance - **Belgium:** Domestic B2B structured e-invoicing became mandatory on **January 1, 2026**. - **France:** All businesses must be able to **receive** e-invoices from **September 1, 2026**; large and intermediate companies must also **issue** from that date. - **Germany:** Businesses have had to **receive** domestic B2B e-invoices since **January 1, 2025**; issuance deadlines tighten on **January 1, 2027** and **January 1, 2028**. - **EU / ViDA:** the package was adopted on **March 11, 2025** and sets the direction for EU-wide digital reporting and e-invoicing, including a major cross-border stage on **July 1, 2030**. ### Europe E-Invoicing Timeline 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 move much closer to mandatory issuance. The ERP output problem becomes urgent for larger domestic B2B issuers. **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 →](/en/pdf-to-xrechnung) [Prefer a hybrid PDF + XML flow? Convert PDF to ZUGFeRD / Factur-X →](/en/pdf-to-zugferd) ### 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 →](/en/pdf-to-ubl) ### France: September 1, 2026 Is The Real Preparation Deadline France's reform matters even to businesses that think their sending obligation is “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, 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. ### What Counts As A Compliant E-Invoice? - **Not enough:** a normal PDF, even if it was created electronically. - **Usually required:** a **structured** invoice that systems can parse automatically. - **Common building blocks:** EN 16931 semantic model plus UBL, CII, XRechnung, or ZUGFeRD / Factur-X depending on the jurisdiction and workflow. - **Operational reality:** generation alone is not enough; you also need validation, error handling, and recipient-specific checks. ### The 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: - **Keep the ERP as system of record** for commercial data. - **Extract and normalize invoice fields** from the source document or output. - **Generate the right structured format** for the target country and recipient flow. - **Validate before sending** so mandatory fields, totals, tax logic, and profile rules fail early. - **Route to the recipient channel** such as Peppol, a national platform, or a partner network. - **Keep a human review step** for low-quality source documents and edge cases. This is the core reason converter-and-validator workflows are growing: they let teams become compliant 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 →](/en/pdf-to-xrechnung) [Convert PDF to ZUGFeRD / Factur-X →](/en/pdf-to-zugferd) [Convert PDF to UBL →](/en/pdf-to-ubl) ### Official Sources - [Germany: BMF E-Rechnung FAQ](https://www.bundesfinanzministerium.de/Content/DE/FAQ/e-rechnung.html) - [France: official e-invoicing reform page](https://www.impots.gouv.fr/reforme-facturation-electronique) - [Belgium: official e-invoicing information portal](https://einvoice.belgium.be/en) - [European Commission: VAT in the Digital Age](https://taxation-customs.ec.europa.eu/taxation/vat/vat-digital-age_en)