fuadhasni
commented
1 year ago Download SDK, it has a folder with sample XML and CSR.
On Sat, Jul 29, 2023 at 2:12 PM, alsabith12 @.***> wrote:
Hello,
I have read about the new implementation of prepaid invoices in ZATCA XML standards. So currently we have 388 (invoice), 383 (debit note), 381 (credit note) and 386 for prepaid invoices.
In the ZATCA's documentation, it shows about the prepaid amount adjustments and doesn't provide any clarity on the how the prepaid invoices XML looks like.
Does anyone has clarity on the following or received any communication from ZATCA?:
1.
When we receive an advance of 100 SAR for a total transaction value of 300 then first we need to issue an advance invoice with code 386. But in that should we show the amount in prepaid amount or show it as payable amount itself in legal monetary total? Also, when issuing the final invoice should the code be 388 or 386? 2.
How should the XMLs be prepared in case of multiple advance receipts? Say for example we received an advance in 3 stages and then we issue the invoice. Should the XML show 386, 386, 386, and then 388? Should the intermediate advance invoices refer to the previous advance invoices? 3.
What should we do in XML in case we issued a 386 invoice and it needs a correction? How can we raise a debit or credit note for that? What happens if we need to refund the advance?
Another doubt about the supplier XML data: When creating certificates for phase 2 e-invoicing, we have to give the address information. If a taxpayer has 20 branches but all of them have the same VAT number, the question is whether we have to make 20 separate certificates for each branch to use for invoicing. Or is it possible to show the different branch addresses in the XML file using only one certificate?
— Reply to this email directly, view it on GitHub https://github.com/wes4m/zatca-xml-js/issues/43, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABPK2CL47DYFPSCQ4KZFYUTXSTHYVANCNFSM6AAAAAA24MFUVE . You are receiving this because you are subscribed to this thread.Message ID: @.***>
alsabith12
Hello,
I have read about the new implementation of prepaid invoices in ZATCA XML standards. So currently we have 388 (invoice), 383 (debit note), 381 (credit note) and 386 for prepaid invoices.
In the ZATCA's documentation, it shows about the prepaid amount adjustments and doesn't provide any clarity on the how the prepaid invoices XML looks like.
Does anyone has clarity on the following or received any communication from ZATCA?:
1) When we receive an advance of 100 SAR for a total transaction value of 300 then first we need to issue an advance invoice with code 386. But in that should we show the amount in prepaid amount or show it as payable amount itself in legal monetary total? Also, when issuing the final invoice should the code be 388 or 386?
2) How should the XMLs be prepared in case of multiple advance receipts? Say for example we received an advance in 3 stages and then we issue the invoice. Should the XML show 386, 386, 386, and then 388? Should the intermediate advance invoices refer to the previous advance invoices?
3) What should we do in XML in case we issued a 386 invoice and it needs a correction? How can we raise a debit or credit note for that? What happens if we need to refund the advance?
Another doubt about the supplier XML data: When creating certificates for phase 2 e-invoicing, we have to give the address information. If a taxpayer has 20 branches but all of them have the same VAT number, the question is whether we have to make 20 separate certificates for each branch to use for invoicing. Or is it possible to show the different branch addresses in the XML file using only one certificate?