InvoiceConvertor

Home / Guides / Hybrid E-Invoices vs. Structured XML: Choosing a Format

Technical & Standards

Hybrid E-Invoices vs. Structured XML: Choosing a Format

FeRD lists ZUGFeRD 2.5.2 / Factur-X 1.09.2 as effective from 1 September 2026, based on CII D22B. The selected profile still determines required data and validation; the version name alone does not establish that an invoice is compliant.

Hybrid and pure XML formats

A hybrid e-invoice pairs a human-readable representation with machine-readable invoice data. Factur-X/ZUGFeRD uses a PDF/A-3 document with embedded XML, so the recipient can view the PDF and software can process the XML. A pure XML invoice such as XRechnung has structured data but normally needs a viewer for people to read it.

Hybrid does not automatically mean compliant. The XML must follow the selected profile, and the visible PDF and structured data must agree. PDF/A-3 conformance, embedded-file association and invoice business-rule validation are separate checks. A recipient may require a particular profile or accept only specific formats.

Choose by recipient workflow

InvoiceConvertor can make a visual PDF draft with an attached CII XML draft. It does not verify PDF/A-3, test a current Factur-X/ZUGFeRD profile, or ensure the PDF/XML match under every rule.

Official sources

Frequently asked questions

Does embedding XML in a PDF make it a valid hybrid e-invoice?

Not by itself. The embedded XML, profile, PDF/A rules, association metadata and recipient requirements all matter.

Is pure XML harder for people to read?

It is structured for software; users can view it with an invoice viewer, but a rendered view is not a replacement for validation.