# ZATCA E-Invoicing - X509Certificate (CCSID / PCSID) Not Valid for VAT Registration Number **URL:** \ **Category:** General\ **Created:** [March 6, 2025, 8:10am UTC](https://zatca1.discourse.group/t/zatca-e-invoicing-x509certificate-ccsid-pcsid-not-valid-for-vat-registration-number/6153 "2025-03-06T08:10:07Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Rahoof](https://avatars.discourse-cdn.com/v4/letter/r/9d8465/32.png) [@Rahoof](https://zatca1.discourse.group/u/Rahoof)\ **Post date:** [March 6, 2025, 8:10am UTC](https://zatca1.discourse.group/t/zatca-e-invoicing-x509certificate-ccsid-pcsid-not-valid-for-vat-registration-number/6153/1 "2025-03-06T08:10:07Z")
While signing invoices using a qualified digital certificate, I receive the following warning from ZATCA Simulation: “warningMessages”: [{ “status”: “WARNING”, “type”: “WARNING”, “code”: “certificate-issuer-name”, “category”: “CERTIFICATE\_ERRORS”, “Message”: “X509Certificate (CCSID / PCSID) used for signing is not valid certificate (CCSID / PCSID) for this VAT Registration Number.” }] ---
**Author:** ![saalotaibi](https://avatars.discourse-cdn.com/v4/letter/s/f9ae1b/32.png) [@saalotaibi](https://zatca1.discourse.group/u/saalotaibi)\ **Post date:** [March 6, 2025, 8:52am UTC](https://zatca1.discourse.group/t/zatca-e-invoicing-x509certificate-ccsid-pcsid-not-valid-for-vat-registration-number/6153/2 "2025-03-06T08:52:20Z")
Dear @Rahoof Thank you for reaching out & welcome to the community. Please make sure that you are using the production CSID and not the compliance CSID for signing invoices. In the onboarding process, 2 CSIDs (X509 certificates) will be returned. First one: after requesting the compliance CSID API, (which is the first step to do in onboarding process), we use this certifecate to sign invoices for the compliance checks step (compliance Invoice API), so we only use this certificate to sign invoices for the testing purposes in the compliance checks phase, as invoices in compliane checks are not being sent to ZATCA. Second one: after requesting the production CSID API, we use this certificate to sign real invoices that are being sent to ZATCA by reporting API for simplified invoices or clearance API for standard invoices, however signing standard invoices is optional & not mandatory. so what suggested is to make sure that you are using the PCSID X5509 certificate to sign your invoices,and check again. Thank you. ---
**Author:** ![Rahoof](https://avatars.discourse-cdn.com/v4/letter/r/9d8465/32.png) [@Rahoof](https://zatca1.discourse.group/u/Rahoof)\ **Post date:** [March 10, 2025, 8:17am UTC](https://zatca1.discourse.group/t/zatca-e-invoicing-x509certificate-ccsid-pcsid-not-valid-for-vat-registration-number/6153/3 "2025-03-10T08:17:37Z")
hi sir thank you for your replay now the simulation of b2c in voice reporting fine { “requestUri”: “[https://gw-fatoora.zatca.gov.sa/e-invoicing/simulation/invoices/reporting/single](https://gw-fatoora.zatca.gov.sa/e-invoicing/simulation/invoices/reporting/single)”, “requestType”: “Invoice Reporting”, “statusCode”: “200-OK”, “reportingStatus”: “REPORTED”, “validationResults”: { “status”: “PASS”, “infoMessages”: [ { “status”: “PASS”, “type”: “INFO”, “code”: “XSD\_ZATCA\_VALID”, “category”: “XSD validation”, “Message”: “Complied with UBL 2.1 standards in line with ZATCA specifications” } ], “warningMessages”: , “errorMessages”: } } but validating the invoice through [https://sandbox.zatca.gov.sa/TestXML](https://sandbox.zatca.gov.sa/TestXML) i get this error ---
**Author:** ![Rahoof](https://avatars.discourse-cdn.com/v4/letter/r/9d8465/32.png) [@Rahoof](https://zatca1.discourse.group/u/Rahoof)\ **Post date:** [March 10, 2025, 8:17am UTC](https://zatca1.discourse.group/t/zatca-e-invoicing-x509certificate-ccsid-pcsid-not-valid-for-vat-registration-number/6153/4 "2025-03-10T08:17:42Z")
my xml (Attachment 311380681800003\_20250310000000\_AMT\_G1\_82272.xml is missing) ---
**Author:** ![Rahoof](https://avatars.discourse-cdn.com/v4/letter/r/9d8465/32.png) [@Rahoof](https://zatca1.discourse.group/u/Rahoof)\ **Post date:** [March 10, 2025, 8:17am UTC](https://zatca1.discourse.group/t/zatca-e-invoicing-x509certificate-ccsid-pcsid-not-valid-for-vat-registration-number/6153/5 "2025-03-10T08:17:46Z")
hi sir thank you for your replay now the simulation of b2c in voice reporting fine { “requestUri”: “[https://gw-fatoora.zatca.gov.sa/e-invoicing/simulation/invoices/reporting/single](https://gw-fatoora.zatca.gov.sa/e-invoicing/simulation/invoices/reporting/single)”, “requestType”: “Invoice Reporting”, “statusCode”: “200-OK”, “reportingStatus”: “REPORTED”, “validationResults”: { “status”: “PASS”, “infoMessages”: [ { “status”: “PASS”, “type”: “INFO”, “code”: “XSD\_ZATCA\_VALID”, “category”: “XSD validation”, “Message”: “Complied with UBL 2.1 standards in line with ZATCA specifications” } ], “warningMessages”: , “errorMessages”: } } but validating the invoice through [https://sandbox.zatca.gov.sa/TestXML](https://sandbox.zatca.gov.sa/TestXML) i get this error - category : SIGNATURE\_ERROR - code :X509IssuerName - message : wrong X509IssuerName - category : SIGNATURE\_ERROR - code :X509SerialNumber - message : wrong X509SerialNumber ---
**Author:** ![idaoud](https://avatars.discourse-cdn.com/v4/letter/i/f9ae1b/32.png) [@idaoud](https://zatca1.discourse.group/u/idaoud)\ **Post date:** [March 10, 2025, 8:36am UTC](https://zatca1.discourse.group/t/zatca-e-invoicing-x509certificate-ccsid-pcsid-not-valid-for-vat-registration-number/6153/6 "2025-03-10T08:36:52Z")
Dear @Rahoof Thanks for reaching out, Please note that the web-based-validator has it’s own certificate this is why you will always face the error regarding the Certificate, However, you can rely on the Reporting API response as the API checking also the validation since the response is 200 OK this means the invoice has been reported successfully, Or you can use our SDK tool to validate your XML before sharing it with ZATCA APIs You can download [Zatca](https://sandbox.zatca.gov.sa/downloadSDK) Additionally, Kindly review the [Educational library](https://zatca.gov.sa/en/E-Invoicing/Introduction/Guidelines/Pages/default.aspx) to know how you can use SDK functionalities. Thanks, Ibrahem Daoud.