Description
Hello ZATCA developer community,
We’ve encountered the following scenario in our local system:
- We successfully issued Invoice #118, updated our local ICV to
118
, and computed its hash. - We submitted the invoice to the FATOORA platform and received its IRN and InvoiceHash.
- Our client’s database suffered a failure, and when we restored from an older backup:
- The local ICV reverted to
117
- Invoice #118 no longer exists in our database
- We still have the original XML file for Invoice 118
- The local ICV reverted to
As a result, there’s now a gap in our local invoice sequence, even though Invoice 118 is officially recorded on ZATCA’s side.
Questions
-
Re‑submission:
Can we re-send Invoice 118 using the existing XML, or will the platform reject it since it’s already registered? -
Local Recovery:
What is the correct procedure to fill this sequence gap locally without breaking the ICV chain or risking penalties? -
Failure Notification:
Should we file a “Failure Notification” via the Verify Taxpayer API for the affected period? -
Continuation:
Once Invoice 118 is restored, how should we proceed with Invoice 119 regarding ICV and PIH?
Additional Details
- Invoice 118 XML: We have the original XML with its IRN and InvoiceHash.
- Previous PIH: Before the incident, PIH(118) = hash of Invoice 117.
- The restore did not affect any other invoices or future IRNs/UUIDs.
Thank you!