Common ZUGFeRD Validation Errors and How to Fix Them
ZUGFeRD validation errors by category: the exact Mustang and veraPDF messages, what causes them and how to fix profile, PDF/A-3, file name and XML rule errors.
Key takeaways
- ZUGFeRD validation errors fall into four groups: missing or misnamed XML, XMP metadata, PDF/A-3 conformance, and schema or business rule errors in the XML.
- According to the FeRD ZUGFeRD FAQ, pure PDF/A errors only count as warnings as long as the XML is valid and can be extracted.
- A ZUGFeRD PDF may carry exactly one invoice XML, named factur-x.xml, or xrechnung.xml for the XRECHNUNG profile.
- BR-DE findings on an EN 16931 profile file do not mean the invoice is wrong: each profile is validated against its own rule set.
- Fix errors in the invoicing software, never in the finished PDF, because any editing can drop the embedded XML or break PDF/A.
On this page
ZUGFeRD validation errors come from four places: the invoice XML is missing or misnamed, the XMP metadata do not match, the PDF is not PDF/A-3 conformant, or the XML breaks the schema or business rules of its profile. The XML is what counts. According to the FeRD, pure PDF/A defects are warnings, while rule violations in the XML are real errors.
This guide is for anyone who receives a red validation report for a ZUGFeRD or Factur-X file: finance teams, foreign suppliers invoicing German customers, and developers who build the export. It maps the exact messages to a cause and a fix. For the full validation procedure, read our guide on how to validate a ZUGFeRD PDF.
What do ZUGFeRD validation messages look like?
The two widely used free tools are the Mustang validator (checks PDF, XMP and XML) and veraPDF (checks PDF/A only). The texts below are taken from the Mustang source code and from the veraPDF PDF/A-3b validation profile on GitHub. They are message templates, not the output of a real validation run:
Mustang: XML data not found in invoice.pdf: did you specify a pdf or xml file
and does the xml file contain an embedded XML file?
Mustang: XMP Metadata: DocumentFileName contains invalid value
Mustang: XMP Metadata: ConformanceLevel contains invalid value
Mustang: Not a PDF/A-3
Mustang: Unsupported profile type urn:...
Mustang: Factur-X/ZUGFeRD and Order-X are always strictly CII only, no UBL allowed.
Mustang: No rules matched, XML too minimal?
veraPDF: 6.2.11.4.1-1 The font program is not embedded
veraPDF: 6.8-3 The file specification dictionary for an embedded file does not
contain the AFRelationship key or it has invalid value type
veraPDF: 6.6.2.3.1-1 XMP property is either not predefined, or is not defined
in any XMP extension schema
Mustang writes each finding into its XML report as an error, warning or notice element with a type number, for example type="19" for the file name check. veraPDF names the clause of ISO 19005-3 and the test number.
The four error groups at a glance
| Group | Typical message | Most common cause | Weight |
|---|---|---|---|
| 1. XML missing or misnamed | "XML data not found", "DocumentFileName contains invalid value" | PDF edited after export, wrong export name | Error: no XML, no e-invoice |
| 2. XMP metadata | "ConformanceLevel contains invalid value", veraPDF 6.6.2.3.1-1 | profile hard-coded in metadata, missing extension schema | Error in Mustang |
| 3. PDF/A-3 | "Not a PDF/A-3", veraPDF 6.2.11.4.1-1, 6.8-3 | export without PDF/A setting, non-embedded fonts | Warning per FeRD; recipient may ask for a fix |
| 4. XML schema and business rules | "Unsupported profile type", BR-CO-10, BR-CO-15 | wrong profile in BT-24, rounding, missing fields | Error |
The order follows the validation order. If the XML is missing, every later check is meaningless, so always fix the group with the lowest number first.
Group 1: The XML is missing or has the wrong name
"XML data not found"
Mustang finds no attachment it recognises as invoice XML. The causes, most common first:
- The PDF was edited after export: merged, stamped, redacted, or re-printed through a PDF printer. Page-based tools copy pages, not attachments. Our article on how to merge ZUGFeRD PDF files shows what gets lost.
- The invoice was exported as a plain PDF instead of ZUGFeRD or Factur-X. It looks identical on screen.
- The XML is embedded under a name the validator does not look for.
Fix: generate the file again in the invoicing software with the ZUGFeRD or Factur-X export option. As a recipient, ask the sender for the original, unedited file.
"DocumentFileName contains invalid value"
In the XMP metadata, Mustang accepts only these file names: factur-x.xml, xrechnung.xml, zugferd-invoice.xml, ZUGFeRD-invoice.xml and order-x.xml. If an XML attachment with another name is present, it adds the notice "Potentially incorrectly named XML file attachments detected".
The FeRD FAQ says that the current version allows exactly one invoice data file per PDF, named factur-x.xml or, for the XRECHNUNG profile, xrechnung.xml. The names zugferd-invoice.xml (ZUGFeRD 2.0) and ZUGFeRD-invoice.xml (ZUGFeRD 1.0) come from older versions.
Fix: change the export name. It must match in two places: the attachment file name and the XMP field fx:DocumentFileName.
Group 2: The XMP metadata do not match the XML
XMP metadata are an XML block inside the PDF that declares the profile, file name, document type and version of the embedded invoice. Mustang reports, among others:
| Message | Meaning | Fix |
|---|---|---|
| ConformanceLevel not found / contains invalid value | profile declaration missing or unknown | allowed: MINIMUM, BASIC WL, BASIC, EN 16931, EXTENDED, XRECHNUNG (plus legacy values such as COMFORT) |
| DocumentType not found / invalid | document type missing | INVOICE for invoices |
| Version not found / contains invalid value | version missing | 1.0 with the Factur-X namespace |
| Could not parse XMP metadata (XML invalid) | XMP block is not well-formed XML | update the generating library |
veraPDF adds 6.6.2.3.1-1 when the properties in the namespace urn:factur-x:pdfa:CrossIndustryDocument:invoice:1p0# are not described in a PDF/A extension schema. PDF/A requires such a schema for every property outside the predefined namespaces.
A frequent special case: the metadata say "EN 16931", but BT-24 in the XML carries a BASIC or XRECHNUNG identifier. This happens when the XMP template is hard-coded and the profile was changed later. The identifier for each profile is listed in our guide to ZUGFeRD profiles and versions.
Group 3: The PDF is not PDF/A-3 conformant
Mustang reports "Not a PDF/A-3" when veraPDF does not confirm PDF/A-3 conformance. veraPDF gives the detailed reasons. The five most common rules from the PDF/A-3b profile:
| veraPDF rule | Message (abridged) | Cause | Fix |
|---|---|---|---|
| 6.2.11.4.1-1 | The font program is not embedded | font such as Arial only referenced | embed fonts on export |
| 6.2.4.3-2 | DeviceRGB colour space is used without RGB output intent profile | no OutputIntent with ICC profile | PDF/A export with an sRGB profile |
| 6.8-1 | MIME type of an embedded file is missing or invalid | attachment without Subtype | set the MIME type, for the XML for example text/xml |
| 6.8-3 | … does not contain the AFRelationship key … | XML not linked as associated file | set AFRelationship, for example Alternative |
| 6.6.4-2 | The "part" property … is %1 instead of 3 | file declared as PDF/A-1 or PDF/A-2 | generate as PDF/A-3 |
How serious is this? The FeRD FAQ quotes a note from the specification: since 1 January 2025, the embedded XML is the invoice in Germany. If it is valid and can be extracted, the file is a valid e-invoice, and technical PDF/A errors only count as warnings. The recipient can still ask for a corrected, PDF/A-conformant version. Senders should fix these errors, but they do not make the invoice worthless.
Rule 6.8-3 matters most in practice. Without the link, some inbound systems treat the XML as an ordinary attachment and never find the invoice.
Group 4: The XML breaks the schema or business rules
"Unsupported profile type"
For ZUGFeRD 2.x, Mustang knows a fixed list of BT-24 identifiers, for example urn:cen.eu:en16931:2017 for EN 16931. Anything else, such as a typo or a Peppol identifier, triggers "Unsupported profile type" with the value found. Mustang detects the XRECHNUNG identifier separately and then also runs the KoSIT rules.
Fix: select the right profile. Avoid MINIMUM and BASIC WL for tax purposes: according to the FeRD, only ZUGFeRD 2.0.1 and later, excluding these two profiles, count as e-invoices in Germany. Our article on ZUGFeRD BASIC WL explains why.
"strictly CII only, no UBL allowed"
A ZUGFeRD PDF may only contain XML in UN/CEFACT CII syntax. If a UBL invoice is embedded, Mustang rejects it. A UBL XRechnung has no hybrid form; it is sent as a plain XML file.
EN 16931 rule violations
This is where arithmetic errors and missing mandatory fields show up. Each finding carries the rule ID and the official rule text:
| Rule | Official text (EN 16931, abridged) | Typical cause |
|---|---|---|
| BR-CO-10 | Sum of Invoice line net amount (BT-106) = Σ Invoice line net amount (BT-131) | total built from unrounded line amounts |
| BR-CO-15 | Invoice total amount with VAT (BT-112) = BT-109 + BT-110 | gross total rounded differently |
| BR-CO-26 | Seller identifier (BT-29), BT-30 and/or Seller VAT identifier (BT-31) shall be present | neither VAT ID nor seller identifier |
For the totals rules, see BR-CO-10 and our list of XRechnung validation errors. How rounding gaps arise is covered in our guide to fixing XRechnung validation errors. The EN 16931 rules are the same for ZUGFeRD and XRechnung.
BR-DE findings on an EN 16931 profile file
This is the most common false alarm, especially for foreign suppliers whose Factur-X files are run through a German XRechnung check. Mustang also checks BASIC and EN 16931 files against the XRechnung rules, but reports the hits only as notice; the --no-notices option hides them. The FeRD states that a valid EN 16931 or EXTENDED invoice can fail an XRechnung-only check without being faulty or inadmissible. Every format must be validated with its own rule set.
BR-DE rules matter only when your customer explicitly asks for XRechnung, typically a public authority. In that case you need the XRECHNUNG profile or a plain XRechnung file.
Does every validation error matter for VAT?
No. The German Ministry of Finance distinguishes format errors, business rule errors and content errors, with different consequences for e-invoice status and input VAT deduction. Our article on e-invoice format errors explains the three classes with a decision table. For ZUGFeRD, the practical reading is: if the XML is missing or syntactically broken, there is no e-invoice. PDF/A defects with an intact XML are treated as warnings by the FeRD.
How to prevent ZUGFeRD errors at the source
| Measure | Prevents |
|---|---|
| Use the EN 16931 profile by default, XRECHNUNG only for authorities | "Unsupported profile type", BR-DE false alarms |
Check the export name factur-x.xml or xrechnung.xml | "DocumentFileName contains invalid value" |
| PDF/A-3 export with embedded fonts and an sRGB profile | veraPDF 6.2.11.4.1-1 and 6.2.4.3-2 |
| Never edit finished invoice PDFs | "XML data not found" |
| Build totals from rounded line amounts | BR-CO-10, BR-CO-15 |
| Validate a test invoice after every software update | new errors from changed libraries |
For the last point, set up a routine like the one in our guide to test an e-invoice before sending. Keep your validators current as well: according to the project changelog, Mustang 2.27.0 of 9 October 2026 is the latest release and uses version 2.6 of the XRechnung Schematron.
How to check a ZUGFeRD invoice with docutools.pro
- Open the tool to extract XML from a PDF and click "Choose PDF". The PDF is processed in your browser. If "E-invoice XML found" appears with a name under "Attachment", group 1 is solved. "Other attachments in this PDF" lists any extra files.
- Click "Download XML" and check the BT-24 identifier in the "XML source" tab.
- Upload the XML to the ZUGFeRD validator. The file is sent to our server for the check. The "KoSIT validation" checks the way the KoSIT validator does (configuration 2026-08-31): the EN 16931 profile runs the EN 16931 rules only, the XRECHNUNG profile also runs the BR-DE rules. There is no scenario for BASIC, EXTENDED, MINIMUM or BASIC WL; such files are rejected before any rule runs. Check those profiles with Mustang.
- Read the result: "KoSIT-conformant" or "Not KoSIT-conformant", with the rule IDs. The free tier allows 2 uploads per day up to 500 KB; the Pro plan removes the upload limit.
Neither the extractor nor the viewer checks PDF/A-3 or XMP; use veraPDF or Mustang for that. More guides are in the validation errors category.
Sources
- FeRD: ZUGFeRD FAQ (German) (opens in a new tab) (profiles, file names, PDF/A errors as warnings, validation with the matching rule set)
- FeRD: ZUGFeRD 2.5.2 information package of 4 August 2026 (opens in a new tab)
- Mustang project: validator source code and changelog (opens in a new tab)
- veraPDF: PDF/A-3B validation profile (opens in a new tab)
Last reviewed: November 2026
This article is general information, not tax or legal advice.
Tools for this article
- ZUGFeRD / Factur-X XML ExtractorExtract, view and download the embedded e-invoice XML from ZUGFeRD and Factur-X PDFs.Open tool →
- XRechnung ViewerParse, validate & repair German e-invoices with GoBD-compliant audit trail.Open tool →
- KoSIT Error HubSearchable reference for all XRechnung validation error codes with fix guides.Open tool →
Frequently asked questions
Is a ZUGFeRD invoice with PDF/A errors invalid in Germany?
Not automatically. The FeRD, which publishes ZUGFeRD, states in its FAQ that the invoice is valid if the embedded XML passes all business rules that apply in Germany and can be extracted from the PDF. Technical PDF/A errors are then only warnings. The recipient may still ask for a corrected PDF/A-conformant file, so senders should fix them anyway.
What does the Mustang error Unsupported profile type mean?
Mustang compares the specification identifier in BT-24 of the XML with a fixed list of known ZUGFeRD and Factur-X profile URNs. If the value is not on the list, for example because of a typo or a Peppol identifier inside a ZUGFeRD PDF, it reports Unsupported profile type followed by the value it found. Set the correct profile in your invoicing software and export the file again.
Why does my Factur-X invoice fail XRechnung rules?
Because it was checked with the wrong rule set. A Factur-X or ZUGFeRD invoice in the EN 16931 or EXTENDED profile does not have to meet the German XRechnung rules (BR-DE). The FeRD states that such files can produce errors under an XRechnung-only check without being faulty or inadmissible. Only invoices in the XRECHNUNG profile, or customers who explicitly require XRechnung, need the BR-DE rules.
Can a ZUGFeRD PDF contain more than one XML file?
Only one invoice XML. According to the FeRD FAQ, each PDF/A-3 document may reference exactly one invoice data file, named factur-x.xml or xrechnung.xml. Other attachments such as delivery notes or timesheets may be embedded in addition. In the EN 16931 and EXTENDED profiles, supporting documents can also be sent Base64-encoded inside the invoice XML itself.
Do I have to validate e-invoices before sending them in Germany?
There is no legal obligation. The FeRD points to the German Federal Ministry of Finance FAQ, which recommends validating when an e-invoice is created and sent. According to the ministry letter of 15 October 2025, as quoted by the FeRD, a business may rely on the technical result of a suitable validation tool and should keep the validation report as evidence.