We are currently experiencing an issue while reporting simplified invoices to ZATCA. Although our system is correctly signing and clearing standard invoices without any issues, we are receiving the following error messages specifically for simplified invoices:
Error: HTTP Status 202 -
{“validationResults”:{“infoMessages”:[{“type”:“INFO”,“code”:“XSD_ZATCA_VALID”,“category”:“XSD validation”,“message”:“Compiled 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”},{“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”} Context:
Our company is registered under the 1100 type, and we obtained the necessary certificate accordingly.
Standard invoices pass validation, signing, and clearance without any problems.
The issue arises exclusively when processing simplified invoices.
We would appreciate your guidance on the following points:
Is there a separate certificate or additional configuration required for simplified invoices under 1100 registration type?
Could this warning indicate a mismatch between the certificate type and the invoice type?
Is there a recommended approach to resolve this warning, ensuring compliance without impacting our ability to issue and report simplified invoices?
Your insights and recommendations would be highly valuable as we work towards resolving this issue.
To provide comprehensive support as usual, can I kindly ask you to collaborate with the below:
1- Are you using our SDK tool? If so, what is the version?
2- Kindly share the API that you are hitting.
3- Can you confirm if you are using the same certificate to sign the invoice in the Authorization in the API as basic auth with encoded Token in user name and secret as password ?
The warning you are receiving related to unmatched certificate that you are signing the simplified invoice with, and the BinaryToken in the authorization part from the API, can I kindly ask you to check this, and if you are using the same, I need to to reach out to your RM to arrange one to one meeting with our technical team, to provide comprehensive support as usual.
Still I’m facing the attached warning message when reporting the simplified Tax invoice, and I’m getting this feedback from chatgpt:
Key Points from the Error:
XSD Validation: The XML file is valid according to the UBL 2.1 standards and ZATCA specifications (status: PASS).
This confirms that the structure and fields in your XML are correct.
Certificate Issue:
The signing certificate being used is not valid for the VAT Registration Number specified in the XML.
The warning specifically states:
The X509 certificate used for signing is not valid for this VAT Registration Number.
This could mean the certificate does not match the registered VAT number for your company.
Please note that I used 1100 on the time of registering the devices, and it works with standard Tax Invoices without any errors, but this appear with simplified Tax Invoices.
Also, I made special registration for simplified invoices in one of these devices by using 0100 = Simplified
To provide comprehensive support as usual, Can I kindly ask you to share the full request and response along with the certificate that you are signing the XML with and the binarySecurityToken in the Reporting_API Authorization, through the below mail.
