15 min readUpdated August 2026
RestaurantsCloud Kitchens

E-Invoicing for UAE Restaurants and Cloud Kitchens: The Dates That Actually Apply

Most UAE restaurants go live on 1 July 2027 and must appoint an Accredited Service Provider by 31 March 2027. Restaurants and groups with revenue of AED 50 million or more go live on 1 January 2027. This page covers what changes at the POS, and what does not.

The Dates for Food Businesses

Revenue below AED 50 million: appoint an Accredited Service Provider by 31 March 2027, issue e-invoices from 1 July 2027. Revenue of AED 50 million or more: ASP by 30 October 2026, go-live 1 January 2027. A voluntary pilot opens 1 July 2026.

The administrative penalty is AED 5,000 per month of non-compliance. It is not charged per invoice.

What E-Invoicing Means for Your Restaurant

An e-invoice is a structured data file, not a document you print. Your POS produces the invoice in the PINT AE format and hands it to an Accredited Service Provider, which exchanges it over the Peppol network and reports it to the Federal Tax Authority (FTA). Your till does not connect to FTA servers. A PDF emailed to a customer is not an e-invoice.

What Changes for Your Restaurant:

Every Order Gets an E-Invoice:

Dine-in, takeaway, delivery, catering. Each one becomes a structured PINT AE invoice, not a paper slip

POS Connects to an ASP:

Your point-of-sale sends invoices to your Accredited Service Provider, which routes them over Peppol. There is no direct POS-to-FTA link

Split Bills Handled Digitally:

When customers split payments, each person gets their own compliant e-invoice

Delivery Platform Orders:

Talabat, Deliveroo and Noon orders need e-invoices that show the commission treatment accurately

Legal Framework: What the Law Says

The regime sits under Cabinet Decision No. 106 of 2025 and the Ministerial Decisions issued under it. The phase dates and the AED 50 million threshold come from there.

Key Legal References:

Which Phase You Are In

Check your revenue, then your dates:

Revenue of AED 50 million or more

ASP appointed by 30 October 2026. Go-live 1 January 2027.

Revenue below AED 50 million

ASP appointed by 31 March 2027. Go-live 1 July 2027. Most independent restaurants and cloud kitchens sit here.

Government entities

ASP appointed by 31 March 2027. Go-live 1 October 2027. Relevant if you run catering contracts with them.

Voluntary pilot

Opens 1 July 2026. Useful if you want to test POS and aggregator flows before your own date.

The threshold is measured on revenue, not on outlet count. A group of six sites under one entity is assessed on the entity's total.

Restaurant-Specific E-Invoicing Challenges

1. High-Volume Transaction Processing

During peak hours, restaurants serve hundreds of customers. Your e-invoicing system must generate compliant invoices within seconds without slowing down service.

Example: A Friday dinner rush turns 180 tables in three hours. Each one needs an e-invoice generated on the spot. A system that lags holds up the pass and the payment.

2. Split Bill Complexity

Groups split bills several ways. Each payment portion needs its own e-invoice with the correct items and VAT, transmitted separately through your ASP.

Example: Table of 6 splits AED 840 bill three ways. System must generate 3 separate e-invoices (AED 280 each) instantly.

3. Delivery Aggregator Integration

Orders from Talabat, Deliveroo take 20-30% commission. Your e-invoice must reflect actual revenue received or show commission clearly as deduction.

Example: Talabat order AED 85. After 25% commission, you receive AED 63.75. E-invoice must show this structure accurately for VAT.

4. Menu Modifiers & Customizations

Extra cheese, no onions, spice level. Every modifier has to appear on the e-invoice line items at the right price.

5. Complimentary Items & Staff Meals

Comped desserts, staff meals, promotional offers still need e-invoices (marked as zero-value or promotional) for inventory and VAT tracking.

Your Restaurant E-Invoicing Roadmap

Work backwards from the ASP appointment date, not the go-live date. Below AED 50 million revenue that is 31 March 2027, which puts Phase 1 in the second half of 2026.

Phase 1: Audit Current Setup (Month 1)

  • • Inventory all POS systems across locations
  • • Review integration with delivery platforms
  • • Document current invoicing process
  • • Identify peak transaction times

Phase 2: POS System Upgrade (Months 2-3)

  • • Appoint an Accredited Service Provider
  • • Confirm the POS can output PINT AE and test generation speed
  • • Configure split bill handling
  • • Integrate with delivery aggregators

Phase 3: Staff Training (Month 4)

  • • Train servers on new invoice process
  • • Educate kitchen on menu modifiers
  • • Practice answering customers who ask where their invoice went
  • • Create troubleshooting protocols

Phase 4: Testing & Go-Live (Months 5-6)

  • • Run parallel systems, or join the voluntary pilot open from 1 July 2026
  • • Test during actual dinner rush
  • • Monitor invoice generation speed
  • • Live before 1 July 2027, or 1 January 2027 above AED 50m revenue

Common Mistakes That Cost Restaurants Heavily

Mistake #1: Treating 1 July 2027 as the Start Date

The ASP must be appointed by 31 March 2027. That is the date that constrains you, and POS integration runs months behind it.

Cost: AED 5,000 per month of non-compliance, plus rush integration fees

Mistake #2: Assuming a PDF Receipt Counts

A PDF is not an e-invoice. The invoice must be a structured PINT AE file exchanged through an Accredited Service Provider. POS vendors that only add a QR code to a printed slip do not meet the requirement.

Cost: Wasted investment, replacement, and downtime mid-service

Mistake #3: Ignoring Delivery Aggregator Invoices

Platform orders need e-invoices like any other sale. Restaurants often leave aggregator volume outside the POS entirely, and the gap only surfaces at audit.

Cost: Penalties plus a VAT reconciliation you cannot support

Mistake #4: No Staff Training

Servers who don't understand e-invoicing cause errors, slow service, and upset customers.

Cost: Lost customers + operational chaos + compliance errors

What Non-Compliance Actually Costs

The Penalty Is Monthly, Not Per Invoice

How it is charged

  • • AED 5,000 for each month you are non-compliant
  • • Charged from your go-live date, not from the pilot
  • • Not multiplied by transaction volume
  • A 530-cover weekend does not create 530 penalties

Six months late:

6 months × AED 5,000

= AED 30,000

The penalty is survivable. The operational cost is not: a POS that cannot issue compliant invoices stops you invoicing corporate and catering clients who require them.

What you get from doing it properly:

  • ✓ Every cover invoiced automatically, dine-in and delivery
  • ✓ No monthly penalty
  • ✓ VAT returns reconcile to POS data without manual work
  • ✓ Aggregator revenue visible in the same ledger as dine-in

POS System Requirements Checklist

Your POS system MUST have these capabilities:

Output in the PINT AE format, not a PDF or printed slip
A working integration with an Accredited Service Provider on the Peppol network
Handle split bills with multiple invoice generation
Integration with delivery aggregator platforms
Menu modifier tracking in invoice line items
Offline mode with automatic sync when connection restored
Multi-location support with centralized reporting
Complimentary/promotional item handling

How Ratio Helps Restaurants

We work with UAE restaurant and cloud kitchen operators on the four pieces that decide whether go-live is quiet or messy:

POS System Assessment

We check whether your current POS can output PINT AE and connect to an ASP, and tell you if it cannot

ASP Selection and Integration

We shortlist Accredited Service Providers, run the POS integration, and test the delivery platform feeds

Staff Training Programs

Practical training for servers, managers, and kitchen staff on new processes

Ongoing Compliance

Monthly checks that invoices are being accepted, rejections are cleared, and VAT returns tie back to POS data

Find Out If Your POS Is Ready

Most restaurants need an Accredited Service Provider appointed by 31 March 2027 and invoices flowing by 1 July 2027. We will tell you where your current setup stands.

Schedule Restaurant E-Invoicing Consultation

Free 30-minute assessment • Same-day response • Restaurant compliance specialists

Frequently Asked Questions

Do cloud kitchens need e-invoicing in UAE?

Yes. Cloud kitchens follow the same timeline as everyone else. At AED 50 million revenue or more, appoint an Accredited Service Provider by 30 October 2026 and go live 1 January 2027. Below AED 50 million, appoint an ASP by 31 March 2027 and go live 1 July 2027. Operating entirely through delivery platforms does not exempt you.

How do I handle split bills with e-invoicing?

Your POS must generate a separate e-invoice for each payment. Each one carries the correct items, amounts and VAT for that customer's portion, and each is sent through your ASP in the PINT AE format. Ask your POS vendor to demonstrate a three-way split before you sign.

What about delivery aggregator orders (Talabat, Deliveroo)?

You must issue e-invoices for orders through delivery platforms. The invoice should reflect the actual amount received after platform commissions, or show the full amount with commission as a line item deduction. This ensures accurate VAT reporting on your actual revenue.

Do we need e-invoices for complimentary meals?

Yes, even complimentary meals (comped items, staff meals, promotional offers) must have e-invoices showing zero value or marked as promotional. This maintains accurate inventory tracking, cost analysis, and VAT compliance for deemed supplies.

What is the penalty for failing to issue e-invoices?

AED 5,000 per month of non-compliance. It is a monthly administrative penalty, not a charge per invoice, so a busy weekend does not multiply it. The larger exposure is commercial: corporate and catering customers will ask for compliant invoices from your go-live date.