# BR-01

Quoted from a public specification. This page is not a validator, and it is not tax, legal, or accounting advice.

- Country: EU
- Syntax: UBL
- Severity: fatal
- Statement language: en
- Last verified: 2026-10-18

## Official statement

> An Invoice shall have a Specification identifier (BT-24).

Source: https://docs.peppol.eu/poacc/billing/3.0/rules/ubl-tc434/BR-01/

Peppol BIS Billing 3.0, May 2026 release, EN 16931 model bound to UBL

Severity note: fatal, from the Flag column of the Peppol BIS Billing 3.0 UBL rules index retrieved 2026-10-18.

## Plain-language reading

An invoice must have a specification identifier (BT-24). The published test checks that cbc:CustomizationID is not blank. The official message and the index cell both end with a non-breaking space, a regular space, and a non-breaking space after the period. The stored statement drops that trailing whitespace. The message says "shall have". It does not name a VAT breakdown, an invoice line, an allowance, or a charge.

## What to change

Fill cbc:CustomizationID with a non-empty specification identifier (BT-24).

## Illustration

Illustration of the condition in the official statement. Not an example published by the source.

**Fails the stated condition.** CustomizationID is missing or blank.

**Passes the stated condition.** CustomizationID contains a non-empty value.

## Published context and test

Copied from the source. Not reimplemented on this page.

```
/ubl:Invoice | /cn:CreditNote
```

```
normalize-space(cbc:CustomizationID) != ''
```

[All rule notes](https://einvoicegoblin.com/rules/index.md) · [JSON](https://einvoicegoblin.com/rules/BR-01.json) · [HTML](https://einvoicegoblin.com/rules/BR-01/) · [llms.txt](https://einvoicegoblin.com/llms.txt) · [Invoice page](https://einvoicegoblin.com/) · [Privacy](https://einvoicegoblin.com/privacy.html)