ZUGFeRD ToolsZUGFeRD Tools

ZUGFeRD vs XRechnung — the format comparison

ZUGFeRD or XRechnung — the defining question in German e-invoicing. Both formats build on EN 16931 but differ in structure, rules and typical deployment. This comparison brings order to the question: which format for which purpose?

By the editorial team ZUGFeRD Tools

  • Both build on EN 16931
  • ZUGFeRD 2.5.2 · XRechnung 3.0.2 (as of 2026-09-29)
  • B2B vs. B2G as the rule of thumb
  • Many companies master both
ZUGFeRD version (FeRD, 2026-08-04)
2.5.2ZUGFeRD version (FeRD, 2026-08-04)
XRechnung, bundle 2026-08-31
3.0.2XRechnung, bundle 2026-08-31
ZUGFeRD profiles
5ZUGFeRD profiles
syntaxes: UBL 2.1 & CII
2syntaxes: UBL 2.1 & CII
EN 16931 rules checked
24EN 16931 rules checked
all tools, no sign-up
€0all tools, no sign-up

ZUGFeRD vs XRechnung: the core difference

The ZUGFeRD vs XRechnung pairing describes the two German ways of exchanging electronic invoices per EN 16931. The formats are not rivals for the same slot but tools for different recipient groups — weighing ZUGFeRD vs XRechnung ultimately means designing your own process landscape. ZUGFeRD is the hybrid: a PDF for humans with an embedded XML for machines. XRechnung is the pure XML file — no visual layer, but with additional German rules (a CIUS) going beyond the European standard.

Both share the same semantic foundation: invoice number, parties, line items, taxes and totals follow EN 16931. The step between the formats is therefore small — content-wise the data is nearly identical, differently packaged and differently strictly regulated.

ZUGFeRDXRechnung
Visual PDFyes (core part)no — pure XML
Structured dataembedded CII XMLUBL or CII XML
Readable without vieweryesno
German extra rules (CIUS)noyes — BR-DE rules
Typical useB2B / mixed workflowsB2G / structured exchange
Current version2.5.23.0.2 (bundle 2026-08-31)
Receivers in DEreceivable since 2025authorities via ZRE/OZG-RE

ZUGFeRD vs XRechnung: when ZUGFeRD is typical

ZUGFeRD typically dominates commercial traffic: small and mid-sized companies appreciate that the invoice lands in the mailbox as a familiar PDF while staying machine-readable. If you serve many different customers — from trades to corporates — a ZUGFeRD invoice in the EN 16931 profile is usually the robust choice.

ZUGFeRD strengths: low entry barrier (the trusted PDF stays), broad support in accounting systems, human-readable without tools, archivable as PDF/A-3. Limits: for public-sector traffic ZUGFeRD usually does not suffice — there, authorities require XRechnung.

ZUGFeRD vs XRechnung: when XRechnung is in demand

As of 2026-09-29 — XRechnung 3.0.2 with bundle 2026-08-31 is current; XRechnung 4.0 is a pre-release and not the active standard (xeinkauf.de).

XRechnung is the standard for invoices to federal authorities and, increasingly, states and municipalities — submitted via portals such as ZRE or OZG-RE or via PEPPOL. The German BR-DE rules tighten EN 16931: first of all BR-DE-15, the Leitweg-ID (BT-10), which every XRechnung must carry. In the ZUGFeRD vs XRechnung comparison this point counts among the practical differences, because it shapes the submission route.

XRechnung is also establishing itself as a second pillar in commercial traffic — for example in supply-chain scenarios that are fully digital anyway. High structure and automated processing favour pure XML; mixed communication and archiving favour ZUGFeRD. “Typically” is meant literally — it is not a legal restriction to B2B or B2G.

ZUGFeRD vs XRechnung: a decision checklist

  • Who receives the invoice? Commercial customers usually speak ZUGFeRD, authorities speak XRechnung — the first filter when weighing ZUGFeRD vs XRechnung.
  • How does booking work? Fully automated systems accept both; manual teams prefer the PDF in the ZUGFeRD vs XRechnung comparison.
  • Which rules apply? In the ZUGFeRD vs XRechnung comparison, BR-DE rules such as the Leitweg-ID apply only to XRechnung.
  • What does your software send? Many systems can send both — check the setting per customer when weighing ZUGFeRD vs XRechnung.
  • How do you archive? ZUGFeRD files double as PDF/A archives; XRechnung needs a separate archiving strategy.

ZUGFeRD vs XRechnung: combining both in practice

Mastering both formats

In practice many companies master both sides of the ZUGFeRD vs XRechnung pair: ZUGFeRD for the broad customer base, XRechnung for authorities and structured partners. Since both build on EN 16931, the data comes from the same source — only the packaging differs. The ZUGFeRD vs XRechnung question therefore rarely ends in either-or; it ends in both-and.

Check instead of guess

The fastest way to identify received files in the ZUGFeRD vs XRechnung pair is validation: the ZUGFeRD validator finds the embedded XML in the PDF; the XRechnung validator checks XML files against schema, EN 16931 and BR-DE rules. The viewer renders XRechnungen readably — also useful for cross-reading ZUGFeRD XML.

FAQ

ZUGFeRD vs XRechnung — which is better?

It depends on the recipient: for many commercial customers ZUGFeRD is typical (PDF plus XML); for federal authorities XRechnung is the standard. Both build on EN 16931 — weighing ZUGFeRD vs XRechnung, you win by mastering both, and most teams settle the ZUGFeRD vs XRechnung question per recipient rather than per company.

Can one file be both?

No, they are separate files: ZUGFeRD is a PDF with embedded XML, XRechnung a pure XML file. The content is largely identical, though, because both build on EN 16931 — and the same tool set here covers both sides of the ZUGFeRD vs XRechnung pair, from the validator to the viewer.

What is the Leitweg-ID?

The Leitweg-ID (BT-10, rule BR-DE-15) identifies the invoice recipient in XRechnung — for authorities it is mandatory and assigned by the recipient. In the ZUGFeRD vs XRechnung picture, B2B ZUGFeRD invoices generally do not need it.

In the ZUGFeRD vs XRechnung comparison, must authorities accept ZUGFeRD?

Federal authorities generally require XRechnung (via ZRE/OZG-RE or PEPPOL). Whether a specific authority additionally accepts ZUGFeRD varies case by case — the reliable route is XRechnung.

Which versions are current?

ZUGFeRD 2.5.2 (FeRD, 2026-08-04) and XRechnung 3.0.2 with technical bundle 2026-08-31 (KoSIT validator 1.6.3). XRechnung 4.0 exists as a pre-release and is not active.

Weighing ZUGFeRD vs XRechnung: is ZUGFeRD allowed for B2G?

For federal authorities the XRechnung standard applies; in the ZUGFeRD vs XRechnung picture, ZUGFeRD is generally not the intended route there. At state and municipal level it can differ — when in doubt, ask the recipient.

Where should I start in the ZUGFeRD vs XRechnung comparison?

Start with the recipient you invoice most: a commercial customer means start with ZUGFeRD; an authority means start with XRechnung. Then add the second side — in the ZUGFeRD vs XRechnung comparison the second step is usually the smaller one, because the underlying data is identical, which is why the ZUGFeRD vs XRechnung decision rarely blocks anyone for long. The tools on this site are free; the effort lies in process adaptation, which modern accounting systems usually already include.

This site provides technical information and does not constitute tax or legal advice. Version status: ZUGFeRD 2.5.2, XRechnung 3.0.2 — as of 2026-09-29.