In brief
Article 53(5) includes conditional information; electronic instruments add requirements. Paragraphs (9)–(11) address delegated powers, decision-based relief and the invoice definition. Evidence defects and input entitlement remain separate.
A Saudi standard tax invoice must contain the information applicable to its supply and invoice type, including the relevant electronic requirements. Article 53(5) is the legislative starting point. It contains both general and conditional items; it does not mean that every invoice needs an entry for a reverse charge or used-goods margin scheme.
The practical objective is a document that accurately connects the supplier, customer, supply, tax point, value and VAT treatment. A complete-looking template can still describe the wrong transaction, while a document defect requires its own evidence and correction analysis.
Read Article 53 with the electronic requirements
Article 53(5) sets out standard-invoice information in Arabic, with additional languages permitted. Paragraphs (6) and (9) provide the electronic-invoicing context and authority for additional information. ZATCA’s Tax Invoicing and Records Guideline, version 3, May 2026, section 4.2.3, pp. 18–20, explains the standard-invoice data in that context.
Use both levels. A checklist based only on the lettered legislative items can miss electronic fields. A software validation result, conversely, does not establish that the supplier correctly classified the actual supply.
Sources: Arabic VAT Regulations, Article 53, pp. 55–58; invoicing guideline, section 4.2.3.
Map each field to its actual function
| Article 53(5) item | Required information and relevant condition |
|---|---|
| (a) Issue date | Identify when the invoice was issued; electronic issue-date/time specifications also apply. |
| (b) Sequential identification | A sequential number uniquely identifying the invoice; distinguish this from additional electronic identifiers. |
| (c) Supplier identification | Use the supplier’s correct tax identification, with its VAT registration/group details as applicable. |
| (d) Customer self-accounting | Customer identification and the relevant statement where the customer accounts for tax; additional customer-data rules also apply beyond this particular paragraph. |
| (e) Parties | Supplier and customer names and addresses. |
| (f) Supply | Nature/quantity of goods or nature/scope of services. |
| (g) Different supply date | State the supply date when it differs from the issue date. |
| (h) Values | Amounts by applicable treatment, unit price excluding VAT and relevant discounts not already included. |
| (i) Rate | The applicable VAT rate. |
| (j) Saudi VAT amount | VAT payable stated in Saudi riyals. |
| (k) Non-standard treatment | Explain the applicable treatment where tax is not charged at the standard rate. |
| (l) Eligible margin method | Refer to the profit-margin treatment where the relevant used-goods scheme applies. |
This is a legislative map, not a complete electronic schema. ZATCA’s standard-invoice guidance adds document title, issue time, customer identifiers and other applicable information. Conditional fields should be correctly triggered, not filled with invented values merely to make every row non-empty.
Identify the actual supplier and customer
Section 4.2.3, p. 19, uses the supplier’s registered legal identity, relevant address and VAT registration number, including group registration where applicable. A commercial registration number does not substitute for a required VAT registration number. Similarly, do not confuse a general tax identifier with every other registration field.
The same page requires customer name/address and the customer’s VAT registration number, or the relevant alternative identification when unregistered. The narrower wording of Article 53(5)(d) concerning customer self-accounting does not establish that customer VAT identification can always be omitted from ordinary electronic B2B invoices.
For self-billing or third-party issuance, retain the supplier’s identity as supplier and the customer’s identity as customer; the person preparing the document does not become the supplier merely by issuing it. See self-billing and supplier controls.
Describe the supply and its timing accurately
The description should identify what was actually provided, its relevant quantity or scope, and the values/treatment applied. Linking a service invoice to a contract period or deliverable can strengthen the evidence trail, but a particular wording or purchase-order format is not prescribed here as a universal legal condition.
Issue date and supply date answer different questions. If an ordinary supply was completed before the invoice was issued, recording only the later date can obscure the correct reporting period. Equally, an earlier invoice or advance can create an earlier tax point; continuous or instalment supplies have particular rules. Do not infer the VAT period solely from the date accounts payable enters the document.
Source: invoicing guideline, sections 4.2.3 and 4.5, pp. 18–20 and 25–27.
ZATCA’s currency example and the SAR tax field
Example 3, section 4.2.2, pp. 17–18, describes Al-Madinah’s dollar-priced chemical sale to Al-Safa in March 2021, without an advance. ZATCA’s invoice example converts VAT to SAR using the stated SAMA invoice-date rate. The commercial currency and the required Saudi VAT figure can therefore differ. Read the official example.
Read that example with Article 61’s actual-tax-point rule. It does not establish that invoice date overrides an earlier delivery, invoice or advance under every fact pattern. The currency guide explains the boundary and a separate Dariba illustration.
Arabic information is also required. Section 4.2.1, pp. 16–17, permits recognised numerals, currency symbols and Latin proper names in the described circumstances. That flexibility does not turn a wholly English invoice into a compliant Arabic tax invoice.
ZATCA’s defective-invoice example: evidence remains a separate decision
Example 22, section 9.5, p. 47, describes registered trader Tariq’s SAR 3,000 purchase. The supplier’s invoice lacks his address and the goods quantity, and the supplier does not provide a corrected invoice despite a request. ZATCA says it may, at its discretion, accept the document with the supporting supply/payment evidence. Read Example 22.
The example supports neither routine omission of required fields nor automatic permanent loss of recovery for every defect. Article 49(7) governs evidence and discretionary alternatives. First seek a compliant correction and substantiate the actual supply, correctly charged tax and entitlement; do not treat discretionary acceptance as already obtained. A compliant document also cannot create recovery for blocked or exempt-use expenditure.
Delegated invoicing powers need the actual decision
Article 53(9) authorises the Governor to change the required invoice information and prescribe additional details for electronic invoicing. Paragraph (6) separately requires electronic issuance in the prescribed cases under an effective regulation issued by the Minister or Board. These provisions explain why the legislative field list must be read with the applicable electronic instruments.
Paragraph (10) gives ZATCA power to suspend or cancel the obligation to apply the E-Invoicing Regulation, wholly or partly, for a category of taxpayers or specified taxpayers, after studying the reasons, and to issue the necessary decisions. The power is not a waiver a business can grant itself. A supplier relying on relief must establish the actual decision, the persons and requirements it covers and its operative period. An internal system failure or a pending request does not, by itself, establish that such a decision applies. This paragraph does not state that relief from electronic requirements cancels the underlying supply, output VAT or every invoice obligation.
Paragraph (11) also defines a tax invoice, wherever the term occurs in the Regulations, to include invoices issued under any of Article 53’s provisions. Read this with Article 49(7)(a)‘s express recognition of a correctly issued simplified invoice. The term does not invariably mean only the standard form, while a commercial receipt still needs to satisfy the applicable rules.
Source: Arabic VAT Regulations, Article 53(6) and (9)–(11), pp. 56–58. The authority to issue a decision and an actual decision applicable to a supplier are distinct evidence requirements.
Dariba’s review approach: connect the document to the return
For each material invoice, establish supplier/customer identity, permitted invoice type, supply description, values, treatment, issue date, tax point and relevant electronic status. Where a field is conditional, document why the condition applies. Where information is wrong, identify the appropriate correction rather than silently editing an issued record.
Article 54(3) addresses party-data errors, while changes in tax or consideration require their applicable adjustment analysis. Keep the original and linked correction records. The needed workflow depends on the error and electronic requirements; no universal cancellation/reissue instruction is asserted here. Continue to credit and debit notes or the invoicing overview.
Key takeaways
- Article 53(5) is the legislative starting point, not the entire electronic schema or twelve universally non-empty boxes.
- A narrow self-accounting paragraph does not remove other standard electronic customer-identification requirements.
- Supplier identity, description, quantities/scope and tax point must match the actual transaction.
- ZATCA Example 3 supports foreign commercial pricing with SAR VAT on its stated timing facts.
- ZATCA Example 22 addresses defective evidence at ZATCA discretion; acceptance is not automatic and correct documents do not create blocked entitlement.
- Corrections should preserve original records and follow the actual error and applicable electronic procedure.
- Article 53(10) relief requires an actual applicable ZATCA decision; the delegated power is not a self-approved waiver.
Sources
- ZATCA - VAT Implementing Regulations, Arabic tenth edition, April 2025Current Arabic Article 53(6),(9)–(11): electronic requirements, delegated information and relief powers, and the meaning of tax invoice. Existing Articles 49(7),54 and 61 analysis retained.
- ZATCA - Tax Invoicing and Records Guideline, version 3, May 2026Detailed types pp13-15,23-24; standard data pp16-20; timing pp25-27; notes and Examples 17-21 pp36-39; alternative evidence Example 22 p47.
- ZATCA - Published E-Invoicing Implementation Resolution, English translationClauses First/Second pp1-4; Annex 1 field1.2 p17. Current legislation page links this resolution; Arabic version prevails. No software/integration-date certification.
General information only. Actual supplies, facts, applicable periods and controlling Arabic legislation determine the result. Official examples are distinguished from Dariba analysis and original illustrations. Seek advice or clarification where the arrangement or source material leaves a specific issue unresolved.
