agenttoolworks

Phasing in · DE

E-invoicing in Germany.

Receiving mandatory since January 2025; issuing phases in through 2027 and 2028.

The calendar

DateWhoWhat becomes mandatory
2019-11-01Public sector entitiesReceiving and processing structured invoices compliant with EN 16931.
2025-01-01Every businessBeing able to RECEIVE an EN 16931 invoice. This half has no turnover threshold.
2027-01-01Businesses above EUR 800,000 turnoverIssuing: paper and unstructured electronic formats stop being allowed.
2028-01-01Every remaining businessIssuing, with no threshold left.

Verified on 2026-08-17 against European Commission, eInvoicing in Germany. Mandate calendars move, and several of these have moved once already. If you are reading this well after that date, check the source before acting on it, and tell us if it has changed.

How invoices actually move

Decentralised, and deliberately so. There is no single national clearing platform for B2B. Public bodies receive through ZRE and OZG-RE with a Leitweg-ID for routing, and Peppol transmission is supported by federal and national authorities.

What the document has to be

XRechnung, a pure XML file, and ZUGFeRD 2.1, a PDF with the XML embedded. Peppol BIS Billing 3.0 is also supported. All three are ways of satisfying EN 16931.

What most summaries get wrong

Where we fit

InvoiceForge builds and checks the document: it generates an EN 16931 invoice, validates one against the rules a real validator reports, and reads one back into structured data. An agent can call it directly.

It does not transmit. Reaching Germany means going through the network above, and that is a separate piece we would rather name than blur. You need both, and knowing which one you are missing is worth more than a page that implies one product does everything.

We are not affiliated with the European Commission, OpenPeppol, or any tax authority. The dates on this page come from the Commission's own country factsheets and, where one exists, the national portal linked above.