Saudi Arabia playbook: Fatoora clearance, simplified-invoice reporting and VAT returns
Saudi Arabia's e-invoicing runs in two phases: a generation phase that has been live since December 2021, and an integration phase with ZATCA's Fatoora platform that taxpayers join in notified waves. Once integrated, your ERP has two different routes. Standard tax invoices (business customers) are cleared by ZATCA before you share them. Simplified tax invoices (mainly consumers) are issued first and reported afterwards. Mixing up the two routes is the most common design error.
Data for Saudi Arabia on this site: Saudi Arabia country page · Saudi Arabia × ERP e-invoicing support · Saudi Arabia e-invoicing status
This playbook uses the same structure as the other country playbooks. Facts come from the Saudi Arabia page and the ZATCA sources it cites. ERP support is on the Saudi Arabia e-invoicing matrix.
What applies
- Integration wave. Your integration date is set by the wave ZATCA notifies you of. The wave 25 announcement, for example, targets taxpayers whose VAT-subject revenue exceeded SAR 187,500 in a specified year from 2022 to 2025, with integration by 1 February 2027 (ZATCA wave 25 announcement). Treat your own notification as the trigger.
- Two routes. Clearance of standard tax invoices before they are shared with the buyer; reporting of simplified tax invoices and related notes within 24 hours of issue (ZATCA detailed guideline).
- Language. The Saudi Arabia page records that simplified tax invoices must be issued in Arabic.
- VAT return. As listed below.
| Requirement | Type | Frequency (from the country page) | Status on this site |
|---|---|---|---|
| VAT return | ordinary return | Monthly if annual supplies exceed SAR 40m; quarterly otherwise | verified |
Operating model
- The ERP classifies each document as a standard or simplified tax invoice, or a credit or debit note linked to one.
- Standard invoices go to ZATCA for clearance. Only a cleared invoice is shared with the buyer.
- Simplified invoices are issued to the customer and then reported within the required time.
- Credit and debit notes keep a reference to the original invoice and follow its route.
- The structured file, ZATCA's response and the customer copy are stored together.
ZATCA states that its list of solution providers is indicative; choosing a listed provider is not in itself proof of compliance (ZATCA e-invoicing hub).
ERP set-up checklist
- Wave, integration date and the solution units registered with ZATCA recorded, with credential owners and renewal dates.
- Separate queues for clearance, simplified reporting and corrections.
- Document type set from customer and transaction data, not chosen by the user at print time.
- Arabic text available for simplified invoices.
- No re-issue under a new identity to recover a lost response.
- For accounts payable, validation of the received tax document kept separate from commercial approval.
Worked example: a cleared invoice and a credit note
The 15% rate is from the Saudi Arabia page, sourced from ZATCA. Amounts are illustrative round numbers.
A company sells goods for SAR 1,000 net to a VAT-registered business. The standard invoice is cleared and then shared. Later, the buyer returns goods worth SAR 100 net, and a credit note referencing the original invoice is cleared as well.
| Step | Account | Debit | Credit | Note |
|---|---|---|---|---|
| Standard invoice, cleared | Trade receivables | 1,150.00 | ||
| Sales revenue | 1,000.00 | |||
| Output VAT | 150.00 | 15% | ||
| Credit note, cleared, linked to the invoice | Sales returns | 100.00 | ||
| Output VAT | 15.00 | |||
| Trade receivables | 115.00 |
Net output VAT is SAR 135 for the period's VAT return. If the first clearance attempt had been rejected, nothing should have been posted or shared until a corrected invoice was cleared. A simplified invoice behaves differently: it is already with the customer, so a reporting failure is followed up in its own queue rather than by cancelling the sale.
Exceptions to plan for
- Clearance rejected before delivery; reporting acknowledgement missing for a simplified invoice.
- Exports and supplies to non-residents, which need their own scope assessment.
- Government customers with their own references.
- Certificate renewal for each solution unit.
- Monthly or quarterly VAT filing, depending on annual supplies as stated on the VAT return row.
Worksheet
Use the Saudi Arabia operating checklist.
Worksheet: Saudi Arabia operating checklist
Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment.
Show the worksheet
Use with the Saudi Arabia playbook.
Scope
- Entity, VAT number:
- Notified wave and integration date (from your ZATCA notification):
- Solution units registered; credential owners; renewal dates:
- VAT filing frequency and source:
Routes
| Document | Route | Queue | Owner |
|---|---|---|---|
| Standard tax invoice | Clearance before sharing | ||
| Simplified tax invoice | Reporting after issue | ||
| Credit or debit note | Follows the original's route |
Tests
- ☐ Standard invoice rejected before delivery: nothing posted or shared
- ☐ Simplified invoice awaiting acknowledgement: tracked, not cancelled
- ☐ Credit note references the original invoice
- ☐ Arabic text on simplified invoices
- ☐ Lost response recovered without a new fiscal identity
Each period
- ☐ Cleared and reported populations = ledger
- ☐ Output VAT accounts = VAT return values
- ☐ Return filed by the deadline on the row; payment made
Sources checked: 27 October 2026, through this site's Saudi Arabia page (ZATCA sources read on 17 October 2026). Detailed security, certificate and geographic rules need ZATCA's current technical pack.
Related guides and data
- Correct an e-invoice without creating duplicate tax or accounting records
- Build an e-invoice status model finance can trust
- Invoice language, tax rounding and number formats across countries
Data on this site: Saudi Arabia country page · Saudi Arabia × ERP e-invoicing support · Saudi Arabia e-invoicing status · E-invoicing country × ERP matrix · VAT reporting requirements by country
In Country playbooks: previous Italy playbook: SdI e-invoicing, conservation and periodic VAT reporting · next Romania playbook: RO e-Factura, the D300, D394 and D390 returns and the D406 SAF-T · Guides by task · All guides
Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-27.
Related: Glossary – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more).
Page last updated: · Markdown version · Suggest a correction