Vai al contenuto
Torna al blog
GermanyPubblicato il 3 luglio 202611 min di lettura

Germany's e-invoicing mandate: E-Rechnung deadlines 2025, 2027 & 2028 explained

Germany's B2B e-invoicing mandate: who must receive from 2025, who must issue from 2027 and 2028, XRechnung vs ZUGFeRD, how to receive and create structured invoices, penalties and a checklist.

Germany is rolling out mandatory B2B e-invoicing (the E-Rechnungspflicht) in phases. The first phase — the obligation to receive structured electronic invoices — has applied to every domestic business since 1 January 2025. Issuing becomes mandatory in 2027 and 2028. This guide explains the E-Rechnung deadlines, the difference between XRechnung and ZUGFeRD, how to receive and create compliant invoices, the penalties, and a short readiness checklist.

What is an E-Rechnung (and what is not)?

Under the German rules an E-Rechnung is a structured electronic invoice that can be processed automatically — issued, transmitted and received in a structured format based on EN 16931. A PDF sent by email is explicitly not an E-Rechnung: it counts as an "other" invoice, because it is not machine-readable structured data. The accepted structured formats are XRechnung (a pure-XML CIUS) and ZUGFeRD 2.x (a hybrid PDF/A-3 with embedded XML).

The E-Rechnung deadlines: 2025, 2027, 2028

  • 1 January 2025 — every domestic business must be able to receive structured e-invoices (XRechnung / ZUGFeRD). Issuing paper or PDF is still allowed during the transition.
  • 1 January 2027 — businesses with annual turnover above €800,000 (prior year) must issue structured e-invoices for domestic B2B transactions; paper/PDF is no longer allowed for them.
  • 1 January 2028 — all remaining businesses must issue structured e-invoices; the transitional exceptions expire.

The practical point people miss: receiving is already mandatory. From 2025 you cannot refuse a supplier's XRechnung or ZUGFeRD — your systems must be able to accept and process it, even if you are not yet obliged to issue one.

Who is affected?

The mandate covers domestic B2B transactions between businesses established in Germany. Both parties must be German-established for a transaction to be in scope. B2G (invoicing public authorities) has required XRechnung for years already. Small-value invoices and certain exempt supplies have special handling, but the safe assumption is: if you invoice German businesses, you are in scope.

XRechnung vs ZUGFeRD — which format?

Both are valid E-Rechnung formats built on EN 16931; the difference is packaging.

  • XRechnung — a pure XML invoice (UBL or CII). It is the mandatory format for German public-sector (B2G) invoicing and a safe default for B2B. No human-readable layer; it is meant to be processed by software.
  • ZUGFeRD 2.x — a hybrid: a human-readable PDF/A-3 with the EN 16931 CII XML embedded inside it. Handy when a person also needs to read the invoice, while machines read the embedded XML.

You can send whichever your buyer accepts. Many German companies standardise on XRechnung for B2G and offer ZUGFeRD for B2B partners who still want a visual PDF.

How to receive e-invoices (the 2025 obligation)

To satisfy the receiving obligation you need to accept an incoming XRechnung or ZUGFeRD and read its structured data. With MyInvoice you can convert an incoming ZUGFeRD / Factur-X PDF or CII XML into whatever your systems consume — the embedded XML is extracted automatically:

curl -X POST https://api.myinvoice.llc/v1/convert \
  -H "X-API-Key: ek_live_..." \
  -F "[email protected]" \
  -F "format=cii" \
  -F "profile=ubl-plain"

This turns an incoming German hybrid invoice into clean structured data you can post into your ERP — most invoices arrive as ZUGFeRD, but few systems can actually read them.

Try reading a ZUGFeRD invoice

How to create an XRechnung or ZUGFeRD

For issuing, you send the invoice data you already have — CSV, Excel, UBL, EDIFACT or legacy XML — and request the profile you need. MyInvoice returns XRechnung 3.0 (or EN 16931 CII XML for ZUGFeRD embedding), validated against XSD and the XRechnung/EN 16931 Schematron:

curl -X POST https://api.myinvoice.llc/v1/convert \
  -H "X-API-Key: ek_live_..." \
  -F "[email protected]" \
  -F "format=csv" \
  -F "profile=xrechnung-3"

Still on EDIFACT? Migrating legacy EDI to Peppol / XRechnung

Many German (and Dutch and Nordic) retail and automotive supply chains still exchange EDIFACT INVOIC. Those messages are not structured e-invoices in the EN 16931 sense, so they do not satisfy the mandate on their own. MyInvoice reads EDIFACT D.96A INVOIC directly and maps it into XRechnung, ZUGFeRD or Peppol BIS 3.0 — so you can keep your existing EDI backbone and still produce compliant German e-invoices, without ripping out your EDI setup.

Penalties and the transition period

German authorities have signalled a soft transition: during 2025–2026, paper and PDF remain permitted, and no specific penalties apply for not issuing structured invoices yet. Once issuing becomes mandatory for your business (2027 or 2028), non-compliance can be sanctioned — German law allows fines up to €5,000 for failing to issue an invoice in the prescribed form. Because receiving is already mandatory, the real work — being able to accept and process an XRechnung / ZUGFeRD — should already be in place.

Readiness checklist

  • Confirm you can already receive and read XRechnung and ZUGFeRD (mandatory since 2025).
  • Check your 2027 exposure: is your prior-year turnover above €800,000?
  • Decide your issuing format(s): XRechnung for B2G, XRechnung or ZUGFeRD for B2B.
  • If you use EDIFACT or a legacy ERP export, set up a conversion path to XRechnung / ZUGFeRD.
  • Validate every outgoing invoice against XSD + EN 16931 / XRechnung Schematron before sending.

Frequently asked questions

Is a PDF invoice still allowed? During the transition (2025–2026) yes, but a plain PDF is not a structured E-Rechnung. Once you are obliged to issue (2027/2028), you must send XRechnung or ZUGFeRD.

Do I have to issue e-invoices already in 2025? No — but you must be able to receive them from 1 January 2025. Issuing is phased in 2027 (large) and 2028 (all).

Is ZUGFeRD enough, or do I need XRechnung? Both are valid. ZUGFeRD 2.x is accepted for B2B; XRechnung is mandatory for B2G. Pick what your buyer requires.

Where MyInvoice fits in

MyInvoice reads incoming ZUGFeRD / Factur-X and EDIFACT and turns your existing data into a validated XRechnung 3.0 or EN 16931 CII XML for ZUGFeRD — and, from the same data, into Peppol BIS 3.0 or any other profile you need. One API, receive and issue, XSD + Schematron validated.

Read the API docs