Guide · 2026-05-16
Markdown exportPDF/A-3 and ZUGFeRD archive readiness
ZUGFeRD combines a PDF/A-3 container with embedded CII XML. The XML can be valid while the source PDF still fails archive checks.
What you may see
- The XML validates, but a receiver or external portal reports PDF/A-3 or archive-readiness errors.
- The app marks the original PDF as not strictly archive-ready.
- A PDF exported as PDF/X still fails a PDF/A-3 check.
Why this matters
ZUGFeRD and Factur-X are hybrid files: the structured invoice is embedded in a PDF/A-3 document. PDF/X is a print standard and does not prove PDF/A-3 archive conformance.
How to fix it
- Export the source document as PDF/A-3b or PDF/A-3 from the authoring tool, for example InDesign or Acrobat.
- Upload the PDF/A-3 source again and run review validation before downloading the hybrid file.
- Validate both layers: the embedded XML and the PDF container.
Before you retry
- Check that the source PDF was re-exported, not only renamed.
- Keep the archive-readiness note as information unless your recipient explicitly requires strict PDF/A-3 acceptance.
- If a portal reports image or font dictionary errors, fix the source PDF export settings first.
Common question
Is PDF/X enough for ZUGFeRD?
No. PDF/X is for print exchange. ZUGFeRD and Factur-X require a PDF/A-3-style hybrid container.
Related articles
Understand ZUGFeRD BT fields, profile matrix (MINIMUM, BASIC, EN 16931, EXTENDED), field mappings, and compliance checks for EU e-invoicing.
ZUGFeRD validators: what to test before you send a hybrid invoiceA practical 2026 guide to validating ZUGFeRD and Factur-X invoices: XML rules, PDF/A-3 checks, profile fit, common failures, and which validator types to
PDF/A-3 Technical Guide: Embedding ZUGFeRD & Factur-X XML for ComplianceTechnical deep-dive into PDF/A-3 (ISO 19005-3) attachment structures: XMP metadata schema, /AF array relationships, font subsetting, and veraPDF validation.