ICV , PIH for two type invoices (standard,simplified) In Same Device

XML and business rules
1

If Device (Server) sending two type invoice (Standard,Simplified) What about PIH , ICV
we know at :

Invoice Simplified , PIH put by device , and you can send any time at 24h from issued.
Invoice Standard , PIH put by last sent doc
The Q. Is PIH is diffreanal for each type(standard,simplified) in same device(owned pcsid) ?

2

Dear @Mohammad.Baker, please note that the PIH for the first sent invoice from the EGS must be a “0” value encoded to base64. This sequence is associated with each device/PCISID onboarded, and after that, it will be the previous hash of the latest submitted invoice, whatever the type of invoice sent when using the same device.

3

The standard document is sent immediately, but it is very difficult to send simplified documents immediately to Zatka in order for the PIH to be unified between them, to be given to the next document.

What can we do for this ?

4

Hi, first generate XML of all it will have PIH and then you can keep reporting/clearing. thanks

5

Dear @Mohammad.Baker,

Invoice XML, including PIH, should be generated in real time regardless of the send time.

6

The Real Problem now for Simplified Invoice PIH
If we have Device POS (offline in worktime) do this steps:
1.save invoice .
2.generate xml ( with PIH) . (if not with the sign will errors)
3.sign xml (bec need QR).
4.print(share) to customer
and end of this day
5.send to Zatca … if sent to Zatca Without Order maybe one Invoice not accept by zatca , now PIH is not correct for next invoice
You say PIH “should be generated in real time regardless of the send time.”
How to slove this.

7

@Mohammad.Baker you can send invoices to ZATCA in any order (you can send invoice # 5 then 4 then 1 then 2). So long as invoices are generated in a sequence sending them can be in any order. Regarding PIH sequence, please note this sequence is regardless of status of acceptance by ZATCA and type of document (B2B or B2C). Let us say 5 invoices are sent 1,2,3,4,5. Invoice number 3 is rejected, even in this case invoice #4 will have PIH as hash of invoice 3 (even though 3 was rejected it doesn’t change hash of 3).