ZUGFeRD validators: what to test before you send a hybrid invoice

What a validator should actually check

For What a validator should actually check, review these points before moving on.

• The embedded XML is present and can be read correctly from the PDF container.
• The invoice data complies with EN 16931 and the selected ZUGFeRD or Factur-X profile.
• Monetary totals, VAT breakdowns, units, and dates are internally consistent.
• The PDF file itself meets the expected PDF/A-3 constraints for a hybrid invoice workflow.

Use more than one kind of validation

A strong workflow usually combines at least two layers. First, validate the business content and XML rules. Second, check the PDF/A-3 container and embedded-file packaging. If a recipient channel applies its own checks, treat that as a third gate rather than your only test.

A practical combination is a ZUGFeRD-aware invoice validator for the XML and business rules, plus a PDF/A validator such as veraPDF for the document container.

Recommended validation workflow

For Recommended validation workflow, this sequence gives the practical order of work.

1. Generate the ZUGFeRD or Factur-X invoice from source data you have already reviewed.
2. Run a rule-based invoice validation against the target profile and EN 16931 expectations.
3. Run a PDF/A-3 check on the final document, not on a draft PDF without embedded XML.
4. Extract or inspect the embedded XML and compare key fields with the reviewed source invoice.
5. Only then send the document through email, portal, or PEPPOL depending on the recipient process.

Common failures and what they usually mean

For Common failures and what they usually mean, review these points before moving on.

• The PDF opens normally, but the XML is missing, malformed, or not attached as expected.
• The XML is valid enough to parse, but required business fields or profile identifiers are wrong.
• Line totals, taxable bases, and VAT amounts do not reconcile after extraction or mapping.
• The document looks right to a human reviewer but fails PDF/A-3 checks because the hybrid container is incomplete or non-compliant.

Official and primary references

For Official and primary references, review these points before moving on.

• FeRD package page for ZUGFeRD 2.5 / Factur-X 1.09.
• KoSIT validator configuration for EN 16931 and XRechnung rules.
• KoSIT support guidance for XRechnung-related validation context.
• veraPDF PDF/A validation project.

Validate the hybrid invoice before you trust the PDF view

Invoice-Converter.com helps teams generate ZUGFeRD from existing invoices, inspect extracted data, and validate the result before delivery. That reduces rejection risk while keeping human review in the loop.