Design a useful chart of accounts for a UAE small business
Build a compact account structure, apply it to two worked purchase entries and document coding decisions without confusing account labels with tax treatment.
A chart of accounts is the agreed list of categories used to organise the business’s records. It should help a UAE small company distinguish cash from revenue, unpaid bills from expenses, assets from current costs and owner funding from trading income. If every unclear transaction goes to “miscellaneous”, the reports may look complete while hiding questions that matter to the founder and tax preparer.
The sample below is a starting operating design, not a mandatory UAE account-numbering scheme or a complete financial-reporting template. Adapt it with the person preparing the company’s accounts. The relevant legal form, reporting framework, business activities and tax registrations determine what detail the finished system needs.
Design around the decisions the business makes
Begin with the reports management actually uses. A service company may need to understand consulting revenue, contractor costs, payroll and recurring subscriptions. A retailer may need inventory, cost of sales and sales channels. Copying a large company’s chart can create hundreds of rarely used categories without improving either business’s decisions.
List the recurring transactions and the balances that must be explained at month-end. Include bank accounts, customer receivables, supplier payables, fixed assets, owner balances and tax-related balances where applicable. Then decide which expense categories need separate visibility because they are large, volatile, controlled by different owners or require different review.
Write a brief definition beside each account: what belongs there, what does not, required evidence and who resolves uncertainty. An account called “professional fees” is more useful when its policy explains whether audit, legal and outsourced bookkeeping costs need separate subcategories.
A compact illustrative structure
The following codes are examples chosen for readability. They do not prescribe statutory treatment or imply that every business needs every account.
| Example code | Account | Typical purpose |
|---|---|---|
| 1000 | Bank: AED operating account | Transactions and balance for one identified bank account |
| 1100 | Trade receivables | Supported customer balances outstanding |
| 1200 | Input VAT under review or recoverable, as appropriately separated | Track VAT assessment and resulting balances |
| 1500 | Equipment | Items meeting the applicable asset criteria |
| 2000 | Trade payables | Supported supplier balances outstanding |
| 2100 | Output VAT and VAT settlement accounts | Track relevant tax balances with appropriate detail |
| 2300 | Owner-loan balances | Reviewed repayable funding arrangements |
| 3000 | Equity contribution accounts | Supported equity arrangements |
| 4000 | Service revenue | Revenue recognised under the applicable accounting basis |
| 6100 | Premises costs | Approved period costs of the premises |
| 6200 | Software subscriptions | Approved software service costs |
| 6300 | Bank charges | Supported charges assessed for accounting and tax treatment |
Maintain separate bank accounts and relevant counterparties rather than merging unrelated balances into one total. VAT under review may need its own account or schedule so an unapproved amount is not silently treated as recoverable. The chart and supporting schedules should work together.
Worked example: two purchases need different entries
Consider an illustrative company buying a laptop for AED 4,200 and a monthly software service for AED 1,050, both inclusive of 5% VAT. Assume the preparer confirms the laptop meets asset-recognition criteria, the software relates wholly to the current month and all AED 250 input VAT is recoverable under the applicable conditions. Ignore all other transactions.
For the laptop, 4,200 ÷ 1.05 = AED 4,000 net cost and AED 200 VAT. The reviewed entry records AED 4,000 equipment and AED 200 input VAT against the AED 4,200 bank payment. For the software, 1,050 ÷ 1.05 = AED 1,000 current service cost and AED 50 VAT, against the AED 1,050 bank payment.
Total cash paid is AED 5,250. The accounting result is not automatically AED 5,250 of current expenses: the example records AED 4,000 equipment, AED 250 input VAT and AED 1,000 expense before any depreciation or other changes. IAS 16’s recognition principles explain why equipment assessment is distinct from recording a payment.
If VAT recovery or asset recognition fails the review, the entry needs reconsideration. Do not reuse the example’s account split as a shortcut around those conditions. The purpose of the chart is to preserve the result of the review clearly, not to decide the result in advance.
Keep accounting categories and tax decisions connected but distinct
A category such as “travel”, “meals” or “bank charges” describes a type of cost. It does not establish corporate-tax deductibility, VAT recovery or whether a document meets invoice requirements. Keep the underlying evidence and the tax review linked to the transaction.
Use the input VAT recovery guide for recovery conditions and the corporate-tax calculation guide for the accounts-to-tax reconciliation. A well-organised chart makes that reconciliation easier because the preparer can identify the transactions behind an adjustment.
Avoid creating an account named “fully deductible” that encourages an automatic answer for every posting. Where a useful tax flag is maintained, document who assigned it and the evidence reviewed. Revisit uncertain classifications when additional facts arrive.
Write a coding policy people can apply consistently
Use examples from the business’s own recurring transactions, with private details removed when preparing training material. Explain where a refundable deposit, loan principal, owner transfer, advance payment and annual subscription should be reviewed. These items commonly look like ordinary income or expense when someone works only from the bank description.
Choose an escalation route for unfamiliar transactions. A temporary suspense account can make an unresolved amount visible, but it needs an owner, explanation and resolution date. Review that account during the monthly close; repeatedly carrying the same unexplained balance is not a completed classification.
Separate account codes from optional management dimensions such as project, branch or customer. Opening a new expense account for every project can make the chart unwieldy. Use the available system and supporting schedules to capture useful detail without multiplying nearly identical categories.
Change the chart with a mapping and a test
Before merging or renaming accounts, identify the opening balances and historical transactions affected. Create an old-to-new mapping with the reason, approver and effective date. Keep the prior structure available so an earlier report can still be understood.
Test the change on a representative set of transactions. Check that bank, receivable and payable totals still reconcile, that management reports remain comparable and that no tax-review evidence was lost. The bank import checklist is useful when a migration also involves reloading transaction files.
Finally, retain the account definitions, mapping, approvals and exception decisions through the record-keeping process. Review the chart when the business adds a material activity or reporting need. A useful chart stays compact enough to apply consistently while keeping the balances and decisions that matter visible.
Source principles checked on 26 October 2026. Account codes, policy choices and purchase examples are illustrative.