Multi Currency Invoice UAE: Getting the AED Line Right Under PINT AE

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.

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. 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.

Five currencies, ninety percent of UAE SME flows

In our advisory work across Dubai SMEs, the same five currencies show up on more than nine out of ten foreign-currency invoices:

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 general rule, as implemented by all major ASPs:

• 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: 4 to 6 decimal places (ASP-configurable, 6 is the practical default)
• Document totals: 2 decimal places

The validation engine reconciles the sum of line amounts to the document total within a tolerance of typically AED 0.02 per invoice. Larger differences trigger rejection.

The rejection we see most often is a cascading rounding error, and it’s a subtle one. The foreign-currency line totals come out right, get converted to AED at a 6-decimal rate, 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.

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. A credit note reverses an invoice, 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.

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 ASP provides this automatically — most do, including Pagero, Avalara, Sovos and ClearTax UAE — or you configure a direct API pull from the Central Bank’s published rates table. 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.

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?

ASPs vary significantly here. The global tax-technology specialists (Pagero, Avalara, Sovos, Edicom, Basware) typically have mature multi-currency handling because they already serve EU and APAC e-invoicing mandates. Some regional UAE providers handle multi-currency less elegantly. If your invoice volume is more than 20% foreign currency, this should be a top-three selection criterion.

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.