Network retries, ERP resubmissions, or manual re-triggers without idempotency protection risk clearing the same invoice twice - creating duplicate tax liability and reconciliation headaches.
Every invoice submission is checked against an idempotency key (a combination of invoice hash and ICV) before it is sent to ZATCA. New invoices proceed normally; duplicates are blocked at the middleware layer and the original clearance status is returned instead.
Zero double-clearance incidents recorded across a deployment handling peak volumes of 65,000 invoices in a single day.
Tell us about your ERP and the mandate you fall under — we’ll show you how we’d handle it.