# BR-DE-15: Buyer reference (BT-10) required

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

An XRechnung must carry the buyer reference, BT-10: `cbc:BuyerReference` in UBL, `ram:ApplicableHeaderTradeAgreement/ram:BuyerReference` in CII. Below: the message, the cause and the fix, and an invoice our validator checked, failing and fixed.

- **Specification:** [XRechnung 3.0 rules](/einvoice-rules/xrechnung), XRechnung 3.0.2 schematron 2.6.0
- **Severity:** error
- **Business terms:** BT-10
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-DE-15 is a rule of the XRechnung 3.0 rules (xrechnung-schematron 2.6.0 (XRechnung 3.0.2)) for UBL and CII. It is an error (fatal): a validator rejects the invoice.

```text
[BR-DE-15] Das Element "Buyer reference" (BT-10) muss übermittelt werden.
```

## What it checks

An XRechnung must carry the buyer reference, BT-10: `cbc:BuyerReference` in UBL, `ram:ApplicableHeaderTradeAgreement/ram:BuyerReference` in CII. For a public buyer it is the Leitweg-ID, which routes the invoice to the right office; for a business, the reference the buyer gave (an order or cost-centre number).

## Why invoices fail it

The Leitweg-ID is written only as the buyer’s electronic address (BT-49) or in a note, or a B2B invoice has no buyer reference at all.

## How to fix it

Write the Leitweg-ID (public buyer) or the buyer’s reference (business) in BT-10; if the buyer gave none, agree one with the buyer, since XRechnung does not allow the field to be missing.

## 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 XRechnung 3.0 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-DE-15.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-DE-15** | error | `/ubl:Invoice` | Das Element "Buyer reference" (BT-10) muss übermittelt werden. |

```diff
  …
    <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
    <cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>
+   <cbc:BuyerReference>EK-2026-0345</cbc:BuyerReference>
    <cac:AccountingSupplierParty>
      <cac:Party>
  …
```

## The rule as published

Where the rule applies (`context`) and what must hold (`test`), unmodified from XRechnung 3.0.2 schematron 2.6.0. An `assert` fails when its test is false.

Text and test: © KoSIT, Apache License 2.0. Quoted unmodified; the explanations on this page are Veriport’s.

```xpath
context: /ubl:Invoice | /cn:CreditNote
test:    cbc:BuyerReference[boolean(normalize-space(.))]
```

```xpath
context: /rsm:CrossIndustryInvoice
test:    rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerReference[boolean(normalize-space(.))]
```

## 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-DE-11: Deliver-to post code (BT-78) required](https://veriport.io/einvoice-rules/br-de-11)
- [BR-DE-14: VAT category rate (BT-119) required](https://veriport.io/einvoice-rules/br-de-14)
- [BR-DE-16: Seller VAT ID, tax number or tax representative](https://veriport.io/einvoice-rules/br-de-16)
- [BR-DE-17: Invoice type code outside the XRechnung list](https://veriport.io/einvoice-rules/br-de-17)
- [All XRechnung 3.0 rules](https://veriport.io/einvoice-rules/xrechnung)
- [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

- XRechnung — the German CIUS of EN 16931 (standard, versions and bundles; version 3.0.2 in force) — https://xeinkauf.de/xrechnung/ (2026-10-28)
- Validator configuration XRechnung v2026-08-31 (XRechnung 3.0.2, CEN schematron 1.3.16, xrechnung-schematron 2.6.0) — https://github.com/itplr-kosit/validator-configuration-xrechnung/releases/tag/v2026-08-31 (2026-10-28)
- XRechnung schematron (xrechnung-schematron) and the XRechnung validator configuration: licence, Apache License 2.0 (LICENSE files; NOTICE of the configuration: « Copyright 2020 Koordinierungsstelle für IT-Standards ») — https://github.com/itplr-kosit/xrechnung-schematron/blob/master/LICENSE (2026-11-17)
