Month-end close checklist template (free Excel)

What this month-end close checklist template does

A month-end close checklist template is a spreadsheet that lists every task needed to close the books for a month, with an owner, a deadline, a status, evidence and a reviewer sign-off. This free Excel template turns the list into a close calendar: it calculates each due date in working days, flags overdue tasks and summarises progress so the team can see what is holding the close up.

Our separate guide on the month-end close explains what each task achieves. This page is about running the close as a tracked process: how the template schedules the work, how to adapt it to your team, and how to use the numbers it produces to make next month's close faster.

What is inside the workbook

The workbook has four sheets. The checklist is the working document during the close; the summary is what the financial controller looks at in the daily close meeting.

• How to use: set-up steps, the formulas in words and good practice notes.
• Checklist: period end date, as-of date, and 32 example tasks with area, task, owner, due working day, status, completion date, evidence, reviewer and review date.
• Grey formula columns: due date, days late, an overdue flag and the sign-off status (Open, Awaiting review, Signed off or N/A).
• Summary: task counts by status, percent complete, overdue tasks, tasks awaiting review, total days late and an overall close status.
• Progress by area: tasks, finished tasks, overdue tasks and percent complete for each area, with a check that the areas add back to the task list.
• Holidays: public holidays that the due-date formula skips.
• Room for 100 tasks and 16 areas, with filters and frozen headings for long lists.

Deadlines in working days

Closing teams talk in working days, because weekends and holidays move calendar dates every month. The template follows that convention. WD 1 is the first working day after the period end, WD 5 is the fifth, and negative numbers are pre-close tasks: WD -1 is the last working day before the period end.

Each due date is calculated with WORKDAY(period end, working day, holidays). In the example the period ends on Monday 31 August 2026, so WD -3 falls on Wednesday 26 August, WD 1 on Tuesday 1 September and WD 7 on Wednesday 9 September. If you add 1 September to the holiday list, every deadline from WD 1 onwards moves one working day later, and a test in the template's test run confirms WD 1 then becomes 2 September.

Scheduling in working days also makes the close comparable month to month. A close that finishes on WD 6 in both a 30-day and a 31-day month is a stable process; one that finishes on WD 6 in one month and WD 10 in the next needs attention.

How to set it up for your team

Setting up the checklist is a one-off job of about an hour. After that, each month is a copy of the file with a new period end date.

• Enter the period end date and the as-of date; replace the as-of date with =TODAY() if you want the overdue flags to update on their own.
• List your public holidays on the Holidays sheet.
• Delete example tasks that do not apply and add your own, one line per task, each starting with a verb.
• Give every task a single named owner; a team name is allowed only when a team lead is accountable.
• Set the due working day so that inputs come before the work that depends on them.
• Name a reviewer for every task that changes the ledger or the financial statements.
• Save the file as close-YYYY-MM.xlsx for each month so the history is kept.

How the example close is sequenced

The 32 example tasks follow the order in which information becomes reliable. Pre-close tasks send cut-off reminders and confirm that the accounting periods are set up. On WD 1 and WD 2 the team posts the last receipts, payments, sales invoices, supplier invoices and payroll, then reconciles the bank, the receivables ledger and the payroll control accounts.

WD 3 and WD 4 are for judgement, accruals and the remaining reconciliations: expected credit losses, unbilled revenue and deferred income, goods received not invoiced, the payables reconciliation, depreciation, prepayments, inventory valuation, VAT, intercompany balances and clearing suspense accounts. WD 5 reviews manual journals, completes balance sheet reconciliations and reviews the trial balance. WD 6 produces the management accounts and the updated cash forecast and locks the period, and WD 7 is the finance director's sign-off.

The order matters more than the exact day. Reconciling the payables ledger before all supplier invoices are posted, or producing management accounts before the accruals, creates rework that is the most common reason a close runs late.

The worked example: the close as of 4 September

The example shows the August 2026 close on Friday 4 September, WD 4. Of 32 tasks, 17 are Done, 1 is N/A because there is no bonus scheme this quarter, 3 are In progress, 1 is Blocked and 10 are Not started, so the close is 56 percent complete (18 of 32).

Two tasks are overdue because their deadline, WD 3 on 3 September, has passed: the expected credit loss review is still in progress and the stock valuation reconciliation is blocked, waiting for count results from one warehouse. Two finished tasks were each one day late. Six tasks are signed off and 11 are done but still awaiting review. Because at least one task is overdue, the summary status reads BEHIND SCHEDULE.

When every task is marked Done or N/A and every Done task has a reviewer and a review date, the status changes to CLOSE COMPLETE. The template's tests check both states with two independent formula engines.

Evidence and sign-off

A tick in a status column proves nothing on its own. The evidence column should point to something an auditor or a new team member could find without asking: a file name, a report name with its run date, a journal number, or a reconciliation reference. 'Done' is not evidence; 'BR-2026-08.xlsx' is.

Reviewer sign-off is the control. The reviewer checks that the evidence supports the task and that anything unusual has been explained, then records their name and the date. The template marks a task Signed off only when both are present, and counts Done tasks still awaiting review, because a close with many unreviewed tasks is not finished even when every status says Done.

Measuring and shortening the close

The days-late column is the most useful number the template produces over time. Save each month's file and compare: tasks that slip every month point to a process problem, such as an input that always arrives late, an owner with too many tasks on the same day, or a reconciliation that needs a better report.

Useful measures are the working day on which the period was locked, the number of overdue tasks on each day of the close, the number of post-close adjustments, and the number of tasks awaiting review at the end. Most teams shorten the close by moving work earlier, for example running reconciliations weekly, agreeing intercompany balances before the period end and accruing recurring costs from a standing schedule, rather than by working faster in the first week of the month.

Common mistakes with close checklists

Checklists fail quietly: the file exists, everyone updates their status, and the close still takes too long or misses errors. These are the usual reasons.

• Tasks that are too vague to be finished, such as 'review balance sheet' instead of named reconciliations.
• Shared ownership, where two people each assume the other has done the task.
• No evidence column, so a review is only a conversation.
• Deadlines in calendar dates that fall on weekends and holidays.
• Tasks marked Done before the reviewer has seen them, and never reviewed afterwards.
• Not locking the period at the end, so late postings change reported numbers.
• Keeping one file for every month, overwriting the history an auditor will want to see.

Adapting it for quarter-end and year-end

Quarter-end and year-end closes use the same checklist with extra tasks, so keep one master list and switch tasks on or off with the N/A status rather than maintaining three different files. Typical quarter-end additions are the VAT or GST/HST return where it is filed quarterly, a review of provisions and contingent liabilities under IAS 37, an impairment indicators review, and a fuller variance commentary for the board.

Year-end adds the physical inventory count and its reconciliation, confirmation of useful lives and residual values under IAS 16, current and deferred tax calculations, going concern and subsequent events reviews, the year-end closing entries, and preparing the lead schedules and supporting files your auditor will request. Give these tasks realistic deadlines: a year-end close normally takes longer than a monthly one, and pretending otherwise only produces a column of overdue flags.

If your group has several companies, give each company its own copy of the checklist and add group tasks, such as intercompany matching and consolidation, to the parent's list with deadlines after the subsidiaries finish.

Doing this in Skyline Nexus ERP

Skyline Nexus ERP enforces the parts of the close that a spreadsheet can only record. In Fiscal Authority, Fiscal Periods holds each fiscal year and its monthly or quarterly periods. Close Period sets a period to Soft Close, Lock Period locks it, and posting into a soft-closed or locked period is refused for both manual journals and documents that post automatically; a soft-closed period can be reopened, a locked one cannot, and status changes are recorded in the audit log. At year end, Close Fiscal Year is refused while any journal or voucher in the year is not posted or cancelled, and closing entries to retained earnings are posted as part of the close.

Several checklist tasks map to screens: Treasury Bank Reconciliation for the bank task, the AR Aging Report and AP Aging Report for receivables and payables, Data Verification to compare the trial balance with GL and POS transactions, and the Trial Balance in Opening / Movement / Closing view for the final review. The Audit Pack (Excel) exports the chart of accounts, trial balance, statements, journals and ledgers for a calendar year in one workbook for the audit file.