Standard
ZUGFeRD
Definition
ZUGFeRD (Zentraler User Guide des Forums elektronische Rechnung Deutschland) is a hybrid invoice format that combines a human-readable PDF/A-3 file with embedded machine-readable XML data. The format is maintained by the Forum elektronische Rechnung Deutschland (FeRD) and exists in several profiles (MINIMUM, BASIC, EN 16931, EXTENDED). It is technically identical to the European Factur-X standard.
Background & context
ZUGFeRD is a hybrid format: the invoice exists as a PDF/A-3 file (human-readable) and at the same time contains an embedded XML file with the structured invoice data (machine-readable). The recipient can therefore view or print the document on screen as usual, while their software processes the XML data automatically. Since ZUGFeRD 2.0, the XML is based on UN/CEFACT CII and is identical to the French Factur-X. ZUGFeRD defines several profiles of increasing scope: MINIMUM and BASIC WL (not EN 16931-compliant, for internal purposes only), BASIC, EN 16931 (full compliance), and EXTENDED. For use towards public buyers or as a legally valid B2B e-invoice, at least the EN 16931 profile is required. The embedded XML file is named `factur-x.xml` by default (formerly `zugferd-invoice.xml`). ZUGFeRD is maintained by the Forum for Electronic Invoicing Germany (FeRD).
In practice — a worked example
A mechanical-engineering company sends a ZUGFeRD invoice in the EN 16931 profile by email to a B2B customer. The customer sees the familiar PDF layout; however, their invoice-receipt software automatically extracts the embedded `factur-x.xml`, reads out the invoice number, amounts and tax rates, and books the invoice without manual entry. Because the EN 16931 profile is used, the invoice is usable both in B2B and — with a correct Leitweg-ID — towards authorities. Important: where the PDF image and the XML data differ, the structured XML content is legally authoritative.
Common mistakes
- •The MINIMUM and BASIC WL profiles are NOT EN 16931-compliant and therefore valid neither as a B2G nor as a B2B e-invoice under the Growth Opportunities Act — they serve internal purposes only.
- •The PDF image and the XML data must match in content; if amounts differ, tax objections may arise because the XML is legally authoritative.
- •A plain PDF/A-1 or PDF/A-2 is not enough — only PDF/A-3 allows embedding the XML file that ZUGFeRD requires.
Frequently asked questions
Is ZUGFeRD a valid e-invoice in the legal sense?
Yes, provided the EN 16931 (or EXTENDED) profile is used, ZUGFeRD counts as a structured e-invoice under EN 16931 and is therefore permitted in B2B from 2025. The MINIMUM and BASIC WL profiles do not meet the requirements.
Can I send a ZUGFeRD invoice to a public authority?
In principle yes, if the EN 16931 profile is used and a valid Leitweg-ID is included. However, many authorities prefer XRechnung (pure XML). Check the requirements of the specific receiving portal (ZRE/OZG-RE).
How does ZUGFeRD differ from Factur-X?
Technically there is none: from ZUGFeRD 2.0 the two are identical. It is the same standard, marketed as ZUGFeRD in Germany and as Factur-X in France. The embedded XML file is named factur-x.xml in both cases.
What happens if the PDF and XML disagree?
The structured XML content is decisive. Accounting and audit systems process the XML data; discrepancies in the PDF image can lead to objections. Make sure your software generates both layers in sync.