SIGNATURE_ERRORS

General
1

Dear

now we face this error with all our costumer

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

regards

1 Like
2

Dear ZATCA team,

The same issue is occurring across our integrations. Everything was working properly using the same certificates for the signature, but the error has suddenly started appearing.

@Ankit.K.Tiwari Could you please check this with priority? The issue is currently blocking the invoicing process for multiple taxpayers.

Thank you in advance for your prompt assistance.

3

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

1 Like
4

@scalvo @hima223384 @MalikRawabi986077683 @hima223384 @EslamSamiH @ucitco @SP_AlMizan @mojtaba please try now and confirm. New validation has been rolled back from ZATCA’s side for immediate relief to impacted taxpayers.

5

We are now facing the following error with all our customers while submitting Simplified Tax Invoices:

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

6

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

2 Likes
7

thanks we report simplified invoices without the warning after 11 today

8

thank you @Ankit.K.Tiwari

its working fine now

9

Hello,

Today again I am facing the following error while submitting Simplified Tax Invoices for reporting/clearance.
This same process was working fine earlier without any code or certificate changes, so it seems the issue might be coming from the ZATCA server side (signature verification).

Below is the complete API response:

400: {
“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”: “Invalid digital signature”,
“status”: “ERROR”
}
],
“status”: “ERROR”
},
“reportingStatus”: “NOT_REPORTED”
}

10

It is working now
thank you

11

We’re now able to report the pending documents.

Thank you @Ankit.K.Tiwari !

12

Hello Hima,
It has been rolled back and is functioning as expected.

1 Like
13

@Ankit.K.Tiwari

The system is working fine now.

@Ankit.K.Tiwari
Can you add that validation to simulation so we can continue fixing that issue.

Regards