BR-CL-04: Currency must use an ISO currency code

What the rule says

[BR-CL-04]-Invoice currency code MUST be coded using ISO code list 4217 alpha-3

Official en16931 source, version 1.3.16. EUPL 1.2; sources, licences and notices. Syntax and business checks are separate; this is not certification.

Currency must use an ISO currency code

Currency must use an ISO currency code. The controlled example changes the specific field or group named by this rule. Set only /*/cbc:DocumentCurrencyCode to 'ZZZ'.

Business terms: No explicit BT number in the official rule text; use the XML context below.

Use the actual ISO 4217 alpha-3 currency and keep amount currencies consistent.

Reproduced failure and correction

Tested on 2 November 2026 with the production SaxonC-HE 13.1 / saxonche 13.1.1 engine, en16931 mode, UBL. The XSD passes; the report then contains BR-CL-04. Restoring this fragment makes the complete original invoice pass the selected checks.

[BR-CL-04]-Invoice currency code MUST be coded using ISO code list 4217 alpha-3

Additional triggered rules: 1. BR-CO-15. Counts include distinct error and warning codes; the target code is excluded.

Precise mutated XPath: /*/cbc:DocumentCurrencyCode.

Before: triggers this rule

<ns0:DocumentCurrencyCode xmlns:ns0="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">ZZZ</ns0:DocumentCurrencyCode>
    

After: passes

<ns0:DocumentCurrencyCode xmlns:ns0="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">EUR</ns0:DocumentCurrencyCode>
    

The context shown is part of a complete invoice; it is not a standalone invoice. Mutation: value at /*/cbc:DocumentCurrencyCode. The passing baseline is validated with the selected pinned package. UBL examples use a controlled single-line adaptation of the official XRechnung example; the CII example uses the official EN 16931 baseline.

Download complete failing invoice · Download complete passing invoice

Check your corrected invoice →

Check the rest of the invoice

Repair the source data and exporter, then validate the complete invoice again with the same package. Review every remaining error and warning; a passing rule is not a guarantee of recipient acceptance.

EN 16931 syntax and business checks · XRechnung profile requirements · Pro/Team batch checks.