Article 69 of the UAE VAT Decree-Law requires that where a Tax Invoice is issued in a currency other than UAE dirhams, the exchange rate used to convert the consideration to AED must be the rate published by the UAE Central Bank on the date of supply. Under the UAE Electronic Invoicing System, this obligation becomes a structured data requirement embedded in the PINT-AE specification through a set of mandatory UAE extension fields. For multi-currency businesses — UAE exporters billing in USD, EUR, GBP, or other currencies, and multinationals with UK, European, or Indian parent companies that invoice UAE subsidiaries in non-AED currencies — this is one of the most technically specific data obligations in the PINT-AE standard.

The Legal Basis: Article 69 of the VAT Decree-Law

Article 69 applies where a supply is made and invoiced in a currency other than UAE dirhams. The rule requires the value of the supply to be expressed in AED using the exchange rate published by the Central Bank of the UAE on the date of supply. The "date of supply" is the tax point under UAE VAT — typically the earlier of the date of supply and the date of payment — which is the same as the Date of Business Transaction under MD 243.

This rule existed before the e-invoicing mandate, but its enforcement was largely retrospective — visible only when the FTA audited the VAT return and compared the AED values declared against the Central Bank rate. Under electronic invoicing, the AED equivalent amounts are transmitted to Corner 5 at the point of invoice exchange, creating a real-time audit trail that the FTA can compare against the published Central Bank rate data for that date. The enforcement mechanism changes from retrospective audit to real-time data matching.

The PINT-AE Fields That Implement the Obligation

BTAE-04 — The Exchange Rate Field

BTAE-04 is the UAE extension field for the Central Bank exchange rate. It carries the rate used to convert the invoice currency to AED, expressed as the number of AED per one unit of the foreign currency (e.g., 3.6725 for USD/AED at the official peg rate, or the daily published rate for other currencies). The BTAE-04 field must appear in the PricingExchangeRate block of the UBL 2.1 XML, which is a specific structural wrapper that does not exist in standard ERP invoice output. Where an invoice is issued in AED, BTAE-04 is not required — it applies only to invoices in currencies other than AED.

BTAE-08 and BTAE-10 — AED Equivalent Line Amount Fields

BTAE-08 is the AED equivalent of the line net amount — the line-level supply value converted to AED using BTAE-04. BTAE-10 is the AED equivalent of the line gross amount including VAT. These fields appear at the invoice line level and must be calculated using the BTAE-04 rate. The schematron validation rules for these fields (the ibr-co-* calculation rules) verify that BTAE-08 equals the line net amount multiplied by BTAE-04, and that BTAE-10 equals the line gross amount multiplied by BTAE-04. Rounding errors in these calculations — which are common where ERP systems use different rounding conventions for currency conversion — produce schematron failures.

BTAE-20 and IBT-111 — AED Equivalent Tax Amount Fields

BTAE-20 is the AED equivalent of the tax amount at the document level. IBT-111 is the standard PINT field for the tax amount in accounting currency (AED) at the document level. Both must be present and consistent on non-AED invoices. The relationship between BTAE-04, BTAE-08, BTAE-10, BTAE-20, and IBT-111 is governed by a cascade of schematron calculation rules that must all pass simultaneously.

The Central Bank Rate Source and Daily Publication

The UAE Central Bank publishes daily exchange rates on its website. The rates are published for the foreign currencies most commonly traded in the UAE. For currencies with a direct USD-AED peg relationship (such as some GCC currencies), the calculation involves a cross-rate methodology. For currencies not directly quoted by the Central Bank, the methodology for deriving the AED equivalent must be documented and consistently applied.

The operational implication is that the business must establish a daily Central Bank rate feed that: retrieves the published rates from the Central Bank on each business day, stores the rates by date in a system accessible to the invoice generation process, applies the rate published on the date of supply (not the date of invoice generation, and not an average or spot rate from a commercial provider), and populates BTAE-04 with that rate for every non-AED invoice generated on that date.

This rate feed must be designed with resilience. If the Central Bank rate is unavailable on a given day — due to a public holiday, a website outage, or a data extraction failure — the invoice generation process must handle that gracefully, either by holding the invoice until the rate is available or by using the most recently published rate with a documented exception process. The penalty for missing the 14-day issuance window while waiting for a rate does not disappear because the Central Bank's website was down.

The Date of Supply vs Date of Invoice

One of the most operationally significant points in the exchange rate obligation is which date determines the applicable rate. Article 69 requires the Central Bank rate on the date of supply. The Date of Business Transaction under MD 243 is the earlier of the date of the transaction or the date of receipt of payment. These two dates may differ.

Where a supply occurs on 15 January and payment is received on 1 February, the Date of Business Transaction is 15 January, and the BTAE-04 rate should be the Central Bank rate published on 15 January. Where an advance payment is received on 1 January for a supply that occurs on 15 January, the Date of Business Transaction is 1 January (the earlier date), and BTAE-04 should use the 1 January rate. The ERP must be configured to use the date of supply — or the earlier payment date where applicable — as the rate lookup date, not the billing document date or the accounting posting date.

ERP Configuration Requirements

For SAP S/4HANA, the exchange rate mechanism for standard invoices uses the OB08 exchange rate table, which stores rates by type (M for average, P for bank selling rate, etc.) and by date. The PINT-AE Central Bank rate requirement is not served by the standard SAP exchange rate types because these pull from commercial rate providers or from internally maintained rates, not from the UAE Central Bank's published daily rates. A custom exchange rate type and a custom rate feed from the UAE Central Bank are typically required.

For Oracle Fusion, the GL daily rates table holds exchange rates by date and currency pair. The UAE Central Bank rate must be loaded into this table daily through an automated integration from the Central Bank's published source. The invoice generation process must be configured to use this specific rate type rather than the default corporate treasury rate.

Practitioner Insight: The exchange rate obligation exposes a systemic risk in multi-currency businesses that use their treasury or group finance rate for intercompany and external invoicing — rather than the Central Bank published rate. The treasury rate is appropriate for management accounting; it is not compliant for UAE VAT invoice purposes. Businesses that have been using treasury or spot market rates rather than the Central Bank rate have a pre-existing VAT compliance issue that e-invoicing makes visible to the FTA in real time. The compliance programme should surface and resolve this before go-live, not after.

Cross-Rate Methodology for Non-Standard Currencies

For currencies not directly quoted by the UAE Central Bank against AED, a cross-rate methodology is required. The standard approach is: (1) obtain the Central Bank rate for the currency against USD, (2) apply the USD/AED rate (3.6725, the official peg) to derive the currency/AED cross-rate. For example, for a EUR invoice: if the Central Bank EUR/USD rate is 1.0850, then the EUR/AED rate is 1.0850 × 3.6725 = 3.9847. This cross-rate methodology must be documented, consistently applied, and embedded in the rate feed mechanism — it cannot be left to ad-hoc calculation at the point of invoice generation.

Preparing the Exchange Rate Data Architecture

The complete exchange rate data architecture for UAE PINT-AE compliance has five components: a daily automated feed from the UAE Central Bank's published rates, a structured storage mechanism that holds rates by currency pair and by date, a rate lookup function that retrieves the correct rate for the Date of Business Transaction for each invoice, a cross-rate calculation mechanism for currencies not directly quoted, and a data quality monitoring process that alerts the business to missing or anomalous rate data before invoice generation runs.

For UK, EU, and Indian multinationals with UAE entities, the exchange rate architecture is likely maintained centrally by a group treasury function that uses a commercial rate feed. Adapting that architecture to incorporate the UAE Central Bank requirement — and ensuring the UAE entity's invoices use the Central Bank rate rather than the group treasury rate — requires specific configuration and, in most cases, a coordination conversation between the UAE tax team and the group treasury and ERP teams.