I would like to seek clarification regarding the behavior of the system when the ZATCA portal is unavailable.
When the ZATCA portal is down, we enable the Offline Posting feature, allowing invoices to be queued locally. Once the portal is back online, these queued invoices are automatically pushed to the portal for synchronization.
However, we would like to understand the implications in scenarios where the ZATCA portal remains offline for more than 24 hours. Specifically:
If Offline Posting remains enabled and the downtime exceeds 24 hours, will the offline invoices still be successfully synchronized once the portal is restored?
Are there any limitations or restrictions on syncing invoices that were generated during an extended downtime (i.e., beyond 24 hours)?
Is enabling Offline Posting recommended in such cases, or are there alternative best practices we should follow?
Does ZATCA provide any exceptions or special handling procedures for outages lasting longer than 24 hours?
Your guidance on this matter will help us ensure compliance and maintain continuity in our invoicing process.
in case of failure, (either from ZATCA’s side or your side).
Your system should be re-submitting the XML documents again and again till receiving a response “200, 202,400”
if you are afraid that you will not be ably to comply with the 24 hours rule for the simplified tax invoices, then, you are advised to raise a failure notification from ZATCA’s website.
We have the following scenario:
The POS terminal is offline, if the program is running and there are invoices that have not been shared with Zatka for 24 hours, the program will stop until the pending invoices are uploaded.
The issue occurs when the device is turned off and not turned on until 24 hours later.
How can we remedy this, of course, the terminals are often Desktop terminals and as long as the internet is not available we will not be able to connect to them.