Chart of Accounts Design for UAE Businesses

The chart of accounts is the skeleton of the ledger: the complete, organised list of every account the business posts to, and the structure that turns thousands of journals into financial statements. A good chart makes the trial balance read like a story — assets then liabilities then equity, revenue then expenses, each balance sitting where the reader expects it. A bad chart makes every close an excavation: postings in the wrong accounts, 'miscellaneous' carrying material balances, VAT accounts that do not reconcile to the return, and comparatives that cannot be trusted because last year's codes meant something different.

The design principles are few and durable. Five families in statement order: assets, liabilities, equity, revenue, expenses. A hierarchical numbering scheme with room to grow — ranges per family, gaps between accounts. One account per distinct reporting purpose, no duplicates, no near-duplicates that force the bookkeeper to guess. Control accounts for every sub-ledger, agreed at every close. And dimensions (departments, cost centres, projects) for analysis, so the chart itself stays lean.

The UAE specifics slot into this structure: dedicated VAT accounts that reconcile to the VAT return, payroll codes that follow the WPS cycle, separate intercompany codes per group counterparty, and account names in the language the business actually uses. This page covers the numbering, the five families, the control-account discipline, and the mistakes that turn charts into jungles.

It is worth saying plainly why this unglamorous document deserves a full design effort: every downstream product of the finance function — the VAT return, the management accounts, the audit file, the Corporate Tax computation, the board pack — is a report on the chart of accounts. A well-designed chart makes each of those reports fall out of the ledger naturally; a poorly designed one makes each of them a manual exercise in reclassification and apology. The chart is the cheapest internal control a business can buy, and the most expensive to fix once years of history are coded into it.

Numbering first: the scheme should sort the trial balance into financial-statement order without manual rearrangement. A common SME scheme: 1000–1999 assets (1010 cash, 1100 bank — current account, 1200 trade debtors control, 1300 inventory, 1500 fixed assets at cost, 1600 accumulated depreciation), 2000–2999 liabilities (2100 trade creditors control, 2200 accruals, 2300 VAT payable, 2400 WPS payroll payable, 2500 intercompany payables, 2600 end-of-service provision), 3000–3999 equity (3010 share capital, 3100 retained earnings, 3200 current-year profit), 4000–4999 revenue (4100 sales — goods, 4200 service revenue, 4300 intercompany sales), 5000–9999 expenses (5000 cost of sales, 6000 staff costs, 7000 general expenses, 8000 depreciation, 9000 finance costs).

The gaps matter: numbering 1010, 1020, 1030 leaves room for 1015 later without renumbering. Four digits are enough for most SMEs; five for groups with consolidation needs. Consistency matters more than the specific numbers: the same code must mean the same thing in every entity, every period, every report.

Hierarchy second: group accounts roll into sub-accounts. '6000 staff costs' is the header; 6010 basic salaries, 6020 allowances, 6030 EOSB provision, 6040 visa and medical costs are the postings. Reports can show the header or the detail; the TB stays readable; analysis does not require new top-level codes. And naming: names should say what the account is for in the business's own language — '6020 allowances — housing' beats '6020 other emoluments'. The bookkeeper posting at speed should never have to guess.

Mapping completes the design: every account carries its financial-statement mapping — which line of the balance sheet or P&L it feeds, and for groups, which consolidation line it maps to. The mapping is documented in the chart master, not kept in the finance manager's head. When the auditor asks why 7050 marketing sits in general and administrative rather than selling expenses, the mapping answers. For groups, the mapping goes further: each subsidiary uses the identical chart (same codes, same names), and the consolidation maps each code to the group line. A group where each entity invented its own chart consolidates by spreadsheet heroics every quarter; a group on one chart consolidates by aggregation. Standardise the chart before the group grows, because retrofitting five entities onto one chart means reclassifying five histories.

Assets (1000s): current assets first — cash, bank accounts (one code per account), trade debtors control, other receivables, inventory, prepayments — then non-current: fixed assets at cost by class, accumulated depreciation by class, deposits, long-term intercompany receivables. The order follows liquidity, matching the balance sheet.

Liabilities (2000s): current — trade creditors control, accruals by type, VAT payable, payroll and WPS payables, short-term loans, intercompany payables — then non-current: long-term loans, end-of-service provision, other provisions. Tax balances get their own codes, never netted: VAT payable and VAT receivable (where it arises) sit separately until offset in the return.

Equity (3000s): share capital, statutory reserves where applicable, retained earnings (prior years), current-year profit (system-generated, never posted to directly), shareholder current accounts (clearly separated from revenue and expenses — drawings are not expenses, contributions are not revenue).

Revenue (4000s): split by what management needs to see — goods vs services, mainland vs free-zone, intercompany vs third-party. Each revenue code needs its VAT treatment defined: standard-rated, zero-rated, exempt, out-of-scope — because the VAT return is built from these codes.

Expenses (5000s–9000s): cost of sales (5000s) kept strictly for direct costs — the gross margin depends on this boundary; staff costs (6000s) with the WPS and EOSB codes; general and administrative (7000s); depreciation and amortisation (8000s); finance costs (9000s) — interest, bank charges, exchange differences. The expense coding determines every management report; get the boundaries right once.

Opening a new company's books deserves the same care: the opening trial balance posts each brought-forward balance to its proper code — bank balances to the bank codes, the share capital to 3010, pre-incorporation expenses where the policy puts them — and the opening TB is agreed to the source (bank statements, incorporation documents) before a single transaction is posted. A surprising number of charts go wrong on day one: the opening bank balance posted to 'miscellaneous', the capital posted to revenue, the prepayments expensed. The chart cannot organise history that was never organised; start clean, because the first TB is the foundation every later period builds on.

VAT accounts are the UAE's signature requirement. Minimum: 2310 output VAT (VAT on sales, credited as sales are invoiced), 2320 input VAT (VAT on purchases, debited as tax invoices arrive), 2330 VAT payable (the net position transferred each return period). Add 2340 reverse-charge VAT and 2350 import VAT where the business needs them. The monthly discipline: the VAT return agrees to these accounts — output VAT to Box 1 equivalents, input VAT to the reclaim boxes — and any difference is investigated before filing, not after.

Payroll codes follow the WPS cycle: 6010 basic salaries, 6020 allowances, 6030 end-of-service provision, 6040 visa/medical/insurance costs, 2410 WPS salaries payable (cleared through the WPS transfer), 2420 accrued leave. The payroll journal posts to these codes every month; the WPS transfer clears 2410. A payroll that posts to a single 'salaries' code cannot produce the EOSB or leave analyses the business needs.

Intercompany codes are per counterparty: 2510 intercompany payable — Abu Dhabi subsidiary, 1510 intercompany receivable — JAFZA subsidiary, and so on. Never a single 'due to/from group' code. And free-zone specifics: where a business operates across mainland and zones, revenue codes split by location support both management analysis and the correct VAT treatment per supply — the chart carries the compliance, not just the bookkeeping.

Finally, the tax codes: Corporate Tax payable (2600s), deferred tax where applicable, and clear separation of tax expense from accounting profit lines. The CT computation references these codes; the auditor traces them. A chart that cannot show the tax position cleanly will produce a painful tax season.

Multi-entity groups add one more requirement: the identical chart in every entity. Same codes, same names, same VAT and payroll structures — so the trial balances aggregate without translation and the intercompany mirrors line up code-to-code. Local variations (a second country's VAT, a different payroll) are handled as additional codes within the shared structure, not as a different chart. And where the group reports in two languages, the account names carry both — the Arabic name alongside the English — because the bookkeeper, the auditor and the FTA reader should all recognise the same account. One group, one chart, one mapping: the consolidation then becomes arithmetic rather than archaeology.

Mistake one is the miscellaneous monster — '7090 miscellaneous expenses' carrying 15% of operating costs because nobody designed the right codes. Miscellaneous should be immaterial; if it is not, the chart is missing accounts. Review its contents quarterly and create codes for the recurring items.

Mistake two is duplicate and near-duplicate codes — 'office supplies', 'stationery', 'office consumables', 'admin supplies' — forcing the bookkeeper to guess and splitting one expense across four lines. One purpose, one code; merge the duplicates and reclassify.

Mistake three is posting to control accounts directly — journals straight to trade debtors control instead of through the sales ledger. The sub-ledger no longer agrees, the control is broken, and the aged-debtor analysis is wrong. Control accounts are posted only by their sub-ledgers.

Mistake four is the dead-code graveyard — codes for closed branches, old projects, long-gone loans, still active and occasionally posted to by habit. Deactivate (never delete) unused codes; deleted codes destroy history, deactivated codes preserve it.

Mistake five is changing the chart mid-year without restatement — renumbering in June and comparing June's 'new' codes against January's 'old' ones. Design well once; add within the gaps; restructure only at year-end with comparatives restated. And mistake six: no VAT codes — VAT posted to generic tax accounts or netted in expenses, making the VAT return unreconcilable. The return is a report on the VAT codes; without them, it is a guess.

Take a Dubai services SME — 25 staff, mainland LLC, VAT-registered, one group subsidiary. Its chart (110 accounts) opens with assets: 1010 petty cash, 1110 bank — Emirates NBD current, 1120 bank — USD account, 1200 trade debtors control, 1250 intercompany receivable — subsidiary, 1300 prepayments — insurance, 1310 prepayments — rent, 1500 office equipment at cost, 1510 accumulated depreciation — office equipment, 1550 motor vehicles at cost, 1560 accumulated depreciation — vehicles.

Liabilities: 2100 trade creditors control, 2200 accruals — audit, 2210 accruals — utilities, 2300 output VAT, 2310 input VAT, 2320 VAT payable, 2400 WPS salaries payable, 2410 accrued leave, 2420 end-of-service provision, 2500 intercompany payable — subsidiary, 2600 Corporate Tax payable. Equity: 3010 share capital, 3100 retained earnings, 3200 current-year profit (automatic).

Revenue: 4100 service revenue — mainland, 4110 service revenue — free zone, 4200 intercompany service revenue. Expenses: 6000s staff (6010 basic salaries, 6020 housing allowances, 6030 EOSB provision charge, 6040 visas and medical), 7000s general (7010 office rent, 7020 utilities, 7030 professional fees, 7040 travel, 7050 marketing), 8000 depreciation, 9000 finance costs (9010 bank charges, 9020 exchange differences).

Month-end: the VAT return agrees to 2300/2310/2320; WPS clears 2400; the intercompany confirmation agrees 1250/2500 to the subsidiary's mirror; the TB reads top-to-bottom as the financial statements. When the business opens a second bank account, it takes 1130 — the gap was waiting. That is a chart doing its job: invisible when right, invaluable always.

Design it once, with this checklist. Structure: five families in statement order; hierarchical numbering with gaps; one code per purpose; headers with posting sub-accounts; names in the business's own language. Completeness: dedicated VAT codes (output, input, payable, plus reverse-charge/import where needed); WPS and EOSB payroll codes; per-counterparty intercompany codes; tax codes separated and un-netted; dimensions (department, project) for analysis instead of duplicate codes.

Discipline: control accounts posted only via sub-ledgers and agreed every close; suspense cleared in days with named owners; miscellaneous immaterial and reviewed; dead codes deactivated, never deleted; additions documented with statement mapping; restructuring only at year-end with restated comparatives.

UAE fit: revenue codes split where VAT treatment or location analysis needs it; the VAT return reconcilable to the VAT codes every period; payroll codes following the WPS cycle; 7-year retention of the chart history and mappings. The chart of accounts is the one document the bookkeeper, the auditor and the FTA all read — make it say what it means.

The chart of accounts is the skeleton everything hangs on — the pages below cover the bookkeeping services that use it daily, the VAT rules it supports, and how accounting firms design the function.