ZATCA's e-invoicing regulation applies to every VAT-registered business in Saudi Arabia, rolled out in phases rather than all at once. The first phase requires businesses to generate invoices electronically with specific fields and a QR code. Later phases require direct integration with ZATCA's platform for clearance and reporting.
What the phases actually ask for
Phase One, the generation phase, is about the document itself: invoices must be issued from a compliant electronic system, carry the required fields, and include a QR code on simplified invoices. Phase Two, the integration phase, is where the system has to talk to ZATCA directly — cryptographic stamping, a digital signature, and either clearance or reporting depending on the invoice type.
For SMEs, the practical question is usually whether existing invoicing software — or a spreadsheet — can meet these requirements at all. In most cases it cannot without add-ons, which is why e-invoicing is often the point where businesses move to a proper ERP.
Where SMEs usually get caught out
- Invoicing and accounting live in separate tools, so the compliant invoice and the ledger entry can drift apart.
- Arabic fields are treated as an afterthought rather than a requirement of the document.
- Credit and debit notes are forgotten, even though they carry the same obligations as the invoice they correct.
- Nobody owns archiving, despite the retention period running for years after the invoice is issued.
Treat e-invoicing as a system change, not a document-formatting fix.
The businesses that handle this smoothly run invoicing, accounting and compliance on the same platform, so QR codes, cryptographic stamps and clearance requests are generated correctly every time, automatically — rather than being assembled by hand each period.
