{"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":[{"type":"WARNING","code":"BR-KSA-98","category":"KSA","message":"[BR-KSA-98] - The simplified invoice should be submitted within 24 hours of issuing the invoice.","status":"WARNING"},{"type":"WARNING","code":"invalid-signing-certificate","category":"CERTIFICATE_ERRORS",
Hello
We are encountering the “invalid-signing-certificate” error when submitting a Production e-Invoice using our CSID.
“invalid-signing-certificate” as warning while onboarding and after “CERTIFICATE_SIGNATURE_QRCODE_INVALID” as while reporting.
All client-side validations have been completed successfully:
-
The private key fully matches the certificate contained in the token (pcsid_binarySecurityToken).
-
The XML is correctly signed, and the certificate in the KeyInfo section matches the token certificate.
-
The certificate is valid by date.
-
The pcsid_secret is valid Base64 (32 bytes in length).
Therefore, all client-side configurations are correct.
It happens only for some customers. Only a few customers encountered this WARNING while onboarding and fails while reporting, others totally fine.
What should we do to fix it ?
Thanks