Two attachments carry the same file name
The `filename` attribute of every embedded attachment must be unique within the document.
Only the issuer holds this value: Factlint reports it and never fabricates it. Test your invoice to find out whether it is affected.
The message your validator prints
Copied verbatim from the sealed artefact: this is the exact sentence the check prints when this rule fails.
cii[BR-DE-22] Not all filename attributes of the embeddedDocumentBinaryObject elements are unique
ubl[BR-DE-22] Das "filename"-Attribut aller "EmbeddedDocumentBinaryObject"-Elemente muss eindeutig sein
Quoted from schematron-xrechnung 3.0.2, licensed under Apache-2.0.
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
A recipient extracts the attachments into a single folder: two files called `annex.pdf` and one silently overwrites the other. The duplicate almost always comes from a loop naming each attachment after its type rather than after its content.
How to fix it
Name the attachments distinctly at generation time. Factlint does not rename: any suffix it picked would be arbitrary, and an attachment's name is often what the recipient files it under.
XML correction example
deux fois <ram:AttachmentBinaryObject filename="annexe.pdf"/>
"annexe-1.pdf" et "annexe-2.pdf"