# "\[Error\] CODE: signatureValue, MESSAGE: Wrong signature value."

**URL:** <https://zatca1.discourse.group/t/error-code-signaturevalue-message-wrong-signature-value/6737>\
**Category:** Signing process\
**Created:** [April 21, 2025, 7:14am UTC](https://zatca1.discourse.group/t/error-code-signaturevalue-message-wrong-signature-value/6737 "2025-04-21T07:14:18Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![MostafaFlexe](https://avatars.discourse-cdn.com/v4/letter/m/dec6dc/32.png) [@MostafaFlexe](https://zatca1.discourse.group/u/MostafaFlexe)\
**Post date:** [April 21, 2025, 7:14am UTC](https://zatca1.discourse.group/t/error-code-signaturevalue-message-wrong-signature-value/6737/1 "2025-04-21T07:14:18Z")

</div>

when using the EInvoiceValidator class from zatca einvioce sdk to validate my invoices it always fails on the step “Validate EInvoice Signature” with an error message “[Error] CODE: signatureValue, MESSAGE: Wrong signature value.” and this only happens with Simplified invoices although I generate the digital signature value as documented in “E-invoicing Detailed  
Technical Guidelines Version 2”

---

<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:** [April 21, 2025, 10:09am UTC](https://zatca1.discourse.group/t/error-code-signaturevalue-message-wrong-signature-value/6737/2 "2025-04-21T10:09:16Z")

</div>

Dear @MostafaFlexe

Thanks for reaching out, Welcome to our community.

To provide comprehensive support as usual, can I kindly ask you to elaborate with the below:

1- Did you successfully integrated with ZATCA?  
2- What is the environment?  
3- What is the SDK version that you are using?  
4- What are the steps that you are followed

Thanks,  
Ibrahem Daoud.

---

<div class="post-metadata">

**Author:** ![mnuaimi](https://avatars.discourse-cdn.com/v4/letter/m/dbc845/32.png) [@mnuaimi](https://zatca1.discourse.group/u/mnuaimi)\
**Post date:** [April 22, 2025, 9:32am UTC](https://zatca1.discourse.group/t/error-code-signaturevalue-message-wrong-signature-value/6737/3 "2025-04-22T09:32:30Z")

</div>

It appears that you are using the developer environment and trying to sign an invoice. The seller data does not match the data you provided in the CSR.

---

<div class="post-metadata">

**Author:** ![Affan](https://avatars.discourse-cdn.com/v4/letter/a/54ee81/32.png) [@Affan](https://zatca1.discourse.group/u/Affan)\
**Post date:** [April 22, 2025, 9:32am UTC](https://zatca1.discourse.group/t/error-code-signaturevalue-message-wrong-signature-value/6737/4 "2025-04-22T09:32:50Z")

</div>

Hi Mostafa, I’m getting the same result on B2C invoices.

Can you please share the documentation link that you are using?

Regards,

---

<div class="post-metadata">

**Author:** ![MostafaFlexe](https://avatars.discourse-cdn.com/v4/letter/m/dec6dc/32.png) [@MostafaFlexe](https://zatca1.discourse.group/u/MostafaFlexe)\
**Post date:** [April 24, 2025, 9:01am UTC](https://zatca1.discourse.group/t/error-code-signaturevalue-message-wrong-signature-value/6737/5 "2025-04-24T09:01:14Z")

</div>

Hi Affan,  
Below is the documentation link I’m using.  
[https://zatca.gov.sa/en/E-Invoicing/Introduction/Guidelines/Documents/E-invoicing-Detailed-Technical-Guideline.pdf](https://zatca.gov.sa/en/E-Invoicing/Introduction/Guidelines/Documents/E-invoicing-Detailed-Technical-Guideline.pdf)

---

<div class="post-metadata">

**Author:** ![MostafaFlexe](https://avatars.discourse-cdn.com/v4/letter/m/dec6dc/32.png) [@MostafaFlexe](https://zatca1.discourse.group/u/MostafaFlexe)\
**Post date:** [May 7, 2025, 7:52am UTC](https://zatca1.discourse.group/t/error-code-signaturevalue-message-wrong-signature-value/6737/6 "2025-05-07T07:52:30Z")

</div>

Yes, I successfully integrated with ZATCA on both NonProduction and Simulation Environment.  
This issue occurs on both environments NonProduction and Simulation.  
The SDK version is 3.4.1.0.  
The Steps are as follows  
1- Canonicalizing the xml using the C14 Standard without the (UBLExtension, QR, Signature )  
Tags.  
2- Hashing the new invoice body using SHA-256.  
3- Signing the generated invoice hash with ECDSA using the private key.  
and this is the digital signature I used in my invoice.

---

<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:** [May 7, 2025, 8:12am UTC](https://zatca1.discourse.group/t/error-code-signaturevalue-message-wrong-signature-value/6737/7 "2025-05-07T08:12:19Z")

</div>

Dear @MostafaFlexe

Thanks for your elaborate, Can I kindly ask you to mention the steps you followed after generating the CSR?

Thanks,  
Ibrahem Daoud,

---

<div class="post-metadata">

**Author:** ![Ali00032](https://avatars.discourse-cdn.com/v4/letter/a/ad7895/32.png) [@Ali00032](https://zatca1.discourse.group/u/Ali00032)\
**Post date:** [June 23, 2025, 7:51am UTC](https://zatca1.discourse.group/t/error-code-signaturevalue-message-wrong-signature-value/6737/8 "2025-06-23T07:51:29Z")

</div>

@MostafaFlexe can you please guide in detail how you that simply by using sdk . I am stuck on this process complaince check
