@psinclair Great, thank you, if the check API returns the signed B2B invoice that would solve everything.
Hi,
In addition to API if portal status page can show reported invoice still one can check but at the moment user end is blind. thanks
1 Like
@psinclair
API to check if hash exists would be helpful but it would much transparent if you can return the QR Code as well in the response of this API since people here are doubtful that they are submitting the invoice first time and getting 409 conflict response.
So in this API if you could return the QR Code as well, would clear the doubt since QR code can be decoded and its data can be matched with internal system data.
Thanks,
@idaoud @psinclair Thanks you for considering my suggestions, but still this won’t resolve the issue, i.e. we need the cleared invoice in case we weren’t able to get it the first time due to whatever reason.
It’s better to add invoice status/cleared invoice along with 409 response of B2C and B2B invoices. So, we can easily identify the status of invoice.
Also consider the @Malik suggestion. It’s good for taxpayers.
1 Like
Hi, Very right there should be API not only to check status but also if signed xml need to download just a GET call b passing a parameter. Technology is very good if all working fine but sometimes an unknown thing can hit you badly and tax matters are legal matters.
I am sure ZATCA team might say every system need to follow instructions and keep a copy and archive sure that is happening but still technical glitches can happen any time and there should be an option. For example Portal status page always having issues till date ZATCA unable to sort it out and always reply if you contact that you just keep API responses. Please consider requests from user side and try to provide enhancements. thanks
1 Like
Hi Philip,
Any update on this matter hope not again will stop with errors. thanks
Hi @psinclair ,
When would we be planning to have the developer session walkthroughs? Just wanted to know so that we can be proactive and avoid unnecessary hiccups.
Dear All,
ZATCA is arranging a 1 hour session - on 26 Nov, 2024 from 10am to 11am KSA time - to discuss specific scenarios regarding 409 errors (duplicate invoices validation). Kindly prepare your questions in advance and share with sp_support@zatca.gov.sa with subject “409 Errors” latest by 25 Nov, 2024 evening.
Meeting schedule:
26 Nov, 2024 Tuesday from 10am to 11am KSA Time.
Below is the meeting link for
Meeting Link
Meeting ID: 347 282 177 290
Passcode: Nn9Xv22p
1 Like
@eCloud @Adithya_Raviraja @mkw @Malik @sameer @Maala @pmohdameen @mohdzeeshan5c0 @Hadi @rudyzidan @Arratech @BEX @plasker @y.khraishi @abin @m.alnoursi @sameer @mohammad.mt
Request all to please block the calendar with above invite.
2 Likes
Dear Philip and Ankit,
It was a pleasure to attend the recent online session discussing the challenges related to 409 errors and other issues encountered by both service providers and taxpayers. Below are the key points noted during the meeting:
- API for Hash Verification
ZATCA will release an API enabling users to verify whether a hash is already present in their database, cleared, or reported. - Timeline for 409 Check Implementation
The 409 error check is scheduled for implementation by the end of December 2024. However, the aforementioned API will be released before this date. - Notification of Implementation Changes
Any changes requiring implementation by stakeholders will be communicated by the ZATCA team at least one week prior to deployment. - Portal Statistics and Scalability
Due to the large volume of transactions, portal statistics will be addressed in the first or second quarter of the upcoming year. - Support Contact
For any required support, users are advised to generate a ticket by contacting sp_support@zatca.gov.sa. - Workaround of 409 for B2B
- In case where users could not receive or could not store the cleared signed XML of B2B invoices and not able to share this invoice with customer then current workaround is to generate a credit note against this invoice and create a new invoice, get it cleared by zatca and share it with customer.
- Request for Signed XML API
An API for retrieving signed XML as a response was discussed. While this involves significant effort, ZATCA has assured that it will be provided, likely in the first or second quarter of the upcoming year. - Handling Missing Signed XML
If, for any reason, the signed XML is not received, it is advisable to:
- Retain the error details as a log for reference.
- Share the XML with the client as proof of submission.
- However, the preferred approach is to adjust the existing entry and submit a new one where possible.
- B2C 24-Hour Time Limit Concern
A concern was raised regarding the 24-hour time limit for B2C transactions. Specifically, if a transaction is pushed to ZATCA and an error occurs due to data issues that take longer than 24 hours to resolve: ZATCA clarified that the initial push must be completed within 24 hours.
Retain the submission proof and present it as evidence in case of subsequent inquiries or audits.
ZATCA emphasized its commitment to resolving technical challenges and improving the overall tax system in KSA.
Please feel free to add if any missed and were discussed.
@Ankit_Tiwari @psinclair
4 Likes
@Malik
Very good documentation of concluded points in today’s session.
Appreciated.
Point no. 6 might need a slight modification as below:-
- In case where users could not receive or could not store the cleared signed XML of B2B invoices and not able to share this invoice with customer then current workaround is to generate a credit note against this invoice and create a new invoice, get it cleared by zatca and share it with customer.
1 Like
thanks and updated. Jazakallah khair
Hi everyone! Our team is also facing the issues mentioned on this thread. @psinclair @Ankit_Tiwari do you have an ETA for this new endpoint for hash verification?
Dear all, any update or progress in this regard. Thanks
Dear @Aturkistani
Saw the announcement about [Invoice Frontend Validation] . Its clearly explained about 409 and 208 status codes but nothing is specified about the API to check whether the invoice hash is already submitted or not , so that your concern regarding excessive usage of reporting and clearance API can be minimized. Please comment on this.
Saw the announcement about [ Release of 409 and 208 Enhancement].
It would be appreciated if we could also have the clarification from zatca regarding the invoices which were being submitted first time but received 409 response.
Thanks,
Dear @mohdzeeshan5c0,
Thank you for reaching out.
This is not possible, as 409,208 responses are being returned only if the InvoiceHash of the invoice has been submitted already before, and having a duplicated hash for different e-invoices is also not possible due to the presence of “UUID” and other unique identifiers fields.
That means no different 2 invoices can have the same invoiceHash.
1 Like
Dear @Aturkistani ,
Please comment on this .
Referring to the announcement available here. Is there any information on when this change will be introduced in the simulation environment? As I understand, the production release date is not yet confirmed.
Currently, we were unable to receive the 208 status code for clearance invoices, on simulation environment which prevents us from testing the changes in our solution. Additionally, the sandbox documentation (Zatca) lacks an example of such a response.