Every ZATCA Phase 2 project comes down to one question: how will the system that creates your invoices talk to FATOORA? The answer decides cost, timeline and how much your finance team has to change. There are three routes. Which one fits depends far more on your systems than on your size.
The three routes
Route 1: the ERP's own ZATCA module
Some ERPs ship, or offer as an add-on, a module that produces Phase 2 invoices and talks to FATOORA directly.
- ERPNext has dedicated KSA compliance apps for Phase 1 and Phase 2, including a free, open-source option.
- Odoo includes a Saudi e-invoicing module for Phase 2 in Odoo Enterprise. It is not part of the free Community edition.
Good fit when: one ERP issues all your invoices and you are on a version the module supports. Watch for: version upgrades, POS or branch systems outside the ERP, and who supports the module when ZATCA changes something.
Route 2: a specialist e-invoicing platform
A dedicated platform sits between your systems and FATOORA. Your ERP sends it invoice data; the platform builds the UBL 2.1 XML, applies the cryptographic stamp, generates the QR code, handles clearance and reporting, stores the results and returns ZATCA's response to the ERP. Taxilla enInvoice is one such platform, and the one we implement as an official partner.
Good fit when: you have several invoicing systems (ERP plus POS, branch or billing tools), an ERP without a Phase 2 module, or an enterprise ERP such as Microsoft Dynamics 365 or SAP that you would rather not customise. Watch for: a subscription cost, and the integration work between your ERP and the platform, which is usually small and repeatable.
Route 3: a custom connector
Your team or a partner builds the FATOORA integration into the system directly, using ZATCA's specifications and APIs.
Good fit when: you run in-house software and have developers who will maintain it. Watch for: the most ongoing work of the three. Every ZATCA specification change becomes your change.
Side by side
| ERP module | Specialist platform | Custom connector | |
|---|---|---|---|
| Typical timeline | Shortest, if the module fits | Short to medium | Longest |
| Covers several source systems | Usually not | Yes | Only what you build |
| Who maintains it when ZATCA changes | ERP vendor or partner | Platform vendor | You |
| Best for | One ERP, supported version | Mixed systems, enterprise ERPs | In-house software |
How the connection is built
Whichever route you choose, the ERP and the e-invoicing layer exchange data in one of a few standard ways:
- APIs and SDKs, the most common for modern ERPs;
- web services;
- FTP / SFTP file exchange, for systems that export files;
- staging tables in a shared database;
- custom connectors where nothing standard exists.
We have used these patterns on integrations we have delivered, including ERPNext with Taxilla.
What to check before you decide
- List every system that issues an invoice, credit note or debit note. If there's more than one, Route 2 usually wins.
- Check your ERP version against the module's supported versions. An ERP upgrade can be bigger than the ZATCA project itself.
- Decide where rejected invoices get fixed. Your finance team should see ZATCA's error in the ERP they already use.
- Plan the onboarding: one CSID per invoicing system, simulation first, then production.
- Ask who maintains it. ZATCA updates its specifications. Know whose job that change is before you sign.
Platform by platform
- ERPNext: Route 1 works well with the KSA compliance apps; Route 2 suits groups with several systems. We are an official Frappe partner. See ERPNext in Saudi Arabia.
- Odoo: Route 1 on Odoo Enterprise; Community users need Route 2 or an upgrade. We are an official Odoo partner. See Odoo in Saudi Arabia.
- Microsoft Dynamics 365 and SAP: Route 2 is the usual choice in the Kingdom, because it keeps the ERP standard. We provide Dynamics 365 implementation and support services.
Next step
If you are in ZATCA's Wave 25, the deadline is 1 February 2027. Start with the list of systems in step 1, and we can tell you which route fits. Request a demo of our ZATCA e-invoicing solution, or read what Phase 2 requires first.
General information. Module availability depends on product versions and editions; confirm with the vendor for your setup.
