Month-End Close Process: A Step-by-Step Checklist Finance Teams Can Automate
By Kirill Stolbushkin
Short answer: The month-end close process is the set of steps a finance team runs after each month ends to make sure every transaction is recorded, recorded once, and recorded in the right period before anyone relies on the numbers. For most small and mid-sized teams it runs in six steps: prepare, cut off, adjust, reconcile, review, and sign off. The accounting is rarely what makes a close slow. The handoffs are.
If you watch a close from the outside, most of the time does not go into accounting. It goes into waiting. Waiting for a bank feed. Waiting for a department head to confirm an accrual. Waiting for someone to notice the payroll file arrived. This guide walks through the close step by step, then shows how to turn the checklist into a workflow that does the chasing for you.
What the month-end close process actually is
A good close proves three things about the month: everything that happened is in the books, nothing is in there twice, and every transaction landed in the right period. Every task on a close checklist exists to support one of those three claims.
The checklist and the process are not the same thing. The checklist is the list of tasks. The process is the order they run in, who does each one, who reviews it, and what happens when something is late or wrong. Most teams have a checklist. Fewer have a process that everyone can see.
The month-end close process, step by step
Step 1: Prepare before the month ends
The cheapest close work is the work you finish before the period ends.
Confirm the close calendar: which day each task is due and who owns it.
Post recurring entries you already know about, such as rent, subscriptions, and loan interest.
List the accruals you expect: open purchase orders, contracts billed in arrears, bonuses.
Check who is out of office during close week and name a backup for each task.
Step 2: Cut off and capture
Set a cutoff date and time, and tell the rest of the company. Anything that arrives after it goes into next month unless it is material. Then collect what the close depends on:
Bank and credit card statements, plus payment processor reports.
Supplier invoices received for the period, so accounts payable is complete.
Customer billing for the period, so accounts receivable is complete.
Payroll reports and, if you hold stock, inventory counts.
Step 3: Post adjusting entries
Book the entries that put revenue and expenses in the right month: accruals for costs incurred but not yet invoiced, prepaid expenses released over time, depreciation, payroll accruals, and deferred revenue if you have it. Every entry gets a preparer and a reviewer, and every entry has its support attached.
Step 4: Reconcile accounts
Tie each balance sheet account to evidence outside the ledger. The usual list: bank accounts, credit cards and processors, accounts receivable to the customer ledger, accounts payable to the supplier ledger, payroll liabilities, sales tax, and any intercompany balances. Unreconciled differences either get fixed or get written down as open items with an owner.
Step 5: Review variances
Compare the month to last month and to budget. Pick a threshold, and anything that moves more than that gets an explanation or a correction. This is where you catch the accrual nobody booked or the invoice coded to the wrong department.
Step 6: Sign off and lock the period
The finance lead or controller reviews the close package (reconciliations, adjusting entries, variance notes), approves it, and locks the period in the ledger so nothing can be posted back into it by accident. Then the reports go out.
The order matters because later steps depend on earlier ones. You cannot reconcile accounts payable before cutoff is done, and you cannot review variances on balances that are still moving. Some steps do run side by side: bank reconciliations and the accounts receivable review can happen at the same time. Knowing which tasks can run in parallel is where a lot of close time is saved.
Who owns each step
Every close task needs three roles, even if one person wears two of the hats in a small team:
Preparer: does the work and attaches the evidence.
Reviewer: checks it and either approves it or sends it back with a comment.
Approver: signs off the whole close, usually the controller, finance lead, or an outside accountant.
People outside finance also own close inputs. Department heads confirm accruals. HR or payroll sends payroll data. Operations confirms inventory. Write those names into the process too, because they are usually where the waiting happens. If you have never written down who owns what, our guide to process ownership and RACI is a good place to start, and a swimlane diagram makes the handoffs visible at a glance.
Where the close slows down
The same few problems show up in most slow closes:
Inputs from outside finance arrive late. Nobody owns the reminder, so the controller sends it by hand every month.
Status lives in a spreadsheet. Someone has to ask around to find out what is done.
Review piles up at the end. Reviewers get everything on the last day instead of as tasks finish.
The same exceptions repeat. The same account fails to reconcile every month and gets fixed by hand every month.
One person holds the process in their head. When they are out, the close stalls.
None of these is an accounting problem. They are workflow problems, which is why they respond well to a workflow.
Turning the close checklist into a workflow
A close checklist maps neatly onto a BPMN process model. If you have not worked with BPMN before, the BPMN symbols cheat sheet covers every shape used below.
Timer start event: the process starts automatically on the last business day of the month.
Parallel gateway: cutoff tasks for bank, payables, receivables, and payroll start at the same time, and a second parallel gateway waits until all of them are done before review begins.
Lanes: one lane per role, such as staff accountant, accounts payable, payroll, department heads, and controller.
User tasks with review: each task goes to the preparer, then to the reviewer. An exclusive gateway after review either moves it forward or sends it back with a comment.
Timer boundary events: a non-interrupting timer sends a reminder when a task is close to its due date. An interrupting timer moves an overdue task to the controller.
Message events: the process waits for inputs from outside finance, such as a department head confirming an accrual.
End event: the period is locked and the reports are sent.
Drawn this way, the close becomes something you can run, not just a list you tick off.
What to automate first, and what to keep manual
Automate the chasing. Keep the judgment.
Good first candidates for automation:
Due date reminders and escalations for overdue tasks.
Requests to people outside finance, with the reply landing back in the right task.
Routing finished work to the reviewer as soon as it is done.
A live status view, so nobody has to ask what is left.
Collecting the evidence for each reconciliation in one place.
Keep with people: estimates and accruals that need judgment, explanations for variances, and the final sign-off. If your company is in scope for SOX or preparing for an audit, keep a record of who did what, when, and who approved it, because that record doubles as evidence. Our guide to SOX internal controls documentation covers what auditors look for.
How to model and automate this in Vevos
You do not need to draw the process by hand. Describe your close in plain English, the way you would explain it to a new hire, and Vevos turns it into a BPMN 2.0 model with lanes, gateways, and timers. For example:
"On the last business day of the month, the close starts. The staff accountant reconciles the bank and card accounts while accounts payable confirms all supplier invoices are in. Department heads confirm their accruals within two days or the controller gets a reminder. Each reconciliation is reviewed by the controller. When everything is approved, the controller locks the period and sends the reports."
Then walk through the model with the people who do the work and fix anything that does not match reality. Our guide to describing a process in plain English has tips on writing that first description.
You can try it now with the free AI process mapper, no account needed. The free Intro plan saves up to three process models, and the $9 and $29 plans add more modeling room. When you want a working app for the reminders, routing, and status tracking, Conductor Agents can build and deploy one from the model after you review it. That starts on Tempo at $199/month. Every plan is on our pricing page.
A short month-end close checklist
Close calendar confirmed, owners and backups named.
Recurring entries posted.
Cutoff communicated and source documents collected.
Adjusting entries prepared, supported, and reviewed.
Bank, card, receivables, payables, payroll, and tax accounts reconciled.
Open items listed with owners.
Variances over threshold explained or corrected.
Close package approved and period locked.
Reports sent.
FAQ
What are the steps in the month-end close process?
Prepare, cut off and capture, post adjusting entries, reconcile accounts, review variances, and sign off and lock the period. The exact tasks depend on your business, but the order holds for almost everyone because each step depends on the one before it.
How long should the month-end close take?
It depends on the size of the company, the number of entities, and how many inputs come from outside finance. A better goal than a fixed number of days is a close that takes about the same time every month and gets shorter as you remove waiting and repeat exceptions.
Who signs off on the month-end close?
Each task has a preparer and a reviewer. The controller, finance lead, or outside accountant signs off the full close package once reconciliations tie out, adjusting entries are reviewed, and variances are explained.
What parts of the month-end close can be automated?
The coordination: reminders, requests to people outside finance, routing work to reviewers, status tracking, and evidence collection. Many recurring entries can also be automated in your accounting system. Judgment calls and the final sign-off should stay with people.
What happens if you find an error after the period is locked?
Small, immaterial errors are usually corrected in the next open period with a note. Material errors need a documented and approved adjustment to the prior period. Agree on the rule with your accountant or auditor before you need it.
Related blog posts
- Work Order Process: From Maintenance Request to Close-Out, Step by Step — The work order process for facilities, property management, and field service teams: eight steps from maintenance request to close-out, how to set priorities and cost approvals, the exceptions that stall jobs, and how to draw it as a flowchart.
- Purchase Requisition Approval Process: Thresholds, Approval Chains, and Workflow — A practical guide to the purchase requisition approval process: the steps from request to approved requisition, how to set spend thresholds and approval chains, which duties to keep apart, and how to handle urgent and over-budget requests.
- Client Onboarding Process: A Step-by-Step Workflow for Agencies and Service Firms — A practical client onboarding process for agencies, consultants, and B2B service teams: seven steps from signed contract to first delivery, which steps every client gets, which depend on the service, and how to map it so nothing gets dropped.