ZUGFeRD is a German hybrid e-invoice standard that embeds a structured XML data set inside a standard, human-readable PDF, letting one file serve as both a printable document and machine-readable data. Unlike XRechnung's XML-only format, ZUGFeRD works for B2B and B2C invoicing where recipients may lack automated intake, while still enabling straight-through data extraction for accounts payable and receivable systems.
ZUGFeRD (Zentraler User Guide des Forums elektronische Rechnung Deutschland) is a hybrid electronic invoice format developed by the German Forum elektronische Rechnung Deutschland. A ZUGFeRD file is a normal PDF/A-3 document that also carries an embedded XML attachment containing the same invoice data in structured form. The PDF layer can be opened and read by any person; the XML layer can be parsed directly by accounting, ERP, or accounts payable software without any manual re-entry.
Since version 2.1, the XML content follows the Cross Industry Invoice (CII) syntax and is aligned with EN 16931, the European semantic standard for electronic invoicing, which is the same underlying standard behind XRechnung.
XRechnung is an XML-only invoice format, with no visual PDF layer at all, and it is the mandated format for invoices billed to German federal public-sector entities. ZUGFeRD, by contrast, is a hybrid: the PDF remains the primary, human-readable artifact, with the XML riding along inside it. This makes ZUGFeRD better suited to everyday B2B and B2C invoicing, where the recipient may not have automated ingestion in place and still needs something they can open and read.
Since ZUGFeRD 2.1, the format includes an XRechnung profile: the embedded XML can be generated so it conforms to the XRechnung specification, while the file still keeps its PDF wrapper. This gives issuers a bridge between the two standards, though most public-sector portals still expect a pure XRechnung XML submission rather than the hybrid file.
ZUGFeRD defines several conformance profiles, each carrying a different level of structured detail:
Technically, this works because PDF/A-3, unlike earlier PDF/A versions, permits arbitrary file attachments inside the document. The XML is embedded as one of these attachments, so any PDF/A-3 compliant viewer displays the invoice normally while any system that knows to look can extract the XML separately.
ZUGFeRD is often framed as an accounts payable and compliance topic, but it has direct consequences for the receivables side too. When an AR team issues invoices in ZUGFeRD, customers receive unambiguous, structured line items, amounts, and tax detail alongside the familiar PDF, which reduces the manual keying and interpretation errors that slow down invoice approval on the buyer's side. Faster, cleaner approval cycles translate into faster payment, which supports DSO targets.
The same structure helps on the incoming side. Customer payments frequently arrive with a remittance advice that references invoice numbers, amounts, and short-pay reasons. When that remittance data traces back to a ZUGFeRD invoice with clean, structured references, cash application matching logic has far less ambiguity to resolve, and fewer payments fall into an unmatched or manual review queue.
Structured invoice data also reduces the volume and ambiguity of deductions: when tax, quantity, and pricing fields are machine-readable rather than embedded only in a PDF layout, disputes over what was actually billed are easier to resolve, and dunning communications can reference the exact structured invoice data rather than a scanned image.
Because the XML is already structured, an AI-native receivables platform does not need to OCR a ZUGFeRD invoice the way it would a flat scanned PDF. Instead, it can extract the embedded XML directly, pulling invoice number, amounts, tax lines, and party details with high confidence and no interpretation guesswork. Transformance's DocSense handles this extraction automatically, and that clean data feeds straight into ClearMatch's matching logic for cash application, so a well-formed ZUGFeRD file moves through intake and matching with minimal manual touch. When a file is malformed, missing its XML attachment, or from a trading partner not yet using the standard, the platform falls back to AI-based document extraction on the PDF layer itself, so the process degrades gracefully rather than stalling.
Not universally. XRechnung is mandated for invoices to federal public-sector entities, while ZUGFeRD is voluntary and widely used for B2B and B2C invoicing. Businesses billing government entities can use ZUGFeRD's XRechnung profile to satisfy that mandate while keeping a PDF wrapper.
A PDF/A-3 file with an embedded XML attachment. The PDF opens normally in any viewer, while accounting or AR software extracts the XML separately for automated processing.
It depends on the trading partner. Basic or Comfort suits typical B2B invoicing, Extended fits complex line-item detail, and the XRechnung profile applies when the recipient is a public-sector entity.
No. That is the point of the hybrid design: it keeps the familiar PDF for people while adding structured XML for systems, unlike XRechnung, which has no visual layer at all.
Structured invoice data reduces processing delays and disputes on the customer's side, which can shorten the time between invoice issuance and payment.
Yes. Modern e-invoicing and cash application platforms parse the embedded XML directly. Transformance's DocSense extracts this data without relying on OCR.
