# Steps after clearing the invoice

**URL:** <https://zatca1.discourse.group/t/steps-after-clearing-the-invoice/3683>\
**Category:** Onboarding, renewal and revocation\
**Created:** [October 16, 2024, 7:43am UTC](https://zatca1.discourse.group/t/steps-after-clearing-the-invoice/3683 "2024-10-16T07:43:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hadi](https://avatars.discourse-cdn.com/v4/letter/h/e99b99/32.png) [@Hadi](https://zatca1.discourse.group/u/Hadi)\
**Post date:** [October 16, 2024, 7:43am UTC](https://zatca1.discourse.group/t/steps-after-clearing-the-invoice/3683/1 "2024-10-16T07:43:34Z")

</div>

Dears ,

Hope this finds you well .

Now we are doing very nice on the simulation enviroment , our documents submissions are getting cleared with no warning , this is the result we get always :

```auto
{"validationResults":{"infoMessages":[{"type":"INFO","code":"XSD_ZATCA_VALID","category":"XSD validation","message":"Complied with UBL 2.1 standards in line with ZATCA specifications","status":"PASS"}],"warningMessages":[],"errorMessages":[],"status":"PASS"},"clearanceStatus":"CLEARED","clearedInvoice":}

```

with the cleared invoice encoded of course .

Next we extarct the QR code from the cleared invoice and print it into the document we usually print . also we have the xml files saved in case if a customer asked us to share .

What else should we do ? is the QR code extracted from ZATCA response is enough ? anything else we should consider before moving to production enviroment ?

Thanks .

---

<div class="post-metadata">

**Author:** ![Aturkistani](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@Aturkistani](https://zatca1.discourse.group/u/Aturkistani)\
**Post date:** [October 22, 2024, 1:24am UTC](https://zatca1.discourse.group/t/steps-after-clearing-the-invoice/3683/2 "2024-10-22T01:24:32Z")

</div>

Dear @Hadi,

It’s nice to hear that you are doing well on the simulation, but please note that it’s mandatory to share the cleared B2B E-invoices with your customer in XML format or human readable format with embedded XML

---

<div class="post-metadata">

**Author:** ![Hadi](https://avatars.discourse-cdn.com/v4/letter/h/e99b99/32.png) [@Hadi](https://zatca1.discourse.group/u/Hadi)\
**Post date:** [October 23, 2024, 7:48am UTC](https://zatca1.discourse.group/t/steps-after-clearing-the-invoice/3683/3 "2024-10-23T07:48:57Z")

</div>

Dear @Aturkistani ,

Thank you , well noted .

could you please also advice on this topic :

> [@Invoice hash is incorrect when signing the invoice and need to generate the hash again](https://zatca1.discourse.group/t/invoice-hash-is-incorrect-when-signing-the-invoice-and-need-to-generate-the-hash-again/3665/14):
>
> @Hadi I agree with you, developers should look into this. I also think this might be a bug, for documents with linearized XML. InvoiceS ignator seems to change the original Invoice structure of the document when saving the invoice and doesn’t recalculate the InvoiceHash when creating the Invoice Request and causes the InvoiceHash to be incorrect.