# PDF/A-3 Technical Guide: Embedding ZUGFeRD & Factur-X XML for Compliance

- Date: 2026-07-03
- Reviewed: July 9, 2026
- Reading time: 9 min read

Technical deep-dive into PDF/A-3 (ISO 19005-3) attachment structures: XMP metadata schema, /AF array relationships, font subsetting, and veraPDF validation.

> Reviewed against FeRD ZUGFeRD, FNFE-MPE Factur-X.

## Article overview

        This article explains PDF/A-3 Technical Guide: Embedding ZUGFeRD & Factur-X XML for Compliance as a practical reference for European e-invoicing. It defines the topic in plain language, places it in the compliance context, and connects the explanation to invoice formats such as XRechnung, ZUGFeRD/Factur-X, UBL, and CII.

Hybrid e-invoices such as ZUGFeRD and Factur-X use a PDF/A-3 file (ISO 19005-3) as the visual document and embed the structured invoice XML alongside it.

For software engineers, PDF-library developers, and validation teams, producing a conforming file means getting the PDF/A rules, associated-file metadata, XMP extension schema, and font and color requirements right.

        ## How to use this guide

        Use the article as a starting point before changing a finance or ERP workflow: identify the applicable country rule or standard, decide which structured format is expected, validate the generated XML, and keep a documented exception process for invoices that require manual review.

## Core Architecture: How PDF/A-3 Differs from PDF/A-2

For Core Architecture: How PDF/A-3 Differs from PDF/A-2, review these points before moving on.

- File attachments: PDF/A-2 permits embedded files only under its more limited rules. PDF/A-3 permits associated files of arbitrary formats, including XML, when the required PDF/A metadata is present.
- Associated Files (`/AF`): The document Catalog, or an individual Page when appropriate, can carry an `/AF` array that points to file-specification dictionaries and their embedded-file streams.
- AFRelationship: Each associated file must declare an `/AFRelationship` value, such as `/Alternative` or `/Data`, describing how it relates to the PDF representation.
- Attachment name: Factur-X and current ZUGFeRD specifications use `factur-x.xml` for the embedded invoice XML. Do not substitute a different name without checking the exact profile and version specification.
## XMP Metadata Extension Schema Requirements

PDF/A-3 validators such as veraPDF inspect the XMP metadata packet referenced by the document Catalog. A Factur-X or ZUGFeRD file must declare the format namespace through the PDF/A extension schema, using the namespace and property definitions from the applicable release.

The invoice extension properties include DocumentFileName (`factur-x.xml`), DocumentType (`INVOICE`), Version, and ConformanceLevel. The allowed profile values depend on the specification version, so use the exact release values rather than assuming that every version has the same list.

## Font Subsetting & Color Space Rules

For Font Subsetting & Color Space Rules, this sequence gives the practical order of work.

- Font embedding: Every font used by the visual document must be embedded. Subsetting is allowed when the resulting font program and character mappings remain valid.
- Color profile (OutputIntent): A PDF/A-3 file must provide an OutputIntent with an ICC profile suitable for the document, such as sRGB IEC61966-2.1, so rendering is reproducible across systems.
- Validation tools: Run veraPDF and, for the invoice profile, the Mustangproject validator before release. They check different layers of conformance and semantic invoice rules.
## Official Technical References

For Official Technical References, review these points before moving on.

- [ISO 19005-3:2012 Specification (PDF/A-3)](https://www.iso.org/standard/55816.html)
- [FeRD / FNFE-MPE - Factur-X / ZUGFeRD Technical Documentation](https://www.ferd-net.de)
- [veraPDF Open Source PDF/A Validator](https://verapdf.org)
## Ready to convert your invoices?

Start converting PDF invoices to XRechnung, ZUGFeRD, and other formats today.

[View Pricing](/en/convert)

## FAQ

### What happens if the XMP metadata namespace is missing?

The file may still open, but a validator will report a conformance error. An attached XML file alone is not enough: the PDF/A extension schema and the Factur-X or ZUGFeRD properties must also match the applicable specification version.

## Official references

- [FeRD ZUGFeRD 2.x](https://www.ferd-net.de/publikationen-produkte/publikationen/detailseite/zugferd-25-english)
- [FNFE-MPE Factur-X resources](https://fnfe-mpe.org/factur-x/)