Clarification on Response Code 208 – Duplicate Invoice Hash

Clearance and Reporting
1

We are experiencing an issue when submitting invoices through the e-invoicing system.

  • VAT Number: 310382800700003

  • Invoice Date: 28 September

  • Invoice Hash in question: wZoJPDiVOvK+SqezPXvCO3cW82Tk9d4gV/FCj+4uDF4=

  • Response Received: 208 – WarningMessages Category: Duplicate-Invoice

    • Warning Message Code: Invoice-Warning

    • Message: Invoice Hash Previously Submitted

    • Status: WARNING

We would like to clarify the following:

  1. Our records show that we did not submit the same invoice hash more than once.

  2. Despite no duplicate submission on our side, the portal is returning 208 – Duplicate Invoice Hash warning.

Could you please investigate and explain why this invoice hash is being flagged as already submitted, and guide us on how to prevent this warning in the future?

2

Dear Aturkistani, idaoud , Ankit.K.Tiwari Can you help me find out? why this warning issue by zatca server?

3

Dear @aliaslam7786

Thanks for reaching out,

To provide comprehensive support as usual, Can I kindly ask you to elaborate with the below:

1- What is the exact API that you are hitting?
2- When the issue started?
3- Are you facing the same issue with other requests?

Thanks,
Ibrahem Daoud.

4

Hello idaoud ,

Thank you for your response. Please find the details below:

  1. I was hitting the Clearance API, where I received the status 208.
  2. The issue occurred today, September 28, 2025, at 1:08 PM.
  3. No, I am facing this issue only for this particular request and not with other requests.
5

Morning @aliaslam7786

Thanks for your elaboration, can I kindly ask you to share the full payload via below mail:

SP mail: sp_support@zatca.gov.sa

Additionally, please share here the email address you will reach out from.

Thanks,
Ibrahem Daoud.

6

I’m encountering this error when making a submission with automatic retry. I believe the steps are as follows:

  1. We submit a valid e-invoice
  2. ZATCA updates their DB
  3. However, the link has a network problem, causing the socket to fail with ECONNRESET
  4. Our system does an automatic retry
  5. ZATCA responds with HTTP 208

However, after augmenting our system to accept HTTP 208 responses, it seems everything is working as supposed. Thank you!