· 5 min read
Choosing practice software in the UAE: a firm's checklist
Most practice software was designed somewhere else, for somewhere else. Here is what a UAE firm should actually test before committing — and the red flags that predict regret.

Choosing practice software is one of the few decisions a firm makes that touches every client, every staff member, and every deadline — and it is usually made under time pressure, from demos designed to flatter. The generic advice (compare features, check reviews, mind the price) is not wrong, it is just insufficient for a UAE firm, because most practice software was designed for other markets and retrofitted here. What follows is the checklist we would use — and it applies whether or not the answer is our product.
Five things to actually test
- UAE tax as a model, not a label.Can the system compute a VAT return box by box from the ledger, and a Corporate Tax computation with the 0% and 9% bands, per client, per period? Or does “UAE support” mean a currency setting and a 5% tax code you configure yourself? Ask to see a filed period locked.
- Arabic client experience.Not an Arabic brochure — an Arabic interface for the client-facing surfaces, laid out right-to-left properly. Your staff may work in English; your clients’ signatories often will not.
- Document ingestion that matches reality.UAE clients send documents over WhatsApp. Test the real path: how does a photographed invoice sent to the firm at 11pm become an attributed, reviewed record? If the answer starts with “the client logs in and uploads”, that is a workflow for clients you do not have.
- An audit trail you can stand behind. Who changed what, when, and can a filed period be reproduced later exactly as submitted? If numbers can drift silently after filing, every dispute becomes archaeology.
- Data isolation between clients. You hold books and identity documents for many businesses. Ask specifically how client data is separated, who at the vendor can see it, and where it is stored.
Questions that separate vendors
Demos show the happy path. These questions show the rest: How do I get my data out, completely, if I leave? What happens to my month-end if your service goes down? Which of the features in this demo are shipping today, and which are “on the roadmap”? Who do I talk to when something breaks during filing week — a person, or a ticket queue in another timezone? None of these have trick answers; what matters is whether the vendor answers them plainly.
Red flags
A few patterns reliably predict regret. Treat them as disqualifying until explained:
- Spreadsheet export sold as integration.If the VAT “workflow” ends with an Excel file you finish by hand, the system has not removed the work — it has renamed it.
- Per-feature pricing traps. A low headline price where tax, documents, portal access, and support are each paid add-ons — priced per client, per user, and per module — is not a price, it is an opening bid. Model the real cost at your client count before signing anything.
- Localisation by translation.An interface that was translated into Arabic but still lays out left-to-right, or “UAE compliance” that is a template pack rather than behaviour built into the ledger.
However you weigh the criteria, insist on seeing the tax computation come out of the ledger rather than a spreadsheet — that one requirement quietly enforces most of the others. If you want to see what that looks like when it is native, the VAT & Corporate Tax workspace is a reasonable place to start.
Not tax advice
This article is general information for accounting practitioners, not tax, legal, or professional advice. Rules, thresholds, and reliefs change and depend on each business’s circumstances — always verify against current Federal Tax Authority and licensing-authority guidance before acting.
