errorsyntaxzugferd

ZUG-XMP-001:ZUGFeRD/Factur-X PDF Missing or Invalid XMP Metadata

Fix: Add the four required fx: XMP metadata properties and the PDF/A Extension Schema declaration.

The ZUGFeRD or Factur-X PDF is missing required XMP metadata properties in the fx namespace.

Severity
Fatal
Rule set
zugferd
Country
All EU
Fix type
BLOCKED
Confidence
70%
Category
pdf-metadata

Engine Classification

Financial or legal field · Modification blocked by policy

What is ZUG-XMP-001?

ZUG-XMP-001 is a fatal validation rule defined in the zugferd specification. It validates the ZUGFeRD 2.1+ requires fx:DocumentType, fx:DocumentFileName, fx:Version, and fx:ConformanceLevel in the urn:factur-x:pdfa:CrossIndustryDocument:invoice:1p0# namespace. element in the UBL invoice XML.

When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.

Target path: ZUGFeRD 2.1+ requires fx:DocumentType, fx:DocumentFileName, fx:Version, and fx:ConformanceLevel in the urn:factur-x:pdfa:CrossIndustryDocument:invoice:1p0# namespace.

This error requires manual correction — financial fields are protected by policy.

Why This Error Matters

Without correct XMP metadata, the PDF is treated as a regular PDF and structured data is ignored.

ZUG-XMP-001 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.

Invoice not recognized as structured. Does not meet German B2B requirement.

Validator Behavior

  • ·Causes invoice rejection
  • ·Error returned: ZUG-XMP-001
  • ·Specification: zugferd

How to Fix It

1.

2.

3.

4.

5.

Before / After

Failing XML
<!-- No fx: metadata -->
Corrected XML
<!-- fx: metadata added with all 4 properties -->

Technical Reference

XPathZUGFeRD 2.1+ requires fx:DocumentType, fx:DocumentFileName, fx:Version, and fx:ConformanceLevel in the urn:factur-x:pdfa:CrossIndustryDocument:invoice:1p0# namespace.
Speczugferd
StrategyInject correct XMP metadata into PDF/A-3.

Common Causes

  • ·PDF library lacks PDF/A-3 XMP support.
  • ·Namespace URI typo.
  • ·Missing Extension Schema declaration.
  • ·ConformanceLevel mismatch.

Seeing this in production? The API handles ZUG-XMP-001 automatically. See the fix response →

Commonly Seen In

Apache PDFBoxiText

Frequently Asked Questions

fx:DocumentType, fx:DocumentFileName, fx:Version, fx:ConformanceLevel.

It validates and flags issues. PDF re-generation is needed.

Related Content

Learn
E-Invoicing DeadlinesWhat is XRechnung?
Countries
E-Invoicing in GermanyE-Invoicing in France
Blog
ZUGFeRD vs XRechnung: A Technical Comparison for ERP DevelopersGermany E-Invoicing 2025: Complete Guide
Validators
ZUGFeRD ValidatorZUGFeRD Validator (DE)

Last updated: 25 March 2026

Share this guide:

Validate your invoice

Drop your XML here to check for ZUG-XMP-001

Detect ZUG-XMP-001 before submission

This error involves a financial field that can't be auto-modified. We'll flag it with a clear diagnosis so you can fix it at the source.

Fix it nowAutomate via API