HomeError code lexicon › BR-CL-25
BR-CL-25 Field BT-34-1 Code list rules (BR-CL)

Fix BR-CL-25: Electronic address scheme invalid (EAS)

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

BR-CL-25 in your own invoice? Upload the file and find every error in seconds.

What does BR-CL-25 mean?

The electronic address (endpoint) of the seller or buyer needs a scheme from the CEF EAS code list so the invoice can be routed.

Common causes of BR-CL-25

How to fix BR-CL-25

  1. Find the faulty spot in the XML. Open the XML of the invoice and go to field BT-34-1 along this XPath://ram:SellerTradeParty/ram:URIUniversalCommunication/ram:URIID/@schemeID
  2. Apply the fix. State the scheme of the electronic address of the seller (BT-34-1) or buyer (BT-49-1) in the @schemeID attribute with a code from the CEF EAS code list (Electronic Address Scheme), e.g. '0204' (Leitweg-ID), '9930' (German VAT identifier), '0088' (GLN), '0060' (DUNS), 'EM' (e-mail).
  3. Validate again. Save the file and validate it again to check that BR-CL-25 is no longer reported.
Concrete fix

State the scheme of the electronic address of the seller (BT-34-1) or buyer (BT-49-1) in the @schemeID attribute with a code from the CEF EAS code list (Electronic Address Scheme), e.g. '0204' (Leitweg-ID), '9930' (German VAT identifier), '0088' (GLN), '0060' (DUNS), 'EM' (e-mail).

XPath//ram:SellerTradeParty/ram:URIUniversalCommunication/ram:URIID/@schemeID

Before / after: the XML example

This is the spot in question before and after the fix (Cross Industry Invoice, ZUGFeRD/Factur-X).

Wrong
<ram:URIUniversalCommunication>
  <ram:URIID schemeID="MAIL">info@verkaeufer.de</ram:URIID>
</ram:URIUniversalCommunication>
Correct
<ram:URIUniversalCommunication>
  <ram:URIID schemeID="EM">info@verkaeufer.de</ram:URIID>
</ram:URIUniversalCommunication>

Frequent questions about BR-CL-25

Which code do I use for an e-mail address?
The EAS code 'EM'. For a Leitweg-ID use '0204', for a GLN '0088' and for the German VAT identifier as endpoint '9930'.
How does this differ from the deliver to location scheme (BR-CL-26)?
The endpoint address uses the CEF EAS list, the delivery location identifier uses the ISO 6523 ICD list. The two overlap in many codes but are maintained separately.

Related error codes

Check BR-CL-25 automatically

Instead of digging through the XML by hand you can validate your ZUGFeRD or XRechnung file online – upload the PDF or the XML and you get every error with rule ID, affected field, fix and XPath, as a readable report or as JSON through the API.

Find every error automatically instead of searching by hand

Upload your ZUGFeRD, Factur-X or XRechnung file – you get every violation back with rule ID, field, fix and XPath.

Validate online for free
Check invoice