# BR-01: Specification identifier (BT-24) missing

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

Every invoice must say which specification it follows, in BT-24: `cbc:CustomizationID` in UBL, `ram:GuidelineSpecifiedDocumentContextParameter/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-24
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-01 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-01]-An Invoice shall have a Specification identifier (BT-24).
```

## What it checks

Every invoice must say which specification it follows, in BT-24: `cbc:CustomizationID` in UBL, `ram:GuidelineSpecifiedDocumentContextParameter/ram:ID` in CII. The receiver picks its validation rules from this value.

## Why invoices fail it

The generator writes only the business process (BT-23, `cbc:ProfileID`) or leaves the identifier empty, often after copying a template written for an older UBL version.

## How to fix it

Write the identifier of the specification you follow: `urn:cen.eu:en16931:2017` for plain EN 16931, or the identifier of a CIUS such as XRechnung (`urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0`) or Peppol BIS Billing 3.0.

## 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-01 and 2 other rules, as a real file with this mistake would.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-01** | error | `/rsm:CrossIndustryInvoice` | An Invoice shall have a Specification identifier (BT-24). |
| [CII-SR-009](/einvoice-rules/cii-sr-009) | error | `/rsm:CrossIndustryInvoice/rsm:ExchangedDocumentContext` | GuidelineSpecifiedDocumentContextParameter must exist exactly once |
| [CII-SR-010](/einvoice-rules/cii-sr-010) | error | `/rsm:CrossIndustryInvoice/rsm:ExchangedDocumentContext` | ID must exist exactly once |

```diff
  …
        <ram:ID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</ram:ID>
      </ram:BusinessProcessSpecifiedDocumentContextParameter>
+     <ram:GuidelineSpecifiedDocumentContextParameter>
+       <ram:ID>urn:cen.eu:en16931:2017</ram:ID>
+     </ram:GuidelineSpecifiedDocumentContextParameter>
    </rsm:ExchangedDocumentContext>
    <rsm:ExchangedDocument>
  …
```

## 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:CustomizationID) != ''
```

```xpath
context: /rsm:CrossIndustryInvoice
test:    normalize-space(rsm:ExchangedDocumentContext/ram:GuidelineSpecifiedDocumentContextParameter/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-02: Invoice number (BT-1) missing](https://veriport.io/einvoice-rules/br-02)
- [BR-03: Invoice issue date (BT-2) missing](https://veriport.io/einvoice-rules/br-03)
- [BR-DE-21: Specification identifier not XRechnung’s](https://veriport.io/einvoice-rules/br-de-21)
- [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)
