Rule at a Glance
| ID | Severity | Context (XPath) |
|---|---|---|
| Series ref. BR-85 | Fatal (error) | /ubl:Invoice | /cn:CreditNote |
| Schematron ID: ibr-159-ae | Field: BTAE-04 — Currency exchange rate | ||
Classification
Contextual — a field that becomes mandatory only once a preceding value (the invoice currency code) takes a particular condition.
What the Rule Is Checking
The assert reads: if the Invoice currency code (ibt-005) is anything other than AED, the currency exchange rate (BTAE-04) must exist somewhere on the document. Where the invoice is already denominated in AED, the field is not required at all — there is nothing to convert.
Why This Rule Exists
The FTA's VAT reporting obligation is always expressed in AED, regardless of what currency a business bills its customer in. A UAE exporter invoicing a European buyer in EUR still has to report a VAT-exclusive and VAT-inclusive amount in AED, and that figure only exists if an exchange rate is captured at the point the invoice is issued. Without BTAE-04 on the document, the AED figures the authority actually cares about cannot be reconstructed later without going back to the transaction's original booking rate — which defeats the purpose of the invoice being the authoritative record.
This is also where a business relying on informal, end-of-month exchange rate conversions for management accounts runs into a structural mismatch. E-invoicing forces the rate to be fixed and transmitted at the transaction level, not applied retrospectively in bulk during period-end close.
Standard / Code List
Related rule ibr-002-ae caps the exchange rate at six decimal places. ibr-153-ae adds a further constraint: where the tax accounting currency is AED and the document currency differs, the source and target currencies on the pricing exchange rate block must map correctly to the document currency and AED respectively. ibr-140-ae separately requires that the VAT accounting currency, where present, is always AED.
UAE Data Example
PASSES ✓ — a EUR invoice with the rate captured:
<cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>
<cac:PricingExchangeRate>
<cbc:SourceCurrencyCode>EUR</cbc:SourceCurrencyCode>
<cbc:TargetCurrencyCode>AED</cbc:TargetCurrencyCode>
<cbc:CalculationRate>3.986521</cbc:CalculationRate>
</cac:PricingExchangeRate>FAILS ✗ — a USD invoice with no rate block at all, common where an ERP's export configuration was built before e-invoicing went live:
<cbc:DocumentCurrencyCode>USD</cbc:DocumentCurrencyCode>
<!-- no cac:PricingExchangeRate present -->What Your ERP / IT Team Must Ensure
- Confirm the ERP's PINT-AE export routine populates the exchange rate block automatically for every non-AED document currency, rather than relying on manual entry.
- Source the rate from the Central Bank of the UAE's published rate for the transaction date, not an internally negotiated or averaged rate, to keep the AED figures defensible.
- Cap the rate field to six decimal places at generation time so ibr-002-ae doesn't reject an otherwise valid invoice on formatting alone.
- Test every foreign-currency price list or customer group separately — a gap here typically surfaces only for the currencies a business rarely bills in, which are exactly the ones least likely to be caught in initial testing.
Related Rules
ibr-002-ae limits the exchange rate to six decimal places. ibr-140-ae requires the VAT accounting currency, where present, to be AED. ibr-153-ae governs the source/target currency mapping when the tax accounting currency is AED and the document currency differs. ibr-175-ae requires the AED-equivalent VAT totals once the invoice currency isn't AED but the tax accounting currency is.