Skip to main content
Convert PDF to ZUGFeRD: when a hybrid invoice workflow fits
Blog

Convert PDF to ZUGFeRD: when a hybrid invoice workflow fits

3 min readReviewed: July 14, 2026
Markdown export

Official references

Use these sources to verify dates, formats, and official rule changes.

This guide is for teams that still start from PDF invoices but need a hybrid e-invoice with both a human-readable document and structured XML.

ZUGFeRD remains useful in 2026 when the recipient process accepts a PDF/A-3 invoice with embedded structured data. The format combines a human-readable PDF with machine-readable XML for automated import, validation, archiving, and matching. The result still needs review before delivery.

When ZUGFeRD is the better choice than pure XML

Choose ZUGFeRD when the recipient workflow uses a readable PDF and also benefits from machine-readable invoice data for import or validation.

If the buyer or submission channel explicitly requires XRechnung, Peppol BIS Billing, or another XML exchange format, generate that target format directly. Do not assume that a ZUGFeRD PDF is accepted everywhere.

What a compliant ZUGFeRD output must contain

Interactive anatomy

One PDF/A-3 file, five layers. Click or tap a layer, or switch the profile, to see what each part holds and which check catches its errors.

ReviewveraPDFXSD + Schematron

Embedded profile

5XSD + Schematron
file
factur-x.xml
syntax
UN/CEFACT CII
BT-24
urn:cen.eu:en16931:2017

What it holds

The invoice data in UN/CEFACT CII syntax. Its specification identifier (BT-24) names the profile. Older files: zugferd-invoice.xml (ZUGFeRD 2.0), ZUGFeRD-invoice.xml (ZUGFeRD 1.0).

What goes wrong

Schema errors, broken business rules such as totals that do not add up, or a profile that differs from the XMP metadata.

What catches it

The XSD and Schematron of the selected profile. The XRECHNUNG profile must also pass the XRechnung rules of the KoSIT validator.

A ZUGFeRD or Factur-X invoice is one PDF/A-3 file (ISO 19005-3) with five parts: the visible invoice page; embedded fonts and an OutputIntent colour profile; XMP metadata with the PDF/A extension schema and the properties fx:DocumentType (INVOICE), fx:DocumentFileName, fx:Version and fx:ConformanceLevel; an /AF associated-file entry whose AFRelationship is Data for MINIMUM and BASIC WL and Data, Source or Alternative from BASIC up; and the embedded CII XML, named factur-x.xml, or xrechnung.xml in the XRECHNUNG profile. A PDF/A validator such as veraPDF checks the container, the profile’s XSD and Schematron check the XML, and only a review compares the visible page with the XML. Sources: ISO 19005-3 (PDF/A-3), FeRD / FNFE-MPE Factur-X and ZUGFeRD specifications, veraPDF. Status: October 2026.
  • A PDF/A-3 file with embedded XML that matches the selected ZUGFeRD 2.5 profile.
  • The same invoice identity, parties, line items, totals, VAT details, and payment information in the visual and XML layers, where applicable.
  • A profile that matches the recipient and use case, rather than simply the easiest profile to generate.
  • Validation of both the PDF container and the embedded XML before the file is archived or delivered.

Recommended workflow from PDF to ZUGFeRD

  1. Upload the PDF and review the extracted parties, invoice dates, tax logic, and line items.
  2. Choose the right ZUGFeRD profile for the recipient and use case before generating the file.
  3. Generate the hybrid invoice and validate the PDF/A-3 container and XML against the expected profile rules.
  4. Review the visual PDF and the structured data together so mismatches are caught before delivery.
  5. Archive or send the file only after the team resolves profile, data, or validation exceptions.

Common failure points

  • Choosing a profile that does not cover the recipient workflow.
  • Assuming the PDF preview proves that the embedded XML is correct.
  • Omitting tax exemption reasons or payment information required by the selected profile.
  • Skipping validation because the hybrid invoice “looks fine” in a PDF viewer.

Frequently asked questions

Is ZUGFeRD better than XRechnung for every German invoice?

No. ZUGFeRD is useful when a readable PDF and embedded XML are both valuable. If the recipient or submission process requires XRechnung or another XML format, generate that format directly.

Do I still need to validate a ZUGFeRD file if the PDF looks correct?

Yes. A PDF that looks correct does not prove that the embedded XML or the PDF/A-3 container is valid. Validate both against the expected profile and business rules.

Can conversion remove the need for review?

No. Conversion accelerates data capture, but profile choice, tax edge cases, low-quality PDFs, and validation failures still require human review.

Ready to convert your invoices?

Convert PDF invoices to XRechnung, ZUGFeRD, and other formats. Subscriptions from €10/month with annual billing (excl. taxes), with a 3-day trial on your first subscription. Or without a subscription: €5 per conversion (excl. taxes).

Try it free without an account, up to 6 PDF pages per conversion, attachments included. Only the download costs: it needs an account and one credit or a subscription.

Related articles