A practical month-end close checklist for UK finance teams.

A month-end close checklist should show what must happen, who owns it, which evidence proves completion and who reviews the result. The useful unit is not a vague task such as ‘reconcile cash’. It is a controlled step with a due date, source, preparer, reviewer and documented exception route.

UK companies must keep accounting records that are sufficient to show and explain their transactions and financial position. See Companies Act 2006, section 386. The checklist below is Clerq's operational synthesis, not a statutory close timetable.

What should a month-end close checklist include?

The checklist should reflect the business's actual close, not a generic accounting calendar. Start with the reporting deadline and work backwards through dependencies. Separate the preparation of evidence from the review of accounting conclusions.

For each line, record the task, frequency, due date, prerequisite, system of record, preparer, reviewer, evidence link, status and exception. This makes ownership visible and gives a future automation a precise contract to follow.

• Close calendar and material reporting deadlines
• Source-system cut-offs and data-completeness checks
• Bank, payment, receivables, payables and balance-sheet reconciliations
• Accrual, prepayment and other approved adjustment processes
• Management review, open-item log and final sign-off

The eight-step close sequence

A simple sequence keeps parallel work coordinated without pretending every task is identical. Adjust the detail to the systems, controls and reporting requirements your finance owner has approved.

• Confirm the close calendar, scope, owners and review deadlines.
• Check that expected source data is complete for the period.
• Collect the approved reports and supporting evidence.
• Prepare recurring reconciliations using consistent rules.
• Route missing, unusual or unreconciled items to an owner.
• Record and approve adjustments under the business's accounting policy.
• Compile the management pack with an open-item summary.
• Obtain final review and retain the evidence and approval trail.

What can be automated safely?

Good candidates are repetitive preparation steps with stable inputs and explicit rules: creating tasks, collecting files, checking whether expected reports arrived, comparing approved fields, ageing open items and assembling a review pack.

Accounting treatment, materiality judgements, unusual transactions and final sign-off should remain with authorised finance people. If the rule cannot be explained, tested and owned, it is not ready to run unattended.

Common close failures to fix first

Late closes are often blamed on workload when the underlying problem is unclear ownership or incomplete inputs. Automating reminders will not repair a disputed data source or an undefined review threshold.

• Tasks are marked complete without linked evidence.
• The same reconciliation is rebuilt differently each month.
• Exceptions remain in email threads rather than one owned queue.
• Review starts only after all preparation is complete, creating a late bottleneck.
• The checklist records activity but not whether the reporting output is reliable.

How to measure improvement

Track close duration, tasks completed on time, first-pass reconciliation success, open exceptions at sign-off and reviewer rework. Define each measure before changing the process so the baseline and post-change result are comparable.

A faster close is useful only if review quality and control evidence remain intact. Pair speed measures with completeness, exception and approval measures.

Frequently asked questions