The Germany 2028 B2B e-invoicing mandate is no longer a distant regulatory footnote — as of mid-2026, the first phase of Germany’s structured invoicing rollout is already live, and the clock is ticking for every business trading with German partners. For forward-thinking finance and IT teams across Europe, this phased German rollout is the most concrete, real-world rehearsal available before the EU-wide ViDa 2030 mandate reshapes the entire invoicing landscape.
- Germany’s Wachstumschancengesetz mandates that all German B2B businesses must be capable of receiving structured e-invoices from January 2025, with sending obligations phased through to 2028 for smaller businesses.
- The EU’s VAT in the Digital Age (ViDa) framework requires structured e-invoicing and near-real-time Digital Reporting Requirements (DRR) across all member states by 2030.
- Peppol is the cross-border interoperability layer that bridges local German compliance (ZUGFeRD / XRechnung) with EU-wide ViDa obligations — a dual-compliance solution your ERP must support.
- Businesses that treat Germany’s 2028 deadline as a ViDa dry run — rather than a one-off local task — will enter 2030 with a measurable competitive advantage.
The German Timeline: From Mandatory Receipt to the Final 2028 Sending Mandate
Germany’s e-invoicing roadmap was set in motion by the Wachstumschancengesetz (Growth Opportunities Act), signed into law in March 2024. The legislation introduced a phased B2B mandate that is deliberately pragmatic: it gives businesses time to adapt their systems without sacrificing the broader goal of full digital tax transparency.
The key milestones are as follows. From 1 January 2025, all German VAT-registered businesses must be able to receive structured e-invoices — meaning a simple email inbox with a PDF attachment is no longer legally sufficient if the sender chooses to issue a structured format. From 1 January 2027, businesses with an annual turnover above €800,000 must actively send structured e-invoices. Finally, from 1 January 2028, the obligation extends to all remaining B2B transactions, including smaller businesses that previously had more time to prepare.
The accepted formats are either XRechnung (a pure XML format aligned with the EN 16931 standard) or ZUGFeRD (also known as Factur-X in France), a hybrid PDF/A-3 format that embeds a structured XML payload. Both formats comply with the mandatory EN 16931 European standard, but their technical architectures have very different implications for your future ViDa obligations — more on that shortly.
The ViDa Connection: Why Germany’s Mandate Is a European Blueprint
The EU Council formally adopted the ViDa regulation in November 2024, setting out a two-pillar approach: mandatory structured e-invoicing and Digital Reporting Requirements (DRR) — essentially near-real-time transaction data reporting to national tax authorities. The target date for full implementation across all EU member states is 2030, though some member states may adopt elements earlier.
Germany’s model is structurally very close to the ViDa blueprint. It uses a mandatory structured format based on EN 16931, it targets B2B transactions, and it creates the data infrastructure that will eventually feed into DRR pipelines. If your business is already navigating the German mandate, you are already building the muscles you will need for 2030. The data fields, the validation logic, the ERP configuration — all of this carries over directly into the ViDa world. You can explore the broader implications in our article on ViDa 2030: Why E-Invoicing Isn’t Enough for Digital Reporting (DRR).
The Hybrid Trap: Why ZUGFeRD Alone Won’t Get You to 2030
ZUGFeRD (Factur-X) is a genuinely elegant solution to a real problem: it lets businesses send a human-readable PDF to customers who aren’t yet ready for pure XML, while also including a machine-readable XML payload for those who are. For domestic German compliance through 2028, it works perfectly well.
But here’s the strategic risk: ZUGFeRD is a document format, not a network protocol. It tells you what the invoice looks like, not how it gets delivered or reported. Under ViDa’s DRR pillar, tax authorities will require structured invoice data to be transmitted through certified, auditable channels — not simply embedded in a PDF and sent via email. The hybrid format’s PDF wrapper, which is its greatest usability advantage today, becomes irrelevant (and potentially problematic) when regulators need clean, structured data streams for real-time reporting.
We’ve covered the interoperability tensions between Factur-X and network-based delivery in depth in our post on Factur-X and Peppol: Solving Cross-Border E-Invoicing in 2026. The short version: if your German compliance strategy is built exclusively around ZUGFeRD email delivery, you are building on a foundation that will need significant rework before 2030.
Peppol as the Bridge: Solving Dual Compliance in One Architecture
Peppol is the open, pan-European network that connects businesses, their access points, and ultimately tax authorities through a standardised, auditable four-corner delivery model. It already underpins B2B and B2G e-invoicing in Belgium, the Netherlands, Italy, France, and increasingly Germany. More importantly, it is the delivery network that the EU’s ViDa DRR framework is expected to build upon.
A Peppol API integration solves what we call the dual compliance challenge: meeting German domestic law (XRechnung/ZUGFeRD, EN 16931 with the German CIUS) while simultaneously positioning your business for cross-border ViDa reporting. Through Peppol, your ERP sends a single structured invoice document — validated against EN 16931 — that can be routed domestically within Germany and cross-border across the EU, without format conversion headaches at either end.
Your Peppol e-invoicing setup also gives you a future-proof delivery channel. When ViDa’s Continuous Transaction Controls (CTC) or near-real-time reporting pipelines are activated in 2030, the Peppol network infrastructure is already in place to handle that data flow. You’re not starting from scratch — you’re activating an extension of existing capability. For businesses navigating multiple national rollouts simultaneously, this matters enormously. See also our coverage of how local CIUS extensions complicate cross-border compliance in a pre-ViDa Europe.
Technical Readiness: EN 16931, CIUS, and Your ERP’s Hidden Gaps
One of the most common technical mistakes businesses make is assuming that