Blog
Processing e-invoices: XRechnung, ZUGFeRD and the rest of your inbox
In short
An e-invoice is structured and machine-readable under EN 16931; a PDF does not count. German B2B companies have had to be able to receive e-invoices since 1 January 2025, and the obligation to send them is phased in from 2027. The real effort, though, lies not in the e-invoice itself but next to it: orders, delivery notes and foreign invoices still arrive as PDFs.
What applies from when?
The changeover is phased. The key dates below come from publications by the Federal Ministry of Finance (Bundesfinanzministerium). Deadlines have shifted during the legislative process, so check the current status before you invest.
| From | What applies | Who it applies to |
|---|---|---|
| 1 January 2025 | Must be able to receive e-invoices | All domestic companies in B2B |
| 1 January 2027 | Obligation to send e-invoices | Companies with prior-year turnover above around €800,000 |
| 1 January 2028 | Obligation to send e-invoices | All other domestic companies in B2B |
What counts as an e-invoice, and what does not
A PDF sent by email is not an e-invoice. What counts is a structured, machine-readable format under the European standard EN 16931. In Germany, two formats mainly meet this: XRechnung, which is pure XML, and ZUGFeRD from version 2.x, where the XML is embedded in a human-readable PDF.
On the receiving side, this means little work at first: a structured format does not need to be recognised, only read in. Recognition is unnecessary exactly where the format makes it redundant.
The real problem is the mixed inbox
The mandate covers invoices. It does not cover order confirmations, delivery notes, bills of quantities (Leistungsverzeichnisse) or purchase orders, and it does not apply to foreign suppliers. For years to come, two routes will therefore run side by side: structured invoices that are read in directly, and everything else, which still arrives as a PDF, a scan or free text in an email.
If you only solve the e-invoice, you have solved the smaller part. What makes sense is an inbox where both routes end up in the same process: structured formats are parsed, unstructured ones are extracted, and both are then handled the same way, checked against your master data and passed to the ERP.
What incoming invoice processing really depends on
Whether an invoice goes through automatically rarely depends on the format. It depends on the checks: does the invoice belong to a purchase order? Do the line items, quantities and prices match? Is the supplier set up? A formally correct XRechnung with a wrong item number can no more be posted than a badly scanned PDF.
The effort therefore shifts from data entry to resolving discrepancies, which is the actual purpose of the changeover. Done manually, this typically costs 30–100 working days a year at an error rate of 5–15%.
Frequently asked questions
Is it enough to be able to archive e-invoices?
Receiving them and storing them in an audit-proof way is the minimum requirement. The changeover only pays off once the data they contain is also checked and posted without anyone retyping it.
What about suppliers who keep sending PDFs?
They will keep coming: foreign suppliers are not covered by the German mandate, and it does not apply to other document types anyway. For this part, you need extraction that works without a template per supplier.
Is ZUGFeRD or XRechnung the better choice?
For sending to public authorities, XRechnung is the standard. ZUGFeRD is more convenient in B2B because the same file stays readable for people. On the receiving side, you should be able to process both.
Do we have to replace our ERP?
No. The inbox can sit in front of it: documents are read and checked before they reach the ERP and handed over as a finished record, via the REST API or an export.
Send us a document and watch the extraction.
30 minutes, your own documents, no preparation needed.