Connecting to the Fatoora platform on a documented path

Yes — Odoo (odoo.com) is listed in the official Solution Providers directory of the Zakat, Tax and Customs Authority (ZATCA), qualified for Phase One: generation and storage. The listing can be verified directly in the directory on ZATCA’s website. To be precise, ZATCA attaches a disclaimer to that directory: it is indicative and non-binding, it is not an approval by the authority of the solutions listed in it, and a taxpayer is entitled to work with any provider, listed or not. Phase Two (integration) is not qualified at brand level: the Compliance CSID and the Production CSID are issued to a single entity bound to its tax number (TIN), and they do not transfer to another entity. In practice, Odoo ships the Saudi localisation (l10n_sa) and e-invoicing (l10n_sa_edi) modules in its standard distribution, and we deliver the full certification path for your entity through to production — with no accreditation claim of our own.

Technically yes, but it adds another maintenance vendor and an upgrade path separate from your Odoo version. The l10n_sa and l10n_sa_edi modules are part of the standard distribution, so we start there unless you have a specific reason not to.

No. We configure and test in the sandbox without touching your current invoicing, and only move to production once the test is passed and your team is trained on the new procedure.

A rejected standard invoice cannot be used for VAT purposes until it clears, so we train your team to read the error code and resolve it, and hand over a written reference of common rejection causes and their fixes.

Yes, but each entity needs its own certification path because it binds to its own tax number. We run the multiple paths inside one project and document each entity’s status separately.

Yes. We configure the seven-year signed-XML archive inside the system’s storage layer, with backup, restore and role-restricted access.

The Compliance CSID is issued after passing the sandbox test — a prerequisite, not a final clearance. The Production CSID is issued after moving to production and ZATCA confirming the system generates valid signed invoices live. You need both.

Odoo is our core specialism. We can assess another system and document its gaps against the six requirements, but if it does not support the API or digital signing at all, the practical route is usually replacing it rather than patching it.

Yes. Training is delivered in Arabic on your own data and covers issuing an invoice, reading clearance and rejection states, and handling platform downtime, with written user guides that stay with you.

Yes. The assessment session establishes whether your system meets the six requirements, what the gaps are, and the expected time to a Production CSID — with no obligation to proceed.

The requirement applies to invoices issued after your entity’s wave date, alongside the seven-year retention duty. We review your position during the assessment and state clearly what, if anything, applies retroactively.

No. The ZATCA mark belongs to a government authority, and using it commercially implies an endorsement that has not been granted. We describe the path and the documents issued in your entity’s name instead.

The ZATCA path is specific to the Kingdom because it binds to the Fatoora platform and a Saudi tax number. Odoo implementation itself we deliver to clients across the region, respecting each country’s local requirements.

Ask for a Compliance CSID document from a client in your own wave, the first-pass acceptance rate in production, two callable references, and a sandbox demonstration before signing. Those four questions separate a ready deck from a tested implementation — and we welcome them.