# Digital signature not found

**URL:** <https://zatca1.discourse.group/t/digital-signature-not-found/8852>\
**Category:** Clearance and Reporting\
**Created:** [October 26, 2025, 3:22pm UTC](https://zatca1.discourse.group/t/digital-signature-not-found/8852 "2025-10-26T15:22:09Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![ucitco](https://avatars.discourse-cdn.com/v4/letter/u/4bbf92/32.png) [@ucitco](https://zatca1.discourse.group/u/ucitco)\
**Post date:** [October 26, 2025, 3:22pm UTC](https://zatca1.discourse.group/t/digital-signature-not-found/8852/1 "2025-10-26T15:22:09Z")

</div>

Before about 2 hours I started getting this error, nothing changed from myside, I’m reporting from more than 3 months.

{  
“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”: [

```auto
],
"errorMessages": [
  {
    "type": "ERROR",
    "code": "invalid-digital-signature",
    "category": "SIGNATURE_ERRORS",
    "message": "Digital signature not found",
    "status": "ERROR"
  }
],
"status": "ERROR"

```

},  
“reportingStatus”: “NOT\_REPORTED”  
}

In development environment it’s working but in production I’m getting this.

Could you please help me with this?

---

<div class="post-metadata">

**Author:** ![mojtaba](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@mojtaba](https://zatca1.discourse.group/u/mojtaba)\
**Post date:** [October 26, 2025, 3:47pm UTC](https://zatca1.discourse.group/t/digital-signature-not-found/8852/2 "2025-10-26T15:47:23Z")

</div>

Same thing here

I think it is from server side

---

<div class="post-metadata">

**Author:** ![hima223384](https://avatars.discourse-cdn.com/v4/letter/h/b77776/32.png) [@hima223384](https://zatca1.discourse.group/u/hima223384)\
**Post date:** [October 26, 2025, 3:56pm UTC](https://zatca1.discourse.group/t/digital-signature-not-found/8852/3 "2025-10-26T15:56:39Z")

</div>

same problems

now we face this error with all our costumer

Error :{ ErrorMessage :Invalid digital signature, ErrorCategories :SIGNATURE\_ERRORS, ErrorCodes :invalid-digital-signature }

---

<div class="post-metadata">

**Author:** ![SP\_AlMizan](https://dub1.discourse-cdn.com/flex013/user_avatar/zatca1.discourse.group/sp_almizan/32/1295_2.png) [@SP\_AlMizan](https://zatca1.discourse.group/u/SP_AlMizan)\
**Post date:** [October 26, 2025, 4:05pm UTC](https://zatca1.discourse.group/t/digital-signature-not-found/8852/4 "2025-10-26T16:05:49Z")

</div>

we are facing the same problem is this from our side or ZATCA But Only as _warning_ {“type”:“WARNING”,“code”:“invalid-digital-signature”,“category”:“SIGNATURE\_ERRORS”,“message”:“The certificate in the invoice implies that it was signed with a private key different from the one associated with this device”,“status”:“WARNING”}

---

<div class="post-metadata">

**Author:** ![EslamSamiH](https://avatars.discourse-cdn.com/v4/letter/e/8dc957/32.png) [@EslamSamiH](https://zatca1.discourse.group/u/EslamSamiH)\
**Post date:** [October 26, 2025, 4:48pm UTC](https://zatca1.discourse.group/t/digital-signature-not-found/8852/5 "2025-10-26T16:48:20Z")

</div>

Facing same problem

SIGNATURE\_ERRORS  
The certificate in the invoice implies that it was signed with a private key different from the one associated with this device

---

<div class="post-metadata">

**Author:** ![hima223384](https://avatars.discourse-cdn.com/v4/letter/h/b77776/32.png) [@hima223384](https://zatca1.discourse.group/u/hima223384)\
**Post date:** [October 26, 2025, 6:14pm UTC](https://zatca1.discourse.group/t/digital-signature-not-found/8852/6 "2025-10-26T18:14:14Z")

</div>

@SP_AlMizan @ucitco @EslamSamiH @mojtaba

any update from your side ?

---

<div class="post-metadata">

**Author:** ![mojtaba](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@mojtaba](https://zatca1.discourse.group/u/mojtaba)\
**Post date:** [October 26, 2025, 6:32pm UTC](https://zatca1.discourse.group/t/digital-signature-not-found/8852/7 "2025-10-26T18:32:41Z")

</div>

still same issue on my side

---

<div class="post-metadata">

**Author:** ![ucitco](https://avatars.discourse-cdn.com/v4/letter/u/4bbf92/32.png) [@ucitco](https://zatca1.discourse.group/u/ucitco)\
**Post date:** [October 27, 2025, 12:02am UTC](https://zatca1.discourse.group/t/digital-signature-not-found/8852/8 "2025-10-27T00:02:04Z")

</div>

In my case,

I found that SignatureValue is going empty,

so that I changed to the latest SDK zatca-einvoicing-sdk-238-R3.4.6 and changed my java version to 11 instead of 21, after that the SignatureValue calculated successfully.

---

<div class="post-metadata">

**Author:** ![MalikRawabi986077683](https://avatars.discourse-cdn.com/v4/letter/m/54ee81/32.png) [@MalikRawabi986077683](https://zatca1.discourse.group/u/MalikRawabi986077683)\
**Post date:** [October 27, 2025, 7:40am UTC](https://zatca1.discourse.group/t/digital-signature-not-found/8852/9 "2025-10-27T07:40:44Z")

</div>

Dear Fatoora / @Ankit.K.Tiwari , we are facing same issue require your guidance.

---

<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:** [October 27, 2025, 7:48am UTC](https://zatca1.discourse.group/t/digital-signature-not-found/8852/10 "2025-10-27T07:48:14Z")

</div>

@MalikRawabi986077683 @hima223384 @EslamSamiH @ucitco @SP_AlMizan @mojtaba @githin @scalvo ZATCA teams are investigating the root cause. Currently one of the reasons identified is if Java version is not between Java 11 and Java 15 then it results in signature error. We will keep you posted here

---

<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:** [October 27, 2025, 8:28am UTC](https://zatca1.discourse.group/t/digital-signature-not-found/8852/11 "2025-10-27T08:28:21Z")

</div>

[  
@MalikRawabi986077683](https://zatca1.discourse.group/u/malikrawabi986077683) @hima223384 @EslamSamiH @ucitco @SP_AlMizan @mojtaba @githin @scalvo please try now and confirm. New validation has been rolled back from ZATCA’s side for immediate relief to impacted taxpayers.

---

<div class="post-metadata">

**Author:** ![shiyaf\_texol](https://avatars.discourse-cdn.com/v4/letter/s/94ad74/32.png) [@shiyaf\_texol](https://zatca1.discourse.group/u/shiyaf_texol)\
**Post date:** [October 27, 2025, 8:31am UTC](https://zatca1.discourse.group/t/digital-signature-not-found/8852/12 "2025-10-27T08:31:57Z")

</div>

We are not using the SDK, so how come this be a java version issue ?

---

<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:** [October 27, 2025, 8:42am UTC](https://zatca1.discourse.group/t/digital-signature-not-found/8852/13 "2025-10-27T08:42:28Z")

</div>

@shiyaf_texol as mentioned, this was “one of identified reasons” and teams are investigating further. In the meanwhile, changes are rolled back.

[  
@MalikRawabi986077683](https://zatca1.discourse.group/u/malikrawabi986077683) @hima223384 @EslamSamiH @ucitco @SP_AlMizan @mojtaba @githin @scalvo can someone please retry and confirm the latest status?

---

<div class="post-metadata">

**Author:** ![githin](https://avatars.discourse-cdn.com/v4/letter/g/5f8ce5/32.png) [@githin](https://zatca1.discourse.group/u/githin)\
**Post date:** [October 27, 2025, 8:50am UTC](https://zatca1.discourse.group/t/digital-signature-not-found/8852/14 "2025-10-27T08:50:02Z")

</div>

Services are back to normal, and all pending invoices have been successfully sent to ZATCA.

Everything is working fine now

---

<div class="post-metadata">

**Author:** ![Magidmonzer](https://avatars.discourse-cdn.com/v4/letter/m/e19b73/32.png) [@Magidmonzer](https://zatca1.discourse.group/u/Magidmonzer)\
**Post date:** [October 27, 2025, 8:50am UTC](https://zatca1.discourse.group/t/digital-signature-not-found/8852/15 "2025-10-27T08:50:33Z")

</div>

It’s working properly now! ….

---

<div class="post-metadata">

**Author:** ![Majd\_Alawadi](https://dub1.discourse-cdn.com/flex013/user_avatar/zatca1.discourse.group/majd_alawadi/32/1518_2.png) [@Majd\_Alawadi](https://zatca1.discourse.group/u/Majd_Alawadi)\
**Post date:** [October 28, 2025, 6:12am UTC](https://zatca1.discourse.group/t/digital-signature-not-found/8852/16 "2025-10-28T06:12:33Z")

</div>

Hi ucitco,

The rollback has been completed, and everything is working as expected now.

Best regards,

---

<div class="post-metadata">

**Author:** ![ucitco](https://avatars.discourse-cdn.com/v4/letter/u/4bbf92/32.png) [@ucitco](https://zatca1.discourse.group/u/ucitco)\
**Post date:** [October 28, 2025, 10:15am UTC](https://zatca1.discourse.group/t/digital-signature-not-found/8852/17 "2025-10-28T10:15:14Z")

</div>

The validation was about SignatureValue in XML,

I was using JAVA 21 and old SDK when I moved to the latest SDK and JAVA 11, the issue was solved and the signed XML contain SignatureValue.