# BR-64: Item standard identifier scheme (BT-157-1)

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

An item standard identifier, BT-157 (`cac:StandardItemIdentification/cbc:ID` in UBL, `ram:SpecifiedTradeProduct/ram:GlobalID` in CII), must carry a scheme identifier from ISO 6523, for example 0160 for a GTIN. 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-157
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-64 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-64]-The Item standard identifier (BT-157) shall have a Scheme identifier.
```

## What it checks

An item standard identifier, BT-157 (`cac:StandardItemIdentification/cbc:ID` in UBL, `ram:SpecifiedTradeProduct/ram:GlobalID` in CII), must carry a scheme identifier from ISO 6523, for example 0160 for a GTIN.

## Why invoices fail it

An EAN or GTIN is written without `schemeID`.

## How to fix it

Add `schemeID="0160"` for a GTIN (EAN), or the ISO 6523 code of the identification scheme used.

## 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 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-64.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-64** | error | `/ubl:Invoice/cac:InvoiceLine[2]/cac:Item/cac:StandardItemIdentification/cbc:ID` | The Item standard identifier (BT-157) shall have a Scheme identifier. |

```diff
  …
        <cbc:Name>Lizenz Bildmaterial</cbc:Name>
        <cac:StandardItemIdentification>
-         <cbc:ID>4006381333931</cbc:ID>
+         <cbc:ID schemeID="0160">4006381333931</cbc:ID>
        </cac:StandardItemIdentification>
        <cac:ClassifiedTaxCategory>
  …
```

## 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: cac:InvoiceLine/cac:Item/cac:StandardItemIdentification/cbc:ID | cac:CreditNoteLine/cac:Item/cac:StandardItemIdentification/cbc:ID
test:    exists(@schemeID)
```

```xpath
context: //ram:IncludedSupplyChainTradeLineItem
test:    normalize-space(ram:SpecifiedTradeProduct/ram:GlobalID/@schemeID) != '' or not (ram:SpecifiedTradeProduct/ram:GlobalID)
```

## 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-62: Seller electronic address scheme (BT-34-1)](https://veriport.io/einvoice-rules/br-62)
- [BR-63: Buyer electronic address scheme (BT-49-1)](https://veriport.io/einvoice-rules/br-63)
- [BR-65: Item classification scheme (BT-158-1)](https://veriport.io/einvoice-rules/br-65)
- [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)
