BR-CL-4 in your own invoice? Upload the file and find every error in seconds.
What does BR-CL-4 mean?
BT-5 sets the currency of the whole invoice. EN 16931 requires an ISO 4217 alpha-3 code - the basis all amounts follow.
Common causes of BR-CL-4
- The field holds a currency name ('Euro') or symbol instead of the code.
- Wrong length or spelling such as 'EURO' or 'eur'.
- A non-existent or outdated currency code was used.
How to fix BR-CL-4
- Find the faulty spot in the XML. Open the XML of the invoice and go to field BT-5 along this XPath:
//ram:ApplicableHeaderTradeSettlement/ram:InvoiceCurrencyCode - Apply the fix. Code the invoice currency (BT-5) with an ISO 4217 alpha-3 code, e.g. 'EUR', 'USD', 'GBP', 'CHF', 'SEK'. Exactly three capital letters, no name, no symbol.
- Validate again. Save the file and validate it again to check that BR-CL-4 is no longer reported.
Concrete fix
Code the invoice currency (BT-5) with an ISO 4217 alpha-3 code, e.g. 'EUR', 'USD', 'GBP', 'CHF', 'SEK'. Exactly three capital letters, no name, no symbol.
XPath
//ram:ApplicableHeaderTradeSettlement/ram:InvoiceCurrencyCodeBefore / after: the XML example
This is the spot in question before and after the fix (Cross Industry Invoice, ZUGFeRD/Factur-X).
Wrong
<ram:ApplicableHeaderTradeSettlement>
<ram:InvoiceCurrencyCode>Euro</ram:InvoiceCurrencyCode>
</ram:ApplicableHeaderTradeSettlement>
Correct
<ram:ApplicableHeaderTradeSettlement>
<ram:InvoiceCurrencyCode>EUR</ram:InvoiceCurrencyCode>
</ram:ApplicableHeaderTradeSettlement>Frequent questions about BR-CL-4
Must the invoice currency match the amounts?
Yes. The invoice currency (BT-5) sets the currency that the @currencyID attributes of the amounts must match.
Can I issue an invoice in a currency other than euro?
Yes, any currency listed in ISO 4217 is allowed, e.g. 'USD' or 'CHF'. What matters is the correct three-letter code.
Related error codes
Check BR-CL-4 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.