What it means
PDF/A-3 permits embedding files inside an archival PDF. Hybrid invoice standards use this to combine a readable PDF with structured XML.
The PDF and XML relationship, profile metadata and embedded filename matter; simply attaching XML to a PDF is not sufficient.
Implementation method
- 1Generate the structured invoice from canonical business data.
- 2Render a readable PDF from the same values.
- 3Embed XML with the correct relationship and metadata.
- 4Validate PDF/A conformance and the embedded invoice profile separately.
Common mistakes
Build an explicit control or test case for this condition.
Build an explicit control or test case for this condition.
Build an explicit control or test case for this condition.
Build an explicit control or test case for this condition.
Questions and answers
Which file is authoritative?
The applicable profile and legal context determine precedence; implementations should keep both synchronized and preserve the original hybrid file.
Can a browser fully validate PDF/A-3?
Not reliably without a dedicated conformance engine and complete embedded-file processing.
Can EInvoiceLab officially certify PDF/A-3 hybrid invoices?
No. EInvoiceLab can inspect, prepare and explain technical data, but official conformance, delivery or acceptance depends on the active authority, network, accredited provider and validation artefacts.
Should I keep the original structured file?
Yes. Preserve the original XML or JSON, its hash, every validation report and the final authority or network response. A readable PDF should not replace the source document.