Clarification Required for Duplicate Accepted Invoices --HTTP code 111

Clearance and Reporting
1

Dear Team,
On April 10, 2025, one of our clients encountered an issue during invoice generation. When the client posted the invoice data, they received the following ZATCA response:

{"result":"{\"ClearanceInvoice\":\"Connection reset\"}","httpCode":111}

Based on this response, the client assumed that the invoice was not submitted to ZATCA. They then attempted to repost the same invoice by changing the reference number, and this time it was successfully cleared by ZATCA.

However, later the client received a mail from ZATCA containing a list of accepted invoices. Upon review, we found that both invoices were accepted by ZATCA:

  • The first invoice (which received HTTP Code 111) is shown as Accepted in the ZATCA system.

  • The second invoice (which received HTTP Success Code 200) is also Accepted in ZATCA.

We request your guidance on how to handle such cases where duplicate invoices are accepted due to transmission or connection interruption issues.
Additionally, please advise on the appropriate steps for correcting the affected invoices in compliance with ZATCA guidelines.

@Ankit.K.Tiwari — we request your help on resolving our Issue.

Connection reset
2

@sameer when you resend the invoice, it must contain exactly same content (particularly hash shouldn’t change) so that ZATCA can identify duplicate records of same transaction. However, as your client changed invoice refence number, ZATCA cannot treat these two records as duplicate (hash being different). You will have to reverse one of those by passing a credit note. You can consider making a replica of invoice and change invoice type code from 388 to 381 while keeping all other details exactly same as original invoice.