Germany's E-Invoicing Mandate: The 2025 to 2028 Roadmap Without the Myths

Since 1 January 2025, e-invoicing in German B2B business is no longer optional. The first stage of the new mandate is in force: every domestic company must be able to receive structured electronic invoices. Issuing them electronically is not yet compulsory, but receiving them is. The legal basis is the Growth Opportunities Act (Wachstumschancengesetz), passed by the Bundesrat on 22 March 2024; the details are set out in the Federal Ministry of Finance guidance of 15 October 2024.

More half-truths circulate around this obligation than around most tax topics. Three are worth clearing up.

Myth 1: “A PDF is an e-invoice”

No. An e-invoice in the sense of the EN 16931 standard is a structured dataset that software can process without a media break. A classic PDF, even if it arrives by email, is merely an “other invoice” once the mandate applies. What counts is the machine-readable XML, not the image for the human eye.

In Germany, two formats meet the standard: XRechnung, a pure XML following the CIUS of EN 16931, and ZUGFeRD from version 2 onward, a hybrid of PDF/A-3 with embedded XML. With ZUGFeRD, the XML leads, not the visible PDF. One important caveat: only the profiles from “EN 16931” (Comfort) upward are standard-compliant. The smaller MINIMUM and BASIC WL profiles carry too little data to count as a full invoice.

Myth 2: “It only matters in 2027, and only for big companies”

Receiving has applied to everyone since January 2025. Only issuing is staggered:

• since 1 Jan 2025: obligation to receive, for all domestic companies
• from 1 Jan 2027: obligation to issue, for companies with more than 800,000 euros prior-year turnover
• from 1 Jan 2028: obligation to issue, for all remaining B2B relationships

Until the end of 2026, paper and unstructured formats may still be used by mutual agreement, and smaller issuers get an additional grace period until the end of 2027. Established EDI procedures remain permissible under conditions, but must move toward the standard. Whoever touches the issuing side only in 2027 still has a receiving task today.

Myth 3: “Receiving just means the email can arrive”

Legally, an email address is enough for an e-invoice to be delivered. Operationally, that is half the job. Three things belong to it:

• Validation: the incoming XML should be checked against the schema and business rules of EN 16931, otherwise faulty invoices land in the records unnoticed.
• Visualisation: a viewer that renders the XML legibly, so departments without XML knowledge can review it.
• GoBD-compliant archiving: what must be retained is the structured original, unalterable and chained in an audit-proof way, not just a PDF printout.

The last point in particular is underrated. Whoever archives only the visual document and discards the XML has not retained the invoice in the legal sense.

What makes sense now

Receiving is mandatory and should be set up cleanly: validation, viewer, an audit-proof archive of the XML. In parallel, it is worth looking at issuing. Which customer relationships fall under the obligation in 2027, which formats do recipients expect, and how does the structured original leave your own system cleanly. In our commercial core Datargo ERP, EN 16931, XRechnung and ZUGFeRD, along with GoBD-compliant chaining, are built in from the start. The point itself, though, is independent of any tool, namely to treat the structured original as the leading record and not as an afterthought to the PDF.

The obligation does not arrive in 2027. It began in 2025, just quietly, on the receiving side.