How to run a month-end close checklist your team actually finishes

Run a month-end close your team actually finishes by turning it into a recurring checklist that rebuilds itself every month, where every task has one owner, a due day counted from month-end (business day 1, 2, 3), a reviewer for anything that changes the numbers, and a place to attach the backup. Everyone looks at the same live view of what is done, late or blocked and who is holding it. The month is not closed until every reconciliation has been prepared by one person and reviewed by another, and the controller or owner signs off. That structure, more than any heroic final weekend, is what turns a close that drifts into week three into one that ends on schedule.

Most small finance teams run the close from a spreadsheet template copied each month, an email thread of "did you get the statement?", and the controller's memory of what always gets forgotten. The template says what to do. It does not say who is stuck, what is late, or whether anyone checked the reconciliation that was marked done.

Why closes drag

• Tasks wait on people outside finance. Bills not approved, receipts not sent, timesheets not submitted.
• Nobody can see blockers. Status lives in people's heads until someone asks.
• "Done" is not reviewed. A reconciliation marked complete with no backup and no reviewer is a guess with a checkmark.
• The template drifts. Each month's copy picks up edits, and next month starts from a slightly different list.
• The work is repetitive. A Zapier survey of businesses with up to 250 people found repetitive tasks take an average of 17.3 hours a week, and a close is mostly recurring work.
• Status chasing eats the time. Asana's Anatomy of Work research reports that workers spend 60% of their time on "work about work," such as chasing status and searching for information.

The close task list

Every company's list is different, but most small finance teams cover these groups. Give each task a due day counted in business days after month-end.

Cut-off (business days 1 and 2)

• Final customer invoices for the month sent and recorded.
• Vendor bills received and entered, and outstanding approvals chased.
• Expense reports and card receipts submitted.
• Timesheets approved for payroll and job costing.

Cash (business days 1 to 3)

• Bank accounts reconciled.
• Credit cards reconciled.
• Merchant and payment processor deposits matched to sales.
• Loans and lines of credit balanced to statements.

Receivables and payables (business days 2 to 4)

• Receivables aging reviewed and agreed to the general ledger.
• Payables aging reviewed and agreed to the general ledger.
• Unapplied payments and credits resolved.

Payroll and people costs (business days 2 to 4)

• Payroll entries recorded and agreed to payroll reports.
• Accrued wages and benefits recorded where needed.

Adjustments (business days 3 to 5)

• Accruals for expenses incurred but not billed.
• Prepaid expenses amortized.
• Depreciation recorded.
• Inventory counted or adjusted, where it applies.
• Deferred revenue adjusted, where it applies.

Review and lock (business days 5 to 7)

• Balance sheet accounts reconciled, with backup attached.
• Results compared to budget and prior month, with large swings explained.
• Management reports prepared.
• Controller or owner review and sign-off.
• Period locked so no one posts into it by accident.

Your accountant decides which entries and reconciliations your business needs. The checklist makes sure the ones you agreed on happen every month.

What each task needs

Statuses at a glance

The rules that make it finish

1. The checklist rebuilds itself. On the first day of each month, a fresh copy of the close appears with due days set. Nobody copies a spreadsheet.
2. One owner per task. Shared tasks are unowned tasks.
3. Prepare and review are separate people. A reconciliation cannot be reviewed by the person who prepared it.
4. No backup, no review. A task cannot move to ready for review without an attachment where one is required.
5. Blockers name a person. "Waiting on bills" is not a blocker. "Waiting on Dana to approve three supplier bills" is.
6. People outside finance get their own short list. The operations manager sees only the two approvals the close needs from them, with the due day.
7. The close ends with sign-off. The controller or owner signs off only when every task is reviewed, and the sign-off is recorded.

Roles

• Preparers see and complete their own tasks, attach backup and flag blockers.
• Reviewers see items ready for review, approve them or send them back with notes.
• Controller sees the whole board, reassigns tasks, edits the template and signs off.
• Department contacts see only the requests the close needs from them.
• Owner sees progress and the final sign-off, and can act as reviewer in very small teams.

Trust in the numbers

A close checklist does not calculate your financials, and it should not. Your accounting system remains the record of every entry. The checklist tracks the work around it: who did each step, what backup supports it, and who checked it. That separation is what lets an owner trust a tool someone in the office built.

If you use AI to help with any calculation, review it like any other preparer's work. In the 2025 Stack Overflow Developer Survey, 66% of developers named "AI solutions that are almost right, but not quite" as their top frustration with AI tools. Microsoft's 2026 Work Trend Index reported that 86% of AI users treat AI output as a starting point. For the books, that is the right instinct.

Reports

• Close progress: percent of tasks reviewed, by group.
• Late and blocked tasks, with who is holding each.
• Days to close, month over month.
• Tasks that are late most often, which are your best targets for change.
• Sent-back rate by task, which shows where instructions need work.
• Sign-off history: who signed off each month and when.

Questions to settle before you build

• What is on the list, and who agreed it? Settle it with your accountant once.
• What is the target close day? Pick a realistic number and shorten it later.
• Who reviews when the team is two people? The owner or your outside accountant.
• Which tasks need backup attached? Usually every reconciliation.
• Who outside finance has a part, and what exactly do they owe the close?

Example request

Example request: "Build a month-end close checklist for our finance team of three at a 60-person distribution company. The controller maintains a template of close tasks in groups: cut-off, cash, receivables and payables, payroll, adjustments, review and lock. Each task has a name, instructions, owner, reviewer, due business day after month-end, depends-on task, whether backup is required, status, blocker note naming the person we are waiting on, attachments, prepared by and date, reviewed by and date. On the first day of every month, create a fresh copy of the close from the template with due dates set. Statuses are not started, in progress, blocked, ready for review, sent back, reviewed and late. A task cannot move to ready for review without an attachment when backup is required, and the preparer cannot review their own task. Remind owners on the due day, remind the person named in a blocker every morning, and show late tasks at the top of the controller's view. Department managers see only the close requests assigned to them. The controller signs off when every task is reviewed, and the sign-off is recorded. Show a report of days to close by month and the tasks that ran late most often. Roles are owner, controller, preparer, reviewer and department manager. Only invited people can sign in."

How to roll it out

1. Write the list once with your accountant, including owners, reviewers and due days.
2. Run next month's close in it, alongside the old spreadsheet if that helps people trust it.
3. Add department contacts after the first close, once the finance team knows the flow.
4. Hold a 20-minute review after each close: what ran late, what was blocked, what to change.
5. Edit the template, not the month. Improvements go into the template so next month starts better.
6. Retire the spreadsheet after two clean closes.

Mistakes to avoid

• A list that is too long. If a task never matters, remove it.
• Due dates instead of due days. Due days counted from month-end move automatically; fixed dates need retyping every month.
• Marking done without review. Reviewed is the status that counts.
• Blockers with no name. Name the person, or nothing happens.
• Editing this month instead of the template. The fix disappears next month.

How to measure that it works

• Business days to close, month over month.
• Tasks late at the target close day.
• Reconciliations sent back on review.
• Time the controller spends chasing status.
• Adjustments discovered after the period was locked, which should fall toward zero.

How FORGE handles it

On FORGE, your controller describes the close in plain words, like the example above, and FORGE builds it. A panel of top AI models plans the tool, a dedicated AI crew builds it, and every piece is checked for quality and security before it is saved. Most teams have their first real tool the same day, which means the next close can run in it.

Every app lives inside your company and people join only by invite. Preparers, reviewers, department managers and the controller each see what their role allows, and there is a complete record of who prepared, reviewed, sent back and signed off every item. Department managers who only answer close requests are $10 a user a month, builders are $49 a seat a month with 3 builds included, and adjusting the template later is a small fraction of a build. Our team onboards every company, starting with a workflow workshop. Talk to us or see pricing.

Questions people ask

Sources

1. Asana: why work about work is bad
2. Zapier: most dreaded tasks survey
3. Stack Overflow Developer Survey 2025: AI
4. Microsoft Work Trend Index 2026