Multi Currency E-Invoicing UAE: Getting the Foreign Currency AED Line Right

Multi currency e-invoicing in the UAE lets you keep invoicing in USD, EUR or SAR while carrying a mandatory AED equivalent. Article 69 of the VAT Decree-Law fixes that conversion to the Central Bank of the UAE rate approved on the date of supply — not your bank’s deal rate, and not a month-end average.

Multi currency e-invoicing UAE: the verified rules

Last verified: 3 August 2026 against the FTA legislation library and Ministry of Finance decisions. Deadlines have moved before — check the primary text before you commit a go-live plan.

Related reading: VAT credit note UAE for foreign-currency credit notes, multi-currency invoicing UAE FX policy for the commercial policy side, multi-currency business account UAE for where the spread actually costs you, dropshipping accounting UAE for cross-border e-commerce postings, and DMCC free zone if you invoice from a free zone licence.

Foreign-currency invoicing is everyday reality for UAE SMEs. A Dubai trading company invoicing a German buyer issues in EUR. A free-zone consultancy serving a US client invoices in USD. A logistics group settling intercompany freight with a Saudi parent uses SAR. Under the UAE e-invoicing mandate, confirmed by Ministerial Decisions 243 and 244 of 2025 and the penalty schedule in Cabinet Decision 106 of 2025, every one of those invoices must continue in its foreign currency while also carrying a fully reconciled AED line for FTA reporting.

This guide explains how multi-currency invoicing actually works under PINT AE — which currencies are permitted, where the AED equivalent comes from, how the Central Bank of the UAE daily rate fits into the workflow, rounding tolerances, and how credit notes handle historical FX rates. If you would rather have this configured for you end-to-end, our e-invoicing setup support in the UAE covers the FX feed, the date-of-supply rate lock and the AED reconciliation as one workstream.

How e-invoicing multi currency works in the UAE

E-invoicing multi currency in the UAE comes down to one principle: you keep trading in whatever currency your buyer pays in, and the system attaches an AED shadow to every figure. Nothing about the UAE e-invoicing mandate forces you to switch your commercial pricing to dirhams. What it does is make the AED equivalent a structured, machine-readable part of the invoice rather than a note in the corner.

The workflow runs in a fixed order. The invoice is raised in the document currency — USD, EUR, GBP, SAR or any other ISO 4217 code. The accounting system reads the Central Bank of the UAE reference rate for that exact issue date. Each monetary value is converted and written back as a second AED figure. The Accredited Service Provider then validates that the two sets of numbers agree before the invoice reaches the buyer and the FTA feed.

For an SME with a handful of foreign clients, this is a one-time configuration job, not a daily chore. Once the rate feed and the invoice-date lock are in place, multi-currency invoices behave exactly like AED ones. The failure cases almost always trace back to a missing feed, a hand-keyed rate, or a system that stores only the foreign-currency amount and leaves the AED line blank.

Can I still invoice in USD or EUR under PINT AE?

The Peppol International UAE invoice specification follows the global PINT base on currency handling, with one UAE-specific layer added: every monetary value on the invoice must be reported in AED equivalent, even when the document currency is something else.

PINT AE uses two header fields to drive this:

• DocumentCurrencyCode — the currency the buyer pays in (e.g. USD, EUR, GBP, SAR)
• TaxCurrencyCode — for UAE invoices this is fixed at AED

When these two codes differ, the invoice must include an FX rate field and an AED-equivalent line for every monetary value. The validation engine in your ASP will reject any invoice where the document currency is non-AED and the AED reporting line is missing.

This isn’t a translation the FTA does for you afterwards. The AED line has to be on the invoice when the ASP transmits it.

Which FX rate the FTA actually accepts

The FTA standardises on one source: the Central Bank of the UAE daily exchange reference rates, published every UAE working day at the CB UAE website. This is the same central bank exchange rate for UAE VAT that already governs VAT return conversion, so the AED line on your e-invoice and the AED figures on your VAT-201 draw from one authoritative feed. The rates are mid-rates between AED and the major trading currencies, fixed against the AED peg to the US dollar at 3.6725.

In practice that plays out simply enough. On a working day you take the CB UAE rate for the invoice issue date. On a weekend or UAE public holiday you fall back to the most recent published rate — typically the previous Friday’s for a Saturday or Sunday invoice. And for a currency the CB UAE doesn’t quote directly, you cross-rate through USD, using the CB UAE USD rate as your anchor.

The fixed AED-to-USD peg simplifies one corner: invoices in USD reduce to a straight 3.6725 multiplication. Every other currency requires the published cross-rate.

One point of vocabulary, because it derails scoping calls more often than it should. The currency conversion your accounting system performs for the AED line is a reporting exercise, not a treasury one. The foreign exchange rate you actually transact at when the money lands — your bank’s spread, a forward you booked, a hedge that matured — belongs in your books as a realised gain or loss on settlement. It never touches the invoice. Businesses running a multi-currency bank account in the UAE sometimes assume the account’s own conversion rate should feed the AED figures, since that is the rate they can see. It should not. The Central Bank exchange rate for the date of supply drives the AED line whatever happens to the cash afterwards.

The five currencies most UAE SME flows run through

The same five currencies account for the bulk of foreign-currency invoicing out of Dubai, and each behaves slightly differently against the dirham:

Other currencies — JPY, CHF, AUD, ZAR, CNY — are less common but follow the same rule. Where CB UAE does not publish a direct rate, cross through USD.

Rounding and decimal precision

PINT AE applies tight rounding tolerances. The working convention across implementations is:

• Line amounts (foreign currency): 2 decimal places
• Line amounts (AED equivalent): 2 decimal places
• Tax amounts (foreign currency): 2 decimal places
• Tax amounts (AED equivalent): 2 decimal places
• FX rate field: carried at the precision the Central Bank publishes, so the AED amounts can be reproduced from the rate shown
• Document totals: 2 decimal places

The validation engine reconciles the VAT totals within a tight tolerance — in the Peppol/EN 16931 model PINT AE builds on, that is 0.02 per tax category. Larger differences trigger rejection.

The classic rejection is a cascading rounding error, and it’s a subtle one. The foreign-currency line totals come out right, get converted to AED at full rate precision, and then the AED subtotals are summed before anyone rounds them. Do it the other way: round each AED amount line-by-line first, then add the rounded values. That order is the whole game.

Example: a USD 12,000 invoice on a UAE working day

A Dubai consultancy invoices a US client USD 12,000 for advisory services on 15 July 2026. Standard rate VAT applies.

FX rate field: 3.672500 (fixed USD/AED peg)

The PINT AE XML carries both columns. The document currency is USD; the tax currency is AED. The buyer pays USD 12,600; the FTA reports VAT output of AED 2,203.50.

If the consultancy’s accounting system pulls the bank’s deal rate of, say, 3.6650 (with a small spread), the AED VAT output reports as AED 2,199.00 — a tiny gap that compounds across hundreds of invoices into thousands of dirhams of unreported output VAT. The validation engine accepts the lower number but the FTA reconciliation catches it.

“

For USD invoices the rate is fixed forever. For every other currency, the difference between yesterday’s rate and today’s rate sits in your output VAT total — and the FTA sees both.

Foreign currency invoice UAE VAT: how the tax line is treated

A foreign currency invoice under UAE VAT still carries a full tax line, and that line is always calculated and reported in AED. Whether you bill in USD, EUR or SAR, the output VAT figure the FTA holds is the AED conversion at the Central Bank reference rate for the invoice date — the document-currency amount is for your buyer, the AED amount is for the return.

This matters because VAT is charged on the place of supply, not the currency of settlement. A standard-rated supply to a UAE customer stays standard-rated whether it is billed in dirhams or dollars. Invoicing in a foreign currency never changes the VAT treatment; it only changes which conversion rate feeds the tax line. The same rate rule that governs your VAT return filing governs the invoice: one authoritative source, applied consistently.

For the buyer, the AED VAT figure on your invoice is what they recover as input tax — not the amount their own bank charged them on the day they paid. If your AED line drifts from the Central Bank rate, their input VAT and your output VAT stop matching, and the gap surfaces in the FTA’s cross-checks. Getting the tax invoice requirements right on the AED line is what keeps both sides reconciled.

Do foreign-currency exports still charge UAE VAT?

Plenty of foreign-currency invoices go to overseas customers, which raises a separate question from the FX rate: is the supply standard-rated, zero-rated or outside scope? Billing a client in USD does not by itself zero-rate the invoice. The treatment depends on the nature of the supply and where the customer belongs, under the export rules in the VAT Executive Regulations to Federal Decree-Law 8 of 2017.

An export of goods outside the GCC implementing states, or a qualifying export of services to a recipient who has no place of residence in the UAE and is outside the country when the service is performed, can be zero-rated where the specific conditions are met. Where they are not, the supply is standard-rated at 5% even though the buyer is abroad and paying in a foreign currency. The distinction is worth confirming case by case, because reading it wrong understates or overstates output VAT.

On a PINT AE invoice this shows up as the tax category and rate applied to each line, alongside the AED conversion covered above. A zero-rated export still needs its AED-equivalent line; the rate is simply 0%. For the detail on how these invoices are built, see our guides on the zero-rated export e-invoice format and zero-rated versus exempt supplies.

Credit notes reuse the original FX rate

When a credit note is issued against an earlier invoice, PINT AE requires the credit note to reference the original invoice number and use the original invoice’s FX rate. This is one of the most counter-intuitive rules in the specification, and one of the most frequently broken.

The logic behind it is straightforward, and it has a statutory anchor rather than resting on convention. Article 60(1)(e) of the VAT Executive Regulation requires a tax credit note to state the value of the supply shown on the tax invoice, the correct value, the difference between the two, and the tax relating to that difference in AED. You cannot state the value shown on the original invoice while quoting today’s rate — the two are the same number by definition. Where several credit notes attach to one invoice, the same clause requires each later note to work from the value already adjusted by the earlier ones.

So if the invoice booked AED 44,070 of revenue at 3.6725, the credit note must reverse AED 44,070 at 3.6725, not the current day’s rate. Use the current rate and you create a phantom FX gain or loss in the FTA’s records that does not exist in the underlying transaction.

Two related deadlines sit alongside this and are easy to lose. Article 62(2) of Federal Decree-Law No. 8 of 2017 requires the tax credit note to be issued within 14 days of the adjustment event in Article 61(1). And Article 70(4) of the same Decree-Law, as amended, requires a registrant subject to the Electronic Invoicing System to issue and transmit that credit note as an electronic credit note — a paper or PDF credit note against an electronic invoice is not a compliant correction once you are in scope.

This applies even where months separate the invoice and the credit note. A credit note issued in January 2027 against an invoice from October 2026 uses the October 2026 FX rate, not the January 2027 rate.

Most accounting systems do not handle this automatically. The cleanest fix is to store the original FX rate as a field on every invoice record, and have the credit note module read that field rather than refreshing from the master FX table.

Four things to configure in your accounting system

Getting a UAE accounting system PINT AE-compliant on multi-currency comes down to four bits of setup.

The first is the daily FX feed from CB UAE. Either your accredited service provider supplies it as part of the platform, or you configure a direct pull from the Central Bank’s published rates table. Ask the question explicitly during selection rather than assuming, and check the provider’s current accreditation on the Ministry of Finance list, which Article 5(2) of Ministerial Decision No. 243 of 2025 makes the authoritative record. Keying rates in by hand is unsustainable and error-prone.

Next is the invoice-date FX lock. When the invoice is generated, the system reads the rate for that exact date and writes both currencies to the invoice record. Don’t let users override the rate at the invoice level; the audit trail breaks the moment they do.

Third, AED reporting fields need to sit on every line. Most cloud platforms support this natively, though some legacy ERPs do not. Where the system only stores foreign-currency amounts, add custom fields for the AED equivalent and let the document generator populate them at issuance.

The fourth is the one that catches legacy systems out: credit note logic that reuses the original rate. Test it explicitly before go-live, by issuing a test credit note against a backdated foreign-currency invoice.

When the quarterly VAT return picks this up

The quarterly VAT return is filed in AED. Your output VAT and input VAT totals must reconcile to the AED amounts on the PINT AE invoices the FTA holds in its real-time feed. Where the invoice AED line uses the CB UAE rate, the reconciliation is clean. Where the invoice uses bank deal rates, internal corporate rates or anything else, every quarter ends with manual reconciliation work to bridge the gap.

For the underlying VAT return workflow, see our UAE VAT return filing complete guide. For where the AED reporting line sits in the broader PINT AE field map, see our UAE tax invoice format 2026 guide. Two sibling PINT AE format guides worth reading alongside this one: our reverse charge invoice UAE guide for gold and scrap supplies, and our disbursement invoice UAE VAT guide for out-of-scope recharges.

Our read on ASPs for FX-heavy businesses

When shortlisting an Accredited Service Provider, multi-currency handling is one of the operational filters worth applying early. The questions to ask:

• Does the ASP pull the CB UAE FX rate automatically, or does my system push it?
• How does the ASP handle currencies CB UAE does not publish directly?
• What is the rounding methodology — line-by-line or total-only?
• How are historical FX rates stored for credit note matching?
• Are FX rate audit trails available for FTA queries?
• What is the validation tolerance for AED rounding?

Capability varies, and the only reliable way to compare is to put those six questions in writing and keep the answers. Accreditation itself is published and maintained by the Ministry of Finance under Article 5(2) of Ministerial Decision No. 243 of 2025, so verify status against that list rather than a sales deck. Where a material share of your invoicing is in foreign currency, weight multi-currency handling heavily in the selection — it is the part of the configuration that is hardest to retrofit once invoices are flowing.

Pre-go-live checklist

Before your group goes live on PINT AE, work through this checklist for every foreign-currency flow.

• Identify every active currency in your invoicing — count both outbound and inbound
• Confirm CB UAE publishes a direct rate; if not, document the cross-through-USD method
• Configure daily FX feed into your accounting system from CB UAE or your ASP
• Test invoice generation with at least three foreign currencies and verify AED line accuracy
• Test credit note issuance against a backdated foreign-currency invoice
• Document rounding methodology and confirm it matches ASP validation rules
• Train accounts team to never override the FX rate at invoice level
• Add monthly FX reconciliation to month-end close — output VAT total vs FTA feed total

How Velmont Crest helps

If your business issues any foreign-currency invoices, multi-currency PINT AE compliance is not an optional extra — it is part of the core invoice format. The cleanest sequence is:

1. Map every active currency and every counterparty flow
2. Set up the CB UAE FX feed in your accounting system
3. Audit credit note logic for original-rate reuse
4. Run a 60-day parallel cycle before your mandatory deadline
5. Build the quarterly reconciliation routine that ties PINT AE AED totals to your VAT return

Done well, multi-currency invoicing under PINT AE is honestly cleaner than the current PDF-and-spreadsheet workflow. The rate locks at the moment of invoice, every AED line reconciles, and the FTA sees the same numbers your accounting system sees. Done late, FX turns into the quiet source of every reconciliation gap for the next eight quarters.

For tailored advisory on your multi-currency invoicing setup ahead of the e-invoicing rollout, contact Velmont Crest — we work alongside your ASP selection, not against it.