thank you @eCloud for your help
the difference between your created csr and mine related with the data of orgnization “O” and orgnization unit “OU” because in my csr i added this data with Arabic not English .
thank you For your Support @eCloud
Dear, please assist us with this issue as it is important.
Based on the provided response, it is clear that the CSR value was initially accepted, and the only remaining step was to complete the compliance process. However, after completing the compliance steps, we received an error stating that the CSR key is invalid. How is that possible? If there was an issue with the CSR from the beginning, we wouldn’t have received confirmation that it was accepted — and you are aware of that.
We have tried multiple OpenSSL versions on different operating systems, but the issue remains the same. The same procedure works perfectly fine in the “core” environment, but this error only occurs in the “simulation” environment.
Additionally, please note that the same procedure was working without any issues before January 7.
The error message we receive is:
“errorMessage”: “The provided Certificate Signing Request (CSR) is invalid.”
@Malik_55 @easyaamal @majazuddin
Could you please let us know if the issue was resolved?
{ [
“requestID”
]=> int(1736342917349) [
“dispositionMessage”
]=> “ISSUED” [
“binarySecurityToken”
]=> “TUlJQjZqQ0NBWStnQXdJQkFnSUdBWlJHR2xEbE1Bb0dDQ3FHU000OUJBTUNNQlV4RXpBUkJnTlZCQU1NQ21WSmJuWnZhV05wYm1jd0hoY05NalV3TVRBNE1UTXlPRE15V2hjTk16QXdNVEEzTWpFd01EQXdXakJETVE0d0RBWURWUVFEREFWVVUxUkRUekVSTUE4R0ExVUVDd3dJVkZOVVEwOHRVMEV4RVRBUEJnTlZCQW9NQ0ZSVFZFTlBMVk5CTVFzd0NRWURWUVFHRXdKVFFUQldNQkFHQnlxR1NNNDlBZ0VHQlN1QkJBQUtBMElBQlBHUDFRNmlhankvNGhTOUZ4d0ZVc1lHNHdGMEZHc0l2QkpkME9XR3QrbjNDZzhBRVp2RTlkTlZxLzhYVGlCQTQ2VTBZRVFCc0JBYlJUUVVCQmY2dTlxamdaOHdnWnd3REFZRFZSMFRBUUgvQkFJd0FEQ0Jpd1lEVlIwUkJJR0RNSUdBcEg0d2ZERWRNQnNHQTFVRUJBd1VNUzFUUkZOQmZESXRSa2RFVTN3ekxWTkVSa2N4SHpBZEJnb0praWFKay9Jc1pBRUJEQTh6TVRBeE5qZzBOelEwTURBd01ETXhEVEFMQmdOVkJBd01CREV4TURBeEVUQVBCZ05WQkJvTUNGSk5Va1V4TWpNME1SZ3dGZ1lEVlFRUERBOVVjbUZ1YzNCdmNuUmhkR2x2Ym5Nd0NnWUlLb1pJemowRUF3SURTUUF3UmdJaEFOZEhMVDMzTmsrREhPcWRSOGZUVjM1Rk4rMFFodkVvaDI2b0cremF1WHdPQWlFQXRzQ2VPWjluZ3llZlY0M094ODVYT01qU2JnUW56SzZPcVJxWXpJQnVzVEU9” [
“secret”
]=> string(44) “m1VP3d/FNwwV5tdnK2X76MTN/9/LHU7Ko8sFM5IHhzs=” [
“errors”
]=> NULL}} array(3) { [“success”]=> bool(false) [“message”]=> “The compliance certificate is not done with the following compliance steps yet [standard-compliant,standard-credit-note-compliant,standard-debit-note-compliant,simplified-compliant,simplified-credit-note-compliant,simplified-debit-note-compliant]” [“data”]=> NULL
Dear @easyaamal, @AmrSobhy
Kindly if you are still facing this issue, reach out to your RMs and request one to one meeting with ZATCA technical team.
Please prepare all the prerequisites, they will be shared in the mail.
Thanks,
Ibrahem Daoud.
This issue is from ZATCA’s side and should appear before obtaining the production CSID. If someone from the support team tries, they will confirm that the issue is from ZATCA’s side, not ours
1 Like
Dear Mr. Ibrahem;
The issue is not for only two or three users, it is a general issue and facing many of us.
As mentioned by others the same procedure was working fine, and then suddenly, it rises this issue, which indicates that something happened in the server side!
It is highly appreciated if you try to figure out the causes of this issue.
Thanks in advance for your cooperation.
Jamal
1 Like
@idaoud
We are ready to attend the meeting at any time.
Could you please confirm if we should send the request to sp_support@zatca.gov.sa?
Looking forward to your confirmation.
Best regards,
1 Like
As I confirmed, the Compliance and production/csids APIs are working fine with no issues.
Please as I mentioned previously, If anyone still facing this issue, kindly reach out to your RM and schedule one to one meeting.
Thanks for your understanding,
Ibrahem Daoud.
@idaoud
I Had also onboarded about 3 EGS units in Sep Oct and Dec
and on the 8-01-2025 i tried to onbaord another one but i am getting this
error of Invalid CSR (Provided CSR is Invalid).
i had changed the OpenSSL version Nothing worked for me
Please Focus on it as it is very important .
2 Likes
Dears,
@allam @AmrSobhy @easyaamal @Shzzamx @Lina-alrehaili1 @idaoud @AbuSaid @eCloud @Malik_55
Thank you for reaching out.
Kindly note that this is a known general issue, that the team is investigating it, we appreciate your patience and apologize for any inconveniences. We will keep you updated once it is solved ASAP.
Thank you!
Regards,
Sara Alotaibi
4 Likes
Dear @saalotaibi @idaoud
We await your response. Please stay informed about the situation. Is it resolved?
Dears @AmrSobhy , @easyaamal , @Shzzamx , @malar
The issue is resolved, Kindly check it now and and confirm.
Thanks,
Ibrahem Daoud
Dear Ibrahem thanks it works with me now but we face a new Issue
when we send any invoice(simplified(b2c)-standard(b2b)) in simulation we get a warning message “X509Certificate (CCSID / PCSID) used for signing is not valid certificate (CCSID / PCSID) for this VAT Registration Number.”
this issue occurs today only.
Kindly see the below response of reporting api
{“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”:“invalid-signing-certificate”,“category”:“CERTIFICATE_ERRORS”,“message”:“X509Certificate (CCSID / PCSID) used for signing is not valid certificate (CCSID / PCSID) for this VAT Registration Number.”,“status”:“WARNING”}],“errorMessages”:,“status”:“WARNING”},“reportingStatus”:“REPORTED”}
thank you for your efforts @idaoud
Dear idaoud
Kindly note that the onboarding problem successfully solved, however we face another problem when sending (simplified invoices only )
{
“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”: “invalid-signing-certificate”,
“category”: “CERTIFICATE_ERRORS”,
“message”: “X509Certificate (CCSID / PCSID) used for signing is not valid certificate (CCSID / PCSID) for this VAT Registration Number.”,
“status”: “WARNING”
}
],
“errorMessages”: ,
“status”: “WARNING”
},
“clearanceStatus”: null,
“reportingStatus”: “REPORTED”
}
Dear;
Thanks for resolving the on-boarding issue.
But we have got another new issue!
A Warning with Simplified invoices, “invalid-signing-certificate” as below:
{
“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”: “invalid-signing-certificate”,
“category”: “CERTIFICATE_ERRORS”,
“message”: “X509Certificate (CCSID / PCSID) used for signing is not valid certificate (CCSID / PCSID) for this VAT Registration Number.”,
“status”: “WARNING”
}
],
“errorMessages”: ,
“status”: “WARNING”
},
“clearanceStatus”: null,
“reportingStatus”: “REPORTED”
}
Now i am getting the same invalid CSR on generating Compliance Certificate id
before it was coming after compliance of the invoice during generating PCSID
now it is coming in generating CCSID
and i aint change a single word in my solution
this is how i am generating my private keys using openssl commands
i can share my csr config file if you want to
Dear Ibrahem,
We are waiting for the solution, since the problem prevent us from integrating our customers to the simulation environment. a lot of wave 11 are waiting for solution
1 Like
Hi,
cau you help me in the same case