What does BR-CL-5 mean?
BT-6 gives the currency in which VAT is additionally reported. It too must be an ISO 4217 code.
Common causes of BR-CL-5
- The field holds a currency name ('Euro') instead of the ISO code.
- Wrong spelling such as 'EURO' or lower case letters.
- The field carries an invalid value although VAT currency and invoice currency are the same.
How to fix BR-CL-5
- Find the faulty spot in the XML. Open the XML of the invoice and go to field BT-6 along this XPath:
//ram:ApplicableHeaderTradeSettlement/ram:TaxCurrencyCode - Apply the fix. Code the VAT accounting currency (BT-6) with an ISO 4217 alpha-3 code, e.g. 'EUR', 'USD', 'GBP', 'CHF', 'DKK'. Exactly three capital letters, no name, no symbol.
- Validate again. Save the file and validate it again to check that BR-CL-5 is no longer reported.
Code the VAT accounting currency (BT-6) with an ISO 4217 alpha-3 code, e.g. 'EUR', 'USD', 'GBP', 'CHF', 'DKK'. Exactly three capital letters, no name, no symbol.
//ram:ApplicableHeaderTradeSettlement/ram:TaxCurrencyCodeBefore / after: the XML example
This is the spot in question before and after the fix (Cross Industry Invoice, ZUGFeRD/Factur-X).
<ram:ApplicableHeaderTradeSettlement>
<ram:TaxCurrencyCode>EURO</ram:TaxCurrencyCode>
</ram:ApplicableHeaderTradeSettlement>
<ram:ApplicableHeaderTradeSettlement>
<ram:TaxCurrencyCode>EUR</ram:TaxCurrencyCode>
</ram:ApplicableHeaderTradeSettlement>
Frequent questions about BR-CL-5
When do I need the VAT accounting currency (BT-6) at all?
Does BT-6 use the same code list as the invoice currency?
Related error codes
Check BR-CL-5 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.