The profile declared in the XMP differs from the one in the XML
`fx:ConformanceLevel` in the PDF's XMP metadata must match the profile URN declared in the embedded XML.
This defect is fixed automatically. Test your invoice to find out whether it is affected, then apply the correction with the Pipeline Pro plan.
Common searches around this code
These phrases mirror what an integrator searches for: code, syntax, rule, business field and correction.
Test your file with this error in mind
Upload the invoice involved: the report will say whether this code appears, where it appears in the document, and whether Factlint can only report it or also fix it.
To automate this check in an ERP flow, call the validation API and link every returned code to its public page.
Why this error happens
The PDF and the XML are produced by two different chains, and the XMP is often frozen in a template while the XML profile moves on. It is a frequent cause of rejection even when the invoice is substantively valid.
How to fix it
The two declarations have to be aligned. Factlint rewrites the XMP to the profile actually found in the XML.
XML correction example
<fx:ConformanceLevel>BASIC</fx:ConformanceLevel>
<fx:ConformanceLevel>EN 16931</fx:ConformanceLevel>
POST /v1/fixThis defect is among those the API rewrites itself: the corrected document comes back in the response. See the endpoint