BT-5Invoice currency code
Official rule text
[BR-05] An Invoice shall have an Invoice currency code (BT-5).
Why this error occurs
The rule checks that the invoice currency is stated: cbc:DocumentCurrencyCode in UBL, ram:ApplicableHeaderTradeSettlement/ram:InvoiceCurrencyCode in CII. All amounts in the document are interpreted in this currency and, in UBL, every currencyID attribute must match it. The element is usually missing when the export assumes EUR implicitly or the ERP mapping leaves the currency field unmapped.
How to fix it
In UBL add cbc:DocumentCurrencyCode after cbc:InvoiceTypeCode (and cbc:Note, if present). In CII add ram:InvoiceCurrencyCode inside ram:ApplicableHeaderTradeSettlement, before the payment and tax elements. Use an ISO 4217 alpha-3 code in upper case, e.g. EUR, USD, GBP, CHF; never a symbol or a numeric code. Make sure the same code is used in all currencyID attributes of the amounts.
Example (valid)
<cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>
What the validator checks
Checked element (context):
UBL
/ubl:Invoice | /cn:CreditNoteTest (XPath):
normalize-space(cbc:DocumentCurrencyCode) != ''CII
/rsm:CrossIndustryInvoiceTest (XPath):
normalize-space(rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:InvoiceCurrencyCode) != ''
Check your invoice
Drop your XML or PDF on the validator and every failed rule is linked to its page here. Free, no account, the file is not stored.
Same check via API:
curl -F file=@invoice.xml https://einvoicechecker.com/v1/validateRelated rules
BR-01Specification identifier (BT-24) is missingBR-02Invoice number (BT-1) is missingBR-03Invoice issue date (BT-2) is missingBR-04Invoice type code (BT-3) is missingBR-06Seller name (BT-27) is missingBR-07Buyer name (BT-44) is missingBR-08Seller postal address is missingBR-09Seller country code (BT-40) is missing
Frequently asked questions
What does BR-05 mean?
BR-05 is a en 16931 core rule: An Invoice shall have an Invoice currency code (BT-5).
Will my invoice be rejected because of BR-05?
Yes. BR-05 is flagged "fatal"; validators (KoSIT, Peppol access points, the German ZRE/OZG-RE portals) reject the invoice until it is fixed.
Which formats does BR-05 apply to?
Every EN 16931 invoice: XRechnung, ZUGFeRD 2.x / Factur-X (profiles EN 16931, EXTENDED, XRECHNUNG), Peppol BIS Billing 3.0, and national CIUS such as the Dutch NLCIUS or the Italian/Spanish profiles. Syntax: UBL and CII.
Source: EN 16931-1:2017 schematron (CEN TC434, via Peppol BIS 3.0.20). Catalogue generated from the official schematron on 2026-10-14.