Could not connect to endpoint

Clearance and Reporting
1

Dear All,
From yesterday night onwards we are getting the below response for several bills. Please respond as our reporting and clearance blocked because of this .Thank you.
{
“httpCode”: “500”,
“httpMessage”: “URL Open error”,
“moreInformation”: “Could not connect to endpoint”
}

2

@anusv are you using the new endpoint https://gw-fatoora.zatca.gov.sa ?

3

@bahaeddine yes i am using
https://gw-fatoora.zatca.gov.sa/e-invoicing/core/invoices/reporting/single
this URL

4

@anusv it’s probably a system overload from zatca . can you try the website xml test to check your invoice is correct ?

5

We are facing the same issue. ZATCA support team, Please review.

6

@Aturkistani Please verify and take action as our many of the invoices getting failed for submission

7

Same problem today, we are using appropriate endpoints, please work on it, thanks

8

Dears @anusv , @bahaeddine , @housunus , @vjsrdev

Thanks for reaching out,

In case of power failure or internet connectivity issues you should share the generated invoice & submit it once fixed & report failure to ZATCA, please refer to the “ e-invoicing guideline, see Section 10 for an in-depth description of ‘Failure Scenarios.’” For more in-depth description with the details.

Also regarding your question on what to do with the invoices if getting one of the below responses:

0 – no response,

500 – Internal server error

502 – Bad Gateway

503 – Service Unavailable

504 – Gateway Timeout

You should re-submit the invoices to ZATCA without changing UUID,ICV and other identifiers, only changing such identifiers if the invoice got rejected by ZATCA when issuing a corrective invoices, a detailed description by scenarios are below:

If ZATCA’s servers are non-responsive

In reporting API (B2C invoices), the taxpayer’s solution (EGS) should be attempting to report, invoices and continue at this way until successful reported response, maintaining the official timeline of reporting, invoices to ZATCA within 24 hours of issuing, you can share the invoice with the client & report it once the service Is back within 24 hours.

In clearance API (B2B invoices), the taxpayer’s solution should re-try to clear the invoice, if servers remain non-responsive, taxpayer shares uncleared invoice , keeps records of the transaction (Art. 7.5) and confirms the existing contact details of buyer, and taxpayer’s solution will continue attempting to clear the invoice and once clearance is successful, taxpayer re-share the cleared invoice with the buyer.

If failure is from taxpayer’s side

In reporting API (B2C invoices), the taxpayer shares the invoice with the buyer, and then he has officially 24 hours to report invoice to ZATCA, EGS can share the invoice anytime once the issue is fixed (power failure, connectivity issue etc.). In case the taxpayer is not able to submit the invoice within 24 hours, he should inform ZATCA through the dedicated form on ZATCA’s website, once the EGS’s function is restored then taxpayer should notify ZATCA & immediately report the invoice to ZATCA.

In clearance API (B2B invoices), similar steps to be followed as reporting, taxpayer merchant processes transactions, shares uncleared invoice1 , keeps records of the transaction (Art. 7.5) and confirms the existing contact details of buyer, after the issue is fixed and the invoice is cleated, taxpayer re-share the cleared invoice with the buyer.

For other scenarios please refer to “e-invoicing guideline,” section 10”.

If you require any further assistance, please don’t hesitate to reach out to our support team via below mail

SP mail: sp_support@zatca.gov.sa

Thanks,
Ibrahem Daoud.

9

@vjsrdev @housunus we are still facing the issue . What about yours ?

10

@idaoud Thank you for the response . we are getting 500 as error

11

Same issue with me till now,