Saudi Arabia's e-invoicing regulation, administered by ZATCA through its Fatoora platform, changed what an invoice is: not a PDF that happens to contain tax details, but a structured, controlled electronic record. For an ERP, that makes compliance a software requirement, not an accounting preference.
Phase one: generation
The first phase, which began in December 2021, requires taxpayers to generate and store invoices electronically. In practice that means invoices created in a system rather than by hand, with sequential numbering, a QR code on simplified invoices, and controls that prevent invoices from being silently edited or deleted. Arabic content is required, and bilingual documents are common.
Phase two: integration
The second phase requires the invoicing system to connect to ZATCA. Standard invoices, typically business to business, are sent for clearance before they are issued to the buyer. Simplified invoices, typically business to consumer, are reported within a defined window after issue. Invoices are produced in a prescribed structured format, carry a cryptographic stamp, and your system must be onboarded to the platform with the certificates ZATCA issues.
It is rolled out in waves
ZATCA brings taxpayers into the integration phase in groups, based on criteria it publishes, and notifies each group in advance. The first step is to find out whether you have been notified, and when your deadline falls.
What your ERP needs
- Separate handling of standard invoices, simplified invoices, credit notes and debit notes
- Generation of invoices in the required structured format with QR code and cryptographic stamp
- Integration with the ZATCA platform for clearance or reporting, including error handling when a submission is rejected
- Tamper-resistant storage, sequential numbering and a full audit trail
- Arabic and English documents with right-to-left layout
- Management of onboarding certificates and renewals
Failure modes worth planning for
- Rejection at clearance. A standard invoice that fails validation cannot be issued, so the system needs clear error messages and a way to correct and resubmit.
- Connectivity. Reporting windows and clearance depend on the platform being reachable, so queueing and retry logic matter.
- Credit notes. They must reference the original invoice and follow the same flow.
- Multiple branches. Each device or solution unit may need its own onboarding.
Scoping the work
Before building, confirm which phase and wave apply to you, which document types you issue, and whether you will integrate directly or through a certified solution provider. These decisions change the scope considerably, and a good proposal states them explicitly.