Q2 2026 E-Invoicing Compliance Check: Germany, France, Belgium, and ViDA
Felix Graeber
Founder, Invoice-Converter.com
Builds practical e-invoicing workflows for EN 16931, XRechnung, and ZUGFeRD adoption.
Q2 2026: The E-Invoicing Window Is Operational, Not Theoretical
Many finance teams still run invoicing through PDFs, email attachments, and ERP print templates. In Q2 2026, that is now a compliance risk in multiple countries. The practical goal is to move from readable invoices to structured invoices that systems can validate and process.
What changed (or is changing) on concrete dates
- Belgium: Domestic B2B structured e-invoicing became mandatory on January 1, 2026.
- France: First legal milestone on September 1, 2026 (receive for all, issue for large/intermediate companies), then SMEs/micro on September 1, 2027.
- Germany: Receive obligation started on January 1, 2025; transition windows tighten through December 31, 2026 and December 31, 2027 depending on turnover.
- EU ViDA: Adopted on March 11, 2025, with cross-border digital reporting impact from July 1, 2030.
Germany: 2026 is your implementation year
The German BMF FAQ is explicit: other invoice formats can still be used during transitional periods, but mandatory structured invoicing is the end state for domestic B2B. If your company still emits only PDF from ERP, you should treat 2026 as a delivery year for extraction, mapping, and validation workflows.
France: September 1, 2026 is not far away
Official French guidance confirms the phased launch: from September 1, 2026, all businesses must be able to receive e-invoices, and large/intermediate companies must issue them; SMEs and microenterprises follow in September 2027. Teams that postpone recipient and routing tests into late 2026 usually create avoidable go-live risk.
Belgium: already mandatory since January 2026
Belgium's national portal states that structured B2B e-invoicing is compulsory from January 1, 2026 for nearly all VAT-registered domestic B2B transactions. A standard PDF by email is not equivalent to a structured, machine-processable invoice flow.
Execution checklist for finance and ERP teams
- Map countries, legal entities, and exact dates that apply to each invoicing flow.
- Decide your primary syntaxes (XRechnung, ZUGFeRD/Factur-X, UBL, CII) per recipient channel.
- Shift from “generate XML” to “generate + validate + handle exceptions”.
- Keep a human review step for poor source quality and edge-case documents.
- Document fallback operations for rejected invoices so billing does not stop.
If you need a low-disruption bridge, use conversion and validation workflows that sit beside your current ERP, rather than attempting a full ERP replacement first.
Convert PDF to XRechnung →
Convert PDF to ZUGFeRD / Factur-X →
Convert PDF to UBL →
Official references
🚀 Ready to Convert Your Invoices?
Start converting PDF invoices to XRechnung, ZUGFeRD, and other formats today. 3-day free trial included.
đź“š Related Articles
KOSIT Validator Error Codes: Complete Guide to All 21 BR-DE XRechnung Validation Errors [2026]
Complete guide to all 21 KOSIT validator BR-DE error codes. Learn what BR-DE-1 through BR-DE-21, UBL-CR-646, and other XRechnung/ZUGFeRD validation errors mean and how to fix them.
Read moreZUGFeRD BT Fields: Complete Guide to Business Terms in E-Invoicing
Master ZUGFeRD BT fields for compliant e-invoicing. Learn about business terms, field mappings, validation rules, and implementation best practices for German and EU electronic invoicing standards.
Read moreXRechnung & ZUGFeRD 2026: Important Updates and Deadlines
Everything you need to know about the mandatory e-invoicing changes in Germany for 2026. XRechnung, ZUGFeRD, and the new B2B obligations explained.
Read more