Country deep dive
Germany's reform is unusually gradual by design — a pure receiving mandate first, then issuance phased in strictly by company turnover, with no domestic reporting obligation attached (yet).
Every invoice sent to a German federal ministry, state authority, or municipal body in scope must comply with XRechnung or an equivalent EN 16931-conformant format — years ahead of any B2B obligation.
The law establishing Germany's B2B e-invoicing mandate clears its final legislative hurdle, setting the phased 2025–2028 timeline described below.
A pure reception obligation — every VAT-registered business, regardless of size, must be technically capable of receiving an EN 16931-compliant structured e-invoice. Sending paper or PDF invoices remains fine during the transition, provided the recipient agrees.
Businesses crossing this threshold must issue structured e-invoices (XRechnung, ZUGFeRD 2.1+, or another EN 16931-compliant format) for domestic B2B sales. Kleinunternehmer under §19 UStG (turnover ≤€25,000 prior year, ≤€100,000 current year) remain exempt from issuing but must still be able to receive.
The obligation extends to every domestic B2B business below the €800,000 threshold, completing the phased rollout. No real-time VAT reporting system is attached to this mandate — unlike France or Poland, Germany treats e-invoicing purely as a format requirement, not a data-reporting one, for now.
Germany accepts two genuinely different national formats side by side, plus Peppol BIS as a third option — there's real choice here, unlike most CTC countries.
Because XRechnung has no human-readable rendering built in, recipients need software that can actually display or process the XML — this is part of why ZUGFeRD is often preferred for B2B.
The embedded XML follows the same CII syntax family as XRechnung's CII option — so a well-built pipeline can often generate both formats from the same underlying data model.
All of this must live in the structured data itself — attaching a compliant-looking PDF alongside a non-compliant XML doesn't satisfy the mandate. "XML" alone isn't a compliance indicator either; it must be a recognised EN 16931 implementation.
Saving only a printed copy of a ZUGFeRD invoice instead of the original file violates GoBD record-keeping rules — the embedded XML is the part that must survive, not just the PDF rendering.
This is the biggest structural difference from France, Italy, or Poland: Germany has no clearance authority and no mandated channel for B2B at all.
The mandate governs the format of the invoice, not how it travels. Two trading partners are free to agree on whatever transmission method suits them, as long as the file itself is a compliant structured invoice.
Your contracting authority tells you which platform and Leitweg-ID to use — check your contract or procurement terms if unsure. Authorities must also offer Peppol as a transmission option where automated exchange is possible.
If your invoice bounces from ZRE or OZG-RE, these four causes cover the large majority of real-world rejections — check the Leitweg-ID and profile version first.
German tax authorities can request any of these three access modes during an audit — keeping invoices systematically archived in a standard, exportable format materially reduces audit friction.
Unlike Romania, France, or Belgium, there's no directory to join or account to open for B2B — Germany's decentralised model means "registration" is really about internal readiness and, where relevant, your specific government customer's portal.
Check your prior-year turnover against the €800,000 threshold to know whether your issuing obligation starts in 2027 or 2028 — and confirm whether Kleinunternehmer status (§19 UStG) exempts you from issuing altogether.
XRechnung suits high-volume automated B2B flows; ZUGFeRD suits relationships where a human still needs to open and read the invoice; Peppol BIS suits businesses already active on that network for other European trade.
Validate that supplier/customer details, transaction detail, and full tax breakdown are embedded in the XML — not just present in an accompanying human-readable PDF.
Register on whichever platform your public-sector customer directs you to, and confirm the correct Leitweg-ID for that specific contracting authority before your first submission.
Since there's no mandated channel, settle this explicitly with your trading partners — email, a shared portal, EDI, or Peppol are all valid as long as the underlying file is compliant.
Store the original structured file (not a printed copy) for the required retention period, and confirm you can produce Z1/Z2/Z3-style audit access if the tax office asks.
Germany has no dedicated e-invoicing fine — non-compliance is folded into existing VAT and bookkeeping law, and the sharpest risk isn't a government fine at all.