# BR-65

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

> The Item classification identifier (BT-158) shall have a Scheme identifier.

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

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

The Item classification identifier (BT-158) must have a Scheme identifier. The message starts with "The", not "Each", and says "shall have a Scheme identifier". It ends with a period. The context is the item classification code on an invoice line or a credit note line. The published test checks that the listID attribute exists. It does not check a schemeID attribute, and it does not check the list value.

## What to change

When an item classification identifier (BT-158) is sent, give that classification code a listID attribute.

## Illustration

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

**Fails the stated condition.** An item classification code has no listID attribute.

**Passes the stated condition.** That classification code has a listID attribute.

## Published context and test

Copied from the source. Not reimplemented on this page.

```
cac:InvoiceLine/cac:Item/cac:CommodityClassification/cbc:ItemClassificationCode | cac:CreditNoteLine/cac:Item/cac:CommodityClassification/cbc:ItemClassificationCode
```

```
exists(@listID)
```

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