🇩🇪 OasisPro · Germany eInvoicing · XRechnung · ZUGFeRD · EU eInvoicing Gateway
The Germany eInvoicing mandate turns to issuing in 2027.
4 steps to take this year.
Germany eInvoicing mandate obligations are further along than many businesses realise. Receiving structured electronic invoices has been mandatory for every domestic B2B business since 1 January 2025. The next phase is issuing: from 1 January 2027, businesses with prior-year turnover above 800,000 euros must issue only structured eInvoices, and from 1 January 2028 the obligation covers everyone. For thousands of companies trading in Germany, 2026 is the last full year to prepare.
This guide explains how the Germany eInvoicing mandate phases in, which formats count as compliant, how Germany differs from clearance countries like Poland and Italy, and the 4 steps to take this year.
It also covers how the OasisPro EU eInvoicing Gateway connects any ERP to the German requirements alongside every other EU mandate.
A PDF is not an eInvoice in Germany. From 2027, the businesses above the threshold cannot issue paper or unstructured formats at all. The transition consent rules that made PDFs workable are running out.
Since 2025, a compliant eInvoice in Germany means a structured, machine-readable data set based on EN 16931: XRechnung, EN-compliant ZUGFeRD profiles, or equivalent. During the transition, paper and PDF have survived where recipients consented. That consent-based workaround expires with the issuing waves. Businesses above 800,000 euros turnover lose it in January 2027, and everyone else in January 2028.
What the Germany eInvoicing mandate requires, phase by phase
The Germany eInvoicing mandate was introduced by the Growth Opportunities Act (Wachstumschancengesetz) and anchored in the German VAT Act, with detail set out in Federal Ministry of Finance guidance.
Phase one has already happened. Since January 2025, every business must be able to receive and process EN 16931 compliant eInvoices, and providing an email address is sufficient reception capability.
Phase two of the Germany eInvoicing mandate lands on 1 January 2027. Businesses with prior-year turnover above 800,000 euros must issue structured eInvoices for in-scope domestic B2B transactions.
For that wave, paper and PDF invoices are no longer permitted for in-scope transactions, whatever the recipient would prefer.
Phase three completes the rollout on 1 January 2028, when all businesses must issue, and remaining transitional allowances, including consent-based EDI arrangements, tighten to the EN-compliant baseline.
The European Commission country page for Germany tracks the framework, and KoSIT maintains the XRechnung standard as the German Peppol Authority.
XRechnung: the pure XML route
XRechnung is Germany's national implementation of EN 16931, a pure XML format designed for system-to-system processing. It has been the backbone of German B2G invoicing and is fully valid for the B2B mandate. Finance teams work with it through their ERP rather than reading it directly.
ZUGFeRD: the hybrid route
ZUGFeRD embeds structured XML inside a readable PDF/A-3, giving humans a document and systems a data set. Only EN-compliant profiles from version 2.0.1 onwards count for the mandate, and legally the embedded XML is the invoice, not the PDF wrapper around it.
No central clearance platform
Unlike Poland, Italy, or France, Germany has no government clearance system today. Invoices flow directly between trading partners via email, Peppol, EDI, or providers. That freedom cuts both ways: recipient validation rules decide acceptance, so robust EN 16931 validation before sending matters.
The 800,000 euro threshold is measured on prior-year turnover. Businesses near the line in 2026 need to plan as if they are above it.
A business whose 2026 turnover exceeds 800,000 euros issues structured eInvoices from January 2027. Waiting for the year-end numbers to confirm scope leaves no implementation window at all. The practical answer for any business near the threshold, and for every group with German entities, is to build issuing capability during 2026 and treat January 2027 as the deadline.
Germany eInvoicing mandate timeline and what comes after 2028
The table below summarises the Germany eInvoicing mandate phases. The row most businesses overlook is the last one: transaction-based e-reporting is the expected next stage after the issuing phases complete.
| Phase | Obligation | From | Status |
|---|---|---|---|
| Receiving | All businesses must receive EN 16931 eInvoices | 1 January 2025 | Live and mandatory |
| Issuing wave 1 | Businesses above 800,000 euros prior-year turnover | 1 January 2027 | Under 5 months |
| Issuing wave 2 | All businesses, transitional allowances expire | 1 January 2028 | Preparation window |
| E-reporting | Transaction-based reporting, ViDA-aligned direction | Expected after 2028 | Plan for it now |
Germany gave businesses the gentlest start of any major EU mandate. It also gave them the clearest deadline: from January 2027, the largest slice of the German economy issues structured invoices or does not invoice at all.
The 4 steps to take in 2026
- Confirm your threshold position and scope. Establish whether each German entity exceeds 800,000 euros prior-year turnover for 2027, and map which transactions are in scope, noting exemptions such as small-value invoices up to 250 euros and B2C sales.
- Harden your receiving process beyond the mailbox. An email address meets the letter of the reception rule, but unprocessed XML in an inbox is not accounts payable. Build validation, conversion, and ERP posting for XRechnung and ZUGFeRD now, while volumes are still building.
- Build issuing capability against EN 16931. Choose formats with your major trading partners, validate outbound invoices before sending, and test with real counterparties. Recipient-side validation decides acceptance in a decentralised model, so testing is not optional.
- Architect for e-reporting, not just exchange. Germany's direction of travel is transaction-based reporting under the ViDA framework. A gateway that already operates clearance and reporting models in Poland, Italy, and France is the architecture that will not need replacing.
For every EU deadline in one view, see the EU eInvoicing deadlines 2026 to 2030 timeline, and for format depth this independent German eInvoicing explainer is a useful companion.
The OasisPro EU eInvoicing Gateway connects any ERP to the Germany eInvoicing mandate.
One middleware connection from any ERP: SAP, Oracle, Odoo, IFS Cloud, Dynamics, NetSuite, or any other. The gateway generates and receives XRechnung, ZUGFeRD, and Peppol BIS, validates against EN 16931, and tracks German regulatory developments including the expected e-reporting stage.
Read about the OasisPro EU eInvoicing GatewayGermany eInvoicing mandate scope confirmed? 2026 is your implementation year.
Talk to OasisPro about your German footprint. We will confirm your threshold position, assess your receiving and issuing readiness against EN 16931, and show you what one gateway connection covers across Germany and the rest of the EU.
What is the Germany eInvoicing mandate?
The Germany eInvoicing mandate, introduced by the Growth Opportunities Act, requires structured electronic invoices for domestic B2B transactions. Since 1 January 2025, every business must be able to receive EN 16931 compliant eInvoices. Issuing becomes mandatory from 1 January 2027 for businesses with prior-year turnover above 800,000 euros, and from 1 January 2028 for all businesses.
Which formats are valid under the German mandate?
Valid eInvoices must comply with the European standard EN 16931. In Germany that principally means XRechnung and ZUGFeRD from version 2.0.1 in EN-compliant profiles, with Peppol BIS also EN-aligned. A plain PDF is not an eInvoice under the mandate. EDI formats can continue under transitional conditions, with EN-compliant data required as the long-term direction.
Does Germany use a clearance platform like Poland or Italy?
No. Germany currently operates a decentralised, post-audit exchange model with no central clearance platform. Businesses exchange eInvoices directly via email, Peppol, EDI, or service providers, and the recipient's validation decides acceptance. Transaction-based e-reporting is the expected next stage, aligned with the EU ViDA framework, which is why an architecture that already supports reporting models is the safer choice.
How does the OasisPro EU eInvoicing Gateway handle Germany?
The OasisPro EU eInvoicing Gateway generates and receives XRechnung, ZUGFeRD, and Peppol BIS invoices from any ERP, validates them against EN 16931, and manages exchange with your trading partners. The same gateway connection covers France, Poland, Belgium, Italy, Spain, and Romania, with German regulatory developments tracked and updates included in the service.
The Germany eInvoicing mandate rewards the businesses that use 2026 well.
Germany's phased approach has given businesses more runway than any comparable EU mandate. That runway ends in January 2027 for the largest wave of companies, and in January 2028 for everyone.
Businesses that connect through the OasisPro EU eInvoicing Gateway handle Germany the same way they handle France, Poland, Belgium, Italy, and Spain: one connection, every mandate, updates included.
Talk to us about your German footprint.