# Invoice hash API body does not match the (calculated) Hash of the XML

**URL:** <https://zatca1.discourse.group/t/invoice-hash-api-body-does-not-match-the-calculated-hash-of-the-xml/7788>\
**Category:** General\
**Created:** [July 24, 2025, 7:41am UTC](https://zatca1.discourse.group/t/invoice-hash-api-body-does-not-match-the-calculated-hash-of-the-xml/7788 "2025-07-24T07:41:35Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![sameer](https://avatars.discourse-cdn.com/v4/letter/s/bbce88/32.png) [@sameer](https://zatca1.discourse.group/u/sameer)\
**Post date:** [July 24, 2025, 7:41am UTC](https://zatca1.discourse.group/t/invoice-hash-api-body-does-not-match-the-calculated-hash-of-the-xml/7788/1 "2025-07-24T07:41:35Z")

</div>

Dear Team,

One of our customer, submitted a set of B2C invoices in December 2024. Out of these, 12 invoices returned the following validation response from the ZATCA.

Could you please review and advise on the corrective actions we need to take for these affected invoices?

@Ankit.K.Tiwari@idaoud

Error :  
“{"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"},{"type":"INFO","code":"XSD\_ZATCA\_VALID","category":"XSD validation","message":"Complied with UBL 2.1 standards in line with ZATCA specifications","status":"PASS"}],"warningMessages":[{"type":"WARNING","code":"invoiceTimeStamp\_QRCODE\_INVALID","category":"QRCODE\_VALIDATION","message":"Time on QR Code does not match with Invoice Issue Time (KSA-25). If ZATCA’s SDK was used to generate QR Code, kindly use the latest version of SDK","status":"WARNING"},{"type":"WARNING","code":"invoiceTimeStamp\_QRCODE\_INVALID","category":"QRCODE\_VALIDATION","message":"Time on QR Code does not match with Invoice Issue Time (KSA-25). If ZATCA’s SDK was used to generate QR Code, kindly use the latest version of SDK","status":"WARNING"},{"type":"WARNING","code":"certificate-issuer-name","category":"CERTIFICATE\_ERRORS","message":"X509Certificate (CCSID / PCSID) used for signing is not valid certificate (CCSID / PCSID) for this VAT Registration Number.","status":"WARNING"},{"type":"WARNING","code":"invalid-signing-certificate","category":"CERTIFICATE\_ERRORS","message":"X509Certificate (CCSID / PCSID) used for signing is not valid certificate (CCSID / PCSID) for this VAT Registration Number.","status":"WARNING"},{"type":"WARNING","code":"certificate-issuer-name","category":"CERTIFICATE\_ERRORS","message":"X509Certificate (CCSID / PCSID) used for signing is not valid certificate (CCSID / PCSID) for this VAT Registration Number.","status":"WARNING"},{"type":"WARNING","code":"invalid-signing-certificate","category":"CERTIFICATE\_ERRORS","message":"X509Certificate (CCSID / PCSID) used for signing is not valid certificate (CCSID / PCSID) for this VAT Registration Number.","status":"WARNING"}],"errorMessages":[{"type":"ERROR","code":"invalid-invoice-hash","category":"INVOICE\_HASHING\_ERRORS","message":"The invoice hash API body does not match the (calculated) Hash of the XML","status":"ERROR"},{"type":"ERROR","code":"invalid-invoice-hash","category":"INVOICE\_HASHING\_ERRORS","message":"The invoice hash API body does not match the (calculated) Hash of the XML","status":"ERROR"},{"type":"ERROR","code":"invoiceHash\_QRCODE\_INVALID","category":"QRCODE\_VALIDATION","message":"Invoice xml hash does not match with qr code invoice xml hash","status":"ERROR"},{"type":"ERROR","code":"invoiceHash\_QRCODE\_INVALID","category":"QRCODE\_VALIDATION","message":"Invoice xml hash does not match with qr code invoice xml hash","status":"ERROR"},{"type":"ERROR","code":"certificate-permissions","category":"CERTIFICATE\_ERRORS","message":"User only allowed to use the vat number that exists in the authentication certificate","status":"ERROR"},{"type":"ERROR","code":"certificate-permissions","category":"CERTIFICATE\_ERRORS","message":"User only allowed to use the vat number that exists in the authentication certificate","status":"ERROR"}],"status":"ERROR"},"reportingStatus":"NOT\_REPORTED"}”,  
“httpCode”: 400  
}

---

<div class="post-metadata">

**Author:** ![idaoud](https://avatars.discourse-cdn.com/v4/letter/i/f9ae1b/32.png) [@idaoud](https://zatca1.discourse.group/u/idaoud)\
**Post date:** [July 24, 2025, 8:26am UTC](https://zatca1.discourse.group/t/invoice-hash-api-body-does-not-match-the-calculated-hash-of-the-xml/7788/2 "2025-07-24T08:26:57Z")

</div>

Morning @sameer

Thanks for reaching out,

Just to ensure that my understanding is correct, do you mean that other B2C invoices that was submitted have been reported successfully?  
If so, then please share some sample for the full request and response to the SP below mail.  
If not and all the invoices are rejecting, Then the issue might be in the signing process, so I would kindly ask you to share the exact steps that you are following to sign your actual invoices.

SP mail: [sp\_support@zatca.gov.sa](mailto:sp_support@zatca.gov.sa)

Thanks,  
Ibrahem Daoud.

---

<div class="post-metadata">

**Author:** ![sameer](https://avatars.discourse-cdn.com/v4/letter/s/bbce88/32.png) [@sameer](https://zatca1.discourse.group/u/sameer)\
**Post date:** [August 5, 2025, 9:09am UTC](https://zatca1.discourse.group/t/invoice-hash-api-body-does-not-match-the-calculated-hash-of-the-xml/7788/3 "2025-08-05T09:09:35Z")

</div>

Afternoon @idaoud ,  
Thanks for the Update regarding the issue … we have shared the requested details - XML payload for the affected invoices on email.. can you please check and update on the reported issue asap to do needful at our side.

---

<div class="post-metadata">

**Author:** ![sameer](https://avatars.discourse-cdn.com/v4/letter/s/bbce88/32.png) [@sameer](https://zatca1.discourse.group/u/sameer)\
**Post date:** [August 11, 2025, 7:21am UTC](https://zatca1.discourse.group/t/invoice-hash-api-body-does-not-match-the-calculated-hash-of-the-xml/7788/4 "2025-08-11T07:21:37Z")

</div>

Any update here, we need to proceed further. please revert on this.

---

<div class="post-metadata">

**Author:** ![idaoud](https://avatars.discourse-cdn.com/v4/letter/i/f9ae1b/32.png) [@idaoud](https://zatca1.discourse.group/u/idaoud)\
**Post date:** [August 11, 2025, 8:04am UTC](https://zatca1.discourse.group/t/invoice-hash-api-body-does-not-match-the-calculated-hash-of-the-xml/7788/5 "2025-08-11T08:04:33Z")

</div>

Dear @sameer

Thanks for following up. I hope you are doing well.

Please share the email from which you reached out.

Thanks,

Ibrahem Daoud.

---

<div class="post-metadata">

**Author:** ![sameer](https://avatars.discourse-cdn.com/v4/letter/s/bbce88/32.png) [@sameer](https://zatca1.discourse.group/u/sameer)\
**Post date:** [August 13, 2025, 3:23pm UTC](https://zatca1.discourse.group/t/invoice-hash-api-body-does-not-match-the-calculated-hash-of-the-xml/7788/6 "2025-08-13T15:23:11Z")

</div>

Dear @idaoud ,

We have shared an email from [amagapu@taxilla.com](mailto:amagapu@taxilla.com) to the ZATCA support email ID [sp\_support@zatca.gov.sa](mailto:sp_support@zatca.gov.sa).

Could you please check and confirm, so that we can proceed with the necessary actions at our end?

Thank you for your assistance.

---

<div class="post-metadata">

**Author:** ![idaoud](https://avatars.discourse-cdn.com/v4/letter/i/f9ae1b/32.png) [@idaoud](https://zatca1.discourse.group/u/idaoud)\
**Post date:** [August 14, 2025, 8:09am UTC](https://zatca1.discourse.group/t/invoice-hash-api-body-does-not-match-the-calculated-hash-of-the-xml/7788/7 "2025-08-14T08:09:06Z")

</div>

Hi mate @Ankit.K.Tiwari, Your support on this is much appreciated.

Thanks,

Ibrahem Daoud.

---

<div class="post-metadata">

**Author:** ![sameer](https://avatars.discourse-cdn.com/v4/letter/s/bbce88/32.png) [@sameer](https://zatca1.discourse.group/u/sameer)\
**Post date:** [August 19, 2025, 11:19am UTC](https://zatca1.discourse.group/t/invoice-hash-api-body-does-not-match-the-calculated-hash-of-the-xml/7788/8 "2025-08-19T11:19:08Z")

</div>

Hi @Ankit.K.Tiwari , please update client is waiting for the solution.

---

<div class="post-metadata">

**Author:** ![Ankit.K.Tiwari](https://avatars.discourse-cdn.com/v4/letter/a/9d8465/32.png) [@Ankit.K.Tiwari](https://zatca1.discourse.group/u/Ankit.K.Tiwari)\
**Post date:** [August 19, 2025, 11:25am UTC](https://zatca1.discourse.group/t/invoice-hash-api-body-does-not-match-the-calculated-hash-of-the-xml/7788/9 "2025-08-19T11:25:17Z")

</div>

> [@sameer](#):
>
> [amagapu@taxilla.com](mailto:amagapu@taxilla.com)

@sameer am following up with SP support team. It would be helpful if you can resend the same email again along with attachments.

---

<div class="post-metadata">

**Author:** ![sameer](https://avatars.discourse-cdn.com/v4/letter/s/bbce88/32.png) [@sameer](https://zatca1.discourse.group/u/sameer)\
**Post date:** [August 25, 2025, 6:37am UTC](https://zatca1.discourse.group/t/invoice-hash-api-body-does-not-match-the-calculated-hash-of-the-xml/7788/10 "2025-08-25T06:37:05Z")

</div>

Hi @Ankit.K.Tiwari , we have resent the mail to the SP team, with the attachments .. Could you please check and confirm, so that we can proceed with the necessary actions at our end?

---

<div class="post-metadata">

**Author:** ![sameer](https://avatars.discourse-cdn.com/v4/letter/s/bbce88/32.png) [@sameer](https://zatca1.discourse.group/u/sameer)\
**Post date:** [September 7, 2025, 2:41pm UTC](https://zatca1.discourse.group/t/invoice-hash-api-body-does-not-match-the-calculated-hash-of-the-xml/7788/11 "2025-09-07T14:41:36Z")

</div>

Dear @Ankit.K.Tiwari , we have shared the mail again.Could you please check and confirm, so that we can proceed with the necessary actions at our end?
