In short
- Germany mandated the document, not the channel. There is no national platform and no clearance step.
- The obligation to receive came first and applies to every established business, with no threshold.
- The obligation to issue is staged by turnover, with transitional arrangements that expire.
- Compliant formats are national profiles of the European standard: pure XML, or the same XML embedded in a PDF.
Germany's approach is the one most likely to be underestimated, precisely because it looks like the least demanding. There is no portal to register with, no clearance response to wait for, and no identifier assigned by the state. That absence is the point: Germany legislated what an invoice must be, and left how it gets there to the parties.
What the law obliges
The mandate distinguishes sharply between receiving and issuing, and the distinction is the whole timetable.
- 2025-01-01Every business established in Germany must be able to receive a structured electronic invoice for domestic business-to-business supplies. No threshold, no transition.in force
- 2027-01-01Issuers above the turnover threshold set in the transitional rules lose the option of issuing in another format.adopted
- 2028-01-01The remaining transitional arrangements, including the treatment of established EDI flows, expire.adopted
Dates are set by federal law and have been amended before. The Federal Ministry of Finance is the authoritative source and is linked at the foot of this article.
The receiving obligation is the one to take seriously. It is not conditional on your size, it is not conditional on whether you also issue, and there is no version of it that can be satisfied by asking your suppliers to keep sending PDFs. If a German supplier decides to send you a conforming invoice, you must be able to accept it.
What counts as compliant
A compliant invoice is one that conforms to the European semantic standard, in one of the syntaxes that standard permits, as narrowed by a national profile. In practice that means one of two things.
Pure XML. The national profile maintained for the public sector became the reference profile for the private sector too. It is a restriction of EN 16931: everything it requires is in the standard, and it makes some optional things mandatory. See XRechnung explained.
A hybrid file. A PDF with the complete structured invoice embedded inside it as an attachment. The XML is the invoice; the PDF is a rendering for humans. This is the format described in hybrid PDF and XML invoices, and it is disproportionately popular in Germany for one unglamorous reason: it lets a supplier satisfy the mandate without forcing every customer's accounts payable clerk to change how they read an invoice on day one.
If the PDF layer and the XML layer disagree, the XML is the invoice. A rendering process that prints a rounded total, or a discount described differently, has created a document that says two things. Reconcile the two at generation time, not at audit time.
What Germany deliberately did not build
No clearance platform. No national identifier assigned to each document. No delivery receipt from the state. That has three consequences a project plan has to account for.
- There is no acknowledgement to reconcile against. Under a clearance model a document either got a number from the platform or it did not, and that is your evidence of delivery. In Germany, evidence of delivery is whatever your transmission arrangement produces, which makes it your responsibility to keep and to be able to produce years later.
- Rejection happens downstream and late. A buyer's own validation may reject an invoice days after issue, at which point it is a business exception rather than a technical failure.
- Addressing is not solved for you. You need to know how each customer wants to be reached, which is why so many German flows have converged on a four-corner network even though no law requires one.
What stops being an invoice
The definitional change is easy to state and its consequences are not. Where the law requires an invoice in a structured electronic format that permits automatic and electronic processing, a document that does not meet that description is not an invoice for the purposes of the obligation — however it looked, however it was sent, and however willingly the recipient accepted it.
That reclassifies a category of document overnight. A PDF attached to an email, which the VAT directive still regards as an electronic invoice in its own general definition, does not satisfy a structured mandate. Neither does a scanned image, a spreadsheet, or a portal print-out. They can still be sent, and they can still be paid, and they are not the thing the obligation requires.
The practical consequence lands on the buyer more sharply than on the seller. A recipient holding a document that is not a valid invoice has a weaker position on the deduction it supports, which is why receiving-side validation has to mean something more than confirming that a file arrived. It also means the two-channel period is not a technicality: for as long as some suppliers send structured documents and others send PDFs, the function is holding two categories of document with different legal weight and needs to be able to tell them apart.
That is a policy decision as much as a systems one, and the honest version of it is written down before go-live rather than improvised by whoever is handed the first ambiguous case.
Where the work actually is
Not in the format. Two things account for most of the effort in German implementations.
Master data completeness. The national profile makes fields mandatory that German ERP systems have historically left blank: a buyer reference, complete address components, tax category codes on every line. Populating them for a live customer master is not a technical task and it does not compress. Start with master data for e-invoicing.
The receiving side. The obligation nobody budgets for. Somebody has to decide where a structured invoice arrives, what validates it, what happens when validation fails, and how the result reaches the ledger. That is a redesign of accounts payable, and it is due before the issuing obligation, not after it.
Reading the dates honestly
Germany's timetable has been amended once already, and other Member States have postponed comparable mandates more than once. Treat the dates above as what the published law currently says, check them against the ministry's own guidance before committing capital, and note in any business case which of them are in force and which are merely adopted. That distinction is the difference between a plan and a hope.
