Skip to content

BR-DE-22: Attachment file names are not unique

Official message

[BR-DE-22] Not all filename attributes of the embeddedDocumentBinaryObject elements are unique

XRechnung (CII) · Error · Message language: English · Version: xrechnung-3.0.2-validator-configuration-2026-08-31

[BR-DE-22] Das "filename"-Attribut aller "EmbeddedDocumentBinaryObject"-Elemente muss eindeutig sein

XRechnung (UBL) · Error · Message language: German · Version: xrechnung-3.0.2-validator-configuration-2026-08-31
Severity
Error The invoice is invalid and may be rejected by the recipient.
Applies to
XRechnung (CII), XRechnung (UBL)

What does this mean?

All embedded attachments (Attached document, BT-125) of an XRechnung invoice must have different file names (filename attribute). At least two attachments have the same file name.

Typical causes

The same file was attached more than once.
Different files have the same name, e.g. several attachments named attachment.pdf.

How to fix the error

Give every attachment its own unique file name, e.g. delivery_note_4711.pdf and timesheet_march.pdf.
Remove files that were attached twice.
CII: ram:AdditionalReferencedDocument/ram:AttachmentBinaryObject/@filename, UBL: cac:AdditionalDocumentReference/cac:Attachment/cbc:EmbeddedDocumentBinaryObject/@filename.
Generate and validate the invoice again.

In E-Rechnungsfreund

In the invoice form ("Experte" view), section "Zusätzliche Dokumente (BG-24)" (additional documents), change the fields "Dateiname (BT-125-2)" so that each name occurs only once, or remove duplicate documents.

Example

Wrong

<ram:AdditionalReferencedDocument>
  <ram:IssuerAssignedID>LS-4711</ram:IssuerAssignedID>
  <ram:TypeCode>916</ram:TypeCode>
  <ram:AttachmentBinaryObject mimeCode="application/pdf" filename="attachment.pdf">...</ram:AttachmentBinaryObject>
</ram:AdditionalReferencedDocument>
<ram:AdditionalReferencedDocument>
  <ram:IssuerAssignedID>TS-03</ram:IssuerAssignedID>
  <ram:TypeCode>916</ram:TypeCode>
  <ram:AttachmentBinaryObject mimeCode="application/pdf" filename="attachment.pdf">...</ram:AttachmentBinaryObject>
</ram:AdditionalReferencedDocument>

Correct

<ram:AdditionalReferencedDocument>
  <ram:IssuerAssignedID>LS-4711</ram:IssuerAssignedID>
  <ram:TypeCode>916</ram:TypeCode>
  <ram:AttachmentBinaryObject mimeCode="application/pdf" filename="delivery_note_4711.pdf">...</ram:AttachmentBinaryObject>
</ram:AdditionalReferencedDocument>
<ram:AdditionalReferencedDocument>
  <ram:IssuerAssignedID>TS-03</ram:IssuerAssignedID>
  <ram:TypeCode>916</ram:TypeCode>
  <ram:AttachmentBinaryObject mimeCode="application/pdf" filename="timesheet_march.pdf">...</ram:AttachmentBinaryObject>
</ram:AdditionalReferencedDocument>
For developers: test expression per syntax

XRechnung (CII) (CII)

Context: /rsm:CrossIndustryInvoice

count(//ram:AdditionalReferencedDocument) = count(//ram:AdditionalReferencedDocument[not(./ram:AttachmentBinaryObject/@filename = preceding-sibling::ram:AdditionalReferencedDocument/ram:AttachmentBinaryObject/@filename)])

XRechnung (UBL) (UBL)

Context: /ubl:Invoice | /cn:CreditNote

count(cac:AdditionalDocumentReference) = count(cac:AdditionalDocumentReference[not(./cac:Attachment/cbc:EmbeddedDocumentBinaryObject/@filename = preceding-sibling::cac:AdditionalDocumentReference/cac:Attachment/cbc:EmbeddedDocumentBinaryObject/@filename)])

Related validation rules

  • BR-DE-1: Payment instructions (BG-16) are missing
  • BR-DE-10: Deliver to city (BT-77) is missing
  • BR-DE-11: Deliver to post code (BT-78) is missing
  • BR-DE-14: VAT category rate (BT-119) is missing in the VAT breakdown
  • BR-DE-15: Buyer reference (BT-10) is missing
  • BR-DE-16: Seller VAT ID, tax number or tax representative is missing

Last updated:
Explanation of the validation rule, not legal or tax advice.