ZUGFeRD format — the technical structure explained
The ZUGFeRD format combines a PDF/A-3 container with embedded CII XML per EN 16931. This page explains the building blocks of the ZUGFeRD format — from file structure to profiles to the Factur-X relationship — for everyone who wants to know exactly what is inside a ZUGFeRD file.
File anatomy: PDF/A-3 └── embedded factur-x.xml (CII, EN 16931 profile) — linked as an Associated File (AF) and registered in the /EmbeddedFiles name tree.
The ZUGFeRD format is a hybrid: one document, two views. Open the file with a PDF viewer and you see an ordinary invoice. Open it with an accounting system and it reads the embedded XML with all invoice data. Formally, a ZUGFeRD file is a PDF/A-3 archival document carrying the XML structure as an associated embedded file.
Three specifications carry the ZUGFeRD format — the container, syntax and semantics of the ZUGFeRD format: ISO 19005-3 (PDF/A-3) governs the container including embedding and metadata; the UN/CEFACT CII data model (CrossIndustryInvoice, D16B) defines the XML syntax; the European standard EN 16931 defines the semantic invoice data and business rules. ZUGFeRD itself is the German application document that ties the three together.
PDF/A-3: the container of the ZUGFeRD format
PDF/A is the ISO-standardised archival flavour of PDF. Only level PDF/A-3 allows embedding arbitrary files — which is why it is the basis of the ZUGFeRD format. A conformant document carries, among other things, an XMP metadata package (marked pdfaid:part 3), embedded fonts, an OutputIntent with an ICC profile and the proper association of the embedded XML via the AF relationship.
In practice this means: a file that merely contains “some” XML is not yet the ZUGFeRD format. The association and the metadata make the difference — and exactly those markers are what the validator checks (explicitly as a structural check, not full archival conformance at veraPDF level).
The embedded XML: the CII data model in detail
The structured layer of the ZUGFeRD format is a CrossIndustryInvoice per UN/CEFACT CII — this layer carries the actual value of the ZUGFeRD format. Key building blocks: ExchangedDocumentContext carries the guideline ID — the URN identifying profile and version (e.g. urn:cen.eu:en16931:2017 for the EN 16931 profile). ExchangedDocument holds header data such as invoice number (BT-1) and date (BT-2).
SupplyChainTradeTransaction bundles the rest: the line items (IncludedSupplyChainTradeLineItem) with product, quantity, price and tax rate; ApplicableHeaderTradeAgreement with seller, buyer and Leitweg-ID; ApplicableHeaderTradeSettlement with currency, VAT breakdown, payment data and the totals. To truly understand a ZUGFeRD file, open the XML in the viewer on our XRechnung page — the same CII syntax is rendered readably there.
The profiles of the ZUGFeRD format
Profiles tier how much structure a ZUGFeRD file must carry at minimum. For the common German B2B case, EN 16931 has prevailed — it contains all fields of the European standard and is fully processed by accounting systems. The tools on this site create and check exclusively the EN 16931 profile: one clear path without half-finished variants.
Profile
Line-item data
Typical use
MINIMUM
no
core data, close to an OCR substitute
BASIC WL
no
document level without line items
BASIC
yes
simple B2B exchange
EN 16931
yes
standard profile, all mandatory fields (most common)
EXTENDED
yes
extra data beyond the standard
The ZUGFeRD format, Factur-X and the versions
Factur-X: the French twin format
ZUGFeRD 2.x and Factur-X are the same specification: PDF/A-3 plus CII XML, the same profiles, the same URNs agreed for both countries. A ZUGFeRD file of version 2.x is simultaneously a Factur-X file — tools that read one read the other.
Version status: ZUGFeRD 2.5.2
The current release is ZUGFeRD 2.5.2, published by FeRD on 2026-08-04 (as of 2026-09-29). The 2.x series has applied since 2019 and replaced the non-EN-16931-based 1.x series. In daily practice versions 2.0 to 2.5 coexist — interoperable, because the core structure stayed stable.
The ZUGFeRD format in practice: recognise and process
Detect: check for an embedded factur-x.xml and profile URN — via the validator in seconds.
Read: a viewer or accounting system renders the XML as an invoice.
Create: the generator produces EN 16931 files with embedded fonts and an ICC profile.
Convert: move existing PDF invoices into the ZUGFeRD format via review.
Archive: PDF/A-3 doubles as an archival format — GoBD-compliant archiving remains your accounting’s topic.
FAQ
What is the ZUGFeRD format?
The ZUGFeRD format is a PDF/A-3 with embedded structured XML (UN/CEFACT CII) following the semantic rules of EN 16931 — one file for humans and machines, and that is what makes the ZUGFeRD format work everywhere.
Which XML is inside a ZUGFeRD file?
A CrossIndustryInvoice per UN/CEFACT CII (D16B). It carries all invoice data from the Leitweg-ID to the VAT breakdown and identifies profile and version via the guideline ID.
Why does the ZUGFeRD format use PDF/A-3, not PDF/A-2?
Only PDF/A-3 allows embedding arbitrary files. PDF/A-2 offers no embedding — the XML could not live inside the document conformantly.
What is the difference between ZUGFeRD and Factur-X?
None technically: ZUGFeRD 2.x and Factur-X are identically specified and mutually readable. The name only differs by origin (Germany/France).
Which file extension does a ZUGFeRD format file have?
Usually .pdf — the embedded XML is mostly named factur-x.xml. The extension alone says nothing about conformance; only inspecting the file is reliable.
Can I produce the ZUGFeRD format myself?
Yes. The generator on this site produces the ZUGFeRD format in the EN 16931 profile — PDF/A-3 container, embedded CII XML, embedded fonts and ICC profile included. To check the ZUGFeRD format, use the validator; to understand it, read this page first. The format itself prescribes no upper bound; our tools cap uploads at 3.5 MB or 1 MB.
Is a ZUGFeRD format file archivable?
PDF/A-3 is designed for long-term archiving; the formal archival conformance of a specific file is checked by specialised tools such as veraPDF. Our check covers the structural markers and says so.
Sources and citations
„Since 1 January 2025 businesses must be able to receive e-invoices; simple PDF files no longer qualify as e-invoices in Germany.“
— Federal Ministry of Finance, e-invoicing FAQ (as of 2026-09-29)