UAE hospitality is a global benchmark sector — Dubai alone hosts 100+ million annual visitors, with hotel inventory ranging from 3-star city hotels to ultra-luxury resorts on Palm Jumeirah and Yas Island. The financial backbone underneath is more complex than the customer-facing experience suggests. A typical mid-size UAE hotel runs 6-8 revenue streams, each with distinct cost-of-goods, distinct VAT treatment, distinct departmental P&L. Distribute the room revenue across OTA channels, layer in Tourism Dirham pass-through, allocate service charge to employees per the Labour Law, reconcile multi-currency guest folios — and you have one of the most demanding accounting workflows in any UAE SMB sector.
HIBR ERP is the UAE-built option designed for this layered structure. Below: the seven hospitality-accounting pains UAE properties face, and what HIBR does about each.
The seven hospitality-accounting pains UAE hotels keep running into
Room + F&B + spa + ancillaries
A mid-size hotel splits revenue across 6-8 streams. Each has different gross margin, different VAT treatment (room is standard 5%, some F&B may be different, spa varies). Generic ERP collapses these into "Revenue" — useless for actual hotel management.
Per-revenue-stream ledger accounts (Room, F&B Restaurant 1, F&B Restaurant 2, Banquet, Spa, Conference, Retail, Parking, Other). Department-level P&L. PMS daily export auto-classifies to correct stream.
DTCM levy pass-through
Dubai's Tourism Dirham is 7-20 per room per night based on hotel classification. Abu Dhabi has a similar tourism fee. The levy is collected on behalf of DTCM (Dubai) or DCT (Abu Dhabi) and remitted monthly. It is NOT revenue — generic ERPs book it as revenue, inflating the P&L and creating VAT-base errors.
Tourism Dirham as a separate liability account. Auto-calculated per room-night per classification. Monthly remittance report for DTCM or DCT upload. VAT calculated on room rate before levy.
Booking.com / Expedia / Agoda reconciliation
Each OTA has a different commission model: Booking.com 15-20%, Expedia 18-25%, Agoda 15-20%. Commission may be deducted at source or invoiced separately. Monthly OTA statements rarely match the bank-side deposits exactly. Reconciliation eats hours.
Monthly OTA statement ingestion + auto-match against bank deposits. Discrepancies flagged. OTA commission as separate expense line per channel. Per-OTA profitability dashboard.
10% service charge per Labour Law
The 10% service charge on F&B bills belongs to employees under UAE Labour Law and must be distributed per a documented policy. Generic ERPs treat it as revenue or lump it into salaries — both wrong. The distribution policy needs documentation for MOHRE inspection.
Service charge as separate liability account. Policy-based allocation (typically pooled and distributed monthly per shifts worked). Payslip-attached service-charge schedule. MOHRE-defensible distribution record.
USD/EUR/GBP/SAR guest folios
International guests pay in 8+ currencies. Each transaction needs FX-locked AED equivalent for the GL while the guest sees their preferred currency. Generic ERPs often pick one or the other — losing data either way.
Multi-currency folios with original-currency preserved + AED-equivalent at transaction-date FX from UAE Central Bank rates. Realized FX gain/loss tracked per currency. Invoice PDFs in guest's currency.
Corporate + BTC + group blocks
Corporate negotiated rates, Bill-To-Company (BTC) accounts, group blocks with allocated room nights — each has its own rate, payment terms, credit limit. Generic ERPs treat them all as A/R; hospitality needs the segmentation visible.
Customer hierarchy: Corporate Group → Booking Account → Individual Folio. Rate plans per corporate account. Credit limits per parent. Aggregated and individual reporting both available.
F&B venues inside a hotel have their own P&L for management purposes but feed the consolidated hotel financials. Recipe-level costing matters. Inter-department transfers (room service consumes restaurant inventory) must be tracked.
F&B venues as separate departments within the hotel entity. Recipe-level food costing. Inter-department transfers as journal entries. Consolidated P&L + per-outlet P&L both available.
What ships in the hospitality-ready HIBR Pro and Enterprise tiers
Per-revenue-stream ledger
Room, F&B (multiple outlets), spa, banquets, retail, parking, ancillaries. Department-level P&L.
PMS integration
Daily revenue export from Opera, Mews, Cloudbeds, Stayflexi. Auto-classified to correct ledger streams.
Tourism Dirham + DCT levy
Auto-calculated per room-night per classification. Separate liability account. Monthly remittance report.
OTA commission reconciliation
Monthly statement ingestion from Booking.com, Expedia, Agoda. Bank-deposit matching. Per-OTA profitability.
Service charge distribution
10% F&B service charge as separate liability. Policy-based monthly distribution. Payslip-integrated.
Multi-currency folios
Original currency on folio + AED-equivalent at UAE Central Bank rates. Realized FX gain/loss tracked per currency.
Corporate hierarchy
Corporate Group → Booking Account → Folio. Rate plans + credit limits per corporate.
Recipe-level F&B costing
BOM-style recipe costs. Inter-outlet transfers. Theoretical vs actual food cost variance.
WPS for hospitality at scale
50-300 employees common in a hotel. Native SIF generation. 50% deduction cap pre-validated.
Common scenarios — what HIBR does that generic accounting doesn't
Scenario 1 — 80-key hotel in Dubai, full daily-revenue close
It's 11:59 PM on a busy Saturday in Dubai. Your hotel has 80 keys, 67 occupied, with three F&B outlets running, the spa just closing, and 24 banquet covers in the ballroom. Standard accounting: someone gets to manually classify the day tomorrow morning. HIBR: Opera PMS sends the daily-revenue export at midnight. Room revenue (67 × average 850 = 56,950 plus VAT) auto-posts to Room Revenue. F&B splits to three outlets per the PMS revenue codes. Spa revenue (4,200) posts to Spa Revenue. Banquet F&B (8,640 + service charge 864) posts with the service charge as separate liability. Tourism Dirham (67 keys × 15 4-star = 1,005) posts to DCT Payable liability. By 7 AM Sunday, the daily-revenue dashboard is fresh.
Scenario 2 — OTA statement reconciliation against bank deposits
Your hotel ran 320 OTA-channel bookings last month split across Booking.com (180), Expedia (90), Agoda (50). The OTA statements arrive on the 5th. Booking.com deducted 18% commission at source on prepay bookings; Expedia invoiced commission separately on the 8th; Agoda paid full and you owe commission within 30 days. Standard: spreadsheet reconciliation that takes 6-8 hours and still ends up with 4,000 unmatched. HIBR: ingests each statement, matches against the booking-side deposits using PMS confirmation numbers, identifies 3 discrepancies for review, posts the rest automatically. The 3 discrepancies are documented for the OTA help desk follow-up.
Scenario 3 — Multi-currency guest folio
A British guest checks out paying GBP 2,400 by Amex. The hotel quoted 11,520 (at GBP/4.80). Card terminal settles in AED but the folio is in GBP. HIBR: records the folio in GBP, books to GL at the day's UAE Central Bank GBP/AED rate (4.79 — slight variance to quoted rate), Output VAT calculated on the AED-equivalent, realized FX gain/loss posted to the FX gain account. The folio PDF emailed to the guest shows GBP; the GL shows AED. Same transaction, both representations accurate.
FAQ for UAE hospitality operators evaluating HIBR
How does HIBR handle Tourism Dirham and DTCM levies?
Tourism Dirham (Dubai: 7-20 per room per night, depending on hotel classification) and equivalent Abu Dhabi Tourism Fee are pass-through levies collected by the hotel and remitted to the tourism authority. HIBR treats them as separate ledger accounts (not revenue), auto-calculates per room-night per classification, and produces the monthly remittance report for DTCM (Dubai) or DCT (Abu Dhabi) upload. VAT is calculated on the room rate before Tourism Dirham, per FTA guidance.
Can HIBR reconcile Booking.com, Expedia, and Agoda commission statements?
Yes. Each OTA's commission model differs (Booking.com typically 15-20%, Expedia 18-25%, Agoda 15-20%), and the commission may be deducted at source or invoiced separately. HIBR ingests the monthly OTA statement, matches against the booking-side bank deposits, identifies discrepancies, and books the OTA commission as a separate expense line per channel. Each OTA's profitability is visible per month.
How is service charge handled under UAE Labour Law?
Service charge (typically 10% on F&B bills, sometimes on room service) is treated under UAE Labour Law as belonging to employees and must be distributed per a documented policy. HIBR tracks service charge as a separate liability account, allocates per the policy (typically pooled and distributed monthly based on shifts worked), and produces the payslip-attached service-charge schedule. VAT is calculated on the pre-service-charge amount.
Does HIBR integrate with hotel property-management systems (PMS)?
HIBR is the financial backbone, not a PMS. The product is designed to integrate with existing PMS systems (Opera, Mews, Cloudbeds, Stayflexi) via daily-revenue-export interfaces. The PMS handles reservations, check-in/out, room assignments, folio management. HIBR consumes the daily revenue snapshot, posts it correctly across room, F&B, spa, and other revenue streams, and handles the accounting + tax + payroll layer underneath.
How does HIBR handle multi-currency guest folios?
International guests often pay in USD, EUR, GBP, SAR, or Indian Rupees. HIBR records the original currency on the folio, books to the AED-functional ledger at transaction-date FX (sourced from UAE Central Bank reference rates), and tracks realized FX gain/loss per currency. Multi-currency invoice PDFs can be generated in the guest's preferred currency while the AED-equivalent flows to the GL.
Is HIBR appropriate for a serviced-apartment operator (not a traditional hotel)?
Yes — and arguably an even better fit. Serviced apartments have longer average stay durations, more corporate-account weight, often a "host fee" pass-through similar to Tourism Dirham, and lower F&B complexity. HIBR's department-level P&L flexes to whatever revenue-stream split your business runs.
What about hotel F&B venues operating as separate brands?
Many hotels operate F&B brands (signature restaurants, lobby cafés, rooftop bars) that have their own brand identity but operate within the hotel entity. HIBR supports this as a single legal entity with multiple departments — each F&B venue is a department with its own P&L, while consolidated hotel financials roll up automatically. If the F&B brand is actually a separate legal entity (different licence, different TRN), it would be a separate HIBR organization.
Reserve a beta seat — hospitality slot
Pro tier (499/mo) fits a single-property hotel up to ~50 keys. Enterprise (14,990/yr) handles multi-property groups + 100+ keys + multi-currency consolidation. Beta opens October 2026.
Reserve founder slot →