What UAE e-invoicing can learn from Saudi ZATCA’s rollout

ZATCA’s phase one, generation, became enforceable on 4 December 2021. It required resident taxpayers to generate and store tax invoices and notes through compliant electronic solutions. Phase two, integration, began on 1 January 2023 and connected those solutions to ZATCA’s systems, wave by wave. ZATCA committed to notifying taxpayers of their wave at least six months in advance.

The UAE did not copy this. Its model routes invoices through accredited service providers that exchange documents between buyer and seller and report tax data to the FTA. There is no separate generation phase; businesses go live on a single date set by their revenue band.

Six months sounded generous to Saudi taxpayers when their wave notice arrived. In practice, procurement, contract signing with a solution vendor, data clean-up and testing filled most of it. UAE businesses below AED 50 million have until 31 March 2027 to appoint a provider and 1 July 2027 to go live. Treat the appointment date as the deadline for having a working test, not for signing a contract.

The technical connection is rarely what holds a rollout back. Invoices fail on buyer VAT numbers, incomplete addresses and inconsistent product codes, and those problems live in the customer and item master, not in the integration. The lasting fix is a one-time clean-up followed by a simple rule: nobody creates a customer without its registration number.

Picture a Dubai group with a Riyadh subsidiary. When the Saudi entity’s wave notice arrives, its team checks 800 customer records and finds 96 without a complete address or VAT number, about 12%. Fixing them takes weeks of calls and emails. The UAE parent, having watched this, starts its own clean-up a year before its UAE go-live and spreads the work across ordinary month-end routines instead of a panic.

The point for UAE readers is timing. Data clean-up is slow because it depends on customers answering emails, not on your own team’s speed. Start it before you sign with a provider.

Under any clearance or reporting model, an issued invoice cannot be quietly changed. Saudi businesses that used to cancel and reissue invoices had to learn to raise credit and debit notes properly. The UAE guidelines say the same thing in their own terms: reductions go through electronic credit notes, increases through an additional invoice.

Testing only a standard sale is not testing. The awkward cases are the ones that fail: exports, discounts, prepayments, mixed-rate invoices, foreign-currency sales. Build a test list from your own last twelve months of invoices.

Build test cases that include amounts in foreign currency and the AED equivalent, because currency rules are where structured formats are strict. A USD 10,000 export converted at 3.6725 should show AED 36,725 consistently on the invoice, in the ledger and in the tax data.

Groups with entities in both countries will run two models side by side. A Saudi invoice and a UAE invoice will follow different technical rules and go to different authorities. Keep each entity’s VAT settings and invoice series separate in your books, even if one team runs both.

• Standard-rated domestic sale with a discount.
• Zero-rated export with a foreign-currency price.
• Credit note against a partly paid invoice.
• Invoice with both standard-rated and exempt lines.
• Advance payment followed by a final invoice.

HelloBooks Business plan supports multiple entities, each with its own chart of accounts, invoice numbering and currency settings, so a UAE company and a sister company can be managed from one login. The AI agent answers questions per entity, such as “which UAE customers have no TRN?”, and keeps the full invoice record your provider will need.

HelloBooks does not connect to ZATCA or to any UAE accredited provider, and it is not a Saudi or UAE e-invoicing solution in its own right. It is the ledger that keeps the data clean before your provider takes over.