Germany's E-Invoicing Mandate, Explained: Deadlines, Formats and Exemptions

Why this mandate matters now

Germany's Wachstumschancengesetz, passed on 27 March 2024, introduced a mandatory structured electronic invoice for domestic B2B transactions. It's anchored in law at Section 14 and 14a of the German VAT Act (UStG). The primary motivation is closing the VAT gap: Germany loses an estimated €23 billion a year to VAT fraud and error, and structured, machine-readable invoice data is the tool the legislator is using to close it.

This isn't a large-enterprise-only issue. The obligation to receive structured e-invoices already applies to practically every business, regardless of size or industry. If your invoicing today is still paper or plain PDF, it's worth auditing your process now, because the obligation to issue e-invoices follows on a fixed, staged timeline.

The compliance timeline: 2025, 2027, 2028

In practice: businesses that regularly cross the €800,000 threshold have noticeably less runway than smaller ones.

• **1 January 2025** — every domestic business must be able to receive and machine-process e-invoices. A normal e-mail inbox is technically sufficient for receiving them. Issuing one remains optional in this phase; paper and PDF invoices are still allowed with the recipient's consent.
• **1 January 2027** — issuing becomes mandatory for businesses whose prior-year revenue exceeded €800,000.
• **1 January 2028** — the transition period ends for everyone else. From this date, e-invoicing is mandatory for all affected domestic B2B transactions, regardless of company size.

What counts as an e-invoice — and what doesn't

The legal definition is narrow: an e-invoice must be created, transmitted and received in a structured electronic format that complies with the European standard EN 16931. In Germany, two formats meet this bar in practice — XRechnung, a pure XML format with no visual layout, and ZUGFeRD, a hybrid format that embeds structured XML inside a human-readable PDF. In ZUGFeRD, if the visible PDF and the embedded XML ever disagree, the XML data is what's legally authoritative.

A second clarifying letter from the Federal Ministry of Finance (BMF), dated 15 October 2025, sharpened the technical requirements further, defining three error classes for invoice validation: format errors, business-rule errors, and content errors in the mandatory VAT fields. Businesses are well advised to build a multi-stage validation process for inbound invoices. A scanned PDF or paper invoice does not meet the format requirement — no matter how complete the information on it is.

Who is exempt

• Small-value invoices up to €250 gross
• Invoices from small businesses under the Kleinunternehmer rule (Section 19 UStG) — they may keep issuing paper or PDF invoices, though they still must be able to receive e-invoices themselves
• Transport tickets that double as invoices
• VAT-exempt supplies under Section 4 numbers 8–29 UStG
• Cross-border B2B transactions
• Sales to private consumers (B2C)

Retention and audit trail

E-invoices carry the same eight-year retention period as other VAT-relevant records. What matters is that the structured data part stays archived in its original, unaltered format and remains machine-readable and complete for the entire period — a screenshot or printout doesn't satisfy this.

For businesses already archiving records under Germany's GoBD requirements, the e-invoicing obligation typically slots into existing audit-proof archiving processes. What's essential is an unbroken audit trail: who accessed which invoice and when, what validation ran against it, and how any deletion is logged.

What SAP-run businesses should do now

For SAP-run businesses, this maps directly onto the existing billing process: OXORY converts SAP billing documents into XRechnung or ZUGFeRD automatically, validates inbound invoices against the German format rules, and — where needed — connects the whole flow to the European Peppol network with audit-proof archiving. See our [Compliance & e-invoicing solutions](/solutions/legal-tools) or get in touch if you want your deadline checked against your actual SAP landscape.

• Confirm you can receive and automatically process e-invoices — this obligation has applied since 2025
• Check your own prior-year revenue against the €800,000 threshold to know whether your issuing deadline is 2027 or 2028
• Audit whether your invoicing and accounting software already supports XRechnung and ZUGFeRD generation and validation
• Set up (or confirm) an eight-year, audit-proof archiving process for the structured original format
• Document your Kleinunternehmer status if it applies, since it changes your issuing obligation

Frequently asked questions

When exactly does the German e-invoicing mandate start affecting my business?

Receiving structured e-invoices has been mandatory since 1 January 2025. Issuing them becomes mandatory on 1 January 2027 if your prior-year revenue exceeded €800,000, or 1 January 2028 for all other domestic B2B businesses.

Is a PDF invoice still acceptable?

Only during the transition period and only with the recipient's consent. From your mandatory issuing date onward, a plain PDF or paper invoice no longer meets the legal definition of an e-invoice — it must be a structured format such as XRechnung or ZUGFeRD.

What's the difference between XRechnung and ZUGFeRD?

XRechnung is a pure XML format with no visual layout. ZUGFeRD is a hybrid format that embeds structured XML inside a human-readable PDF; if the two ever disagree, the XML data is legally authoritative.

Are small businesses (Kleinunternehmer) exempt?

They're exempt from the issuing obligation and may keep using paper or PDF invoices, but they still have to be able to receive e-invoices like every other business.

How long do we need to keep e-invoices?

Eight years — the same retention period as other VAT-relevant records — and the structured data must stay archived in its original, unaltered format for the full period.