[warning : certificate issuer name] in real B2C invoices on production and production CSID is sent , not the complice CSID

XML and business rules
1

{“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”:“certificate-issuer-name”,“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”}

2

Dear @Jamil

Thanks for reaching out, Welcome to our community.

For the CERTIFICATE_ERRORS Warning, can I kindly ask you to check and confirm if you are signing your simplified invoices with the right PCSID not the CCSID for the same VAT in the XML.

Thanks,
Ibrahem Daoud.

1 Like
3

Make sure it’s the production CSID

1 Like
4

Thank you for the reply.
I checked again and confirmed that the certificate is PCSID and not the CCSID .
And I need to add that this warning only raises with B2C invoices
I mean if I’m singing B2B for the same company and same certificate, it will pass and its status is success,

5

dear @Jamil,

signing is not required for B2B invoices, there are no validations on the B2B invoices digital signature, as it will be signed by ZATCA.

For this warning, please ensure the most common reasons for receiving it:

1- using the PCSID instead of CCSID: In reporting, only PCSID should be used for signing and sending the invoices.

2- using a CSID from simulation in production or vice versa: sim & prod are independent environments, mixing the CSIDs between them will lead to “errors & warnings”

3- signing invoices with CSID that belongs to another VAT: the CSID used for signing must be matched with the seller VAT number inside the XML invoice.

If you have ensured all of the above and the issue still persists, reach out to SP_Support@ZATCA.gov.saproviding the details of the issue & supporting attachments.

Regards,

6

Thank you for the follow-up.
After we ensure all of those requirements, we figure out what the issue was:
It was in the format of the IssueName after each comma-separated component, there should be a space after the comma

thank you for support
zatca