Digital signature not found

Clearance and Reporting
1

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

],
"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?

1 Like
2

Same thing here

I think it is from server side

3

same problems

now we face this error with all our costumer

Error :{ ErrorMessage :Invalid digital signature, ErrorCategories :SIGNATURE_ERRORS, ErrorCodes :invalid-digital-signature }

1 Like
4

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”}

5

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

6

@SP_AlMizan @ucitco @EslamSamiH @mojtaba

any update from your side ?

7

still same issue on my side

8

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.

9

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

10

@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

1 Like
11


@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.

1 Like
12

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

13

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


@MalikRawabi986077683 @hima223384 @EslamSamiH @ucitco @SP_AlMizan @mojtaba @githin @scalvo can someone please retry and confirm the latest status?

14

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

Everything is working fine now

15

It’s working properly now! ….

16

Hi ucitco,

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

Best regards,

17

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.