# BR-52: Supporting document reference (BT-122) missing

Source: https://veriport.io/einvoice-rules/br-52 (published 2026-11-17)

Every additional supporting document (BG-24: `cac:AdditionalDocumentReference` in UBL, `ram:AdditionalReferencedDocument` in CII) must have a reference, BT-122 (`cbc:ID`, `ram:IssuerAssignedID`). Below: the message, the cause and the fix, and an invoice our validator checked, failing and fixed.

- **Specification:** [EN 16931 business rules](/einvoice-rules/en16931), CEN EN 16931 validation artefacts 1.3.16
- **Severity:** error
- **Business terms:** BT-122, BG-24
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-52 is a rule of the EN 16931 business rules (CEN validation artefacts 1.3.16) for UBL and CII. It is an error (fatal): a validator rejects the invoice.

```text
[BR-52]-Each Additional supporting document (BG-24) shall contain a Supporting document reference (BT-122).
```

## What it checks

Every additional supporting document (BG-24: `cac:AdditionalDocumentReference` in UBL, `ram:AdditionalReferencedDocument` in CII) must have a reference, BT-122 (`cbc:ID`, `ram:IssuerAssignedID`).

## Why invoices fail it

An attachment (a timesheet PDF) is embedded without an identifier.

## How to fix it

Give each attached or referenced document an identifier, for example its file name or document number.

## A failing invoice and its fix, checked

We start from our sample invoice (two lines at 19 %, Berlin to Stuttgart), written by our own generator as EN 16931 in UBL. The change below (`-` the failing version, `+` the fixed one) makes the rule fail. Both versions went through our validator on 2026-11-17 (the XML schema and the official rule files, as `POST /einvoice/validate` runs them): the fixed one is valid, the failing one reports BR-52.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-52** | error | `/ubl:Invoice/cac:AdditionalDocumentReference` | Each Additional supporting document (BG-24) shall contain a Supporting document reference (BT-122). |

```diff
  …
    <cbc:BuyerReference>EK-2026-0345</cbc:BuyerReference>
    <cac:AdditionalDocumentReference>
-     <cbc:ID/>
+     <cbc:ID>STD-2026-10</cbc:ID>
      <cbc:DocumentDescription>Stundennachweis Oktober 2026</cbc:DocumentDescription>
    </cac:AdditionalDocumentReference>
  …
```

## The rule as published

Where the rule applies (`context`) and what must hold (`test`), unmodified from CEN EN 16931 validation artefacts 1.3.16. An `assert` fails when its test is false.

Text and test: © CEN/TC 434, EN 16931 validation artefacts, EUPL 1.2. Quoted unmodified; the explanations on this page are Veriport’s.

```xpath
context: cac:AdditionalDocumentReference
test:    normalize-space(cbc:ID) != ''
```

```xpath
context: //ram:AdditionalReferencedDocument
test:    normalize-space(ram:IssuerAssignedID) != ''
```

## Check your own invoice

Drop your XRechnung, ZUGFeRD or Peppol file into a free validator ([Peppol BIS](/tools/peppol-validator), [XRechnung](/tools/xrechnung-pruefen), [Factur-X](/tools/valider-factur-x)): each runs the same rule files and links every finding to its rule page. From your own code, `POST /einvoice/validate` ([reference](/docs/einvoice)) returns the same check as JSON, each finding with an `explanation` field pointing here (5 calls a check, anonymous within the daily allowance).

## Read next

- [BR-50: Payment account (BT-84) for a credit transfer](https://veriport.io/einvoice-rules/br-50)
- [BR-51: Full card number (BT-87) on the invoice](https://veriport.io/einvoice-rules/br-51)
- [BR-53: VAT total in accounting currency (BT-111)](https://veriport.io/einvoice-rules/br-53)
- [BR-54: Item attribute name and value (BT-160/BT-161)](https://veriport.io/einvoice-rules/br-54)
- [BR-TMP-4: Supporting document description repeated (CII)](https://veriport.io/einvoice-rules/br-tmp-4)
- [BR-TMP-5: Two attachments in one document reference (CII)](https://veriport.io/einvoice-rules/br-tmp-5)
- [All EN 16931 business rules](https://veriport.io/einvoice-rules/en16931)
- [All e-invoice rules, search](https://veriport.io/einvoice-rules)
- [Check an e-invoice free (XRechnung prüfen)](https://veriport.io/tools/xrechnung-pruefen)
- [Create a valid e-invoice free (German form)](https://veriport.io/tools/e-rechnung-erstellen)

## Sources

- EN 16931 validation artefacts 1.3.16 (UBL and CII schematron, the business rules BR-*) — https://github.com/ConnectingEurope/eInvoicing-EN16931/releases/tag/validation-1.3.16 (2026-10-28)
- EN 16931 validation artefacts: licence, European Union Public Licence (EUPL) v1.2 (LICENSE.txt, the README « License » section and the release notes of validation-1.3.16) — https://github.com/ConnectingEurope/eInvoicing-EN16931/blob/master/LICENSE.txt (2026-11-17)
