BR-DE-22Two attachments have the same file name
Also in:Deutsch
What it means
Every file attached inside an XRechnung needs its own file name, so the receiving system can tell them apart.
Official message
Rejects the invoice (fatal)[BR-DE-22] Das "filename"-Attribut aller "EmbeddedDocumentBinaryObject"-Elemente muss eindeutig seinXRechnung Schematron 2.6.0, KoSIT, released 2 September 2026 · Read the rule at the source
KoSIT publishes the XRechnung messages in German only.
Text compared with the published file on 17 November 2026.
Typical causes
- Two documents were both exported as 'attachment.pdf'.
- The same file was attached twice.
How to fix it
- Give each attachment a unique file name, e.g. timesheet-2026-10.pdf.
- Remove duplicates and export again.
Check your invoice for BR-DE-22
Open the free validator with BR-DE-22 already explained: paste or upload your XML and the finding, if any, is highlighted with its exact line.
Check my invoice3 free validations a month without an account. Invoice contents are never stored.
Germany · XRechnung
Check this rule in German
The free German checker runs BR-DE-22 and the other XRechnung rules in your browser, with the fix in German. Nothing is uploaded.
- XRechnung ValidatorPaste an XRechnung (UBL or CII) or a ZUGFeRD PDF and see 32 XRechnung rules (BR-DE) with the fix in German. Runs in your browser; nothing is uploaded.in German
- XRechnung vs. ZUGFeRDXRechnung or ZUGFeRD: how they are built, the profiles, and which format suits which customer.in German
Prefer English?XRechnung validatorGermany's e-invoicing obligation: 2025, 2027 and 2028
What the rule says (technical)
The filename attribute of every embedded attachment (BT-125) must be unique.
Rename one of the attached files so every attachment has its own file name.
More errors with a worked fix
Related rules
- BR-CL-24Attachment type isn't allowedSame field: BT-125
- PEPPOL-EN16931-CL001Attachment type not allowed in PeppolSame field: BT-125
- IV-SYN-01Invoice file cannot be read
- IV-SYN-02Invoice format is not supported
- IV-SYN-03Number or date format is incorrect
- IV-SYN-04Invoice profile contains too little detail
- PEPPOL-EN16931-R008Remove empty fields from the export
- SI-V20-INV-R000Not marked as an SI-UBL 2.0 invoice