ZATCA Phase 2 E-Invoicing (KSA)

This is build-to-order, so there is an honest lead time. After a short scoping call to confirm your VAT setup, branches and document layouts, typical delivery is around 3 to 5 weeks: build and unit-test in a sandbox, complete ZATCA compliance CSID onboarding, validate sample cleared B2B and reported B2C invoices against ZATCA, then promote to production. Existing or complex multi-branch setups can extend this, and we give you a firm timeline before you commit.

No. There is no instant AppSource download. ECOSIRE builds and installs it as a per-tenant AL extension directly on your Business Central environment (Online or on-prem) and supports it. This lets us tailor the UBL mapping, onboarding and layouts to your tenant rather than shipping a one-size-fits-all listing.

ZATCA periodically revises the Fatoora technical spec (schema, validation rules, API versions) and Microsoft ships BC platform updates roughly monthly. Your agreed support and update window covers regression-checking against those changes and shipping a refreshed extension build, so you stay compliant without re-engineering it yourself.

Yes. Standard tax invoices go through the real-time clearance flow and are only issued once ZATCA returns a cleared XML; simplified (B2C) invoices are reported, with the QR code printed at point of issue and submission within the 24-hour window enforced by a job queue. Credit and debit notes are handled with the correct hash chaining (PIH/ICV).

No. It uses AL event subscribers on the standard Business Central posting routines rather than replacing them, and it ships as an isolated per-tenant extension with its own permission set. It coexists with your other ISV apps and keeps your normal Post / Post and Send flow intact — compliance just happens alongside it.

Clearance status, ZATCA UUID, the cryptographic hash, the cleared UBL XML, the QR payload and any ZATCA warning/error codes are stored on the posted sales invoice via table and page extensions inside your own tenant. You can filter and report on them in BC, and the cleared XML is retained for audit and reconciliation.