In short

ZUGFeRD 2.5.2 = Factur-X 1.09.2 (4 August 2026). A PDF/A-3 that people read, with CII XML that software reads; if the two differ, the XML counts. In Germany, ZUGFeRD from version 2.0.1 is an accepted e-invoice in every profile except MINIMUM and BASIC WL.

How ZUGFeRD works

A ZUGFeRD invoice is one PDF/A-3 file with two layers. The visible PDF is a normal invoice that any PDF reader shows. Embedded in it is an XML file, usually named factur-x.xml, that holds the same invoice as structured data in CII syntax, following the EN 16931 data model.

The XML is the invoice

For German VAT purposes the structured part leads. The Finance Ministry’s letter of 15 October 2025 says that in a hybrid invoice, where the XML and the picture differ, the XML data take precedence. A total that is right in the PDF and wrong in the XML is a wrong invoice.

Why PDF/A-3

PDF/A is the archival form of PDF: fonts and colour profiles are embedded, so the file looks the same years later. PDF/A-1 and PDF/A-2 do not allow arbitrary file attachments; PDF/A-3 does, which is what lets the XML travel inside the PDF.

Making one

  1. Render the PDF as PDF/A-3: embedded fonts, an output colour profile, no encryption or JavaScript.
  2. Write the CII XML in the profile you need (see the table below).
  3. Embed the XML as an associated file and declare the profile in the PDF’s XMP metadata.
  4. Check the XML against the EN 16931 rules before sending. Check a ZUGFeRD invoice

Why ZUGFeRD matters

Profiles

A profile fixes how much data the XML carries. Whether it counts as an invoice in Germany follows from the BMF letter of 15 October 2025, which excludes MINIMUM and BASIC WL.

ProfileWhat it carriesE-invoice in Germany
MINIMUMHeader data only, roughly what an OCR header capture givesNo
BASIC WLDocument-level data, no invoice linesNo
BASICBASIC WL plus the core line dataYes
EN 16931 (formerly COMFORT)All information of EN 16931Yes
EXTENDEDEN 16931 plus additional data for complex casesYes
XRECHNUNG (reference profile)EN 16931 data under the German XRechnung rulesYes; the ZUGFeRD profile documented for federal authorities
EXTENDED-CTC-FR (reference profile)A subset of EXTENDED for the French e-invoicing reformUsed in France

Which profile to use

  • German B2B: EN 16931 is the safe default. BASIC is also accepted; MINIMUM and BASIC WL are not.
  • German federal authorities: the XRECHNUNG profile, accepted by the federal platform since 1 March 2022 and sent to OZG-RE as its XML file.
  • France: the same file is a Factur-X; see Factur-X for the French rules.

What changed in ZUGFeRD 2.5

  • 2.5 / Factur-X 1.09 (10 June 2026): code lists and validation artefacts follow the current EN 16931 code-list release; EXTENDED gets new elements from the revised data model of EN 16931-1:2026. FNFE-MPE names sub-line management (subtotals, kits, bundles) as the main addition and says the release also reflects the preparation of the French reform and fiscal points from the BMF letter of 15 October 2025.
  • 2.5.2 / Factur-X 1.09.2 (4 August 2026): a corrigendum that mainly fixes inconsistencies in the new EXTENDED functionality.
  • Next: FeRD expects a further release in autumn 2026 and aims to publish close to each half-yearly EN 16931 code-list update. As of 3 November 2026, 2.5.2 is still the current version.

For senders on BASIC or EN 16931, 2.5 brings updated code lists, not a new structure; Germany accepts every ZUGFeRD version from 2.0.1, so an older 2.x file is still a valid e-invoice. For receivers, EXTENDED files from 2.5 onwards can carry the new elements, such as sub-lines, which your import has to read or reject explicitly.

The German mandate

DateWhat applies
1 January 2025Every business must be able to receive e-invoices.
Until 31 December 2026Paper, or another electronic format if the recipient agrees, is still allowed for sending.
1 January 2027Businesses with prior-year total turnover above €800,000 must issue e-invoices.
1 January 2028Everyone issues e-invoices for domestic B2B supplies (EDI with consent until 31 December 2027).

Invoices up to €250, tickets and Kleinunternehmer invoices are exempt. Full timeline: Germany e-invoicing guide.

ERP-specific setup:

Common errors

Rejections we see most often on ZUGFeRD files:

No usable XML in the PDF. The PDF has no embedded invoice XML, or a different file than the invoice. Then there is no e-invoice at all, however good the PDF looks.

BR-CO-10: the total of line net amounts (BT-106) does not equal the sum of the individual line net amounts (BT-131). Usually rounding per line in one place and on the total in another.

BR-CO-15: total with VAT (BT-112) is not total without VAT (BT-109) plus the VAT total (BT-110).

BR-CO-17: a VAT category’s tax amount is not its taxable amount times the rate, rounded to two decimals.

BR-DE-15: in the XRECHNUNG profile, the buyer reference (BT-10) is missing. For public buyers that is the Leitweg-ID.

BR-DE-7: in the XRECHNUNG profile, the seller contact e-mail (BT-43) is missing.

Profile mismatch. The XML declares one profile and the PDF metadata another, or the data do not fit the declared profile.

All validation errors

Comparisons

ZUGFeRD vs XRechnung: ZUGFeRD is PDF plus XML, XRechnung is XML only. Both are accepted for German B2B. For federal authorities, the federal e-invoicing platform documents ZUGFeRD in the XRECHNUNG profile. Compare in detail

ZUGFeRD vs Factur-X: one specification, two names. ZUGFeRD 2.5.2 and Factur-X 1.09.2 are technically identical.

ZUGFeRD vs UBL: ZUGFeRD always uses CII. UBL is the other EN 16931 syntax, used by Peppol. Both express the same data model, so data can be mapped between them. Compare UBL and CII

ZUGFeRD vs Peppol BIS: Peppol BIS Billing is a UBL format sent over the Peppol network; ZUGFeRD is a file, usually sent by e-mail or portal upload.

How to get started

Step 1: Pick the profile

EN 16931 for business customers in Germany and abroad; XRECHNUNG for German federal authorities.

Step 2: Produce a real PDF/A-3

Embedded fonts, an output colour profile, no encryption. A PDF that looks fine is not necessarily PDF/A-3.

Step 3: Embed and check the XML

Embed the CII XML, declare the profile in the XMP metadata, then check the XML against the EN 16931 rules (and the BR-DE rules for the XRECHNUNG profile).

Check a ZUGFeRD invoice · API documentation

Sources

Facts checked against these sources on 3 November 2026.

Further reading

Questions

What is the current ZUGFeRD version?
ZUGFeRD 2.5.2, published on 4 August 2026 together with the identical Factur-X 1.09.2. It corrects ZUGFeRD 2.5 of 10 June 2026. FeRD expects the next release in autumn 2026.
Is ZUGFeRD the same as Factur-X?
Yes. FeRD and FNFE-MPE publish one specification: ZUGFeRD 2.5.2 and Factur-X 1.09.2 are technically identical. ZUGFeRD is the German name, Factur-X the French.
Is ZUGFeRD accepted for the German B2B mandate?
Yes, from version 2.0.1 and in every profile except MINIMUM and BASIC WL (BMF letter of 15 October 2025). Receiving e-invoices is required since 1 January 2025; issuing them from 1 January 2027 for businesses with prior-year turnover above €800,000 and from 1 January 2028 for all.
Which ZUGFeRD profile should I use?
EN 16931 for most business invoices. XRECHNUNG for German federal authorities. Avoid MINIMUM and BASIC WL: they do not count as an invoice in Germany.
What changed in ZUGFeRD 2.5?
Code lists and validation artefacts follow the current EN 16931 release, and EXTENDED gained new elements from EN 16931-1:2026; FNFE-MPE names sub-lines for subtotals, kits and bundles as the main addition. 2.5.2 fixes inconsistencies in that new EXTENDED functionality.
If the PDF and the XML differ, which one counts?
The XML. Under the BMF letter of 15 October 2025, the structured data of a hybrid invoice take precedence over the picture.
Can I open a ZUGFeRD invoice in a normal PDF reader?
Yes. It is a normal PDF; the reader shows the invoice and lists the XML as an attachment. Accounting software reads the XML.
Can I convert a regular PDF to ZUGFeRD?
Only by creating the XML from the invoice data and embedding it in a PDF/A-3. A PDF without that XML is not an e-invoice, however it looks. Our converter creates the XML from a PDF invoice and embeds it.