German E-Invoicing Checklist: ZUGFeRD & XRechnung Compliance Step by Step
Germany's e-invoicing mandate under Section 14 of the German VAT Act (UStG) replaces PDF and paper invoices for domestic B2B transactions with structured formats based on EN 16931 — in practice XRechnung (pure XML) and ZUGFeRD (PDF with embedded XML). Reception has been mandatory since 2025; the duty to issue phases in through 2028. Any international group with a German entity, and any supplier serving German enterprise customers, needs a working answer.
The good news: this is an implementation project with clear acceptance criteria, and existing PDF invoice layouts can usually be preserved by moving to ZUGFeRD. The work is in scoping which invoice flows are affected, getting the structured data complete and valid, and making sure reception and archiving are as compliant as issuance. The checklist below sequences it.
Your checklist
- 1Assess applicability: identify which of your entities make domestic German B2B supplies and map each invoice flow (outbound and inbound) against the § 14 UStG phase-in dates.
- 2Confirm reception capability now: ensure your German entity can receive and process EN 16931 e-invoices — this has been mandatory since January 2025 and an email inbox for e-invoices is the minimum.
- 3Choose your outbound format: pick ZUGFeRD (PDF with embedded XML, keeps your layout) for B2B, and XRechnung where public-sector or customer requirements demand pure XML.
- 4Close the data gaps: verify your billing system captures all EN 16931 mandatory fields (buyer reference, tax details, payment terms, line-item data) with clean master data.
- 5Validate before sending: run generated invoices through an EN 16931 / ZUGFeRD validator so schema errors are caught before customers or auditors find them.
- 6Convert legacy workflows: route existing PDF invoice processes through a conversion step to ZUGFeRD instead of rebuilding the billing stack, if a full system change is not warranted.
- 7Archive compliantly: store e-invoices with their structured XML unchanged for the statutory retention period under German bookkeeping rules (GoBD), not just the rendered PDF.
- 8Update accounts payable: teach AP to detect, validate and book inbound e-invoices automatically, and to reject non-compliant supplier invoices with a clear correction request.
- 9Inform suppliers and customers: communicate your format capabilities and requirements so both directions of your invoice traffic switch over without payment disruption.
Frequently asked questions
Can we keep our current invoice layout?
Yes, with ZUGFeRD. The format embeds the structured EN 16931 XML inside your existing PDF, so recipients see the familiar document while their systems process the data automatically. That makes ZUGFeRD the usual choice for companies that want compliance without changing what customers see.
Do intra-EU or export invoices fall under the German mandate?
The core issuance mandate covers domestic B2B supplies between businesses established in Germany. Cross-border invoices are generally outside it, though EU-level initiatives are moving the same direction and German customers may contractually request structured formats anyway. Scope each flow individually rather than switching everything blindly.
What does 'compliant archiving' mean for e-invoices?
The structured data is the invoice, so the original XML (or ZUGFeRD file with its XML intact) must be stored unaltered, retrievable and machine-evaluable for the statutory retention period under German bookkeeping rules (GoBD). Printing to paper or keeping only a rendered PDF does not satisfy this.