VAT Tax Invoice Requirements Saudi Arabia: A Field-by-Field Guide

A practical checklist for choosing, reviewing, and recording full and simplified Saudi VAT invoices without confusing tax, e-invoicing, and IFRS timing.

What do VAT tax invoice requirements Saudi Arabia cover?

VAT tax invoice requirements Saudi Arabia businesses must follow start with one practical question: what document proves this taxable supply, and what must it show? A tax invoice is not just a receipt. It supports the supplier's output VAT, the customer's input VAT review, and the balance in [accounts receivable](/glossary#accounts-receivable-ar). A missing field can therefore become a tax-control problem even when the sale itself is real.

The legal starting point is Article 53 of ZATCA's [VAT Implementing Regulations](https://zatca.gov.sa/en/RulesRegulations/Taxes/Pages/VATImplementingRegulations.aspx). It distinguishes a full tax invoice from a simplified tax invoice and sets the core information for each. The electronic-invoicing rules then add generation, format, security, QR, clearance, or reporting requirements depending on the invoice type and whether the taxpayer has entered the integration phase.

Keep three dates separate. The supply date helps determine when VAT becomes due. The invoice date records when the document was generated. For a taxable supply to a VAT-registered customer or another legal person, the tax invoice is generally due no later than fifteen days after the end of the month in which the supply occurred. That deadline is not permission to delay recording a transaction whose accounting and tax point already arose.

This guide is educational, not a substitute for advice on unusual transactions. Use the current ZATCA regulations, your integration-wave notice, and professional advice when a fact pattern involves self-billing, agents, margin schemes, exports, or complex continuous supplies.

Which invoice should you issue: tax or simplified?

The buyer and transaction usually determine the starting form. A full tax invoice is the normal document for a taxable supply to a VAT-registered business or another legal person. A simplified tax invoice is normally used for supplies to an end consumer and may also be used for a supply below SAR 1,000, subject to the regulatory exclusions and conditions. It is not available for an internal GCC supply or an export of goods merely because the amount is small.

Do not treat “tax” and “electronic” as competing labels. Both full and simplified tax invoices can be electronic invoices. ZATCA defines an electronic invoice as one generated in a structured electronic format through electronic means; scanning a paper invoice does not convert it into an e-invoice. The [ZATCA e-invoicing guide](/learn/zatca-e-invoicing-guide) explains the generation and integration phases in more depth.

Phase 2 changes the workflow. For taxpayers notified to join Phase 2, the process matters as much as the visible PDF. Full tax invoices follow the clearance model, while simplified tax invoices are reported after issue within the prescribed window.

A compliant system must preserve structured data and controls; a visually convincing document created in a word processor is not enough. ZATCA's [e-invoicing overview](https://zatca.gov.sa/en/E-Invoicing/Introduction/Pages/What-is-e-invoicing.aspx) is the current official orientation page.

VAT tax invoice requirements Saudi Arabia: full invoice checklist

For a full invoice, review the document field by field before asking whether the total looks reasonable. Article 53 requires the invoice details in Arabic; another language may also appear as a translation. That means an English-only invoice should not pass your Saudi VAT review simply because its arithmetic is correct.

A checklist is stronger when each field ties to evidence. Match the customer name to the contract or order, quantities to delivery evidence, prices and discounts to approved terms, and the VAT treatment to the tax code configured in the accounting system. If one invoice contains standard-rated, zero-rated, or exempt lines, do not hide them inside one undifferentiated total.

Recalculate the document. Recheck line extensions, subtract genuine discounts before VAT where appropriate, group taxable amounts by treatment, calculate VAT, and reconcile the result to the gross amount.

Rounding should follow the invoicing solution's compliant logic consistently; staff should not overwrite the VAT total merely to force agreement with a customer's purchase order.

What must a simplified tax invoice contain?

A simplified invoice is shorter, but “simplified” does not mean informal. Under Article 53, its core details are: the issue date; the supplier's name, address, and tax identification number; a description of the goods or services; the consideration payable; and the VAT payable or a statement that the consideration includes VAT. ZATCA's e-invoicing requirements add the prescribed invoice title and a mandatory QR code for simplified invoices.

When a customer scans the QR code, the basic encoded information includes the seller's name, the seller's VAT registration number, the invoice timestamp, the total including VAT, and the VAT total. Phase 2 specifications add technical data and security controls. Accountants should validate the human-readable invoice and the system workflow, not attempt to rebuild the technical standard from a visual checklist. The latest documents are collected in ZATCA's [official e-invoicing library](https://zatca.gov.sa/en/E-Invoicing/Introduction/Guidelines/Pages/default.aspx).

A practical daily control is to select several simplified invoices from different tills, scan the QR codes, and reconcile their gross sales and VAT to the point-of-sale summary. This catches configuration errors that a single perfect sample would miss.

Worked example 1: full B2B tax invoice and journal entry

Al Manar Office Systems in Riyadh delivers ten monitors to Wadi Projects Company on 18 August. The approved unit price is SAR 2,000, and a documented trade discount of SAR 2,000 applies to the order. Both entities are VAT registered, the goods are standard-rated, and control passes on delivery. Al Manar generates the full tax invoice on 19 August.

The invoice should show both legal names and addresses, Al Manar's VAT number, Wadi Projects' VAT number, the unique sequence, issue and supply dates, quantity, unit price excluding VAT, discount, taxable amount, 15% rate, VAT of SAR 2,700, and gross total of SAR 20,700. The arithmetic alone is not enough; the field evidence makes the document reviewable.

Because delivery and the relevant performance obligation are complete in this example, the [journal entry](/glossary#journal-entry) is:

This entry follows the same mechanics explained in the [Saudi VAT accounting guide](/learn/vat-accounting-saudi-arabia). But do not turn the invoice date into an automatic revenue-recognition rule. Under IFRS 15, revenue follows satisfaction of the performance obligation. If Al Manar had invoiced before transferring control, the accounting could involve a contract liability instead. Review the [IFRS 15 revenue recognition guide](/learn/ifrs-revenue-recognition) when billing and performance occur at different times.

Worked example 2: simplified B2C invoice and daily control

Najd Bean Café in Dammam sells drinks and food to end consumers through a compliant point-of-sale system. On 20 August, one customer order has a tax-exclusive value of SAR 160. The items are standard-rated, so VAT is SAR 24 and the customer pays SAR 184. The system generates a simplified invoice immediately with the required Arabic details and QR code.

At day-end, the café does not post 240 separate sales manually. Suppose the compliant till summary shows tax-exclusive sales of SAR 8,000, output VAT of SAR 1,200, and gross receipts of SAR 9,200. The accountant can post the controlled daily batch using those totals, provided the underlying invoices remain available and the batch reconciles to payment settlements and the [general ledger](/glossary#general-ledger).

The control should prove four things: invoice numbers are complete, gross receipts agree to cash and card sources, output VAT agrees to the tax report, and simplified invoices were reported to ZATCA within 24 hours if the café is in Phase 2. If the card processor settles SAR 9,100 after withholding SAR 100 of fees, do not reduce sales to SAR 9,100. Record the gross sale, output VAT, receivable from the processor, and fee separately.

This example shows why invoice compliance and accounting control belong together. A valid QR code cannot explain an unreconciled cash shortage, while a balanced entry cannot cure a missing or unreported electronic invoice.

What common VAT invoice mistakes should you watch for?

Most invoice failures are ordinary process mistakes, not advanced tax puzzles. Reviewers should look for patterns rather than correcting one document at a time.

  • Wrong document type: a B2B supply is pushed through a consumer receipt flow without the required customer information or clearance process.
  • English-only full invoice: the layout looks professional, but Article 53 requires the prescribed details in Arabic; another language is a translation, not a replacement.
  • Commercial registration used as VAT number: the two identifiers serve different purposes. Validate the VAT number captured in the customer and supplier masters.
  • Supply date omitted: staff assume the issue date is always the supply date, even when delivery occurred earlier.
  • Discount applied after VAT: the system calculates VAT on SAR 20,000 even though the genuine taxable amount after trade discount is SAR 18,000.
  • Zero-rated and exempt treated as synonyms: both may produce no output VAT on the line, but the legal treatment and input-tax consequences differ. The invoice needs the correct explanation when the standard rate is not charged.
  • PDF mistaken for compliance: a PDF can be the human-readable presentation, but Phase 2 also depends on structured data, clearance or reporting, and the required security controls.
  • Issued invoice edited or deleted: corrections should use compliant credit or debit notes and preserve the audit trail.
  • Net settlement posted as revenue: payment fees, refunds, and cash differences are buried in sales, breaking both revenue and VAT reconciliation.
  • No evidence of review: the business has a checklist but cannot show who reviewed exceptions or how they were resolved.

Turn the checklist into a repeatable control. Assign an owner, select samples across branches and invoice types, retain exception evidence, and trace totals from invoices to the VAT return. A control that only asks “does the total look right?” will miss identity, timing, treatment, and integration failures.

How should you practise Saudi VAT invoice review?

Start with blank documents, not memorized lists. For each scenario, decide whether the customer needs a full or simplified invoice, identify the supply date, assemble the required fields, recalculate VAT, and post the entry. Then introduce one defect—an incorrect VAT number, a missing supply date, a discount applied after tax, or a Phase 2 reporting gap—and explain its consequence.

Use a four-pass review rhythm:

  • Identity: supplier, customer, VAT numbers, and addresses.
  • Transaction: goods or services, quantities, prices, discounts, and supply date.
  • Tax: taxable amount, treatment, rate, VAT, and gross total.
  • System: sequence, QR code, structured record, clearance or reporting status, and retention.

Candidates preparing for the Saudi VAT Specialist exam can connect this field-level practice to the broader [tax-invoices and records exam guide](/learn/vat-specialist-tax-invoices-records), then use [VAT Specialist exam preparation](/prep/socpa/vat-specialist) for applied question practice. Accountery complements official ZATCA material; it is not affiliated with or approved by ZATCA or SOCPA, and practice does not guarantee an exam result.

The professional habit to keep is simple: classify, evidence, calculate, post, reconcile. When every invoice passes those five verbs, the document supports tax compliance, the accounting entry, and the audit trail instead of becoming a PDF stored without control.