What it means
The identifier of the place where the goods are delivered (BT-71) carries a scheme code (BT-71-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 location number, for example as a GLN. An unknown code cannot be interpreted, so the invoice fails validation and is rejected.
How to fix it
In the delivery section of the invoice, look for the location ID and its type. Set the type to the matching four-digit ICD code, for example 0088 for a GLN, and remove any spaces or extra text. If you do not need a location identifier, remove it.
The rule as published
Any scheme identifier for a Delivery location 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-08 still fails, and which other rules do.
Related rules
- 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
- BR-DEX-13 Third party payment amount has at most 2 decimals
- BR-DEX-14 Third party payment must use the invoice currency