Four points to establish first
Structured, not scanned
ZATCA defines an e-invoice as a structured electronic invoice generated through electronic means. Scanning a paper invoice or saving an image/PDF alone does not make it a compliant e-invoice.
Two common tax-invoice types
A tax invoice is generally used for B2B transactions. A simplified tax invoice is generally used for B2C transactions.
Two implementation phases
Phase One began on 4 December 2021. Phase Two began in waves from 1 January 2023 and requires integration with ZATCA systems for notified groups.
The PDF is not the whole system
Human-readable output is only one part. The generating solution, structured data, security controls, storage, and integration obligations also matter.
Tax invoice or simplified tax invoice?
Tax invoice — usually B2B
For Phase One, ZATCA highlights the invoice type title and the buyer’s VAT registration number when the buyer is VAT-registered. A QR code may be added but is optional for this type in the Phase One summary.
Simplified tax invoice — usually B2C
For Phase One, ZATCA highlights the invoice type title and a mandatory QR code generated by the compliant e-invoicing solution according to ZATCA specifications.
What changes between the phases?
Phase One — generation and storage
Stop handwritten invoices and invoices produced only with text-editing tools. Use a compliant electronic invoicing solution that generates and stores invoices with the required fields and without prohibited functions such as uncontrolled access or invoice/log tampering.
Phase Two — integration
From 1 January 2023, ZATCA has introduced integration in waves. Taxpayers in notified groups need a solution integrated with ZATCA systems and invoices in the required structured format.
Questions to answer before issuing a Saudi tax document
- Is the transaction B2B or B2C, and which invoice type applies?
- Is the buyer VAT-registered, and is its VAT number required?
- Has your taxpayer group been notified for Phase Two integration?
- Does the generating solution meet the current ZATCA business, technical, and security specifications?
- Are the required structured fields, human-readable fields, QR data, storage, notes, and sequence controls implemented?
