Issuing a ZATCA-compliant tax invoice
Generating the digitally-signed e-invoice per ZATCA's requirements.
Reading time: 1 min · Updated 2026-11-21
What this page is for
Generates a unique UUID, a hash chain, a QR code, and an XAdES-B digital signature for every tax invoice, then submits it to ZATCA.
Who can access this
Any user with sales-invoicing permission, provided ZATCA integration is enabled for the company.
Required permission
manage sales + ZATCA integration enabled
Workflow
- Issue a normal sales invoice first.
- A UUID, QR code, and digital signature are generated automatically for it.
- The invoice is submitted to ZATCA (Clearance or Reporting depending on invoice type).
- ZATCA's response is stored alongside the invoice for audit.
Practical scenario
A retail shop issues a Simplified invoice to a walk-in customer — it's automatically submitted as "Reporting" to ZATCA within the allowed window, and a QR code appears ready to print on the paper receipt.
Note: this part is currently blocked in this guide because it needs real third-party access (not because the feature is missing) — see the accompanying report for the exact status.
Common errors and how to resolve them
- The invoice is stuck "submitting" for a long time — It automatically retries with increasing delays (10, 30, 60, 300, 900 seconds) up to 5 times — check the error log if the issue persists.
Frequently asked questions
Does this feature actually work in production right now?
The code and digital signature are complete and independently verified, but full activation against ZATCA's real portal is on hold until real portal login access (a real OTP) is available — this is a "blocked on external access" status, not a code defect.