What it means
Every document embedded in an XRechnung (BT-125) has a filename attribute, and no two attachments may share the same file name.
Why it matters
The recipient's system saves the attachments under their file names. Two files with the same name would overwrite each other, so one of them would be lost; XRechnung therefore rejects the invoice.
How to fix it
Rename the files before attaching them so that each name is different, for example by adding a number or a date, and export again. Watch out for software that names every attachment attachment.pdf. In the XML the name is the filename attribute of cbc:EmbeddedDocumentBinaryObject (UBL) or ram:AttachmentBinaryObject (CII).
The rule as published
Das "filename"-Attribut aller "EmbeddedDocumentBinaryObject"-Elemente muss eindeutig sein Where XRechnung 3.0 (CII) run it, the rule reads:
Not all filename attributes of the embeddedDocumentBinaryObject elements are unique Where this rule applies
| Rule set | Version |
|---|---|
| XRechnung 3.0 (UBL) | 3.0.2 |
| XRechnung 3.0 (UBL credit note) | 3.0.2 |
| XRechnung 3.0 (CII) | 3.0.2 |
Check your file
Drop your e-invoice to see whether BR-DE-22 still fails, and which other rules do.
Related rules
- BR-DE-26 A corrected invoice should refer to the invoice it corrects
- BR-DE-27 The seller's phone number should contain at least three digits
- BR-DE-28 The seller's email address should be well formed
- BR-DE-30 Creditor identifier is required
- BR-DE-31 Account to be debited is required
- BR-DE-21 The specification identifier should be the XRechnung one