A monthly bank reconciliation checklist for UAE small businesses
Reconcile a UAE small business bank account with a worked example, an exception log and a monthly review checklist that keeps tax questions separate.
A bank reconciliation explains why the balance on a bank statement differs from the balance for that account in your books. Its useful output is a supported balance, a record of corrections and a list of genuine timing differences. Two matching totals are insufficient if a missing customer receipt and a missing supplier payment happen to cancel each other out.
For a UAE small business, a monthly reconciliation is a practical control: it catches incomplete imports, duplicated entries and transactions placed in the wrong account before they feed management reports and tax work. The monthly schedule below is an operating recommendation, not a statutory filing deadline. Use a shorter interval when transaction volume or the risk of errors makes it worthwhile.
Start with one account, one currency and a complete period
Collect the bank’s complete statement, the corresponding ledger transactions and the previous signed-off reconciliation. Confirm that the company, account, currency and start and end dates match. A statement for an AED account cannot be reconciled directly against a combined total that also includes a USD account.
Check the opening balance against the prior month’s closing balance. If the opening numbers disagree, investigate that difference before reviewing the current month’s transactions. Otherwise, the same old error can be disguised as a new unexplained adjustment every month.
Keep the bank’s original file unchanged. If you create a working CSV, retain both versions and document any transformation, such as standardising date formats. Use the bank import checklist to check completeness before trying to reconcile a dataset. Missing statement pages and an overlapping export are data problems that categorisation cannot repair.
Match by evidence rather than amount alone
Compare the date, amount, direction, bank reference and counterparty for each entry. A payment made near month-end may appear in the books before it clears the bank; that can be a legitimate timing item. A payment that never appears in a later statement needs investigation rather than indefinite rollover.
Do not assume that two AED 1,000 payments on the same day are duplicates. They may settle separate invoices. Conversely, one transaction imported twice can carry slightly different descriptions in two bank exports. Match to the original bank reference and the underlying invoice or payment instruction where possible.
Customer receipts also need a destination in the books. A bank deposit proves cash arrived, but it does not identify which receivable was settled or whether the money was an owner contribution, loan, refund or customer advance. Record the accounting explanation before treating every incoming transfer as sales revenue.
Worked example: corrections that belong in the ledger
Consider an illustrative business whose September bank statement closes at AED 98,500, while its ledger bank account shows AED 100,000. The difference is AED 1,500. Reviewing the statement reveals two debits missing from the ledger: a supported bank charge of AED 500 and a supplier direct debit of AED 1,000.
The supplier payment is checked against the payment instruction and the outstanding supplier balance. The bank charge is checked against the bank’s fee evidence. Once the appropriate accounting entries are posted, the working paper reads:
| Reconciliation step | AED |
|---|---|
| Ledger balance before corrections | 100,000 |
| Record bank charge omitted from ledger | −500 |
| Record supplier payment omitted from ledger | −1,000 |
| Corrected ledger balance | 98,500 |
| Statement closing balance | 98,500 |
| Remaining difference | 0 |
The entries explain identifiable transactions. A single AED 1,500 posting labelled “reconciliation adjustment” would produce the same closing balance without explaining the expense, supplier settlement or evidence. It could also leave a supplier invoice incorrectly outstanding.
Check whether either item was already recorded elsewhere before posting. Correcting an account allocation is different from adding a second copy of a transaction. Keep the correction reference in the reconciliation so a reviewer can trace the movement into the ledger.
Worked example: timing items that should not be posted twice
In a separate illustrative month, the statement closes at AED 98,500 and the ledger closes at AED 97,000. The books already include a customer deposit of AED 1,000 that has not reached the statement and an issued supplier payment of AED 2,500 that has not yet cleared.
The adjusted bank position is 98,500 + 1,000 − 2,500 = AED 97,000. The amounts agree after accounting for the two documented timing items. The bookkeeper should not post them again merely to force the unadjusted bank statement to equal the ledger.
Record the evidence supporting each timing item and check it against the next statement. If the customer deposit fails to appear, find out whether it was rejected, reversed or incorrectly recorded. If the supplier payment remains outstanding, confirm whether it was actually released and whether the creditor balance is correct. Ageing unresolved items is more useful than repeatedly copying the same explanation forward.
Keep a small exception log with an owner
For every unresolved difference, capture the bank or ledger reference, amount, suspected cause, evidence needed, responsible person and next review date. Use a concrete action such as “obtain supplier payment confirmation” rather than “investigate later”. Keep the status open until the evidence or correction resolves the question.
Separate missing ledger entries, duplicate imports, wrong-account postings and timing items. These categories need different actions. A missing entry may require a supported posting; a duplicate requires checking how to correct the extra record; a timing item requires follow-up. Treating them all as “bank differences” makes the review harder to complete.
In TaxAI, use the transaction review workflow to inspect imported records, categories and tax-treatment questions. The reconciliation described here is a review process supported by your statement and working paper; retain the decisions and evidence alongside the books.
A reconciled bank account still needs a tax review
A matched bank payment does not establish that an expense is deductible for corporate tax or that its VAT can be recovered. Keep the invoice, contract and business-purpose explanation needed for that separate assessment. For a loan repayment, distinguish principal from any interest or charges; the total cash payment does not tell you the expense amount.
Likewise, a transfer between two accounts of the same business should be checked on both sides rather than counted as revenue in one account and an operating expense in the other. Reconcile each account individually, then confirm that the transfer pairing is consistent across the books.
Before closing, save the original statement, reconciliation, correction references, exception log and reviewer sign-off. Confirm that the next month’s opening balance agrees with the signed-off closing position. Follow the corporate-tax archive guidance for the supporting records; the FTA’s retention guidance explains why records need to remain available beyond the month in which they were created.
Reviewed on 26 October 2026. Both reconciliations are illustrative bookkeeping examples; tax treatment requires its own evidence and review.