We would like to inform you that we have received numerous complaints from our customers stating that the Zatca platform has been completely out of service since 07:00 AM today, Aug 23, 2025, until the time of sending this message.
This outage has disrupted our ability to provide our services as required, leading to customer dissatisfaction and impacting their business.
We hope you can urgently clarify the reasons for this outage and the expected timeframe for resuming service.
@idaoud and @Ankit.K.Tiwari we are fang the same response code error 200 and response body = NULL since yesterday early morning and the issue is still appear and cause stopping for our customers the sales operation since they couldn’t generate the invoices as usual.
please we are waiting your response and cooperation to resolve this NEW issue which a lot of system Vendors and companies were facing since yesterday.
Many of our clients are facing the same issue.
We didn’t take this situation into account, because we didn’t expect it in the first place, and our system considers the standard invoice to be neither cleared nor rejected nor accepted.
So please guide us on what we can do so that the chain is not affected.
Also, these invoices may be considered as cleared by Zatca but not by our internal system, so they will not be included in the tax return, and this may result in a liability of some kind.
Dear @Ankit.K.Tiwari, I hope this message finds you well. We are currently receiving the following response for all of our clients when connecting to the ZATCA API:
{StatusCode: 401, ReasonPhrase: 'Unauthorized'}
Could you kindly provide us with more details regarding this issue? Additionally, we would appreciate it if you could share an estimated timeline for when this matter is expected to be resolved. This is at simulation portal and at Production we are receving Object reference not set to instance of object and response body is emty
Dear @Ankit.K.Tiwari, @idaoud
I have already updated the SDK version but the issue is still the same. If I bypass the Compliance API and directly call the Clearance API, it works fine without any problem. But since Compliance API is mandatory for checking invoice status, the Unauthorized (401) response is creating a blocker.
We are also facing the same issue where we are getting null response from Zatca but the status marked as 200 for both REPORTING and CLEARANCE api. Kindly please help one this.
We are having similar issue. We cleared B2B invoice and received response 200 but the body was empty. Therefore we have a successfully reported B2B invoice without clearedInvoice payload. Without this payload we cannot “generate” the QR code as it is located inside returned payload,.
When it is expected to be solved? What we should do for the problematic invoices? Retry?
@sergei.shishov team checked some of the hashes shared by community members above in this thread, majority of those hashes are not found on ZATCA’s side, implying those invoices were not received by ZATCA. Teams are investigating this issue, appreciate if you and all members can share some sample request, response, IP address, certificate details on SP Support email.
Dear @Ankit.K.Tiwari , kindly advise, what should we tell our clients about these impacted invoices? Have they consumed at all at ZATCA’s end? We want to avoid duplicate submissions and willing to share clear instructions to clients, please assist us with precise communication.