I am seeking guidance on integrating Manager API with KSA Fatoora E-Invoicing for Phase II of our business. We have been using Manager for a considerable period, and finding a local developer with expertise in this area has been challenging.
I have seen Access Tokens in Managre time before, but I am uncertain about the process of utilizing them with Fatoora. The ZATCA help center has provided us with a temporary access key consisting of 8 characters, which is crucial for developers to integrate the accounting solutions seamlessly with Fatoora online this key ends after 1 hour.
@lubos@Ealfardan all members, any assistance or insights into this matter would be greatly appreciated.
I also have a similar request for the manager API, it is needed for virtual fiscalisation of Zim invoices to allow our accounting system to speak to the Zimra Data Management System. Please developers, this is critical.
That is not a problem. The question is whether accounting software can directly connect to ZATCA servers or whether there are whitelisted gatekeepers. If accounting software can directly communicate with ZATCA servers, that would be ideal.
The best approach would be open source HTML5 app that would link Manager.io with ZATCA. If there is a developer who can take on it, then Manager.io would sponsor these efforts.
it is very important to connect to ZATCA portal by manager. as suggested before add on service charge could be interduce in the portal for such services. manager.io must sort out the issue to link and comply with II phase other wise it will start loosing Saudi Arabia Customer in the long term.
Most of local accounting software they are doing this service with extra charge ( 1 for upgrading the system and 2 for doing the integration).
From my side Iam not expected manager to do everything for free and I really want to continue using the system unless otherwise I am forced to by law
please try to set up the road map for II phase to avoid customer leakage to others
This is interesting, maybe in the future my country will also implement a system like this.
Can someone clarify, what should be done or added to the manager. How should managers work to address these needs?
(I’ve tried reading the guide from @Ehab link, but I still don’t understand what the logic/technique is like.)
Could it be like this
Create Invoice
Send the invoice to the ZATCA Portal, and wait for a response from the server.
Write a response on the invoice / update invoice if the invoice is approved.
Print or send the approved invoice to the customer.
Yes something like this. When invoice is sent to the tax authority an another invoice number is generated which should be mentioned on invoice and incorporated in QR code.
In my country currently its done on POS level but will soon be required for all businesses in the supply chain to implement it.
If I understand correctly, the concise response is affirmative. As per ZATCA’s guidelines, any accounting or invoicing solution that complies with ZATCA regulations will have access to Fatoora E-Invoicing, even if these solutions are not formally authorized and listed by ZATCA. You can refer to the Solution Providers Directory from ZATCA for further details and clarification here:
For developers looking to integrate with ZATCA, all essential information can be found in the Developer’s Portal, including technical requirements and specifications, accessible here:
I believe that integrating with Manager will be more straightforward than seeking a third party.
here is an example from a local solution providing integration for free for its customers:
Has someone worked on this topic?
I’m very interested about this.
I heard that the tax authorities in my country will release a new system later in June or July. I also heard they introduced UBL or XML in this system.
I don’t understand web programming, I just want to understand how this eInvoice works, because maybe I will need it later.
I found this topic on github zatca-xml-js. Looks like it was made for Zatca eInvoice. Maybe we can use it in Manager.
I’ve lost hope in this matter. If I had the authority, I would close this topic immediately, as our deadline for electronic invoice integration is April 30, 2024, just three days away. Unfortunately, there has been no response from the relevant parties in Manager, except for suggesting sponsoring efforts of any local developer can handle it. I appreciate @Ealfardan attempt to contact the Saudi office for integration insights.
Despite searching for a more suitable local software actually, we found many, I continue to monitor the situation for any updates. I wish everyone success, but I advise all users within Saudi Arabia or anyone reading this in search of reassurance to act now and find an alternative solution. It appears this matter will take more time, and there’s no clear plan or commitment to implementing necessary requirements, even from a governmental entity, as currently observed.
I have asked and searched for 2phase what I come to know is that
There services providers who is their service is working as broker for the integration which their responsibility will be authenticating the invoice and stamp it. Also you will know the status if the invoice rejected or accepted and where is the issue.
All what is required is providing the API to the service provider with the code from business owner registered mobile
Please accept my apologies but I will translate in Arabic to make it clear and to support manager.io
منذ فترة وانا ابحث عن المرحلة الثانية كانت الامور غير واضحة بعد كتابة رسالتي الاخير بدأت التحقق اكثر الى ان توصلت الى ان في شركات تقدم خدمات الربط و تعمل كوسيط لعملية التحقق من مطابقة الفواتير لمتطلبات الهيئة.
عملية التحقق لا تتعدى ١٠ ثواني
في شركات محلية و اجنبية منها EY PWC وغيرها من الشركات
سأشارك الرابط المعتمد من الهيئة للشركات التي تقدم خدمات الربط
From what I can see, there is RESTful API for e-invoicing so it should be possible to create the entire integration within Manager.io as an extension in javascript. Similar how QR codes are already done. This way there wouldn’t be any 3rd-party system involved and no fee.
I’m actively looking into this and the integration will be available. One way or another. There are multiple countries coming up with similar requirements so this is very much on my radar.
I believe this can be done in Manager, Generate Signed Invoice, Compliance, Clearance and Reporting worked well with Zatca Development Portal in my experiments.
It just works, but I’m still confused about some things, and I hope someone can provide a simpler explanation for me.
If anyone is willing to provide assistance,
What is the difference between Simplified Invoice and Standard Invoice?
How do I differentiate between Manager transaction being Simplified Invoice or Standard Invoice?
I’ve tried looking at examples of Invoices from the Zatca SDK, and I don’t find any definite differences between the two except InvoiceTypeCode.
What is the difference between Clearance and Reporting?
When is it used?
Do all invoices have to go through clearance, then reporting?
I understand this should be asked via the Zatca development forum, unfortunately I can’t create an account on the forum, I have also read several guides published by Zatca Development, but unfortunately, I still don’t understand, maybe because of my limited language skills, or maybe because I didn’t experience it directly.
Currently my code is working well for Sales Invoices, but I need to tidy up my codes, before I share them on this forum as an additional reference for those who want to develop them.
To my understanding, clearance is for uncleared transactions for the full tax invoice process while the reporting is for transactions that aren’t cleared immediately such as for POS registers or when the ZATCA servers are down and full tax invoices have already been issued uncleared.
I’m not exactly sure if my understanding is a 100% correct, but we can learn more by experimenting with both the required data and the responses we get from ZATCA
@Mabaega
this is the E-invoicing Details from the page 14 to page 19 is the differentiate between Manager transaction being Simplified Invoice or Standard Invoice
Clearance:
Purpose: The primary objective of the Clearance process is to verify the Electronic Tax Invoices and associated Electronic Notes transmitted to the authority.
Submission: Taxpayers submit e-invoices, credit, or debit notes to ZATCA’s FATOORA platform using APIs for validation and clearance.
Validation: ZATCA processes and validates the submitted documents against specified standards and specifications during the Clearance process.
Outcome: The submission is either accepted as valid, accepted with warnings, or rejected with errors, with corresponding notifications provided to the taxpayer.
Storage: Valid and accepted documents, along with any warnings, are stored by the FATOORA platform for ZATCA.
Timing: Clearance applies primarily to Standard documents (B2B) for Business to Business transactions.
Reporting:
Purpose: The Reporting process involves the submission of e-invoices, credit, or debit notes to ZATCA’s FATOORA platform using the Reporting API.
Submission: Taxpayers report all invoices generated throughout the day to the FATOORA portal using the Reporting API.
Validation: ZATCA performs validation checks on the invoice data submitted through the Reporting API.
Outcome: The submission is validated, and based on the validations, it is either accepted as valid, accepted with warnings, or rejected with errors.
Timing: Reporting applies primarily to Simplified documents (B2C) for Business to Consumer transactions.
Here is what i could get
Well, if I may draw a conclusion,
Clearance is used to report B2B Standard Invoices.
Reporting is used to report B2C Simplified Invoices.
If it’s true,
How do we determine whether an invoice to a manager is a Standard Invoice or a Simplified Invoice?
Are there any special differences that we can use as a reference?
or will this be selected manually by the User?
