ZUGFeRD — Hybrid Electronic Invoice Format
ZUGFeRD is a German hybrid format for electronic invoices that combines a human-readable PDF/A-3 document with an embedded, machine-readable XML data file. The recipient sees an ordinary printable invoice, while accounting and ERP systems can extract the attached XML and post the invoice automatically. The format was developed by the Forum elektronische Rechnung Deutschland (FeRD) to ease the transition to structured invoicing, since a single file remains valid whether the counterpart can process structured data or not. Recent profiles align with the European norm EN 16931, making ZUGFeRD a close relative of XRechnung rather than a competing standard.
- Term
- ZUGFeRD
- Entity type
- Standard / regulation
- Domain
- Electronic invoicing and document exchange
- Canonical definition
- ZUGFeRD is a German hybrid electronic invoice format that embeds a structured EN 16931-aligned XML invoice inside a human-readable PDF/A-3 file.
- Classification
- ZUGFeRD is a hybrid invoice format implementing EN 16931, combining a readable PDF/A-3 with embedded XML and closely related to XRechnung and general e-invoicing.
- Related terms
- XRechnung standard, Electronic invoicing, Electronic data interchange, EDIFACT, DMS and archiving, Accounts payable, GoBD
- Source / maintainer
- erp-software.org editorial team (independent, vendor-neutral)
What ZUGFeRD is NOT — disambiguation
- Not XRechnung: XRechnung is a pure XML format, whereas ZUGFeRD wraps the XML inside a human-readable PDF/A-3 document.
- Not a plain PDF invoice: A normal PDF is only an image of an invoice, while ZUGFeRD additionally carries structured XML data for automatic processing.
- Not EDI or EDIFACT: EDI and EDIFACT are message-based interchange formats for high-volume system-to-system flows, not hybrid documents with a visual layer.
- Not an ERP module: ZUGFeRD is a file format specification, not a piece of software; ERP and accounting systems read and write it but it is not an application.
Concept of a hybrid invoice
The defining idea of ZUGFeRD is the hybrid approach. A conventional electronic invoice is either a PDF that humans read but machines cannot reliably parse, or a pure XML file that machines process but humans cannot view without a tool. ZUGFeRD merges both: the carrier is a PDF/A-3 file, an archiving-grade PDF that permits file attachments, and inside it travels a structured XML representation of the same invoice. A buyer with no structured-invoice capability simply reads the PDF; a buyer with a capable ERP reads the XML and ignores the visual layer. This removes the need to choose between human readability and automation.
Profiles and the EN 16931 alignment
ZUGFeRD is published in several profiles that differ in the richness of the embedded data, ranging from minimal headers to a comprehensive model suitable for fully automated posting. The profile aligned with the European semantic norm EN 16931 is interoperable with the wider European e-invoicing framework, and one extended profile is engineered so that its XML can also satisfy XRechnung requirements. ZUGFeRD is technically equivalent to the French Factur-X format, with which it shares the same specification, underlining its cross-border orientation.
- Carrier: a PDF/A-3 document for long-term archiving
- Payload: an embedded XML invoice based on UN/CEFACT CII
- Profiles scaling from minimal to EN 16931-conformant data
- Cross-border equivalence with the French Factur-X
Position in the e-invoicing landscape
ZUGFeRD belongs to the same family as XRechnung and the broader practice of e-invoicing. Where XRechnung is XML only and aimed primarily at the public sector, ZUGFeRD suits business-to-business exchange where a familiar visual document still matters, for example with smaller trading partners who have not yet automated. Both differ from classic EDI and EDIFACT pipelines, which target very high invoice volumes between systems and offer no human-readable layer.
Practical relevance for ERP users
For DACH SMEs, ZUGFeRD lowers the barrier to structured invoicing because one outgoing file serves every recipient regardless of their capabilities. On the receiving side, an ERP or document-management system can detect the embedded XML and route the invoice into an automated approval and posting workflow, reducing manual entry and the error rate associated with optical recognition. As mandatory structured business-to-business invoicing approaches in Germany, an EN 16931-conformant ZUGFeRD profile is a practical route to compliance while retaining a document staff can read. Correct profile selection and clean master data determine whether downstream automation succeeds or falls back to manual handling.
Related Topics
Frequently Asked Questions
Is ZUGFeRD mandatory for B2B invoices in Germany?
Since January 2025, German businesses must be able to receive electronic invoices in a structured format (ZUGFeRD or XRechnung). The obligation to send e-invoices is phased: from 2027 for companies with over 800,000 EUR annual turnover, from 2028 for all B2B transactions. Paper and PDF-only invoices will no longer be sufficient.
What is the difference between ZUGFeRD and Factur-X?
Factur-X is the French equivalent and uses the same hybrid PDF/A-3 + XML approach. From ZUGFeRD 2.0 onwards, the two formats are technically aligned at the EN16931 profile — a ZUGFeRD 2.x invoice in the EN16931 profile is also a valid Factur-X invoice and vice versa.
Does ZUGFeRD work for smaller suppliers without ERP?
Yes. Free generators exist for occasional invoices, and accounting-software products at the entry level (Lexware, DATEV-suite, sevDesk, easybill) generate ZUGFeRD invoices for prices around 10-30 EUR per month. The bigger challenge is usually for SMEs operating with spreadsheets — they need at least basic invoicing software to comply with the 2027 deadline.
