What it means
A legal registration identifier of a party (for example the seller's company number BT-30 or the buyer's BT-47) carries a scheme code, such as BT-30-1, that says which register the number comes from. The code must be a single code from the ISO 6523 ICD list used by the XRechnung extension, with no spaces. Unlike the party identifier rule BR-DEX-04, SEPA is not allowed here. 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 which register the company number belongs to. A code that is not on the list cannot be interpreted, so the invoice fails validation and is rejected.
How to fix it
Find the company registration number in the company details of your invoicing software and check its type or scheme. Pick the four-digit ICD code for the register the number comes from, for example 0002 for a French SIREN number or 0106 for a Dutch KvK number, and remove any spaces or extra text. If you do not need the registration number on the invoice, 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-05 still fails, and which other rules do.
Related rules
- 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
- BR-DEX-11 Third party payment needs an amount