Travel Aggregators Bookkeeping UAE: OTA Settlement Records

Thousands of bookings, each with two sides

A travel aggregator sits between travellers and suppliers — airlines, hotels, car hire, activities — taking bookings through its platform and settling with suppliers afterwards. Every booking has two economic sides: what the customer paid and what the supplier is owed, with the aggregator's margin in between. Bookkeeping that records only the margin, or only the cash, loses the ability to prove either. The defining discipline of aggregator books is therefore settlement accounting: every booking traced from the booking engine through the supplier statement to the bank settlement, with differences investigated, not parked.

Volume is the risk

An aggregator can process thousands of bookings a month across multiple suppliers, currencies and settlement cycles. At that volume, manual bookkeeping is not an option and spreadsheet reconciliation is a liability — the books must be system-driven, with the booking engine feeding the ledger and supplier statements imported for matching. The FTA's Article 78 records include every tax invoice and credit note; with high transaction volumes, completeness can only be demonstrated by system controls, not by human memory. Design the process for the volume you have, not the volume you started with.

The recognition decision shapes everything

Whether the aggregator acts as agent or principal is the single most consequential accounting judgement in the business. An agent arranges someone else's service: revenue is the commission or mark-up, and supplier costs never touch the profit-and-loss as cost of sales. A principal sells the travel service itself: revenue is the full customer consideration and supplier payments are cost of sales. The answer turns on the contracts — who bears inventory risk, who sets the price, who is responsible to the traveller if the service fails — and it can differ by product line: agency for flights, principal for packaged holidays, for example.

Confirm it, then build the ledger around it

This page does not determine any aggregator's status: it is a facts-and-contracts test that must be confirmed with a qualified adviser against IFRS principles and the VAT legislation, because it drives both reported revenue and the VAT treatment. Once determined, the chart of accounts implements it: commission income accounts for agency lines, gross revenue and cost-of-sales accounts for principal lines, supplier payables analysed by supplier type (airlines/BSP, hotels, GDS, ground services), customer refund liabilities, and chargeback provisions. A ledger built on the wrong recognition basis misstates revenue by orders of magnitude — the error the FTA notices first.

Accounts for a two-sided business

Beyond the recognition decision, the chart of accounts must handle the settlement machinery. Supplier payables need sub-ledgers by supplier and settlement cycle — BSP billing periods for airlines, monthly or contractual cycles for hotel consolidators, GDS segment fees. A settlement-clearing account holds timing differences between the booking event and the supplier statement. Customer-side, carry deferred revenue for bookings paid but not yet travelled (an agent holds customer money as a liability until the service is delivered or the commission is earned), refund provisions, and loyalty or voucher liabilities where the platform issues them.

The accounts that prevent surprises

Chargebacks deserve their own tracking: card disputes on travel bookings are frequent and slow to resolve, and an unprovided chargeback is a profit overstatement. Foreign-exchange differences arise wherever bookings, supplier costs and settlements cross currencies — keep them visible in their own accounts under IFRS for SMEs rather than netting them into margins. Marketing spend (the aggregator's largest discretionary cost), technology and platform costs, and customer-service payroll each need clean lines so unit economics per booking can actually be computed.

Exceptions reviewed while they are fresh

Bookings flow daily; supplier statements arrive on their own cycles. The daily discipline is exception review, not full reconciliation: failed payments, duplicate bookings, bookings without supplier confirmation, refunds requested but not processed, and settlement mismatches flagged by the matching routine. A small finance-operations team reviewing exceptions daily prevents the month-end avalanche.

The weekly settlement watch

Weekly, review the ageing of supplier payables against statement due dates — late BSP settlement has commercial consequences beyond accounting — age customer receivables (corporate clients and B2B partners pay on terms), and check the refund pipeline: requested, approved, processed, matched to supplier recovery. The weekly review also watches the deferred-revenue balance for travelled-but-unreleased bookings, the classic aggregator leak where revenue earned is never recognised because nobody told the ledger the trip happened. Travel-date feeds should drive the release automatically; where they do not, a weekly manual sweep catches it.

Cut-off, statements, refunds, VAT

The monthly close follows the settlement calendar. First, booking cut-off: every booking dated in the month captured with its correct recognition treatment. Second, supplier statement reconciliations — BSP billing periods, hotel consolidator statements, GDS invoices — each agreed to the booking sub-ledger, with differences aged and chased, not carried indefinitely. Third, refund matching: every customer credit note tied to its booking and to the supplier's refund or adjustment. Fourth, bank reconciliation across all settlement accounts and currencies.

The VAT analysis from the ledger

Fifth, run the VAT output analysis from the ledger by supply type and recognition basis — the agency-vs-principal determination made earlier decides what counts as the taxable supply and its value. Sixth, accrue marketing, technology and payroll costs, and review the chargeback and refund provisions. A closed month produces the booking-margin report by product line, the aged supplier payable and receivable schedules, the refund pipeline status and the VAT working papers. If the supplier statements do not reconcile to the ledger, the month is not closed — it is merely dated.

From bookings to filings

The annual close turns twelve reconciled months into the corporate tax return: accounting profit adjusted for tax, with attention to provisions (chargebacks, refunds, vouchers) that tax law recognises only when utilised, and to any related-party transactions — common where the aggregator is part of a regional group sharing technology or marketing costs — that need transfer-pricing support. Small Business Relief through 31 December 2029 may simplify the CT position for eligible smaller aggregators, but the conditions must be tested and the election made, not assumed.

What the auditor tests

The audit concentrates on the areas of maximum judgement and volume: revenue recognition (sampled bookings traced from engine to ledger under the confirmed agency/principal basis), supplier payable completeness (statements to ledger, including BSP), refund and chargeback provisions, and cut-off around period-end. Keep the agency/principal analysis — the contracts reviewed, the conclusion reached, the adviser's confirmation — as a permanent file: it is the document the auditor asks for first and the FTA would ask for second. Register for corporate tax within the applicable deadline once required; the reported late-registration penalty is AED 10,000 under CD 75/2023.

BSP, GDS and hotel settlements

Supplier settlement records are the aggregator's equivalent of a retailer's goods-received notes — without them, cost of sales cannot be evidenced. BSP billing statements for airline sales must be filed by billing period, reconciled to the ticketed population, and settled on time; each period's statement, adjustments and settlement confirmation form one packet. GDS segment-fee invoices, hotel consolidator statements and direct-hotel settlement records get the same treatment: imported or entered, matched to bookings, differences investigated.

The matching discipline

Unmatched supplier items fall into three buckets: timing (statement not yet received), error (booking or statement wrong), and leakage (supplier charged for something never booked, or a refund never recovered). Only the first bucket is acceptable at month-end, and it must clear the following month. Maintain an ageing of unmatched items by supplier and chase them on a schedule — a supplier credit never claimed is margin lost, and a supplier debit never recorded is profit overstated. The settlement files, kept by period, are also the first thing requested in any supplier dispute and any tax review of cost of sales.

Corporate and B2B settlement cycles

Corporate clients and B2B partners buy on terms — monthly invoicing, 30-day payment — which creates a receivables ledger the retail side never sees. Keep corporate agreements with their rate schedules and credit limits filed with the customer record, invoice on the contractual cycle without drift, and age the receivables weekly: a corporate account sliding past terms is both a cash problem and a VAT problem, since output VAT was already accounted for on invoice. Where the aggregator extends credit, document the credit decision and the limit; where it does not, enforce prepayment in the booking flow. Uncollectible corporate balances need write-off approvals and, where VAT was accounted for, the bad-debt relief conditions checked against the legislation — not assumed.

What Article 78 requires, in aggregator terms

Article 78 of FDL 8/2017 requires records of all supplies made and received, tax invoices and credit notes, and the records supporting the tax return. For an aggregator: customer tax invoices and booking confirmations for every booking, credit notes for every refund or amendment, supplier invoices and BSP/GDS/hotel settlement statements, bank statements for every settlement account, marketing and technology invoices, payroll files, and the VAT working papers behind each return. Corporate-tax records add the general ledger, financial statements and the recognition-analysis file, kept seven years from the end of the tax period.

Retention at high volume

VAT records: five years from the end of the tax period. CT records: seven years. High booking volumes make retention a systems question, not a filing-cabinet question: the booking database, the ledger and the document store must all retain the period's population retrievably, with backups that are actually restorable. Owned office premises bring the fifteen-year VAT record rule under Cabinet Decision 52/2017. And the universal rule: nothing for a period under FTA review or dispute is destroyed, however the retention clocks read — at aggregator volumes, a litigation hold must be a system flag, not a memo.

What moves the price

No responsible provider quotes a fixed AED fee for aggregator bookkeeping without seeing the operation. The drivers are volume-led: monthly booking count, number of suppliers and settlement cycles, currency count, whether BSP/GDS statement matching is included, the complexity of the agency/principal mix across product lines, and whether payroll and WPS are in scope. A niche aggregator with one supplier type costs a fraction of a full OTA with flights, hotels, packages and multi-currency settlement.

In-house, outsourced, or hybrid

Aggregators with an in-house finance-operations team usually keep daily exception review and settlement matching inside, with an external accountant owning the monthly close, VAT analysis and filings. Smaller aggregators outsource the whole function but must still feed it clean booking-engine data — the provider cannot reconcile what it cannot see. Either way, the service agreement should specify matching coverage: which supplier statements are reconciled, to what tolerance, and what happens to unmatched items. Demand the monthly pack: booking-margin report, supplier payable ageing, refund pipeline, VAT workings. Data entry without matching is not bookkeeping for an aggregator; it is typing.

The errors reviewers find first

The classic aggregator failures: an agent booking the full customer consideration as revenue, inflating turnover and the VAT base; supplier statements posted without matching, so cost of sales drifts from reality; refunds processed for customers but never recovered from suppliers (or recovered but never credited to customers); BSP differences carried forward for years instead of resolved; personal travel posted as business expense; and the agency/principal determination made once, never documented, and wrong.

Deadlines that do not negotiate

If the FTA assesses additional tax, reconsideration must be requested within 40 business days of notification under Article 29 of FDL 28/2022; the FTA decides within 40 business days; a TDRC objection follows within 40 business days of that decision; the TDRC decides within 20 business days. Errors discovered internally are corrected by voluntary disclosure within 20 business days of discovery. Every deadline runs on documents — booking records, settlement statements, the recognition analysis — which is why the settlement discipline on this page doubles as dispute readiness. An aggregator whose bookings reconcile to its settlements argues from evidence; one that cannot, settles.

Pilot voluntary, mandate dated — and volume matters

The e-invoicing pilot has been voluntary since 1 July 2026. Structured e-invoices become mandatory from 1 January 2027 for businesses with AED 50 million or more in annual turnover, and from 1 July 2027 for everyone else. Aggregators are high-volume invoice issuers — every booking confirmation that functions as a tax invoice, every B2B invoice to corporate clients — which makes this the most operationally significant mandate in this batch: the invoice format touches the booking engine itself, not just the finance tool.

Readiness at scale

Map which booking documents are tax invoices under the VAT law and confirm the booking engine or billing layer can emit them in the mandated Peppol-based format with the required fields, including the correct VAT treatment per the confirmed agency/principal analysis. Clean up customer master data at scale — TRNs for business customers, legal names, addresses — because validation failures at volume become a customer-service event. On the purchase side, ensure structured supplier invoices can be ingested for input VAT capture. Start during the voluntary pilot: for an aggregator, e-invoicing readiness is a systems project measured in months, and the mandatory date will not move for anyone.