Restaurant E-Invoicing in Saudi Arabia: How ZATCA Rules Apply to Every Guest Bill

Restaurant e-invoicing in Saudi Arabia is the ZATCA requirement for restaurants and cafés to issue every guest bill as an electronic simplified tax invoice, generated by a compliant system and carrying a QR code. In the integration phase (Phase 2), each bill is also cryptographically stamped and reported to ZATCA's Fatoora platform within 24 hours of issue.

The rules are the same as for any retailer, but restaurants meet them in harder conditions: bills are opened, changed and split at the table, items are voided in the middle of a rush, several tills and handhelds run at once, and a growing share of orders arrives through delivery apps. This guide explains how ZATCA's rules apply to each of those situations and ends with a checklist you can hand to your operations and finance teams. If you are also choosing or replacing the system itself, see our page on the restaurant POS system we build and integrate for Saudi F&B brands.

Is every restaurant bill a tax invoice?

Yes. When a VAT-registered restaurant sells a meal to a guest, the bill it hands over is a simplified tax invoice, the invoice type ZATCA uses for sales to consumers. It is not cleared by ZATCA before the guest receives it. Instead, the restaurant issues it immediately and reports it afterwards. ZATCA's E-Invoicing Detailed Guideline says the compliant simplified invoice must be presented to the buyer immediately as a printed copy, or shared electronically if the two parties agree.

Two situations change the picture:

• A business guest asks for a full tax invoice. A company booking a working lunch or catering order may want an invoice in its name with its VAT number. That is a standard tax invoice, which in Phase 2 must be cleared by Fatoora before it is shared. If you take corporate orders, your system needs both flows.
• The pre-bill. Many restaurants print a check for the table to review before payment. Design your system so this is clearly a draft and the stamped simplified invoice is generated once, at settlement.

The human-readable invoice must be in Arabic. Other languages can appear alongside it, and ZATCA's guideline accepts either Arabic or Hindi numerals. Bilingual receipts are therefore fine, provided the Arabic is complete, including item names and notes.

What does a restaurant's e-invoice have to contain?

E-invoicing began with Phase 1 (generation) on 4 December 2021 and Phase 2 (integration) started on 1 January 2023, rolled out in waves of taxpayers, according to ZATCA's simplified e-invoicing guide. What a bill must carry depends on which phase applies to you:

Element	Phase 1 (generation)	Phase 2 (integration)
Format	Electronic invoice from a compliant solution	XML, or PDF/A-3 with embedded XML
QR code	Basic QR code: seller name, VAT number, date and time, total and VAT amount	Expanded QR code with nine tags, including the hash and signature data
Cryptographic stamp	Not required	Every invoice stamped with the unit's cryptographic stamp identifier (CSID)
Sharing with ZATCA	Not required	Reported to Fatoora within 24 hours of issue
Edits after issue	Not allowed; corrections go through credit or debit notes	Not allowed; credit and debit notes are stamped and reported like invoices

Guests can scan the QR code with ZATCA's app to check basic invoice details, so a smudged or truncated QR code on a thermal printer is not a cosmetic problem. Test it on every printer model you use.

How does 24-hour reporting work during a busy service?

Reporting happens in the background. The guest receives the bill at once; the system sends the invoice XML to Fatoora afterwards and must do so within 24 hours of issue. Fatoora validates the invoice and returns a response. For a restaurant, three practical points follow:

• Do not make the till wait for Fatoora. Service must continue if the internet drops. A well-designed system stamps the invoice locally, prints it and queues it for reporting.
• Watch the queue, not just the sales. Someone should see, every morning, whether any invoices from yesterday are still unreported or were rejected. Rejected invoices are not edited; they are corrected and submitted as new documents.
• Have an incident routine. ZATCA's guideline expects taxpayers to keep retrying when Fatoora does not respond, keep evidence of those attempts, and notify the Authority of incidents that stop them issuing or sharing e-invoices.

How should voids, refunds and corrections be handled?

This is where restaurants most often get e-invoicing wrong. ZATCA's detailed guideline is explicit that persons subject to the regulation may not modify or delete invoices once issued, and that an invoice can only be "cancelled" by issuing a credit note and, where needed, a new invoice. Credit and debit notes must reference the original invoice, and notes linked to simplified invoices are reported in the same way as the invoices themselves.

Situation at the restaurant	What the system should do
An item is removed before the bill is settled	Edit the open order; no invoice exists yet. Keep a void log with the user and reason for internal control.
A guest is refunded after paying	Issue a credit note referencing the original simplified invoice and report it.
The wrong amount or item was billed	Issue a credit note for the original invoice, then a new correct invoice.
Something is added after the bill was issued	Issue a new invoice for the extra items, or a debit note referencing the original, as your tax adviser recommends.
The table splits the bill	Generate a separate simplified invoice for each payer at settlement, rather than reprinting or editing one invoice.
Complimentary dishes and staff meals	Record them in the system with a reason code instead of deleting lines, and agree the VAT treatment with your tax adviser.

Your system should make the right path the easy one: managers approve voids and refunds with their own login, the credit note prints automatically, and nobody has a button that deletes an issued invoice. ZATCA's guidance also lists tampering with invoice records and changing the solution's date and time among the things a compliant solution must prevent.

How does e-invoicing work across multiple branches and devices?

ZATCA calls each invoicing system an e-invoice generation solution (EGS), which can contain one or more units. Each unit is onboarded through the Fatoora portal using a one-time password and receives its own cryptographic stamp identifier. ZATCA's FAQ in the detailed guideline answers the common question directly: every device issuing invoices under the same VAT number should be registered.

For a restaurant group, that turns into some concrete decisions:

• Architecture. If each till, kiosk and handheld generates and stamps its own invoices, each one must be onboarded. If devices send orders to a central invoicing service that generates the invoices, the onboarding follows that design. The choice affects how many certificates you manage, so settle it with your solution provider early.
• New branches and replaced devices. Opening a branch or swapping a broken tablet is an e-invoicing event. Build onboarding into your opening checklist so a new device never issues bills before it is registered.
• Numbering and visibility. Invoice reference numbers can differ by branch, but each unit must keep its own unbroken sequence. Fatoora lets you view the list of integrated solutions and devices, which is worth checking monthly against your asset register.
• Security. Taxpayers must preserve cryptographic stamp identifiers and their components safely, so treat device keys like any other credential.

Our ZATCA e-invoicing integration service covers this onboarding and architecture work for multi-branch businesses.

Who issues the invoice for delivery-app orders?

It depends on your VAT registration and on each platform's business model. ZATCA addresses this in its guideline on deemed suppliers, which has a section on food delivery platforms. The worked examples there show two patterns:

• A VAT-registered restaurant issues its own simplified tax invoice for the meal to the customer and shares it through the app. The platform acts as an intermediary for the meal, issues its own simplified invoice to the customer for its delivery or service fees, and issues a tax invoice to the restaurant for its commission.
• A restaurant that is not VAT-registered is treated differently from 1 January 2026, under Article 47(3) of the VAT Implementing Regulations. The platform is generally the deemed supplier, issues the tax invoice to the customer and gives the restaurant a sales document that is not a tax invoice.

The guideline stresses that the outcome depends on the facts and contracts, for example whether the platform uses its own drivers, and that refunds and compensation for late or spilled orders can be handled through the platform's own credit notes. Its English version is for guidance only and the Arabic text prevails. Restaurants should therefore confirm the invoicing arrangement with each platform and with their tax adviser, in particular:

1. Which party generates the invoice for the meal, and from which system: your POS when the order is accepted, or a tool the platform provides.
2. How the invoice reaches the customer and how it is reported to Fatoora.
3. How refunds and cancellations are documented, and who issues the credit note.
4. How the platform's commission invoices reach your accounts so the input VAT is captured.

Operationally, the cleanest setup brings delivery orders into the same POS queue as dine-in orders, so the invoice, stock deduction and settlement reconciliation all follow one record.

Does Wave 25 bring smaller restaurants and cafés into Phase 2?

Very likely. ZATCA's Wave 25 announcement of 24 July 2026 targets taxpayers whose revenue subject to VAT exceeded SAR 187,500 in any year from 2022 to 2025, with integration with Fatoora required by 1 February 2027. That threshold catches many single-branch cafés, juice bars, bakeries and food trucks that sat outside earlier waves. ZATCA notifies targeted taxpayers in advance, but a café owner can check today by looking at the taxable sales in each year's VAT returns.

If you are in this group, the main question is whether your current POS can be onboarded to Fatoora and will report reliably. Our Wave 25 countdown guide covers the onboarding steps week by week, and the complete e-invoicing guide for Saudi Arabia explains invoice types and mandatory fields in more depth.

A practical e-invoicing checklist for restaurants

1. Confirm your integration date from ZATCA's notification or your own revenue figures for 2022 to 2025.
2. List every device that issues bills in every branch, including kiosks, handhelds and the catering desk.
3. Confirm with your POS provider that the solution supports Phase 2 and decide where invoices are generated and stamped.
4. Print and scan test bills on each printer model to check the QR code and the Arabic text.
5. Remove any ability to edit or delete issued invoices and set up manager-approved credit notes for refunds and corrections.
6. Define how split bills, pre-bills, complimentary items and staff meals are handled in the system.
7. Agree the invoicing arrangement in writing with each delivery platform and review it with your tax adviser.
8. Make sure corporate customers can receive a standard tax invoice that is cleared before it is shared.
9. Assign someone to review the reporting queue and rejected invoices every day.
10. Add device onboarding to your new-branch and device-replacement procedures.

When does a restaurant need more than a compliant till?

A single café can usually meet these rules with a ready-made POS that supports Fatoora integration. The picture changes for groups with several branches, brands or a central kitchen, where invoices also need to flow into stock, settlements and accounting without re-keying. In those cases the e-invoicing layer is best designed together with the rest of the operation, through a connected ERP and custom software setup or a restaurant POS system built around how your branches actually work.

If you are unsure how your current setup handles voids, delivery orders or multiple devices, send us a short description of your branches and systems. Amwaj Solutions will review it and reply within 24 to 48 business hours.