UAE VAT & Multi-Currency for Travel Agencies

Currency and tax are the two areas where travel platforms most often fail quietly. Nothing breaks, no error appears — you simply discover at audit that your invoices were never compliant, or you discover through chargebacks that customers did not understand what they were charged.

This article covers both, from the practical standpoint of running a UAE travel business. It is general information rather than tax advice; the treatment of travel supplies has genuine complexity and you should confirm your specific position with a qualified adviser.

Why currency is harder in travel than elsewhere

In most e-commerce you buy stock in one currency and sell in another, and the exchange happens once at purchase. Travel is different: you buy at the moment you sell, from suppliers who each price in their own currency, for a customer who expects to pay in theirs.

A single booking might involve a bedbank quoting EUR, a consolidator quoting USD, a customer expecting AED, and a payment gateway settling to your bank in AED. Handle that carelessly and the customer sees one price on your site and a different amount on their statement.

The settlement currency principle

The cleanest approach is to choose one settlement currency — for a UAE business, normally AED — and enforce it consistently:

• Prices are displayed in AED.
• The customer is charged in AED by your gateway.
• The invoice is issued in AED.
• Supplier prices in EUR, USD or elsewhere are converted to AED at the point of pricing, before markup.

The customer never encounters the supplier’s currency. Their card statement matches your site exactly. This single decision eliminates a large category of disputes.

Getting conversion right

Three practical requirements:

Convert before markup, not after. Convert the supplier’s net cost to your settlement currency first, then apply your margin. Applying markup in one currency and converting afterwards produces inconsistent margins across suppliers.

Use live rates with a sensible refresh, and a fallback. Rates should update regularly — several times a day is normally sufficient — with cached values so a rate provider outage does not stop trading, and a static fallback table as a last resort.

Store the rate used on each booking. When you reconcile a supplier invoice months later, you need to know the exact rate applied at the time. Without it, reconciliation becomes guesswork.

Consider adding a small buffer to the conversion rate. Rates move between pricing and settlement, and a thin margin can be erased by an adverse movement on a large booking.

Displaying other currencies

Showing prices in a customer’s home currency is good for conversion, particularly for inbound travellers. It is compatible with a single settlement currency provided you are explicit: display the converted figure as an indication, state clearly that the charge will be made in AED, and show the AED amount at checkout before payment.

What matters is that the amount the customer authorises is the amount that appears on their statement.

UAE VAT: the essentials

VAT in the UAE is charged at a standard rate of 5%. Registration is mandatory above the prescribed turnover threshold and available voluntarily below it. Most travel businesses of any scale will be registered.

Two aspects matter most for your systems.

1. What a tax invoice must contain

A compliant tax invoice is a specific document, not a booking confirmation. It generally must show:

• The words “Tax Invoice” clearly displayed
• Your name, address and Tax Registration Number (TRN)
• The customer’s name and address, and their TRN where they are registered
• A sequential invoice number
• The date of issue, and the date of supply where different
• A description of the goods or services supplied
• The amount payable excluding tax, the tax rate applied, and the tax amount
• The gross amount payable
• Any discount applied

Sequential numbering matters more than people expect. Gaps and duplicates are exactly what an auditor looks for, so invoice numbers should be generated by the system rather than assembled by hand.

2. Foreign-currency invoices must show tax in AED

This is the requirement most commonly missed. Where a tax invoice is issued in a currency other than the dirham, the tax amount must also be stated in AED, converted using an accepted exchange rate applicable at the date of supply.

So an invoice denominated in USD must still show the VAT converted to AED. A generic invoice template that simply prints the transaction currency will not satisfy this, and the exposure accumulates silently across every invoice you issue.

This is a strong practical argument for settling in AED in the first place: if the invoice is already in dirhams, the requirement is satisfied automatically.

Agent versus principal — and why it matters

A central question in travel taxation is whether you supply the travel service yourself, or arrange it on behalf of a supplier.

If you act as principal, you are supplying the travel service to the customer, and VAT considerations attach to that supply. If you act as agent, arranging a supply between the customer and the actual provider, the treatment can differ — frequently focusing on your commission or service fee.

Which applies depends on the substance of your arrangements: who contracts with the customer, who bears the risk, how the supplier agreement is written, and how the transaction is presented. It can differ product by product within the same business.

This genuinely requires professional advice specific to your contracts. It also has a systems consequence: your platform needs to be able to apply different tax treatment by product and supplier rather than a single global rate. Choosing software that only supports one blanket VAT setting will constrain you.

Place of supply, briefly

Travel services frequently involve consumption outside the UAE, which raises place-of-supply questions and, in some circumstances, zero-rating. The rules are detailed and the analysis is fact-specific.

What matters practically is that your system records enough information to support whatever position your adviser establishes — destination, customer location, service dates and the nature of the supply. Retrofitting that data onto historical bookings is far harder than capturing it from the start.

What your platform must do

1. Store your TRN and print it on every tax invoice.
2. Generate sequential invoice numbers automatically, with no gaps.
3. Support different tax treatment by product and supplier, not one global rate.
4. Show the AED tax equivalent on any foreign-currency invoice.
5. Record the exchange rate used on every booking.
6. Handle credit notes correctly when a booking is cancelled or amended — a cancelled booking needs a credit note, not a deleted invoice.
7. Produce a VAT report for the filing period, showing output tax collected and input tax on supplier costs.
8. Retain records for the statutory period, which is longer than most businesses expect.

Reconciliation: where currency and tax meet

At month end you need to match three things: what customers paid you, what suppliers charged you, and what tax is due. Multi-currency makes this harder, because supplier invoices arrive in their currency while your books are in AED.

Practical guidance:

• Store both the original supplier currency and amount, and the AED equivalent at the rate used.
• Expect small differences between your booked rate and the rate at actual settlement — treat these as FX gain or loss rather than errors.
• Reconcile supplier statements against bookings monthly, not annually. Discrepancies are far easier to resolve while recent.
• Track refunds separately — a refund crossing a filing period needs care.

Common mistakes

Treating booking confirmations as invoices. They are different documents with different requirements.

Omitting the AED tax figure on foreign-currency invoices. Silent, cumulative, and entirely avoidable.

Applying one VAT rate to everything. Different products and supply arrangements may need different treatment.

Not storing the exchange rate used. Makes reconciliation and any audit unnecessarily difficult.

Deleting cancelled invoices. Breaks sequential numbering. Issue a credit note instead.

Leaving it until after launch. Retrofitting compliant invoicing across historical bookings is far more work than building it in.

Getting it right from the start

Decide your settlement currency before you launch and enforce it end to end. Configure your TRN, tax treatment and invoice numbering before the first real booking. Take advice on agent versus principal for your specific model. Then verify by generating a real invoice and having your accountant review it — before you have issued a thousand.

None of this is glamorous, and none of it wins customers. But it is the difference between a business that scales cleanly and one that discovers a systematic problem two years in, across every transaction it has ever processed.

Practical example: a booking end to end

It helps to trace a single transaction through the whole chain. Suppose a customer in Dubai books a hotel in Rome for four nights.

Your bedbank returns a net rate of EUR 480. Your platform converts at the prevailing rate — say 3.95 AED to the euro — giving a net cost of AED 1,896. Your markup rule for European hotels adds 8%, producing a sell price of AED 2,048. The customer sees AED 2,048, pays AED 2,048 by card, and receives a tax invoice in dirhams showing the amount excluding VAT, the 5% rate, the VAT amount and the total.

Behind that, three things must be recorded: the original supplier amount and currency (EUR 480), the exchange rate used (3.95), and the AED equivalent (1,896). When the supplier invoices you six weeks later, possibly at a marginally different effective rate after their own settlement, you can match the booking precisely and account for the difference as an FX movement rather than an unexplained discrepancy.

Notice what the customer never sees: euros. They searched in dirhams, paid dirhams, and hold a dirham invoice. That consistency is not a cosmetic choice — it is what makes the transaction defensible if it is ever questioned.

Rate movement risk on longer horizons

Travel introduces an unusual exposure: you often sell today for a service delivered and settled months later. If you sell a package in AED for travel in eight months, and your supplier bills in euros at the time of travel, currency movement in the interim comes directly out of your margin.

On individual leisure bookings this is usually tolerable. On large group bookings, long-lead corporate travel, or a season of pre-sold packages it can be material — a 3% adverse move on a thin margin is the whole margin.

Mitigations worth considering, in rough order of practicality: build a small buffer into your conversion rate rather than using the mid-market rate; price longer-dated products with a wider margin; where possible pay the supplier at the time of sale rather than at travel, converting the risk into a working-capital cost you can quantify; and for genuinely large exposures, discuss forward contracts with your bank. The first is sufficient for most agencies; the last only becomes relevant at scale.

Record-keeping and what an audit will ask for

Beyond invoices, keep the supporting trail: supplier invoices and statements, evidence of the exchange rates applied, payment gateway settlement reports, credit notes with their references to original invoices, and cancellation correspondence where a refund was partial. Retention periods under UAE law are longer than many businesses assume, and records must be produced in a readable form on request.

The practical test to apply to your own systems is simple: pick a booking from twelve months ago at random and try to reconstruct it completely — what the customer paid, what the supplier charged, which rate was used, what tax was collected, and what document was issued. If that takes more than a few minutes, your record-keeping will not survive scrutiny, and the time to fix it is before anyone asks.

Frequently asked questions

Do travel agencies pay VAT in the UAE?

Travel businesses meeting the registration threshold must register for VAT, currently charged at a standard rate of 5%. How it applies to a specific booking depends on factors including whether you act as agent or principal and where the service is consumed, so the treatment should be confirmed with a qualified tax adviser for your model.

Can I issue invoices in a currency other than AED?

Yes, but where a tax invoice is issued in a foreign currency, the tax amount must also be shown converted to AED using an accepted exchange rate for the date of supply. Many generic booking systems omit this, which creates a compliance gap that accumulates across every invoice issued.

What is settlement currency and why does it matter?

It is the single currency your customer sees, pays in and is invoiced in. Suppliers price in their own currencies, so those amounts are converted at the point of pricing. Enforcing one settlement currency means the amount on the customer's card statement matches the price they agreed, which removes a large source of disputes and chargebacks.

What must a UAE tax invoice contain?

It must be clearly marked as a tax invoice and include your name, address and TRN, the customer's details, a sequential invoice number, the issue date, a description of the supply, the amount excluding tax, the tax rate and tax amount, and the total payable. A booking confirmation alone does not meet these requirements.

How should I handle refunds for VAT purposes?

A cancelled or amended booking generally requires a credit note referencing the original invoice, rather than deleting or altering that invoice. Deleting invoices breaks sequential numbering, which is one of the first things reviewed in an audit. Refunds crossing a filing period need particular care.