ZATCA Phase 2 E-Invoicing for ERPNext (Saudi Arabia)

ECOSIRE builds a proper Frappe app that installs cleanly on your bench alongside ERPNext, so nothing in core is patched and every future bench update stays safe. The app adds its own DocTypes — a per-branch/device ZATCA Device holding the CSR configuration, private key, compliance CSID and production CSID, and a ZATCA Invoice Log that stores the generated XML, the invoice hash, the previous-invoice hash for the chain, the signed QR TLV, the ZATCA request/response payloads, and the clearance or reporting status. Custom fields on Sales Invoice surface the ZATCA UUID, ICV counter, QR image and clearance status directly on the document, and a role profile keeps signing keys and logs visible only to Accounts and Compliance roles.

Technically, the flow is driven by hooks.py document events. On Sales Invoice on_submit, a server-side handler builds the UBL 2.1 XML from the invoice, computes the SHA-256 hash, chains it to the previous invoice's hash, canonicalizes and signs the document with the device private key (ECDSA), and generates the TLV-encoded, Base64 QR per the ZATCA spec. Standard (B2B) invoices are POSTed to the clearance API and only marked valid once ZATCA returns the cleared, counter-signed XML; simplified (B2C) invoices are reported and queued. A scheduler event retries any documents left in a pending state (network blips, ZATCA maintenance) so nothing is silently dropped, and credit/debit notes carry the correct reference and reason codes. Onboarding — CSR generation, compliance checks and production CSID issuance — is exposed as whitelisted methods callable from a guided setup screen, and the whole thing is reachable over the Frappe REST API for POS or external systems.

Because this is build-to-order, ECOSIRE builds the version scoped to your exact setup — your ERPNext/Frappe v15 or v16 bench, your branches and devices, your B2B/B2C mix, POS or not, and any print-format branding. After a short scoping call we confirm scope in writing, then build, test on a staging bench against the ZATCA sandbox, run UAT with your finance team, and cut over to production CSIDs. Typical delivery is 2–4 weeks from confirmed scope. You receive the full source, a git repository handover, documentation and training, and a post-go-live support window — no instant download, because a compliance integration this consequential should be built and verified for your environment, not shipped blind.