KF-PDF-XMP-NOM: The XMP announces a different file name
This code shows up when an electronic invoice is validated. Here is what it means, why it fires, and what to change in the file.
Why this code appears
The name declared in the metadata (fx:DocumentFileName) is not that of the attachment actually present. The recipient looks for a file that does not exist.
How to fix it
Bring the two into agreement. This is the classic symptom of an XMP template copied from project to project without being reread.
Where it happens
This check is ours, not a code from the standard: we do not cover enough of EN 16931 to borrow its numbers, and a misattributed official code would send you to fix the wrong field. It concerns PDF.