# BR-02: Invoice number (BT-1) missing

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

The invoice must carry its number, BT-1: `cbc:ID` at document level in UBL, `rsm:ExchangedDocument/ram:ID` in CII. 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-1
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-02 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-02]-An Invoice shall have an Invoice number (BT-1).
```

## What it checks

The invoice must carry its number, BT-1: `cbc:ID` at document level in UBL, `rsm:ExchangedDocument/ram:ID` in CII. The rule fails when the element is absent or holds only whitespace.

## Why invoices fail it

The number is assigned after the XML is built (a draft exported before booking), or the mapping writes the number into another field such as the order reference.

## How to fix it

Assign the invoice number before export and write it in BT-1; it must identify the invoice uniquely in the seller’s numbering.

## 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-02 and 1 other rule, as a real file with this mistake would.

| Rule | Severity | Where | Message |
|---|---|---|---|
| XSD | error | `line 12` | Element 'ram:TypeCode': This element is not expected. Expected is ( ram:ID ). |
| **BR-02** | error | `/rsm:CrossIndustryInvoice` | An Invoice shall have an Invoice number (BT-1). |

```diff
  …
    </rsm:ExchangedDocumentContext>
    <rsm:ExchangedDocument>
+     <ram:ID>2026-017</ram:ID>
      <ram:TypeCode>380</ram:TypeCode>
      <ram:IssueDateTime>
  …
```

## 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: /ubl:Invoice | /cn:CreditNote
test:    normalize-space(cbc:ID) != ''
```

```xpath
context: /rsm:CrossIndustryInvoice
test:    normalize-space(rsm:ExchangedDocument/ram:ID) != ''
```

## 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-01: Specification identifier (BT-24) missing](https://veriport.io/einvoice-rules/br-01)
- [BR-03: Invoice issue date (BT-2) missing](https://veriport.io/einvoice-rules/br-03)
- [BR-04: Invoice type code (BT-3) missing](https://veriport.io/einvoice-rules/br-04)
- [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)
