BR-DE-22: Not all filename attributes of the…

StandardXRechnung 3.0.2 (KoSIT, German CIUS of EN 16931)SeverityError: the invoice is rejectedSyntaxUBL, CIIApplies toXRechnung in UBL or CII syntax, including ZUGFeRD / Factur-X PDFs with the XRECHNUNG profile. Invoices to German public authorities (federal, state and municipal) must pass it.

Official rule text

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

Why this error occurs

The validator evaluates the XPath test above against the context element; the assertion is false for your file.

How to fix it

Compare your file with the rule text and the test expression, adjust the element named in the context, and validate again.

What the validator checks

Checked element (context):

UBL

/ubl:Invoice | /cn:CreditNote

Test (XPath):

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

CII

/rsm:CrossIndustryInvoice

Test (XPath):

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

Check your invoice

Drop your XML or PDF on the validator and every failed rule is linked to its page here. Free, no account, the file is not stored.

Check your invoice →

Same check via API:

curl -F file=@invoice.xml https://einvoicechecker.com/v1/validate

Related rules

BR-DE-1 Payment instructions (BG-16) are missing
BR-DE-2 Seller contact (BG-6) is missing
BR-DE-3 Seller city (BT-37) is missing
BR-DE-4 The element "Seller post code" must be transmitted
BR-DE-5 Seller contact point (BT-41) is missing
BR-DE-6 Seller contact telephone number (BT-42) is missing
BR-DE-7 Seller contact email address (BT-43) is missing
BR-DE-8 The element "Buyer city" must be transmitted

Frequently asked questions

What does BR-DE-22 mean?

BR-DE-22 is a xrechnung rule: Not all filename attributes of the embeddedDocumentBinaryObject elements are unique

Will my invoice be rejected because of BR-DE-22?

Yes. BR-DE-22 is flagged "fatal"; validators (KoSIT, Peppol access points, the German ZRE/OZG-RE portals) reject the invoice until it is fixed.

Which formats does BR-DE-22 apply to?

XRechnung in UBL or CII syntax, including ZUGFeRD / Factur-X PDFs with the XRECHNUNG profile. Invoices to German public authorities (federal, state and municipal) must pass it. Syntax: UBL and CII.

Source: XRechnung 3.0.2, schematron 2.6.0 (KoSIT, September 2026). Catalogue generated from the official schematron on 2026-10-14.

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