If you run finance or operations for a UAE hotel, resort, or F&B group, your compliance problem is not the mandate itself. It is the folio. A single guest bill can carry a room rate, food and beverage charges, spa services, a 10% service charge, a 7% municipality fee, the Tourism Dirham, and 5% VAT, all posted from different systems and often settled in multiple currencies. Turning that folio into a structured XML invoice that clears the Federal Tax Authority (FTA) framework, without breaking your Property Management System (PMS) or your guest checkout experience, is where hospitality operators get stuck. This blog walks through what to fix, and in what order.
Most UAE businesses issue one invoice per transaction. Hospitality issues one folio per stay, built from dozens of postings across the PMS, POS terminals in outlets, the spa system, and the events module. Each posting carries its own tax treatment. Room revenue is subject to 5% VAT. The 10% service charge, when it forms part of the consideration for the supply, is generally VATable. The Tourism Dirham fee, a fixed nightly charge set between AED 7 and AED 20 by hotel category in Dubai, sits outside the VAT base as a government levy and must be shown as a separate line. Abu Dhabi applies a percentage-based tourism fee instead. Getting these categorisations wrong at posting time means every e-invoice generated downstream will inherit the same error.
The FTA framework does not accept a scanned or PDF folio. Under Ministerial Decisions No. 243 and 244 of 2025, a valid UAE e-invoice must be a structured XML file in the PINT-AE (Peppol International Invoice, UAE Profile) format, exchanged through an Accredited Service Provider (ASP) on the Peppol 5-corner network. Your PMS output has to map cleanly to that structure before any ASP will accept it.
The PINT-AE data dictionary treats VATable supplies, exempt items, and government-imposed charges differently. That distinction matters at the line level, not just at the invoice total. In practical terms, your data mapping needs to:
Getting the taxonomy right once, at the PMS level, is what stops thousands of downstream corrections. This is exactly the mapping work our advisory team completes before ASP onboarding begins.
Most UAE hospitality operators run a stack that includes Opera or Protel on the front desk, Simphony or Micros in F&B outlets, a separate spa or MICE booking engine, and a back-office ERP such as SUN, Sage Intacct, or Microsoft Dynamics. Each system speaks a different data language. The e-invoicing mandate forces all of them to converge into one structured output per taxable transaction.
Three integration questions decide how painful this becomes:
A readiness assessment that maps every charge code in your PMS to a PINT-AE data field, and flags the gaps, saves months of rework. Our team runs this exercise before we help clients shortlist an ASP, because the ASP contract only delivers value once the upstream data is clean.
Hospitality operators often assume the mandate touches only their finance team. It touches sales and revenue management too. Corporate rate agreements, DMC and travel agency contracts, MICE bookings for government entities, long-stay bookings paid by employers, and outside catering contracts are all e-invoicing B2B B2G UAE transactions inside the scope of the mandate. B2C guest folios are excluded for now, but the moment a company or a government body is the bill-to party, the invoice must be issued through the framework.
For a mid-sized hotel, this can mean thirty to forty percent of monthly invoicing volume moves into scope on day one. For a chain with government MICE contracts, or a resort group with corporate retreat business, the share is often higher. Revenue managers should be part of the scoping conversation from the start, because segment mix, rate code structure, and how commissionable business is contracted all shape the eventual e-invoice flow. A hotel that treats compliance purely as a back-office project usually discovers the misalignment only after the first rejected transmission.
The phased rollout published by the UAE Ministry of Finance places large taxpayers (annual revenue of AED 50 million or more) at the front of the queue, with an ASP appointment deadline of 30 October 2026 and mandatory go-live on 1 January 2027. Smaller operators follow in July 2027, and government entities in October 2027. Penalties under Cabinet Decision No. 106 of 2025 reach AED 100 per missing electronic invoice, capped at AED 5,000 per calendar month.
A workable readiness plan for a hospitality group typically moves through five stages: a scope and data assessment covering every revenue-producing system, a charge-code mapping to PINT-AE fields, a vendor-neutral ASP shortlist based on your PMS and ERP stack, an integration and testing phase in the pilot environment, and staff enablement for front office and finance teams. This is the sequencing our compliance advisory team uses across e-invoicing engagements. Sequencing matters. Appointing an ASP before the data mapping is complete usually forces expensive rework, because the ASP will surface every gap between your PMS charge codes and the PINT-AE schema during onboarding tests, not before contract signature.
Compliance in hospitality is not a software purchase. It is a data problem that begins at the PMS charge-code level and only ends when every folio, corporate invoice, and MICE contract flows cleanly through an ASP into the FTA framework. The Tourism Dirham, service charge, and municipality fee are not accounting nuisances. They are the exact fields that regulators will audit line by line once the framework is live. Operators who fix the mapping now, in parallel with ASP selection, avoid the two most expensive outcomes: monthly penalties, and a rushed go-live that disrupts guest checkout.
For a compliance-first walk-through of where your PMS, POS, and back-office stack stand against the PINT-AE requirements, speak to our UAE e-invoicing specialists or explore our broader compliance resources.
No. The Tourism Dirham is a government-imposed nightly fee collected by hotels on behalf of the relevant tourism authority. It sits outside the VAT base because it is not consideration for a supply of goods or services by the hotel itself. Under FTA guidance, it must appear as a distinct, non-VATable line on the guest folio and, once e-invoicing is live, on the structured PINT-AE invoice as well.
Not yet. The current UAE e-invoicing framework covers B2B and B2G transactions only. Individual guest folios paid by consumers remain outside scope until the Ministry of Finance issues further guidance. However, corporate bookings, DMC and travel agency contracts, MICE events for government entities, and any invoice raised to a business account fall inside the mandate and must be issued through an Accredited Service Provider.
The 10% service charge is generally treated as part of the consideration for the underlying supply, which means it is included in the VAT calculation unless the hotel licence or contract states otherwise. On a PINT-AE structured invoice, it appears as a separate line item with the appropriate VAT category code. Correct posting at the PMS level is essential to avoid mismatches during FTA reconciliation.
Most leading PMS platforms used in UAE hospitality do not yet offer native Peppol PINT-AE connectors and rely on middleware or an ASP-provided integration layer to translate PMS charge codes into structured XML. The complexity depends on your version, customisations, and how folio postings are consolidated. A pre-implementation data mapping review is the fastest way to confirm which integration path fits your specific stack.
Hospitality groups with annual revenue of AED 50 million or more must appoint an Accredited Service Provider by 30 October 2026 and go live on 1 January 2027. Operators below that threshold follow by 1 July 2027, and government-owned hospitality entities by 1 October 2027. Given PMS and POS integration lead times, most operators start scoping and data mapping at least nine months before their go-live date.
