Duplicate Invoice Submission: Same UUID but Different IRNs – How to Reconcile with Internal Gaps

Clearance and Reporting
1

Hello ZATCA Team,

We are facing a situation due to an internal issue during invoice submission to the FATOORA platform.

Let me explain the scenario in detail:

We originally generated and submitted an invoice with the following metadata:

UUID = XXXXX

ICV = 5000

IRN = 5000

PIH = Hash(4999)

However, due to a technical issue, this invoice was submitted again with the same UUID, but a new set of technical values:

UUID = XXXXX (same UUID as before)

ICV = 5001

IRN = 5001

PIH = Hash(5000)

The second version (with IRN = 5001) was the one saved into our internal system.

This issue occurred for 17 invoices in total (Simplified).

As a result:

The invoice with IRN = 5000 was submitted to ZATCA, but does not exist in our internal system.

We now have a gap in our internal IRN sequence (IRN 5000 is missing).

There is a duplicate UUID submitted with different technical values (ICV, IRN, PIH).

We have preserved all the original XML files for both versions.

Our questions:

  1. Since the version saved in our system is IRN = 5001, is it acceptable to recreate the missing IRN = 5000 in our internal system using the original XML, including the original UUID, IRN, and issue date?

  2. Once recreated, can we then issue a Credit Note to reverse the IRN = 5000 version, and maintain compliance?

  3. Is there any special procedure or risk related to submitting the same UUID twice with different IRNs and ICVs?

We appreciate your guidance on how best to reconcile this situation while remaining fully compliant with ZATCA regulations.

Thank you in advance.

2

you can search the topics, you will find many postts with different cases, i hope it helps you

image
image573×695 36.4 KB

3

Dear @mnuaimi please consider responses below:

1 Since the version saved in our system is IRN = 5001, is it acceptable to recreate the missing IRN = 5000 in our internal system using the original XML, including the original UUID, IRN, and issue date?

Response: You do not have to generate and reverse an invoice just for missing IRN, you can explain the gap in future as a technical issue. However, if duplicate invoices are successfully sent to ZATCA with different hashes, then you must send credit notes (from middleware) to reverse the duplicate invoice.

2 Once recreated, can we then issue a Credit Note to reverse the IRN = 5000 version, and maintain compliance?

Response: As explained above, it is not recommended to generate and reverse invoice just to bridge the gap in IRN. On a safer side, you can submit a Failure Notification using this e-service

3 Is there any special procedure or risk related to submitting the same UUID twice with different IRNs and ICVs?

Response: You can submit a failure notification as explained above, make sure to reverse any duplicate XMLs sent with different hashes.

1 Like