A live ZATCA Phase 2 integration on your ERP — Odoo in most of my delivery work, though the compliance logic itself is regulator-driven rather than platform-specific. That covers the clearance and reporting flow itself, an in-UI status indicator so staff can see per-invoice compliance state without leaving the app, and invoice numbering and sequencing that actually satisfies what ZATCA expects, including edge cases like down payments that don't map cleanly onto standard sequencing. If you already have a Phase 2 integration and aren't certain it's solid, I audit existing implementations the same way — checking clearance status, sequencing and data mapping against the regulator's requirements.
New integrations start with a review of your current invoicing setup — branch structure, invoice types, and any existing numbering scheme — before any code changes. Audits of existing integrations run as read-only scripts against production, so I can check live clearance state and sequencing without any write access to the system I'm reviewing. Either way, the engagement ends with a written compliance report: what's compliant, what isn't, and what changed.
Saudi Arabia-based businesses, or businesses with Saudi operations, that need to move onto ZATCA Phase 2 for the first time, and businesses that already have a Phase 2 integration but want an independent audit before an inspection or after a numbering or clearance issue has come up. Most full-stack developers don't touch regulated invoicing at all — this is engineering where getting it wrong has a regulator attached to the consequence.
Tell me what's breaking — or what you're building.