← All guides · Formats & conversion
XRechnung vs ZUGFeRD: Germany's two e-invoice formats compared
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Convert an invoice free
Put this guide into practice now: convert one invoice free — validated UBL 2.1 XML plus a Factur-X PDF, with the acceptance checker for your client’s country. See pricing for bulk conversion, country rule packs and monitored clients.
Short answer
XRechnung and ZUGFeRD are Germany's two EN 16931 shapes. XRechnung is a pure structured XML invoice — data only, built for systems, and the public sector's standard profile. ZUGFeRD is the hybrid: a readable PDF carrying the structured invoice embedded inside it, the German sibling of France's Factur-X. This product produces the matching pair — UBL 2.1 XML and a Factur-X PDF — so both kinds of German client are covered.
XRechnung vs ZUGFeRD in one line
XRechnung is Germany's CIUS of EN 16931 as a standalone XML document; ZUGFeRD is the German hybrid format pairing a visual PDF with embedded EN 16931 XML. EInvoice Translator's mandate table lists Germany's channel as 'EN 16931 (XRechnung / ZUGFeRD)', and its outputs map onto the pair: the UBL 2.1 XML download is the structured document, the Factur-X PDF is the hybrid document with byte-identical embedded XML.
XRechnung: the invoice as pure data
XRechnung exists for machine-first processes, above all German public administration, which standardised on it for supplier invoicing. There is no visual layer to approve; the XML is the invoice, validated against the profile's rules on intake and booked from its elements. A supplier to German public bodies meets XRechnung as a stated requirement, with the buyer's routing details (their Leitweg-ID culture of precise addressing) as part of onboarding.
For a private-sector supplier, XRechnung's lesson is broader than its public-sector home: it demonstrates the end-state of structured invoicing, where the document a human reads is a rendering, not the record. If your systems can produce a core-valid EN 16931 invoice, you hold the substance XRechnung asks for; the profile's specifics are a country-layer check, which is what Pro's country rule packs are for.
ZUGFeRD: the invoice people can read
ZUGFeRD answers the adoption problem: businesses think in documents. Its PDF looks like the invoices German Mittelstand firms have exchanged for decades, while the embedded XML carries the same invoice as EN 16931 data. The approver reads; the system books; neither waits for the other. It is the same architecture as Factur-X — the two were developed in French-German cooperation from one idea, which is why the names are used almost interchangeably in supplier conversations.
The construction quality bar is identical, too: the embedded XML must be the validated invoice, identical to the structured copy, generated from the same data as the page. This product's builder proves it mechanically — the test suite extracts factur-x.xml back out of generated PDFs — because a hybrid whose layers disagree is worse than either format alone.
Which one does your client want?
Read the client's words carefully. 'XRechnung' names the pure XML profile — public buyers mean it literally. 'ZUGFeRD' (or Factur-X) names the hybrid — send the PDF-with-XML. 'E-invoice' or 'EN 16931 invoice' unqualified usually means: structured data must arrive; the hybrid satisfies most private-sector intakes, and sending both files satisfies everyone. Germany's receiving duty — in force since January 2025 — means every German business must be able to receive structured invoices, so either artefact has a home.
When in doubt, the pair is the answer: UBL XML plus Factur-X PDF, same invoice, both validated. The client files whichever their process consumes and archives the other. The only wrong answers are a lone plain PDF (no data) and a lone screenshot-like scan (no data, worse) — the two artefacts German systems are now built to refuse.
Data demands: identical underneath
Both formats stand on the same invoice discipline, because both express the same core model. Complete parties and addresses; VAT identifiers in place for cross-border reverse charge (category AE lines require the buyer's identifier, and cross-border B2B requires the seller's); lines itemised with categories and rates in agreement; totals computed from lines and reconciled under BR-CO.
Germany's phased issuing timetable — January 2027 above EUR 800k turnover, January 2028 for all — decides when your German clients must issue in these formats, not whether the formats work. As a supplier you are on the receiving-readiness side: their January 2025 receiving duty means your structured invoice is welcome today, whichever of the two shapes you send.
Producing both from one conversion
The workflow that covers Germany is the workflow that covers Europe: enter the invoice once, validate against the core rules, download both artefacts. Validation failures return as named rules with an exception workspace to correct them — fix the data, not the file — and the generated XML is parsed back and re-checked so the structured copy is proven as a file, not just as form entries.
Firms invoicing Germany at volume add the Pro layer: bulk conversion for whole billing runs, the German country rule pack for the profile specifics, and monitored clients tracking each German client's phase position as 2027 and 2028 arrive. The formats stop being a research topic and become what they should be: a dropdown you no longer think about, because both outputs are always in the download.
Answering a German format request in 5 steps
- Identify the ask: XRechnung means pure structured XML; ZUGFeRD/Factur-X means the hybrid PDF; unqualified means send both.
- Convert the invoice through core validation — fix any named rule failures in the exception workspace first.
- Download the UBL XML and the Factur-X PDF from the same conversion so both describe the identical invoice.
- Check the German layer (buyer size, phase date) with the acceptance checker and country rule packs.
- Send the requested artefact — or the pair — and archive both with the invoice record.
Worked example: one invoice, both German shapes
A consultancy bills a German client EUR 4,000.00 plus standard-category VAT at 20% — tax EUR 800.00, payable EUR 4,800.00. The client's supplier letter asks for 'e-invoices per EN 16931 (XRechnung or ZUGFeRD)'. The consultancy converts once: the UBL XML is the XRechnung-shaped structured document; the Factur-X PDF is the ZUGFeRD-shaped hybrid, readable page on top, identical XML inside.
Both files go out with the same email. The client's system ingests the XML; their project lead approves from the PDF. No second version was created, no totals were retyped, and when the client's auditor asks for 'the invoice', both artefacts answer with the same EUR 4,800.00.
Frequently asked questions
Is Factur-X acceptable where ZUGFeRD is asked?
They are the French and German names for the same hybrid architecture — a readable PDF with the EN 16931 invoice embedded. This product labels its hybrid Factur-X; its construction (validated XML embedded byte-identically) is what ZUGFeRD asks for.
Do private German companies require XRechnung?
XRechnung is chiefly the public-sector profile. Private clients more often ask for EN 16931 or the hybrid. Germany's mandate channel is listed here as 'EN 16931 (XRechnung / ZUGFeRD)' — send the pair and both readings are covered.
Can I send only the hybrid PDF to a systems-driven client?
If their intake wants pure XML, send the UBL file — it is generated in the same conversion, from the same validated data. The pair exists precisely so you never have to choose blind.
When do German clients have to issue these formats?
Issuing phases in: January 2027 above EUR 800k turnover, January 2028 for all. Receiving structured invoices has been mandatory since January 2025.
What data do both formats require?
The EN 16931 core: complete parties, identifiers for cross-border rules, per-line VAT categories and rates, and BR-CO-reconciled totals — all checked by conversion-time validation.
Keep going
Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides
Related guides
- Germany's e-invoicing rules: receiving since 2025, issuing phased 2027–2028
- What is a Factur-X invoice? The PDF with the invoice inside it
- What is a CIUS? How countries tailor the EN 16931 core invoice
- France's e-invoicing reform: receive from September 2026, SMEs issue from 2027
- What is a UBL 2.1 invoice and when do you need one?