What it means
A standard identifier of an item, such as a barcode number (BT-157), carries a scheme code (BT-157-1) that says what kind of number it is. The code must be a single code from the ISO 6523 ICD list used by the XRechnung extension, with no spaces. The rule only runs on invoices that use the XRechnung extension, and XRechnung CII files are checked the same way.
Why it matters
The scheme code tells the recipient how to read the product number, for example as a GTIN. An unknown code cannot be interpreted, so the invoice fails validation and is rejected.
How to fix it
On the invoice line, find the product's standard identifier (the barcode, EAN or GTIN field) and its type. Set the type to the matching four-digit code, normally 0160 for a GTIN, the number under a barcode, with no spaces or extra text. If the product has no standard identifier, remove it from the line.
The rule as published
Any scheme identifier in MUST be coded using one of the ISO 6523 ICD list. Where this rule applies
| Rule set | Version |
|---|---|
| XRechnung 3.0 (UBL) | 3.0.2 |
| XRechnung 3.0 (UBL credit note) | 3.0.2 |
| XRechnung 3.0 (CII) | 3.0.2 |
Check your file
Drop your e-invoice to see whether BR-DEX-06 still fails, and which other rules do.
Related rules
- BR-DEX-07 Electronic address scheme must be from the EAS code list
- BR-DEX-08 Delivery location scheme must be an ISO 6523 code
- BR-DEX-09 Amount due must add up, including third party payments
- BR-DEX-10 Third party payment needs a payment type
- BR-DEX-11 Third party payment needs an amount
- BR-DEX-12 Third party payment needs a description