ZATCA Phase 2 E-Invoicing for KSA (Fatoora Integration)

This is a build-to-order engagement, not an instant apps.odoo.com download. Typical delivery is 2-4 weeks depending on your Odoo version, chart-of-accounts complexity, number of VAT registrations, and how quickly your Fatoora portal access and CSID onboarding can be completed. We scope with you first, build and test against ZATCA's sandbox, then run a supervised production go-live.

Every engagement includes a defined post-go-live support and warranty window for bug fixes and issue resolution. ZATCA periodically updates its Phase 2 specification and business rules, and Odoo ships new major versions — we offer an ongoing maintenance path so your module stays compliant across those changes. Support scope, response times, and the update arrangement are agreed in writing before the build starts.

Yes. The module is built the native Odoo way (extending account.move, standard security via ir.model.access.csv and record rules, XML/OWL views, QWeb reports) so it runs on Odoo 17, 18, and 19. It works on both Community and Enterprise; on Enterprise it complements the built-in accounting features rather than replacing them, and it aligns with the l10n_sa localization.

ZATCA Phase 2 requires standard tax invoices (typically B2B/B2G) to be cleared in real time — the invoice is sent to Fatoora and returned government-signed before it is issued. Simplified invoices (typically B2C, including POS) are reported to ZATCA within 24 hours. The module handles both: real-time clearance on invoice confirmation for standard invoices, and reporting with automated retry (via a scheduled action) for simplified invoices.

During onboarding we request and install your CSID and cryptographic stamp certificate via the Fatoora portal API. For each invoice the module computes a UUID and an invoice hash, chains it to the previous invoice hash (PIH) to form the anti-tamper chain, applies the cryptographic stamp, and renders a TLV-encoded, Base64 QR code on the PDF/A-3. The QR carries the seller name, VAT number, timestamp, totals, VAT amount, XML hash, and stamp, and validates in the official ZATCA app.

Yes. Because it lives inside Odoo, any transaction that becomes an account.move can be cleared or reported. For external systems we expose Odoo's XML-RPC / JSON-RPC API and automated actions so a POS, e-commerce front end, or third-party billing platform can push transactions into the same compliant pipeline, keeping a single audit trail in the ERP.

Every invoice carries a ZATCA status (Not Submitted / Cleared / Reported / Rejected) and stores the full request and response payload for audit. Hard errors are surfaced to the finance user with the ZATCA validation message; warnings are logged but do not block issuance. A scheduled action retries transient failures, and rejected invoices can be corrected and re-submitted without breaking the invoice-hash chain.