What does BR-52 mean?
Every additional supporting document (BG-24) must carry a supporting document reference (BT-122). The reference is the number or mark under which the document is filed, for example a delivery note number. Without it the attachment cannot be matched.
Common causes of BR-52
- The element ram:AdditionalReferencedDocument is in the invoice, but ram:IssuerAssignedID is missing.
- Only a name (ram:Name) or an attachment is set, but no reference.
- The document number was empty in the system and never filled in.
How to fix BR-52
- Find the faulty spot in the XML. Open the XML of the invoice and go to field BT-122 along this XPath:
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:AdditionalReferencedDocument/ram:IssuerAssignedID - Apply the fix. Set the element ram:IssuerAssignedID in every ram:AdditionalReferencedDocument with the number of the attachment, for example LS-2026-0815.
- Validate again. Save the file and validate it again to check that BR-52 is no longer reported.
Set the element ram:IssuerAssignedID in every ram:AdditionalReferencedDocument with the number of the attachment, for example LS-2026-0815.
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:AdditionalReferencedDocument/ram:IssuerAssignedIDBefore / after: the XML example
This is the spot in question before and after the fix (Cross Industry Invoice, ZUGFeRD/Factur-X).
<ram:AdditionalReferencedDocument>
<ram:TypeCode>916</ram:TypeCode>
<ram:Name>Lieferschein</ram:Name>
</ram:AdditionalReferencedDocument>
<ram:AdditionalReferencedDocument>
<ram:IssuerAssignedID>LS-2026-0815</ram:IssuerAssignedID>
<ram:TypeCode>916</ram:TypeCode>
<ram:Name>Lieferschein</ram:Name>
</ram:AdditionalReferencedDocument>
Frequent questions about BR-52
Which attachments does this cover?
Is the name of the attachment enough?
Related error codes
Check BR-52 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.