Live · Phase 2 ZATCA Phase 2,
actually built in.
Saudi e-invoicing that clears with the authority in the background: device onboarding, cryptographically signed UBL invoices, QR codes, clearance for standard invoices and reporting for simplified ones — validated against ZATCA's own sandbox.
Sandbox-verified
signing and submission validated against ZATCA's developer sandbox
Async and resilient
submissions retry with backoff; nothing blocks your invoicing
Credit notes too
corrections follow the compliant path
From onboarding to cleared invoices.
Onboard your device
Enter the OTP from the ZATCA portal; OneBooks obtains and renews your CSID certificates for you.
Issue invoices
Sending an invoice signs the UBL XML, chains the hash, and prints the QR code — automatically.
Cleared
Standard invoices clear, simplified ones report; the status and the authority's own QR appear on the invoice.
Compliance at the posting event.
E-invoicing artefacts are minted at the moment an invoice is issued, atomically with its accounting entry — drafts carry nothing, issued invoices carry everything.
- ✓ Signed UBL 2.1 XML — XAdES-signed, with the invoice hash chain the authority requires.
- ✓ QR codes — generated for every invoice; the authority's own QR is printed on cleared standard invoices.
- ✓ Clearance and reporting — standard invoices go to clearance, simplified invoices to reporting, in the background with retries.
- ✓ Credit notes — issued as compliant e-invoices too.
- ✓ Kill-switches — pause clearance or freeze issuance if the authority asks.
Sell in Saudi Arabia without a compliance project.
Phase 2 requirements are exacting. Here they're an implementation detail your invoices simply meet.
- ✓ No separate tool — e-invoicing lives inside the same invoice you already send.
- ✓ Voids blocked after clearance — corrections happen through credit notes, as the rules require.
- ✓ Arabic and English — invoices and the whole product, right to left.
ZATCA integration — common questions
What do I need to get started?
A OneBooks account and your ZATCA onboarding OTP. Device onboarding, certificate issuance and renewal, signing and submission all happen inside OneBooks.
Does a slow authority block my invoicing?
No — submissions are asynchronous with backoff and retries. The invoice is issued and posted immediately; clearance follows.
What about credit notes?
Credit notes are issued as compliant e-invoices and submitted the same way.
Is it really validated?
Yes — the signing conventions and submission flow were verified end-to-end against ZATCA's developer sandbox.
Issue your first cleared invoice.
Start free, onboard your device, and send an invoice that clears with ZATCA on its own.