Travel Aggregator Audit in the UAE: 2026 Settlements, Revenue and Deadlines

A travel aggregator — the platform that sits between travellers and airlines, hotels and other suppliers — is audited at the points where money pauses: customer prepayments held before travel, supplier payables accrued before settlement, and the margin or commission retained in between. The statutory external audit is the independent examination of the financial statements under IFRS, ending in an audit opinion for shareholders, the licensing authority, suppliers and lenders. Internal review of settlement controls and reconciliations is management's own discipline, existing to catch breaks before the auditor does. The FTA tax audit examines the corporate tax and VAT positions and can reach back several years.

For an aggregator, the statutory audit concentrates on four areas shaped by the model. Revenue recognition is the first and most judgemental: whether the platform is principal or agent determines whether revenue is the gross booking value or just the commission, and the answer moves the top line by an order of magnitude. Supplier settlements are the second: payables to airlines, hotels and bed banks must be complete and correctly stated. Refund and cancellation liabilities are the third: an aggregator holding customer money for future travel carries obligations that must be measured. Customer prepayments and cut-off are the fourth: cash collected before travel is not yet revenue.

Why aggregators attract audit attention

The model combines high transaction volumes, thin margins, complex supplier contracts and significant customer money held in advance — the exact combination where small percentage errors become material absolute amounts. An auditor who finds the settlement reconciliations clean and the principal-versus-agent analysis documented will move quickly; one who finds unreconciled supplier statements and an undocumented revenue policy will not.

The shape of this guide

Each section addresses one audit pressure point — revenue recognition, settlements, refunds, prepayments, appointment, timeline, records, tax readiness, penalties and fees — so the finance team can prepare each workstream independently and the audit can proceed in parallel rather than in sequence.

The Commercial Companies Law, Federal Decree-Law No. 32 of 2021, carries the auditor provisions for mainland companies, and limited liability companies are generally required to appoint an auditor — a requirement typically repeated in the memorandum of association. Travel aggregators operate as mainland LLCs, free-zone companies or branches of foreign platforms, and each form carries its own trigger. In practice the binding constraint is often the licensing authority: many free zones require annual audited financial statements for licence renewal, and travel businesses may also hold sector-specific registrations whose conditions should be checked individually.

Requirements vary between authorities and change, so the current position should be confirmed with the specific licensing authority rather than assumed. Beyond the licence, commercial counterparties impose their own audit demands: airlines and hotel chains extending credit or preferred rates, global distribution systems, and payment processors setting transaction limits routinely ask for audited statements. An aggregator negotiating supplier credit or higher processing limits should expect the audited accounts to be requested.

Group structures are common — a UAE operating company with an offshore holding or technology company — and each entity's audit requirement is assessed separately. The operating company's audit does not cover the offshore entity, and intercompany balances for technology fees, brand charges or management services need their own testing and transfer-pricing support. Branches of foreign aggregators generally maintain audited branch accounts for the UAE operation.

Check every licence in the structure

Map each entity, each licence and each sector registration at appointment. The auditor plans around the full legal structure; discovering an additional licensed entity during fieldwork restarts the planning.

Principal-versus-agent is the single most consequential accounting judgement a travel aggregator makes, and the auditor examines it first because it determines what "revenue" means. Under IFRS 15, a principal controls the service before it is transferred to the customer and recognises the gross amount; an agent arranges for another party to provide the service and recognises only its commission or margin. For an aggregator selling a hotel room for AED 1,000 with an AED 850 supplier cost, the difference is AED 1,000 of revenue versus AED 150 — the same economics, a radically different top line.

The auditor applies the control indicators: does the aggregator hold inventory risk — pre-purchased room allotments or airline seats it must pay for whether sold or not? Does it set the price, or merely pass through the supplier's price plus a disclosed mark-up? Is it primarily responsible for fulfilment when things go wrong — rebooking, refunds, customer service — or does the supplier own the customer relationship? Is the supplier paid regardless of whether the traveller pays the aggregator? Each indicator is tested against contracts and actual practice, because practice can differ from the contract wording.

Mixed models are common and must be analysed separately: the flight component might be agency while a packaged hotel allotment is principal, or corporate travel management might be agency while the leisure platform takes inventory risk. The auditor expects a documented principal-versus-agent analysis for each material revenue stream, applied consistently, with the contracts and operational evidence that support it. An undocumented position, or a position that changed from last year without explanation, will be challenged.

Document the analysis once, defend it every year

A short paper per revenue stream — indicators assessed, conclusion, contracts referenced — prepared by management and reviewed by the auditor at interim. This single document prevents the most disruptive audit debate an aggregator can have.

Supplier payables are typically an aggregator's largest liability, and the auditor tests them for completeness — the risk being that the platform has sold travel it has not yet recorded as owed to suppliers. The standard procedure starts with the supplier statement: for each material supplier — airlines, hotel chains, bed banks, car-hire consolidators — the auditor agrees the payable in the ledger to the supplier's own statement, investigates differences, and may confirm balances directly with the supplier where material.

The auditor then tests the settlement mechanics. Bookings made through the platform are traced to the supplier's invoice or settlement file: was the booking recorded, was the contracted rate or commission applied correctly, and was the payable recognised in the right period? Commission and mark-up schedules are re-performed on samples — the auditor recalculates what the platform should have retained and checks it against what was recorded. Overrides, net-rate versus sell-rate structures and incentive rebates from suppliers each get their own testing, because each is a place where the contract and the system can diverge.

Cut-off around year-end is critical: travel sold before year-end for departure after, supplier invoices received late, and estimated accruals for uninvoiced supplier costs. The auditor examines the accrual methodology — is it based on actual booking data with contracted rates, or on broad percentages? — and tests it against invoices received after year-end. A booking system that can produce a supplier-cost report by departure date makes this testing straightforward; one that cannot forces the auditor into estimation, which rarely favours the company.

The monthly settlement discipline

Reconcile every material supplier statement monthly, investigate differences immediately, and keep the reconciliation file. An aggregator that does this finds the payables section of the audit takes days; one that reconciles annually finds it takes weeks and produces adjustments.

An aggregator that takes customer money before travel carries refund and cancellation obligations, and the auditor measures them under IAS 37. The starting point is the cancellation terms: what the platform promises the traveller, what the supplier allows the platform, and the gap between the two — because the platform's liability to the traveller can exceed its recovery from the supplier. Non-refundable supplier costs against refundable customer bookings are the classic exposure, and the auditor quantifies it.

The provision methodology is tested against evidence. Historical refund rates by product and season, the ageing of unrefunded balances, post-year-end actual refunds compared with the provision, and specific provisions for known events — a cancelled charter, a supplier failure, a regulatory travel restriction. The auditor compares the provision with what was actually paid out after the reporting date; a provision consistently below actual refunds was understated, and the auditor will adjust it and question the methodology.

Chargebacks add a parallel liability. Card payments for travel are subject to dispute, and the auditor examines the chargeback log, the provision for expected chargebacks and the controls over disputed transactions. Fraud-related chargebacks — stolen cards used for bookings — are tested for both the provision and the underlying controls, because a spike in fraud indicates a control failure as well as a financial exposure.

Voucher and credit-note liabilities are examined too. Where the platform issues travel credits instead of cash refunds, the outstanding credit balance is a liability measured at expected redemption, and breakage — credits never redeemed — can only be recognised on a supportable basis. The auditor tests the redemption data behind any breakage assumption.

Keep the refund file honest

Cancellation terms per product, historical refund statistics, the provision calculation with its assumptions, post-year-end refund actuals, and the chargeback log. Updated quarterly, this file turns a judgemental audit area into an evidenced one.

Customer prepayments — cash collected for travel not yet taken — are deferred revenue, not revenue, and the auditor tests the cut-off with the same rigour applied to any advance-payment business. The procedure: extract the bookings ledger at year-end, identify travel departing after the reporting date, and verify that the related cash sits in deferred income rather than in revenue. The auditor samples bookings across the cut-off boundary — departures just before and just after year-end — and traces each to the departure records and the revenue entry.

Loyalty programmes and member credits complicate the picture. Points issued with bookings, promotional credits and wallet balances are all liabilities until redeemed or expired, and breakage assumptions need the same evidential support as voucher breakage. The auditor examines the programme terms, the redemption history and the basis for any breakage recognised, and tests that expired credits are released correctly rather than lingering as liabilities or being released early to flatter revenue.

Foreign-currency bookings add a translation test: prepayments in foreign currencies are monetary items retranslated at the reporting date, while the related deferred revenue follows the applicable standard. The auditor checks the rates used and the completeness of the foreign-currency population. For aggregators selling in multiple currencies with settlement in others, the currency controls — who sets the rates, how often they update, how differences are recorded — are walked through as well.

Freeze the bookings ledger

A formal cut-off: the bookings ledger frozen at year-end, departures extracted, deferred revenue scheduled by departure month. Performed as a close step rather than an audit request, this keeps the revenue cut-off clean even in peak season.

The auditor must be independent and registered with the Ministry of Economy under the audit-profession framework (Federal Law No. 12 of 2014, as amended). Registration is the minimum; several licensing authorities maintain approved-auditor lists, and the appointment should be verified against the relevant list before engagement. A report signed by an unregistered practitioner, or by a firm missing from a required list, can be rejected at licence renewal — which means commissioning the audit twice.

Sector experience matters more than usual for aggregators. The principal-versus-agent analysis, supplier-settlement testing and refund-provision work are specialised; an auditor who has never audited a travel business will spend the engagement learning the model, while one with travel, hospitality or platform experience will plan the right procedures from the start. Ask prospective firms for relevant experience, confirm which senior team members will lead the revenue and payables work, and agree how the principal-versus-agent paper will be reviewed — ideally at interim, not at final fieldwork.

Independence needs explicit confirmation where the firm also provides bookkeeping, VAT compliance or systems advice. Appoint early in the financial year: interim procedures can cover the principal-versus-agent analysis, a walkthrough of the settlement cycle and testing of a sample month's supplier reconciliations, leaving year-end fieldwork for balances, cut-off and provisions. An interim review that endorses the revenue-recognition position removes the audit's biggest potential dispute before it can delay the opinion.

What to agree at appointment

Registration and approved-list status, the interim timetable for the revenue paper and controls walkthrough, the approach to supplier confirmations, the inventory of reports the booking system must produce, and the deadline driven by the licence-renewal date. Put the reporting deliverables in the engagement letter.

Travel is seasonal — summer holidays, Eid periods, the winter sun season — and the audit timetable must accommodate both the financial year-end and the licence-renewal date, with the booking curve as a third input. The typical sequence: interim work in a quieter quarter covering the principal-versus-agent paper, settlement-cycle walkthroughs and sample supplier reconciliations; year-end close with the bookings cut-off and supplier accruals; substantive fieldwork on revenue, payables, provisions and prepayments; the audit opinion; licence renewal; and the corporate tax return within 9 months of year-end reconciled to the audited figures.

Peak-season timing creates specific pressures. A December year-end falls mid-winter-season for UAE-outbound travel, which means the cut-off population is large and the finance team is busy; a June year-end falls in the summer peak with the same effect. There is no quiet year-end in travel — only less-bad ones — so the close checklist must be executable under load: the bookings-ledger freeze, the supplier-accrual run and the refund-provision update should be rehearsed procedures, not improvisations.

Supplier-statement availability affects fieldwork scheduling. Some suppliers issue statements weeks after month-end; the auditor plans confirmations and subsequent-payment testing around those cycles. Agreeing the fieldwork dates with the auditor after confirming when the major supplier statements will be available avoids a fieldwork team sitting idle waiting for statements.

Plan from the renewal date backwards

Licence-renewal date, minus fieldwork weeks, minus close weeks, gives the appointment date and the interim-work window. Add the supplier-statement cycle to the planning, and the audit stops colliding with the season that creates its hardest evidence.

The statutory auditor opines on the financial statements; the FTA examines the tax position, and its record requests for an aggregator centre on the booking-to-cash chain. FTA readiness means retaining, for the tax horizon: the corporate tax registration certificate and filed returns with workings; VAT returns with workings reconciled to reported revenue; the principal-versus-agent analysis that determines what was reported as revenue; booking data with supplier references; supplier contracts, commission schedules and settlement statements; refund, chargeback and voucher logs; and customer-prepayment schedules.

Revenue completeness is the FTA's first test, and the principal-versus-agent position is central to it: the FTA will examine whether the revenue reported for VAT and corporate tax is consistent with the documented analysis and with the audited statements. An aggregator reporting net commission for VAT but gross bookings for corporate tax — or vice versa — without a documented basis invites detailed inquiry. The three figures — VAT returns, corporate tax return, audited statements — should reconcile, with documented explanations for legitimate differences.

The VAT treatment of travel supplies follows the general VAT legislation, including the place-of-supply rules for services and the treatment of international transportation where relevant. Aggregators sometimes assume simplified or special treatments apply to package travel; whether any special provision applies to a particular supply should be confirmed against the legislation and FTA guidance rather than assumed from industry practice. An incorrect VAT position on the principal-versus-agent question compounds quickly across high volumes.

If the FTA issues an assessment or penalty the aggregator disputes, reconsideration must be requested within 40 business days of the relevant decision under Article 29 of Federal Decree-Law No. 28 of 2022. The Tax Disputes Resolution Committee objection window is likewise 40 business days with a 20-business-day decision timeline, and voluntary disclosure of return errors carries a 20-business-day correction window. Each mechanism runs on its own clock from its own triggering date.

Reconcile the three revenue figures

VAT returns, corporate tax return, audited financial statements — one revenue story, documented differences. The aggregator that can walk the FTA from bookings to each reported figure in one sitting will spend far less time under audit than one that cannot.

The corporate tax penalty regime under Federal Decree-Law No. 47 of 2022 penalises failures across registration, filing, payment and record-keeping, and the FTA publishes the penalty tables. For an aggregator, the record-keeping limb is the live risk: booking data, supplier settlements and refund records that cannot be produced when asked expose the company to both tax adjustments and administrative penalties for the record failure itself. This guide does not quote penalty figures that cannot be verified in an official source; the current figures should be checked against the FTA's published tables.

The verified figure worth carrying exactly is the AED 10,000 late corporate tax registration penalty per Taxable Person — relevant to aggregators that launched the platform, obtained the licence and deferred tax registration until the business "became real". Beyond tax penalties, weak records carry sector-specific commercial costs: suppliers restrict credit to aggregators whose settlement records are unreliable, payment processors lower limits where chargeback controls look weak, and acquirers discount valuations where the principal-versus-agent position is undocumented.

System migrations are the classic evidence risk for aggregators: a platform that changes booking engines without archiving the old booking and settlement data will struggle to support prior-year balances in a later FTA audit. The retention policy should require complete, re-producible archives of booking, settlement and refund data across system changes, designed for FTA horizons rather than for the statutory audit year alone.

Verify figures before relying on them

Penalty amounts and their application change by Cabinet decision. Where this guide describes exposure in general terms, confirm the current position against the FTA's published penalty tables rather than relying on commentary.

No reputable auditor quotes a fixed fee without scoping the engagement, and this guide publishes no fee figures. The drivers that move the fee for a travel aggregator are clear. Transaction volume is the first: millions of bookings mean larger samples across revenue, settlements and refunds. Supplier count and diversity is the second: each material supplier relationship adds statement agreement, commission testing and potential confirmation procedures.

Revenue-model complexity is the third driver: mixed principal and agency streams, loyalty programmes and voucher liabilities each add judgemental audit areas. Refund and chargeback volumes are the fourth: high cancellation rates mean heavier provision testing. Multi-entity and cross-border structures are the fifth: offshore technology or holding companies add consolidation and transfer-pricing procedures. Record and system quality is the sixth and most controllable: reconciled supplier statements, a documented principal-versus-agent analysis and archived booking data compress fieldwork; reconstruction expands it.

Manage cost by tendering on scope and timetable rather than headline price, appointing early enough for interim work on the revenue paper and settlement controls, and investing in the monthly reconciliation disciplines described in this guide. The cheapest aggregator audit is the one where the auditor's procedures confirm what the reconciliations already prove — and that outcome is produced in the finance function during the year, not at the fee-negotiation table.