What it means
An electronic address in the invoice, such as the seller's (BT-34) or the buyer's (BT-49), states with a scheme code what kind of address it is. The code must be a single code from the CEF EAS list (Electronic Address Scheme) as 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 tells the recipient or the network how to read the address, for example as an email address or a GLN. 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 electronic address of the seller or buyer in your invoicing software. There is normally an address type or scheme next to it. Choose the code that matches the address, for example EM for an email address or 0088 for a GLN, and remove any spaces or extra text. If you are not sure which scheme the buyer uses, ask them.
The rule as published
Any scheme identifier for an Endpoint Identifier in MUST belong to the CEF EAS code 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-07 still fails, and which other rules do.
Related rules
- 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
- BR-DEX-13 Third party payment amount has at most 2 decimals