B2C - Regeneration of Invoices

Clearance and Reporting
1

After submission to ZATCA and receiving a ‘NOT REPORTED’ response, the understanding is that we need to generate a new Invoice based on the transaction data.

Please confirm if the below are applicable scenarios:

  1. In the case that the issue is on the EGS, after the bug is fixed, an automated process can regenerate and resubmit the Transaction as a new Invoice

  2. In the case that the issue is on the POS/Terminal, after the bug is fixed, it would need to resubmit the Transaction to the EGS, which would just generate an Invoice as if it was a new one.
    In such case, would it matter if the Transaction is submitted via a different EGS?

2

If the EGS is registered under the same VAT number then it does not matter from which EGS you are resending the invoice

3

[quote=“leonidas.s, post:1, topic:389”]

  • In the case that the issue is on the EGS, after the bug is fixed, an automated process can regenerate and resubmit the Transaction as a new Invoice - Yes, the invoice can be regenerated and submitted for reporting but since B2C transaction is completed before “Reporting” XML to ZATCA, the information contained in B2C Invoices (including date, time, IRN, line item details etc) must remain same on regenerated XML. Only data that gets changed would be UUID, ICV, PIH and Hash of invoice.
  • In the case that the issue is on the POS/Terminal, after the bug is fixed, it would need to resubmit the Transaction to the EGS, which would just generate an Invoice as if it was a new one.
    In such case, would it matter if the Transaction is submitted via a different EGS?
    [/quote] - There is no issue in sending the regenerated XML from a different EGS so long as the VAT Registration Number is same on both EGS.
1 Like