What it means
An identifier of a party in the invoice (for example the seller identifier BT-29, the buyer identifier BT-46 or the payee identifier BT-60) carries a scheme code 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 only other value allowed is SEPA, and only on the seller or the payee. 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 number, for example as a GLN or a DUNS number. With an unknown code the number cannot be interpreted, so the invoice fails validation and is rejected.
How to fix it
Find the identifier in the company or customer details of your invoicing software, where it usually has an ID type or scheme next to it. Choose the correct four-digit ICD code, for instance 0088 for a GLN or 0060 for a DUNS number, and make sure it is one code with no spaces or extra text. If you do not need the identifier, remove it.
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-04 still fails, and which other rules do.
Related rules
- BR-DEX-05 Company registration scheme must be an ISO 6523 code
- BR-DEX-06 Item identifier scheme must be an ISO 6523 code
- 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