Rule at a Glance

ID Severity Context (XPath)
BR-05 Fatal (error) ubl:Invoice
Series reference: BR-05  |  Schematron ID: ibr-005

Classification

Transaction Data — The invoice currency code is a transaction-level field that identifies the currency in which all monetary amounts on the invoice are expressed.

What the Rule Is Checking

BR-05 requires that every invoice contains a non-empty cbc:DocumentCurrencyCode element at the invoice header level. This is BT-5 in the PINT-AE data model — the Invoice currency code. The element must be present and must contain a valid ISO 4217 three-letter alphabetic currency code. The rule fails fatally if the element is absent or empty.

BT-5 declares the currency in which all invoice amounts — line totals, VAT amounts, and the payable amount — are denominated. It applies to the entire invoice. Where a foreign currency invoice is issued, BT-5 carries the foreign currency code (e.g., USD, EUR, GBP) and the AED equivalent must be provided through the Central Bank exchange rate field (BTAE-04) — a separate UAE-specific obligation.

Why This Rule Exists

VAT in the UAE is calculated and reported in AED. Where invoices are issued in foreign currencies, Article 69 of the UAE VAT Decree-Law requires conversion at the Central Bank of UAE published rate on the date of supply. The invoice currency code (BT-5) is the starting point for that calculation: without it, the FTA's data platform cannot determine whether the amounts on the invoice are already in AED or require conversion.

For international supply chains — where a UAE entity invoices a GCC or EU customer in USD or EUR — BT-5 signals to the receiving ASP and the FTA that the monetary amounts are in a non-AED currency and that BTAE-04 must also be present. This makes BR-05 a gateway rule for a chain of downstream currency validation requirements. See also: BTAE-04 Exchange Rate Obligation.

Standard / Code List

BT-5 must contain a valid ISO 4217 alphabetic currency code. The most common values in UAE invoicing are:

CodeCurrencyAED conversion required?
AEDUAE DirhamNo
USDUS DollarYes — BTAE-04 required
EUREuroYes — BTAE-04 required
GBPPound SterlingYes — BTAE-04 required
SARSaudi RiyalYes — BTAE-04 required

For the full ISO 4217 reference in the context of PINT-AE, see ISO 4217 Currency Codes in UAE E-Invoicing.

UAE Data Example

PASSES ✓ — AED invoice (no conversion needed):
<cbc:DocumentCurrencyCode>AED</cbc:DocumentCurrencyCode>

PASSES ✓ — USD invoice (BTAE-04 must also be present):
<cbc:DocumentCurrencyCode>USD</cbc:DocumentCurrencyCode>

FAILS ✗ — Element absent:
<!-- No cbc:DocumentCurrencyCode present -->

FAILS ✗ — Numeric ISO 4217 code instead of alphabetic:
<cbc:DocumentCurrencyCode>784</cbc:DocumentCurrencyCode>

FAILS ✗ — Currency name instead of code:
<cbc:DocumentCurrencyCode>UAE Dirham</cbc:DocumentCurrencyCode>

FAILS ✗ — Empty element:
<cbc:DocumentCurrencyCode></cbc:DocumentCurrencyCode>

What Your ERP / IT Team Must Ensure

  • The ERP currency code stored against each transaction must map to the ISO 4217 alphabetic code — ERP systems that store numeric currency codes (e.g., SAP uses numeric codes internally) must translate to the alphabetic code before UBL output.
  • Where BT-5 is not AED, the mapping layer must also populate BTAE-04 (the Central Bank of UAE exchange rate) with the rate published on the invoice issue date. Omitting BTAE-04 on a non-AED invoice will cause a UAE-specific fatal rule to fail.
  • The tax amounts in cac:TaxTotal and the payable amount in cac:LegalMonetaryTotal/cbc:PayableAmount must be expressed in the currency declared in BT-5 — not in AED — even though VAT is ultimately accounted for in AED. The AED equivalent is calculated by the system using BTAE-04, not by converting the invoice amounts.
  • Multi-currency ERP environments must ensure that the transaction currency — not the company code currency or the reporting currency — is used for BT-5.

Related Rules

BR-04 (Invoice type code), ISO 4217 Currency Codes in UAE E-Invoicing, BTAE-04 Exchange Rate Obligation