What it means
When an invoice line gives a standard identifier for the item (BT-157), such as a GTIN barcode number, it must also say which scheme it belongs to (BT-157-1), using a code from the ISO 6523 ICD list, for example 0160 for GTIN.
Why it matters
An identifier means nothing without the list it comes from: the same digits can be a VAT number, a company number or a GLN. The scheme tells the recipient's software how to read it, so an identifier without one is rejected.
How to fix it
In your product data, mark the barcode or article number as a GTIN (or the scheme it really belongs to), so your invoicing software writes the scheme with it. If you build the XML yourself, add schemeID="0160" to cac:StandardItemIdentification/cbc:ID (UBL) or schemeID to ram:GlobalID (CII). If the number is your own article number, put it in the seller's item identifier instead.
The rule as published
The Item standard identifier (BT-157) shall have a Scheme identifier. Business terms: BT-157
Where this rule applies
| Rule set | Version |
|---|---|
| EN 16931 (UBL) | 1.3.17 |
| EN 16931 (UBL credit note) | 1.3.17 |
| EN 16931 (CII) | 1.3.17 |
| XRechnung 3.0 (UBL) | 3.0.2 |
| XRechnung 3.0 (UBL credit note) | 3.0.2 |
| XRechnung 3.0 (CII) | 3.0.2 |
| Peppol BIS Billing 3.0 (invoice) | 2026.5 |
| Peppol BIS Billing 3.0 (credit note) | 2026.5 |
| Factur-X 1.09 BASIC | 1.0.9-2 |
| Factur-X 1.09 EN 16931 | 1.0.9-2 |
| Factur-X 1.09 EXTENDED | 1.0.9-2 |
| ZUGFeRD 2.5 BASIC | 2.5.2 |
| ZUGFeRD 2.5 EN 16931 | 2.5.2 |
| ZUGFeRD 2.5 EXTENDED | 2.5.2 |
| SI-UBL 2.0 / NLCIUS (invoice) | 2.0.3.13 |
| SI-UBL 2.0 / NLCIUS (credit note) | 2.0.3.13 |
| NLCIUS (CII) | 1.0.3.13 |
| France CTC (UBL invoice) | 1.4.0-04 |
| France CTC (UBL credit note) | 1.4.0-04 |
| France CTC (CII) | 1.4.0-04 |
| CIUS-RO UBL Invoice 1.0.9 | 1.0.9 |
| CIUS-RO UBL Credit Note 1.0.9 | 1.0.9 |
Check your file
Drop your e-invoice to see whether BR-64 still fails, and which other rules do.