Clearing every invoice
through Fatoora, in real time.

Three separate engagements in the Kingdom — ATCL, Alomar Furniture and Al Watania — all running Microsoft ERP. Two on Dynamics 365 Finance & Operations, one still on Dynamics AX. Different industries, the same regulatory deadline.

Alomar Furniture manufactures and retails furniture across Saudi Arabia. Al Watania operates in FMCG and agriculture. Between them they cover manufacturing, retail and distribution — three different invoicing patterns, one specification to satisfy.

ZATCA Phase 2 requires integration, not just formatting. Each invoice has to carry a UUID, a cryptographic stamp, a hash chained to the previous invoice and a QR code, and it has to be submitted to the Fatoora platform for clearance or reporting depending on invoice type. Get any element wrong and invoices are rejected — which means the business cannot bill.

The deadline was fixed and external. Unlike most ERP work, there was no option to descope: an implementation that is 95% complete on the compliance date is an implementation that has failed.

• R1Invoice generation conforming to ZATCA's technical specification and implementation resolution
• R2Cryptographic stamping and hash chaining applied to every electronic invoice
• R3QR codes generated and printed on both simplified and standard invoices
• R4Live integration with the Fatoora platform for clearance and reporting
• R5Arabic and English invoice output, correct on both
• R6Rejection handling that surfaces the reason rather than failing silently

We implemented e-invoicing inside each client's existing ERP rather than bolting on a middleware product, so invoices are stamped and cleared as part of the normal posting process instead of through a parallel system finance has to reconcile against.

The part most projects underestimate: the failure path. Clearance can be rejected for reasons that have nothing to do with the invoice a user just raised — a broken hash chain, a certificate nearing expiry, a schema change. Handling that visibly, in language a finance team can act on, is most of the real work.

• 01Invoice generation. Electronic invoice documents built to ZATCA's required structure, for both standard and simplified invoice types.
• 02Cryptographic stamping. Stamping, hashing and chaining applied per invoice, in line with the published rules.
• 03QR codes. Compliant QR codes generated and rendered on printed and PDF invoice output.
• 04Fatoora integration. Direct integration with the clearance and reporting endpoints, handling responses and rejections.
• 05Bilingual output. Invoice layouts correct in Arabic and English, including numerals and date treatment.
• 06Rollout support. Deployment and post-go-live support across three client estates on two Microsoft ERP generations.