Invalid Digital Signature Error

Signing process
1

Dear ZATCA Support Team,

We are currently experiencing the following issue across all our clients when submitting invoices to ZATCA:

errorMessages: [
{
type: “ERROR”,
code: “invalid-digital-signature”,
category: “SIGNATURE_ERRORS”,
message: “Invalid digital signature”,
status: “ERROR”
}
]
status: “ERROR”
HTTP Status: 400
Message: “submitted request is invalid”

1 Like
2

@Ankit.K.Tiwari ,

We are receiving exactly the same 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"
            }
        ],
        "warningMessages": [],
        "errorMessages": [
            {
                "type": "ERROR",
                "code": "invalid-digital-signature",
                "category": "SIGNATURE_ERRORS",
                "message": "Invalid digital signature",
                "status": "ERROR"
            }
        ],
        "status": "ERROR"
    },
    "reportingStatus": "NOT_REPORTED"
}

Could you please clarify the nature of this error and how to fix it? I assume all clients of us are affected. We are using self-crafted solution and not using SDK at all. But it was working for us for the last 2 years without issues.

It would be nice if you can clarify what is wrong with the signature and how to fix it.

– Sergei

3

Hi Sergei,

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

Best regards,

4

Hi Mreda,

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

Best regards,

1 Like
5

Hi @Majd ,

As it was rollback, it means these changes will be deployed sooner or later. Should ZATCA team notify us about it please, that we have time to prepare and validate our setup.

– Sergei