By error, I have submitted an invoice twice. What should I do next? Issue a credit note?
First you need to check if the invoice is submitted with same content particularly check the technical identifiers such as “UUID”, "ICV’, “PIH” and “hash”. If everything remains exactly same on both instances then you can ignore duplication as ZATCA will treat both XMLs as one single transaction by validating technical identifiers.
But if any of the technical identifiers are different in the duplicate invoices then these will be treated as separate invoices. In this scenario, taxpayer must issue Credit notes to reverse duplicate transaction by referring IRN and also UUID of duplicated invoice in BillingReferenceID (BT-25) tag.
Hi @Ankit_Tiwari ,
What if just the “UUID” is different?, remaining all identifiers, “InvoiceHash”, “Pih”, “Icv” are different ? Could you please advise?
Dear @Shruthi ,
It’s not possible to have two valid XML invoices where the UUID is different across them while the invoiceHash is the same for both invoices. Each change in the XML invoice will result for a completely different hash.
In this scenario, they will be treated as a separate invoices and credit note should be issued.
Thanks for replying, our use case is such that we have two invoices with the same invoice number the same invoice content, and the same UUID as well, but with different "ICV’, “PIH” and “hash”. @Aturkistani, please advise if we need to submit the credit notes. Both the original and the re-sent duplicate one has been conditionally accepted by ZATCA.
@Shruthi as the hash has changed, you need to issue credit note for the duplicate invoice sent with a different hash. If every thing (including hash ICV and PIH) was same then ZATCA would disregard duplicate records and consider only one instance. But in the given scenario different XMLs (as hash is different) is sent for same transaction, therefore, you need to reverse duplicate record by sharing credit note.