Month-end close has a reputation for being stressful, and the reason is usually not the accounting. It is the coordination: ten people, five systems and a deadline, with nobody sure which task comes before which. When the close runs from memory, steps get skipped, numbers move after they were reviewed and the same questions come up every month.
A checklist fixes that. It turns the close into a calendar with owners, so everyone knows what is due, who does it and what "done" looks like. This guide gives you a template you can copy, explains the reasoning behind each phase, and shows where automation helps and where it should not be trusted.
A note before you start: accounting methods, reporting obligations and tax rules differ by company, state and country. Treat this guide as an operating template, not accounting or tax advice, and have your accountant confirm that the steps fit your situation.
What the close is actually for
The close has three jobs:
- Make the numbers complete. Every transaction that belongs in the month is recorded in that month.
- Make the numbers correct. Balances agree with outside evidence such as bank statements and supplier statements.
- Make the numbers final. After review, the period is locked so figures cannot change without a visible, approved reason.
Every step on a good checklist serves one of those three jobs. If you cannot say which, the step may not belong.
The close calendar: a day-by-day template
Business days are counted from the first working day after month-end, written as BD1, BD2 and so on. The timings below are an illustrative starting point for a small team. Yours will differ, so adjust them to your own volume and systems.
| Day | Phase | What happens |
|---|---|---|
| Last day of month | Cut-off | Stop new entries for the period where practical. Send reminders to teams that submit expenses, timesheets or invoices |
| BD1 | Collect | Import bank and card transactions. Confirm all invoices received are entered. Confirm payroll is posted |
| BD2 | Subledgers | Review accounts payable and accounts receivable. Post missing invoices and credit notes. Check unapplied payments |
| BD3 | Reconcile | Reconcile bank, card and payment-processor accounts. Investigate and clear differences |
| BD3 to BD4 | Adjust | Record accruals, prepaid expense release, depreciation and any recurring journals |
| BD4 | Review balances | Reconcile or review balance sheet accounts such as loans, deferred revenue and inventory if you hold them |
| BD5 | Analyze | Compare the income statement with the prior month and with budget. Investigate large changes |
| BD5 | Approve | Controller or finance lead reviews and signs off. Post final adjustments |
| BD6 | Lock and report | Lock the period in the accounting system. Publish the monthly report |
If your close takes longer than this, do not copy the calendar. Instead, record how long each phase takes for two or three months and shorten the slowest one first.
The checklist (copy and adapt)
Each task has an owner and a proof column. "Proof" is what a reviewer or auditor could look at to see that the task was done: a reconciliation report, a signed approval or a link to a file.
Phase 1: Cut-off and collection
| Task | Owner | Proof |
|---|---|---|
| Send the close calendar and cut-off reminder to all teams that submit expenses, bills or time | Finance lead | Sent message |
| Import bank, card and payment-processor transactions | Accountant | Import log |
| Confirm all supplier invoices received this month are entered | AP clerk | AP report by date |
| Confirm payroll journal is posted and agrees to the payroll report | Accountant | Payroll report match |
| Confirm customer invoices for the month are issued | AR clerk | Invoice register |
Phase 2: Subledgers
| Task | Owner | Proof |
|---|---|---|
| Review AP aging and check for duplicate or unusual invoices | AP clerk | Reviewed aging report |
| Review AR aging and follow up on overdue balances | AR clerk | Reviewed aging report |
| Apply unapplied customer payments and supplier credits | AR and AP clerks | Zero or explained unapplied balance |
| Confirm subledger totals equal the general ledger control accounts | Accountant | Tie-out schedule |
Phase 3: Reconciliations
| Task | Owner | Proof |
|---|---|---|
| Reconcile each bank account to the statement | Accountant | Signed reconciliation |
| Reconcile credit cards and payment processors | Accountant | Signed reconciliation |
| Clear or explain reconciling items older than one month | Accountant | Notes on each item |
| Review the reconciliations prepared by another person | Controller | Reviewer sign-off and date |
Phase 4: Adjustments
| Task | Owner | Proof |
|---|---|---|
| Record accruals for goods or services received but not yet billed | Accountant | Accrual schedule |
| Release prepaid expenses for the month | Accountant | Prepaid schedule |
| Record depreciation and amortization | Accountant | Fixed asset schedule |
| Post recurring journals and check they ran | Accountant | Journal list |
| Review manual journal entries and attach support | Controller | Approved journal with attachment |
Phase 5: Review and lock
| Task | Owner | Proof |
|---|---|---|
| Compare the income statement with last month and budget; explain large changes | Controller | Variance notes |
| Check that balance sheet accounts make sense (no unexpected negatives or old balances) | Controller | Review note |
| Approve the close | Finance lead | Signed checklist |
| Lock the period in the accounting system | Controller | System lock confirmation |
| Publish the monthly report and file the close checklist | Finance lead | Link to report |
Copy these tables into your document tool as they are. Save the completed checklist for each month. It is your evidence that the close was done and reviewed.
Free tool
RACI matrix generatorGive every close task one clear owner. Build a RACI matrix and copy it into your close document.
Four rules that make a close reliable
1. One owner per task. Shared ownership means nobody checks. Name a person for each line, and a backup for when they are away.
2. Separate preparing from approving. Where your team size allows, the person who prepares a reconciliation or journal should not be the only person who approves it. In a very small team, a periodic review by the owner or an outside accountant provides a similar check. COSO, the organization behind a widely used internal control framework, describes internal controls as supporting reliable information and objectives beyond compliance alone. The framework page on coso.org is a good starting reference if you want the formal background.
3. Keep evidence, not just results. A reconciliation with no date, preparer or reviewer is a number, not proof. Save the report that shows the match.
4. Lock the period. Once the close is approved, lock it. If a correction is needed later, make it a visible, approved adjustment in the next period or through a documented reopening process, rather than editing history quietly.
A worked example (illustrative)
Imagine a 25-person company with one finance manager and a part-time bookkeeper. Before the checklist, the close ran from the manager's memory. Each month, a few invoices arrived after the books were reviewed, the bank reconciliation was done last and the report went out when it was ready.
After adopting the calendar:
- On the last day of the month, the manager sends a short reminder with the cut-off for expense reports.
- On BD1 and BD2 the bookkeeper imports transactions and enters invoices. The manager spends ten minutes looking at the list of missing items.
- On BD3 the bookkeeper reconciles the bank and card accounts. The manager reviews and signs them on BD4.
- On BD5 the manager compares the results with the prior month, writes notes on the three largest changes and approves the close.
- The period is locked on BD6, and the report goes out the same day.
None of this required new software. The improvement came from a shared calendar, named owners and evidence kept in one folder. The numbers in this example are illustrative, and your own calendar may be longer or shorter.
Where automation helps (and where it should not)
Automation is useful when a step is repeated every month, follows clear rules and can be checked.
| Good candidates | Why |
|---|---|
| Reminders and the close calendar | Pure coordination, no judgment |
| Bank and card feeds | Removes manual entry and typing errors |
| Matching payments to invoices | Rule-based, easy to review exceptions |
| Recurring journals | Same entry every month, schedule and check |
| Pulling data into a report template | Saves hours of copying |
| Reading invoices into your system | Works well with a review step, see AI invoice processing |
Be cautious with automation for anything that needs judgment: unusual accruals, one-off adjustments and explanations of large changes. Keep a person in charge of approving those. If you are unsure where to start, the automation readiness scorecard helps you check whether a process is stable enough, and what to automate first explains how to prioritize.
How to speed up the close without cutting corners
- Find the slowest step. Track how long each phase takes for three months. Most closes have one bottleneck, often late invoices or reconciliations left to the end.
- Do work earlier. Reconcile weekly, not monthly. Review the aging reports mid-month. A shorter close is often just less left to do at the end.
- Fix the source of late items. If expense reports arrive late, move the deadline, not the close. If invoices arrive by email in a pile, give suppliers a single address and a clear approval workflow. See invoice approval thresholds and controls.
- Reduce exceptions. Many delays come from mismatches. Three-way match exceptions lists the usual causes.
- Write it down. A documented procedure lets someone else cover when you are away. See how to write an SOP people follow.
Common mistakes
- No cut-off. Without a clear cut-off date, transactions keep arriving and numbers keep changing after review.
- Reconciling last. If reconciliations are the final step, problems found there cause rework. Do them early.
- Preparer and approver are the same person. Errors and fraud are harder to catch.
- No evidence. The task was done but nobody can show it.
- Unlimited late entries. Without a lock, the period never really closes.
- A checklist nobody updates. Review it every quarter and after any change in systems or staffing.
- Starting with software. A new tool cannot fix an unclear process. Fix the process first.
How long to keep close records
Retention rules depend on the type of record and the rules that apply to your business. For US federal tax purposes, the IRS explains that you should keep records that support an item on a return until the period of limitations for that return expires, and it lists different periods for different situations, so check its guidance and your accountant's advice. The IRS page How long should I keep records? sets out the details. State and other rules may differ.
Key takeaways
- A close checklist is a calendar with named owners and proof of completion, not a list of ideas.
- Every step should make the numbers complete, correct or final.
- Reconcile early, separate preparing from approving where you can and keep evidence for each task.
- Lock the period after approval and make later corrections visible.
- Automate stable, rule-based steps first. Keep people in charge of judgment and approvals.
- Review the checklist every quarter and confirm the approach with your accountant.
Sources and further reading
Links were checked on October 25, 2026. Rules and guidance change, so confirm on the source before you act.
- IRS: How long should I keep records?. Explains US federal tax record retention periods and when they start.
- COSO: Internal Control, Integrated Framework. Describes the purpose of the widely used internal control framework.
The calendar, tables and example in this guide are illustrative templates written by OpsGrit, not accounting, tax or legal advice.
