Convert PDF to ZUGFeRD: when a hybrid invoice workflow fits

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

• A PDF/A-3 file with embedded XML that matches the selected ZUGFeRD 2.3.2 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.