Core/Production API returning response like compliance api

Onboarding, renewal and revocation
1

Hi All

I have passed simulation mode and then applied for production. First, I made a request for a compliance CSID, which I received. After that, I uploaded 6 documents (3 for standard, 3 for simplified).

Three of them were reported, and three were cleared.

Next, I requested a PCSID and received it.

Afterwards, I sent one simplified invoice to the core reporting API and got a “Reported” status, and one standard invoice to the core clearance API and got a “Cleared” status.

I followed the same process for both credit notes and debit notes.

For reference:

My question: When I am sending live invoices, I am still getting responses like this:

{
“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”: “BR-KSA-85”,
“category”: “KSA”,
“message”: “The Buyer’s contact phone number (BT-57) shall start with “0“ or “+”, followed by a maximum of 15 numbers and minimum of 4 characters after the “+“ or “0“, if present.”,
“status”: “WARNING”
}
],
“errorMessages”: ,
“status”: “WARNING”
},
“reportingStatus”: “REPORTED”
}

However, I was expecting the Reporting API response as mentioned in the integration sandbox API Swagger:

{ “invoiceHash”: “4JFgbmivjFU/otPSMfZCJTSISc123DbdQkOKHLe1J1Q=”, “status”: “REPORTED”, “warnings”: null, “errors”: }

2

Dear @manjitkm

Thanks for reaching out,

Please find the attached (Sandbox_Reporting_Response.png) showing that the response from Sandbox.

Additionally, note that what you shared ({ “invoiceHash”: “4JFgbmivjFU/otPSMfZCJTSISc123DbdQkOKHLe1J1Q=”, “status”: “REPORTED”, “warnings”: null, “errors”: })
Is a static text, and will be updated to match the response, meanwhile, Kindly note that there are no different between the sandbox response and simulation.

One more thing to inform, that you can only successfully integrate with ZATCA during the simulation or production environments only, and Sandbox is only to clarify the integration steps.

Sandbox_Reporting_Response
Sandbox_Reporting_Response1899×1000 60.2 KB

For any further support, do not hesitate to reach out.

Thanks,
Ibrahem Daoud.

3

First of all Thank You.

In my production environment, In response of CORE Reporting API, i am getting data in above format like you have shared as screen. Word “REPORTED” clear mentioned in response. So does it mean that my production environment is working totally fine according to above response.

My CSR details are also showing on portal onboarded device list., so i can assume that onboarding completed and all documents are uploading to production environment.

4

Morning @manjitkm

Yes, you are correct since you are seeing the same response from reporting API (https://gw-fatoora.zatca.gov.sa/e-invoicing/core/invoices/reporting/single)
and you can see your device in the devices list, this mean that you are fine.

One thing to mention related the warning message (BR-KSA-85), ensure to correct the phone number (BT-57) format, in further invoices, since it’s a warning this mean the response from API comes as 202 (Accept with warnings) this mean the invoice has been submitted successfully to ZATCA.

Thanks,
Ibrahem Daoud.

1 Like