ZATCA E-Invoicing for Restaurants: A Practical Checklist

ZATCA — the Zakat, Tax and Customs Authority — is the standards body that governs how every commercial transaction is invoiced in the Kingdom of Saudi Arabia. For a restaurant, that means the cloud-based POS at the front counter is a regulated piece of software: every receipt is a tax invoice and must satisfy a specific set of rules.

Here's what the rules actually demand, plain.

Phase 1 — what every POS must already do

If you're operating today, you're under Phase 1 (Generation Phase). The point-of-sale system must:

• Generate invoices electronically — no handwritten or scanned receipts for taxable sales.
• Include a serial invoice number that increments and never resets mid-period.
• Display the VAT registration number (TRN) of the venue.
• Print a TLV-encoded QR code containing the seller name, TRN, timestamp, total, and VAT amount in the ZATCA-defined Tag-Length-Value format.
• Show the VAT breakdown (subtotal, VAT 15%, total) clearly on the receipt.
• Support both Arabic and English in the invoice fields — the receipt should be readable to a ZATCA inspector and to a customer.

If your current solution misses any of those — particularly the TLV QR — it isn't compliant. That's not a "nice to have," it's a regulatory pass/fail.

Phase 2 — what's coming

Phase 2 (Integration Phase) is rolling out in waves. It adds:

• Cryptographic stamps on each invoice, proving the POS hasn't been tampered with.
• Real-time clearance for B2B invoices — submission to the ZATCA portal before the invoice is final.
• UUIDs on every invoice for traceability.

For most B2C restaurant operations, Phase 2 obligations apply on the date ZATCA notifies your business — typically with a 6-month lead time. The right cloud POS vendor handles this rollout for you; you shouldn't be re-implementing crypto.

What to ask your POS vendor

A short, direct list:

1. "Show me a current production invoice. Where's the TLV QR?"
2. "Walk me through how you handle Phase 2 — do I need a hardware module, or is it baked into your cloud-based POS?"
3. "What happens if ZATCA changes the invoice schema mid-year? Will my system update automatically?"
4. "Can your tax invoices export cleanly to my accountant's tools for VAT filing?"
5. "When the internet drops at the venue, what happens to the invoice serial sequence?"

Vendors that can't answer these in plain language are vendors you don't want.

Why this matters beyond compliance

Compliance isn't just about avoiding fines. A restaurant management solution that handles ZATCA cleanly also handles:

• Daily Z-reports your accountant can drop into VAT returns.
• Per-branch tax invoice splits for multi-outlet operations.
• A customer-readable receipt that builds trust at checkout.

Get the invoicing layer right and the rest of your financial management gets quieter.

How TheOctopus AI handles ZATCA

TheOctopus AI is ZATCA Phase 1 compliant out of the box: TLV QR codes on every invoice, automatic VAT breakdown, dual-language receipts, and a serialised invoice sequence that survives offline operation. Phase 2 readiness is part of our product roadmap and rolls out automatically — no service call required.

Read more on our ZATCA compliance page, or book a demo and we'll print a sample invoice live from your menu.