# BR-CL-25: Electronic address scheme not in the EAS list

Source: https://veriport.io/einvoice-rules/br-cl-25 (published 2026-11-17)

The scheme of an electronic address, BT-34-1 or BT-49-1 (`schemeID` of `cbc:EndpointID` in UBL, of `ram:URIID` in CII), must come from the CEF EAS code list. Below: the message, the cause and the fix, and an invoice our validator checked, failing and fixed.

- **Specification:** [EN 16931 business rules](/einvoice-rules/en16931), CEN EN 16931 validation artefacts 1.3.16
- **Severity:** error
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-CL-25 is a rule of the EN 16931 business rules (CEN validation artefacts 1.3.16) for UBL and CII. It is an error (fatal): a validator rejects the invoice.

```text
[BR-CL-25]-Endpoint identifier scheme identifier MUST belong to the CEF EAS code list
```

## What it checks

The scheme of an electronic address, BT-34-1 or BT-49-1 (`schemeID` of `cbc:EndpointID` in UBL, of `ram:URIID` in CII), must come from the CEF EAS code list.

## Why invoices fail it

A label such as « email », « peppol » or « GLN » is written instead of the EAS code.

## How to fix it

Use the EAS code: EM for an e-mail address, 0088 GLN, 0204 Leitweg-ID, 0208 Belgian enterprise number, 9930 German VAT number, 9925 Belgian VAT number.

## A failing invoice and its fix, checked

We start from our sample invoice (two lines at 19 %, Berlin to Stuttgart), written by our own generator as EN 16931 in UBL. The change below (`-` the failing version, `+` the fixed one) makes the rule fail. Both versions went through our validator on 2026-11-17 (the XML schema and the official rule files, as `POST /einvoice/validate` runs them): the fixed one is valid, the failing one reports BR-CL-25.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-CL-25** | error | `/ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointID` | Endpoint identifier scheme identifier MUST belong to the CEF EAS code list |

```diff
  …
    <cac:AccountingSupplierParty>
      <cac:Party>
-       <cbc:EndpointID schemeID="email">rechnung@hartmann-webdesign.example</cbc:EndpointID>
+       <cbc:EndpointID schemeID="EM">rechnung@hartmann-webdesign.example</cbc:EndpointID>
        <cac:PostalAddress>
          <cbc:StreetName>Lindenstraße 14</cbc:StreetName>
  …
```

## The rule as published

Where the rule applies (`context`) and what must hold (`test`), unmodified from CEN EN 16931 validation artefacts 1.3.16. An `assert` fails when its test is false.

Text and test: © CEN/TC 434, EN 16931 validation artefacts, EUPL 1.2. Quoted unmodified; the explanations on this page are Veriport’s.

```xpath
context: cbc:EndpointID[@schemeID]
test:    ((not(contains(normalize-space(@schemeID), ' ')) and contains(' 0002 0007 0009 0037 0060 0088 0096 0097 0106 0130 0135 0142 0147 0151 0154 0158 0170 0177 0183 0184 0188 0190 0191 0192 0193 0194 0195 0196 0198 0199 0200 0201 0202 0203 0204 0205 0208 0209 0210 0211 0212 0213 0215 0216 0217 0218 0219 0220 0221 0225 0230 0235 0240 0244 0242 0245 0246 0248 9910 9913 9914 9915 9918 9919 9920 9922 9923 9924 9925 9926 9927 9928 9929 9930 9931 9932 9933 9934 9935 9936 9937 9938 9939 9940 9941 9942 9943 9944 9945 9946 9947 9948 9949 9950 9951 9952 9953 9957 9959 AN AQ AS AU EM ', concat(' ', normalize-space(@schemeID), ' '))))
```

```xpath
context: ram:URIUniversalCommunication/ram:URIID[@schemeID]
test:    ((not(contains(normalize-space(@schemeID), ' ')) and contains(' 0002 0007 0009 0037 0060 0088 0096 0097 0106 0130 0135 0142 0147 0151 0154 0158 0170 0177 0183 0184 0188 0190 0191 0192 0193 0194 0195 0196 0198 0199 0200 0201 0202 0203 0204 0205 0208 0209 0210 0211 0212 0213 0215 0216 0217 0218 0219 0220 0221 0225 0230 0235 0240 0244 0242 0245 0246 0248 9910 9913 9914 9915 9918 9919 9920 9922 9923 9924 9925 9926 9927 9928 9929 9930 9931 9932 9933 9934 9935 9936 9937 9938 9939 9940 9941 9942 9943 9944 9945 9946 9947 9948 9949 9950 9951 9952 9953 9957 9959 AN AQ AS AU EM ', concat(' ', normalize-space(@schemeID), ' '))))
```

## Check your own invoice

Drop your XRechnung, ZUGFeRD or Peppol file into a free validator ([Peppol BIS](/tools/peppol-validator), [XRechnung](/tools/xrechnung-pruefen), [Factur-X](/tools/valider-factur-x)): each runs the same rule files and links every finding to its rule page. From your own code, `POST /einvoice/validate` ([reference](/docs/einvoice)) returns the same check as JSON, each finding with an `explanation` field pointing here (5 calls a check, anonymous within the daily allowance).

## Read next

- [BR-CL-23: Unit code not UN/ECE Rec 20 or 21](https://veriport.io/einvoice-rules/br-cl-23)
- [BR-CL-24: Attachment MIME code not allowed](https://veriport.io/einvoice-rules/br-cl-24)
- [BR-CL-26: Delivery location scheme not ISO 6523](https://veriport.io/einvoice-rules/br-cl-26)
- [All EN 16931 business rules](https://veriport.io/einvoice-rules/en16931)
- [All e-invoice rules, search](https://veriport.io/einvoice-rules)
- [Check an e-invoice free (XRechnung prüfen)](https://veriport.io/tools/xrechnung-pruefen)
- [Create a valid e-invoice free (German form)](https://veriport.io/tools/e-rechnung-erstellen)

## Sources

- EN 16931 validation artefacts 1.3.16 (UBL and CII schematron, the business rules BR-*) — https://github.com/ConnectingEurope/eInvoicing-EN16931/releases/tag/validation-1.3.16 (2026-10-28)
- EN 16931 validation artefacts: licence, European Union Public Licence (EUPL) v1.2 (LICENSE.txt, the README « License » section and the release notes of validation-1.3.16) — https://github.com/ConnectingEurope/eInvoicing-EN16931/blob/master/LICENSE.txt (2026-11-17)
