# BR-55: Preceding invoice reference (BT-25) missing

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

Every preceding invoice reference (BG-3: `cac:BillingReference/cac:InvoiceDocumentReference` in UBL, `ram:InvoiceReferencedDocument` in CII) must contain the number of the invoice referred to, BT-25. 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-25, BG-3
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-55 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-55]-Each Preceding Invoice reference (BG-3) shall contain a Preceding Invoice reference (BT-25).
```

## What it checks

Every preceding invoice reference (BG-3: `cac:BillingReference/cac:InvoiceDocumentReference` in UBL, `ram:InvoiceReferencedDocument` in CII) must contain the number of the invoice referred to, BT-25.

## Why invoices fail it

A credit note references the original invoice only by date (BT-26).

## How to fix it

Write the number of the corrected or credited invoice in BT-25; the date may follow in BT-26.

## 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 CII. 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-55.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-55** | error | `/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:InvoiceReferencedDocument` | Each Preceding Invoice reference (BG-3) shall contain a Preceding Invoice reference (BT-25). |

```diff
  …
        </ram:SpecifiedTradeSettlementHeaderMonetarySummation>
        <ram:InvoiceReferencedDocument>
+         <ram:IssuerAssignedID>2026-011</ram:IssuerAssignedID>
          <ram:FormattedIssueDateTime>
            <qdt:DateTimeString format="102">20260930</qdt:DateTimeString>
  …
```

## 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:BillingReference
test:    exists(cac:InvoiceDocumentReference/cbc:ID)
```

```xpath
context: /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:InvoiceReferencedDocument
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-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-56: Tax representative VAT identifier (BT-63)](https://veriport.io/einvoice-rules/br-56)
- [BR-57: Deliver-to country code (BT-80) missing](https://veriport.io/einvoice-rules/br-57)
- [BR-DE-26: Corrected invoice (384) without a preceding invoice](https://veriport.io/einvoice-rules/br-de-26)
- [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)
