Month-end close checklist: the 30-step routine for clean books

You are downloading month-end-close-checklist-uae.pdf (4 KB): a 30-step PDF across 7 phases for the monthly close. The phases are Cut-off (5 steps), Reconciliations (6), Review (5), Reporting (4), Tax (4), Payroll (3), and Sign-off (3). Each step has an owner, a working-day deadline and a sign-off box — the checklist prints, the close is worked on paper or screen, and the completed checklist files as the month's close evidence.

The close is the monthly transformation: a month of transactions becomes reviewed, reported numbers. Without it, the books are a pile of postings — possibly right, unproven. With it, each month ends with a known position: profit true (cut-off performed), cash proven (reconciled), balances sensible (reviewed), reported (management accounts issued), tax current (returns prepared), payroll complete, and the whole thing signed off. Thirty steps sounds like a lot; a practiced close runs them in a week — and each step exists because its absence has caused a known failure.

The working-day calendar is the checklist's backbone: WD1–2 transactions complete and cut-off performed; WD3–4 reconciliations (bank, receivables, payables, intercompany); WD5–6 review (trial balance, variances, suspense cleared); WD7–8 reporting (management accounts issued); tax and payroll running in parallel streams; sign-off closing the month. Owners per step, deadlines per phase, the checklist initialled as each completes. A close without a calendar drifts; a close with one lands.

At month end, work the checklist in phase order — each phase's steps before the next phase begins. Cut-off (WD1–2): all transactions posted, accruals and prepayments reviewed and posted, depreciation posted, cut-off scan (GRNs, payments, contracts) complete, suspense cleared. Reconciliations (WD3–4): bank reconciled per account, receivables agreed to aged list, payables agreed to aged list, intercompany agreed, petty cash counted, inventory movements recorded. Review (WD5–6): trial balance extracted and reviewed (natures, variances, stagnation), control accounts agreed, management review of unusual items, prior-month actions confirmed cleared. Reporting (WD7–8): P&L issued with variance commentary, balance sheet issued, cash position reported, KPI pack issued. Tax and payroll in parallel: VAT position computed, WPS cleared, gratuity updated. Sign-off: preparer signs, reviewer signs, the packet files.

Synthetic example — not real business data. Desert Rose Trading LLC (fictional) closes October 2026: WD1 Layla Haddad (fictional bookkeeper) posts final invoices and runs the cut-off scan — finds a 12,000 supplier invoice uninvoiced, accrues it (JE-2026-0148). WD2 accruals/prepayments/depreciation posted. WD3 bank reconciled (the 177,480 proof), receivables agreed (80,000 = aged list). WD4 payables agreed, petty cash counted (360 + vouchers = 2,000 float). WD5 trial balance extracted: totals 1,842,350 = 1,842,350; variances reviewed — utilities +300% explained (accrual true-up). WD6 reviewer (Omar Q., fictional) challenges two items, both explained. WD7 management accounts issued: October profit 84,200, variance commentary attached. WD8 VAT position computed (output 15,230, input 9,410). Sign-off: both sign, the packet files — October known, November begins clean.

Carry-forward discipline: each month's open actions (the two challenged items, the uninvoiced accrual's true-up) become next month's WD1 checks. The close is a loop, not an event — each month's end is next month's clean start.

Cut-off first, because everything else reads from complete transactions. All sales and purchase invoices posted (the day books complete to month end), cash posted, journals posted — the "transactions complete" step is the gate: nothing unposted lurks. Then the cut-off scan: GRN file for uninvoiced receipts (accrue), payment file for advance payments (prepay), contract file for periodic fees, the recurring-entry schedule for the month's standards. Accruals and prepayments reviewed per the schedule — estimates trued-up, releases posted. Depreciation posted per the schedule. Suspense cleared — zero balances in unclassified accounts before the close proceeds.

Reconciliations second: the independent proofs. Bank per account (the 15-column template's routine). Receivables: ledger agreed to the aged list, unallocated receipts investigated, old balances challenged. Payables: ledger to aged list, debit balances investigated, statement agreements for major suppliers. Intercompany: counterpart agreed (both sides, same amount — the classic group failure is one-sided balances). Petty cash counted to the float. Inventory: movements recorded, count scheduled per the policy. Each reconciliation signed, dated, filed — the month's proofs, complete.

The phase discipline: no phase 3 until phases 1–2 are signed. The temptation is to start reviewing while reconciliations are still open — reviewing moving numbers. The checklist's sequencing prevents it: cut-off signed, reconciliations signed, then review. A close that overlaps its phases is a close that reworks them.

Review is where the close becomes a control: the trial balance extracted (post-all-routines), reviewed for natures (wrong-column balances questioned), variances (every significant movement explained in notes), and stagnation (unmoving balances challenged). Control accounts agreed to their sub-ledgers — the agreements evidenced, not assumed. The reviewer's challenge: the unusual items explained, the prior month's actions confirmed cleared, the judgment areas (accrual estimates, provisions) assessed. Review evidenced by signature — the review that is not signed did not happen.

Reporting follows the reviewed TB: the P&L (by reporting group, with variance commentary against budget and prior month), the balance sheet (summarised, with the cash proven and the working capital narrated), the cash position (reconciled balances, forecast updated), and the KPI pack (the handful of metrics the business manages — gross margin, debtor days, cash runway). Reporting is presentation of reviewed numbers — never the discovery of them. The variance commentary is the value: numbers explained, actions identified.

The gate holds throughout: no reviewed trial balance, no management accounts. The business never presents unreviewed numbers — to itself, to the bank, to anyone. The discipline feels slow in month one; by month six it is the rhythm the business thinks in. Monthly profit known by WD8, with commentary: that is the product of phases 3–4.

Tax runs as a parallel stream: the VAT position computed from the reviewed books (output from the sales day book, input from the purchase day book, the return prepared — filed per the tax period calendar, monthly or quarterly), the payable or refund recognised, the payment scheduled. Corporate tax: the year-to-date position tracked (profit to date against the 375,000 threshold awareness, Small Business Relief eligibility monitored), instalment or provisioning considerations noted. The tax stream's rule: computed from the closed books, never from estimates — the close's earlier phases are the tax computation's foundation.

Payroll runs alongside: the month's payroll entry posted (the 14-column template's routine), WPS batch cleared to nil, gratuity provision updated, the payroll packet filed. Leavers processed, joiners added, advances recovered. The payroll stream closes with the same sign-off: computed, paid, reconciled, filed.

The parallel-stream design matters: tax and payroll do not wait for reporting — they run on the reviewed trial balance alongside it. Dependencies are explicit: the VAT computation needs the reviewed revenue and purchase figures (phase 3 done); the payroll needs nothing but its own register. The checklist shows the streams side by side so nothing waits unnecessarily and nothing starts prematurely. A close where tax is "done later" is a close with a hole in it.

Sign-off closes the month: the preparer signs (every step initialled, the evidence filed), the reviewer signs (the challenge performed, the explanations accepted), and the packet files — the checklist, the reconciliations, the reviewed TB, the management accounts, the tax computation, the payroll packet. The filed packet is the month's audit evidence: a future reviewer — auditor, new accountant, the owner in a dispute — can reconstruct October from the file.

The loop: open actions carried forward explicitly — the challenged items pending true-up, the accrual awaiting its invoice, the disputed payable — each becomes next month's WD1 check, named and dated. Nothing open is forgotten; the carry-forward list is the first page of next month's checklist. And the post-close review: what slipped, what was late, what can improve — the close itself reviewed quarterly, the calendar tuned, the owners confirmed.

Twelve signed packets are the year's backbone: the audit's analytical procedures walk them, the tax filings reference them, the management story is told in them. A business with twelve closed months knows its year; one with a single year-end close discovers it — usually expensively. The checklist is the routine; the loop is the discipline; the year of clean months is the result.

A checklist without a calendar is a wish list. The close calendar turns the checklist into a schedule: every task assigned an owner and a due date measured in working days from month end, with dependencies mapped so nothing waits on something nobody knew was late. Publish it before the month starts, not during the close — the calendar is a planning document, and planning it mid-close is just firefighting with better stationery.

The shape is standard and worth adopting whole: Day 1, cut-off — AP/AR subledgers closed to new postings, bank statements pulled, cash counted. Days 2–3, reconciliations — bank, receivables, payables, intercompany, each owned by name. Days 3–4, journals — accruals, prepayments, depreciation, provisions, each posted and reviewed. Day 5, review and reporting — trial balance reviewed, variances explained, management accounts drafted. The tax and payroll streams run in parallel with their own owners, converging at the review. Your business will adjust the days; the sequence — cut-off, then reconcile, then journal, then review — does not change.

Two disciplines make the calendar work. First, dependencies are explicit: accruals cannot be finalised until AP cut-off is confirmed; the VAT computation cannot start until AR/AP are reconciled; nothing is "reviewed" before it is posted. The checklist's dependency column exists so a late task's blast radius is visible immediately. Second, status is tracked daily during close week — a fifteen-minute standup, each owner reporting done, blocked, or at risk. The calendar plus the standup is what compresses a three-week drift into a five-day close. Archive each month's completed calendar with the close file; next month's planning starts from what actually happened, not from what was supposed to.

Thirty steps in seven phases: the close sequenced. Middle column: the steps. Right column: timing and ownership.

The meta-mistake is the annual close: eleven months unclosed, the year-end becoming archaeology — errors compounded, cut-off guessed, the audit expensive. Close monthly; the routine is cheaper than the rescue. Second, the calendar-free close: no working-day deadlines, so the close drifts — "we'll close when we can" means never. The WD1–8 calendar is the discipline.

Third, the overlapping phases: reviewing while reconciliations are still open — reviewing moving numbers, then reworking. Phase order is the rule: cut-off signed, reconciliations signed, then review. Fourth, the unsigned review: the challenge performed but not evidenced — the review that is not signed did not happen. Sign it. Fifth, the gate breached: management accounts issued from an unreviewed TB — presenting unreviewed numbers, to the business itself. The gate holds every month.

Sixth, the tax afterthought: VAT computed from estimates "to be trued later" — computed from the closed books, always. Seventh, the uncarried actions: open items forgotten between months — the carry-forward list is next month's page one. Eighth, the packet unfiled: the close performed but the evidence scattered — twelve filed packets are the year's backbone; twelve performed-but-unfiled closes are hearsay.

This checklist runs the close; it does not do the underlying work (the journals, reconciliations, schedules and reviews are the bookkeeping operation — this library's templates structure each), set the accounting policies (accrual thresholds, depreciation lives, provision methods — the policy manual), or prepare the tax filings (the VAT return and CT computation are built from the closed books, not from the checklist).

The file also does not manage the close's people (capacity planning, cover for absence, training — the finance function's management), handle the audit (the packets are the audit's evidence; the audit itself is the auditor's), or fix a broken close (months of unclosed books need the catch-up project before the routine can start — our messy-books cleanup scopes it). It does not replace the finance system's close module at scale — the checklist's logic transfers, the tooling upgrades.

When the close needs running properly — the calendar kept, the phases sequenced, the review real, twelve clean months a year — TaxAdvisors' accounting team runs the full month-end: the checklist as this PDF structures it, the packet filed, the numbers known by WD8. The PDF is the routine; the close is the operation.

Compliance basis: commercial practice for month-end close; supports financial reporting under IFRS and tax filings under the VAT and Corporate Tax laws. Seven-year retention for close packets (Article 56 of the Corporate Tax Law).

Caveat: the close calendar is the business's policy — set working-day deadlines and enforce them; the reviewer must be independent of the preparer. As of October 2026 — rules change; re-check before relying.