E-RECHNUNG
XRechnung vs ZUGFeRD: the same invoice, packaged differently
The two names dominate every German e-invoicing conversation, and the choice between them is less dramatic than it sounds: both implement the same European norm, EN 16931, so both are compliant e-invoices under § 14 UStG. What differs is packaging, and packaging decides who can work with the file. This guide lays out the differences that actually matter and gives a decision rule per customer segment.
Last updated: September 16, 2026
The one-sentence versions
XRechnung is pure XML: the German reference profile of EN 16931, operated by KoSIT, with no human-readable layer, current version 3.0.2. ZUGFeRD is a hybrid: a PDF/A-3 with the same kind of EN 16931 data record embedded, maintained by FeRD together with France’s Factur-X, current version 2.5.2. An XRechnung is only data; a ZUGFeRD invoice is data wearing a PDF.
Because both carry the same semantic model, the same information exists in both; a system that understands the Business Terms processes either. The differences live in who else can use the file, what public-sector channels accept, and how much discipline your process needs to always work from the structured layer.
Side by side
The decision, by customer segment
Issuers rarely need one answer; they need a rule per segment:
- Public-sector customers. XRechnung, addressed with the customer’s Leitweg-ID, through the prescribed portal or Peppol. This segment is not a choice.
- Large automated B2B partners. Either format works; pure XRechnung or Peppol delivery keeps the pipeline free of PDF detours and manual temptation.
- The long tail of smaller partners. ZUGFeRD in profile EN 16931 or higher: their systems, or their people, can still read the PDF layer while yours books from the XML.
- French counterparties. ZUGFeRD doubles as Factur-X, so one export path can serve both countries’ conventions.
- Everyone, before configuring. Whatever the format, verify version and profile in the export settings and validate outbound invoices against EN 16931; a MINIMUM-profile file fails your issuing duty regardless of how nice its PDF looks.
Receivers do not choose
The comparison reads differently from the accounts-payable side, because since January 1, 2025 compliant e-invoices of either format may arrive without your consent, and the BMF foresees no receiving exceptions. Your intake must parse XRechnung’s two syntaxes, unpack ZUGFeRD’s container, always work from the structured layer, and archive it unaltered for eight years. Running one process for XML and another for hybrids doubles the surface for errors.
The pragmatic architecture is one pipeline that treats format as an input detail: Talonic resolves XRechnung, ZUGFeRD, Peppol invoices, plain PDFs, and paper scans into the same schema-validated output, with confidence scores and per-field provenance, so the XRechnung-vs-ZUGFeRD question disappears at the moment of booking.
Work with e-invoices in practice
Reading about formats is one thing; an accounts-payable inbox full of them is another. Two free resources and one production path:
- Peppol e-Invoice Extractor: pull the seller, buyer, line items, VAT breakdown, and totals out of an e-invoice, free in the browser
- Peppol e-invoice extraction guide: the EN 16931 field model (Business Terms) explained field by field
- Invoice parsing with schema validation: process XRechnung, ZUGFeRD, Peppol invoices, PDFs, and paper scans into one validated output schema, with confidence and provenance on every value
Frequently asked questions
Which format should I use for B2B invoices?+
Both satisfy the mandate, so decide by audience: ZUGFeRD in profile EN 16931 or higher where partners still read invoices by eye, XRechnung or Peppol delivery for fully automated relationships. Many issuers run both, chosen per customer segment.
Do German authorities accept ZUGFeRD?+
The public-sector channels are built around XRechnung, submitted via portals like ZRE and OZG-RE or over Peppol with the authority’s Leitweg-ID; ZUGFeRD’s XRECHNUNG reference profile exists to bridge toward those requirements. For B2G, treat XRechnung as the safe answer.
Is one format more compliant than the other?+
No. Both implement EN 16931, and § 14 UStG accepts either; ZUGFeRD only adds the profile condition (version 2.0.1 or later, profile BASIC or higher). Compliance problems come from thin profiles, outdated exports, and broken business rules, not from the format choice itself.
Can I convert between XRechnung and ZUGFeRD?+
The data models align, so mapping between them is technically feasible, and tools do it. The risk sits in dropped or mis-mapped fields: a conversion that loses a mandatory element produces non-compliant invoices at scale. Validate the output of any conversion step against EN 16931.
Will one of the two formats win?+
Neither needs to. Both are implementations of the same European norm with institutional backing, XRechnung in the public sector, ZUGFeRD/Factur-X in Franco-German B2B practice. Receivers should plan for both indefinitely; that is what EN 16931 makes cheap.
The E-Rechnung guides
- E-Rechnung: the guide hub
- What is an E-Rechnung?
- E-Rechnung Pflicht: the deadlines
- The formats: XRechnung, ZUGFeRD, Peppol
- Creating e-invoices
- XRechnung: the German standard
- ZUGFeRD: the hybrid format
- XRechnung vs ZUGFeRD
- Receiving and processing e-invoices
- E-Rechnung for Kleinunternehmer
- Archiving e-invoices: GoBD
- Peppol: the delivery network
Sources
Primary sources, last checked September 2026. Statutory texts and BMF publications are authoritative; where guidance rests on the BMF letter of 15 October 2025, the text says so.
- XRechnung standard (KoSIT / XStandards Einkauf)
- ZUGFeRD standard and releases (FeRD)
- BMF: FAQ on the E-Rechnung (qualifying formats and profiles)
- BMF letter of October 15, 2025 (hybrid precedence)
- E-Rechnungsverordnung (B2G requirements)
This guide is general information for businesses, compiled from the cited official sources. It is not legal or tax advice; for decisions about your own obligations, consult your tax advisor (Steuerberater).
One inbox, every invoice format, one schema
The mandate makes structured formats the norm, but your accounts payable will keep receiving paper scans and plain PDFs beside XRechnung and ZUGFeRD for years. Talonic normalizes that mixed inflow into one schema-validated output: typed fields, a confidence score, and provenance on every value, processed on EU infrastructure in Germany. Send a sample batch and judge the output field by field.