The compliance certificate is not done with the following compliance steps yet

i got the issue

before january i was sending the sha 256 in the csr cnfg file
but when you told us the issue is fixed i faced the issue of invalidd csr on generating ccsid but when i read out the comments the issue was fixed
then i did some rnd and change this sha 256 to sha256 just removed the space and it works well i onboarded 4 differenr entites on simulation without any error again

@techcoder you shoulfd also review your xv csr cnfg file

thanks for your reply
My code had some other issues, but they were fixed, and now the submission works fine.

hi can you please share your code on how your using Chilkat to get csr and response from zatca

Hi Malik, can you please share a sample of your config file. we are facing issue with the csr.
please check our file if something is missing in it.

hello,

i am facing some troubles while trying to move to simulation environment:

here is the same csr information used:

csr.common.name=TST-886431145-30500675xxx3003

csr.serial.number=1-TST|2-TST|3-ed22f1d8-e6a2-1118-9b58-d9a8f11e445f

csr.organization.identifier=30500675xxx3003

csr.organization.unit.name=Riyahd Branch

csr.organization.name=Maximum Speed Tech Supply LTD

csr.country.name=SA

csr.invoice.type=1100

csr.location.address=RRRD2929

csr.industry.business.category=Supply activities

the error i am currently getting:
{
“errors”: [
{
“code”: “Invalid-OTP”,
“message”: “The provided OTP is invalid”
}
]
}

Two days back, the error was different from this. could you please help out here? it is urgent.

Have you moved from Sandbox to Simulation?

  1. You require the simulation template named “PREZATCA-Code-Signing” for the CSR.
  2. You also require the OTP from Fatoora’s simulation portal [as a separate button.]

Dear @ramitha

Thanks for reaching out,

To provide a comprehensive support as usual, can I kindly ask you to share your full concerns along with the steps that you followed to generate your CSR with your configuration file, to the below mail.

SP mail: sp_support@zatca.gov.sa

Thanks,
Ibrahem Daoud.

Dear idaoud,
Thanks for your quick response. some of my clients successfully onboarded simulation with same code i provided. i send the email with requested information. awaiting your kind advise.

Dears,

I have a few inquiries and would appreciate any clarification:

  1. Should the QR code be returned from the Clearance API? If not, how can I generate it myself?

  2. From my understanding, when using the invoice type “1000”, I need to send three types of invoices to the Compliance API in order to obtain the PCSID. Will the same behavior apply in the production environment as well?

Thanks,

Dear @Mnajjar

Thanks for reaching out. Welcome to our community.

Please find the answers below in order:

  1. Yes, after successfully integrating with ZATCA and starting to use the clearance API to send your actual B2B invoices, the response should be the cleared invoice signed by ZATCA, including the QR. This invoice “Cleared one“ should be shared with the client.
  2. Yes, you need to complete the compliance checks successfully to ensure the successful integration with ZATCA, or you will not be able to receive your PCSID.

I hope it’s clear enough now. Please do not hesitate to reach out if you require any further clarification.

Thanks,
Ibrahem Daoud.