Month-End Checklist

A finance team wants management accounts seven working days after month end, so it needs transactions posted, balances reconciled and unusual results reviewed in a sensible order. The checklist starts before the last day of the month, when teams can gather supplier statements, confirm payroll data and chase missing invoices, because waiting until day one to discover missing information slows the whole close.

QuickBooks describes month-end closing as reviewing and finalising financial records for a period, and Oracle's NetSuite documentation shows that close tasks can have dependencies. These references illustrate a process, not one mandatory checklist for every accounting framework.

Map recurring tasks to the actual books and systems: bank and card accounts, accounts receivable, accounts payable, payroll, inventory, fixed assets and loans may all require checks. Name the preparer and reviewer for each material task, because a label such as "finance" can hide whether the work is assigned, and use independent review where risk is high and staffing allows.

Add a due date, a dependency and evidence of completion: a cash reconciliation needs bank data and should link to the bank statement, ledger balance and explanation of reconciling items, while consolidated accounts may need subsidiary packs and intercompany matching, so one late upstream task can hold several downstream tasks. Accruals and prepayments need judgement about period, so record expenses incurred but not yet invoiced where required, allocate prepaid costs to the right months and keep reversal or release instructions so an adjustment does not remain on the books indefinitely.

Fixed-asset steps may include additions, disposals and depreciation under the entity's policy, and inventory teams may check cutoffs and adjustments, but do not copy an item into a company that has no relevant asset merely to make the document look complete. Review unusual movements after routine postings by comparing actual results with budget, prior month and business activity, since a large margin change could be real or could point to a missing invoice or misclassified expense.

Use an exception log for unresolved items, noting the amount, owner, planned fix and effect on reporting; a close can sometimes proceed with a documented immaterial exception, but the decision should follow policy and materiality judgement. Locking a period can prevent accidental edits after sign-off, so confirm required postings, reviews and approvals first, and route corrections after closure through a controlled process that records who authorised them.

Define when the close is complete, because posting all transactions is different from approving management accounts, and if reports are issued on the sixth working day, describe the cycle as six working days under the chosen convention rather than mixing calendar days and working days. A simple cycle-time metric is the number of working days from period end to approved report issue, tracked alongside error rates and late adjustments, because faster is not better if the team skips reconciliations to hit a target.

Connect the checklist to a reporting calendar and label versions, since management may need a draft for operational discussion while lenders require a final pack later. Automated tasks still need monitoring because a bank feed can fail, a recurring journal can post to the wrong account and an integration can duplicate invoices, so assign someone to confirm exceptions, not just system completion.

Review the checklist after each close, change the upstream process or deadline if the same issue delays every month, remove steps that no longer matter and add controls for new accounts, entities or business lines; for owners, the goal is numbers they can trust soon enough to act, so ask what remains unresolved, who reviewed the balances and when the final pack was approved.