DE-R-022
Attached documents provided with an invoice in "ADDITIONAL SUPPORTING DOCUMENTS" (BG-24) shall have a unique filename (non case-sensitive) within the element ″Attached document″ (BT-125).
What does this rule mean?
Two attachments carry the same file name (BT-125, @filename).
Receivers store attachments by file name, so the second overwrites the first and a document goes missing with nobody noticing. Note that attachments with no file name at all also compare as equal.
- BG-24
- Additional supporting documents (group)
- BT-125
- Attached document
Official rule message (standard)
Attached documents provided with an invoice in "ADDITIONAL SUPPORTING DOCUMENTS" (BG-24) shall have a unique filename (non case-sensitive) within the element ″Attached document″ (BT-125).
Where the rule applies
Syntax: UBL
Affected element (XPath):
(/ubl-invoice:Invoice | /ubl-creditnote:CreditNote)[$supplierCountryIsDE and $customerCountryIsDE]
Technical test
The rule passes when this Schematron expression holds true:
count(cac:AdditionalDocumentReference) = count(cac:AdditionalDocumentReference[not(./cac:Attachment/cbc:EmbeddedDocumentBinaryObject/@filename = preceding-sibling::cac:AdditionalDocumentReference/cac:Attachment/cbc:EmbeddedDocumentBinaryObject/@filename)])How to fix it
A missing or incorrect business entry only you can supply. Add or correct it, then re-check.
Give each attachment its own meaningful file name (e.g. timesheet-week14.pdf and delivery-note-4711.pdf), and make sure every attachment has a name in the first place.
Correct the affected entry in your XML, then re-check the invoice. Validation runs locally in your browser — your file never leaves your machine.
Check an e-invoice here
Drop an XML or ZUGFeRD PDF file here. Validation runs locally in your browser against EN 16931 — your file never leaves your machine.