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
- Plain text such as 'EMAIL' or 'GLN' entered in @schemeID instead of the EAS code.
- Mixed up with ISO 6523 ICD; the endpoint address needs the CEF EAS list.
- @schemeID is missing entirely although an electronic address (URIID) is given.
How to fix BR-CL-25
- 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 - 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).
- Validate again. Save the file and validate it again to check that BR-CL-25 is no longer reported.
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).
//ram:SellerTradeParty/ram:URIUniversalCommunication/ram:URIID/@schemeIDBefore / after: the XML example
This is the spot in question before and after the fix (Cross Industry Invoice, ZUGFeRD/Factur-X).
<ram:URIUniversalCommunication>
<ram:URIID schemeID="MAIL">info@verkaeufer.de</ram:URIID>
</ram:URIUniversalCommunication>
<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?
How does this differ from the deliver to location scheme (BR-CL-26)?
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.