BR-DE-22 in your own invoice? Upload the file and find every error in seconds.
What does BR-DE-22 mean?
Not all filename attributes of the embeddedDocumentBinaryObject elements are unique. The rule comes from KoSIT (XRechnung) and is an error there.
Common causes of BR-DE-22
- Two attachments carry the same file name, for example 'attachment.pdf' twice.
- The software gives every attachment the same fixed name, for example 'receipt.pdf'.
How to fix BR-DE-22
- Find the faulty spot in the XML. Open the XML of the invoice and go to the spot in question along this XPath:
//ram:AdditionalReferencedDocument/ram:AttachmentBinaryObject/@filename - Apply the fix. Every embedded attachment (embeddedDocumentBinaryObject) needs a unique 'filename' — give each attachment a different file name.
- Validate again. Save the file and validate it again to check that BR-DE-22 is no longer reported.
Concrete fix
Every embedded attachment (embeddedDocumentBinaryObject) needs a unique 'filename' — give each attachment a different file name.
XPath
//ram:AdditionalReferencedDocument/ram:AttachmentBinaryObject/@filenameFrequent questions about BR-DE-22
How do I fix BR-DE-22?
Every embedded attachment (embeddedDocumentBinaryObject) needs a unique 'filename' — give each attachment a different file name.
Related error codes
Check BR-DE-22 automatically
Instead of digging through the XML by hand you can validate your ZUGFeRD or XRechnung file online: upload the PDF or the XML and you get every error with rule ID, affected field, fix and XPath, as a readable report or as JSON through the API.