Most month-end close processes break down in the same place. Finance builds a checklist, hands it to the ops manager, and expects it to run itself. The ops manager, organized and competent but not an accountant, looks at items like “post accruals” and “reconcile subledgers” with no clear picture of what they own, what they approve, or what happens when something arrives late.
The result is a close that drags past day 10, with finance chasing down expense reports and ops unsure which month-end close steps actually require their attention. At CoCountant, the controller designs the close system and owns the accounting side. The ops manager gets a defined lane with explicit tasks, deadlines, and handoff points. This guide shows how to build a month-end close checklist that gives both teams that same clarity.
The Short Answer
A month-end close checklist is a structured task list covering every step required to finalize the prior month’s financial records. Each item specifies an owner (finance or operations), a due date by business day, and a clear definition of done. A complete checklist covers both the accounting layer (reconciliations, journal entries, sign-off) and the upstream inputs that accounting depends on.
What the Monthly Accounting Close Process Actually Requires
The monthly accounting close process is the sequence of steps that converts a month of raw transactions into controller-signed financial statements. It typically runs 5 to 10 business days after month-end. High-performing teams close in 5 to 7 days; most mid-size companies average 8 to 10.
The close is not purely an accounting exercise. It requires upstream inputs from operations: approved expense reports, vendor invoices cleared from the approval queue, payroll confirmations, project cost allocations, and accurate inventory counts. When those inputs arrive late or incomplete, the accounting team cannot proceed.
That is the core problem a well-designed checklist solves. It makes the ops manager’s responsibilities explicit rather than assumed.
The Four Phases of the Monthly Accounting Close Process
Breaking the monthly accounting close process into phases gives ops managers a calendar they can map their tasks to.
| Phase | When | Who Leads | What Happens |
| Pre-Close Prep | Days -2 to 0 | Finance + Ops | Expense submission cutoff enforced; vendor invoices approved; payroll data finalized; bank feeds verified |
| Data Collection | Days 1-2 | Finance | All transactions imported; cutoffs applied; subledger data pulled |
| Reconciliations | Days 2-4 | Finance (Controller) | Bank, AP, AR, inventory reconciled; accruals posted; prepaid schedules updated |
| Review and Close | Days 4-7 | Controller | Adjusting entries finalized; financial statements prepared; controller sign-off |
Most close failures happen in the Pre-Close phase. Expense submissions and invoice approvals that arrive on Day 2 push every downstream reconciliation by at least two business days. The ops manager’s window is Days -2 to 0, and it must close on time.
The Full Month-End Close Checklist
This month-end close checklist separates tasks into two ownership tracks: Finance and Operations. Both tracks must run on schedule for the close to land on time.
| Phase | Task | Owner | Due Day | Done When |
| Pre-Close | Notify team of expense submission cutoff | Ops | Day -2 | Notification sent; acknowledgment received |
| Pre-Close | Submit all employee expense reports | Ops / All Depts. | Day 0 | All reports submitted and approved |
| Pre-Close | Clear all pending vendor invoice approvals | Ops | Day 0 | AP queue shows zero pending approvals |
| Pre-Close | Confirm final payroll figures with payroll contact | Ops / HR | Day 0 | Payroll provider confirms final numbers |
| Pre-Close | Complete inventory count (if applicable) | Ops | Day 0 | Physical count reconciled to system |
| Pre-Close | Verify bank feeds are synced with no import errors | Finance | Day 0 | All accounts connected; no errors flagged |
| Data Collection | Import and categorize all transactions | Finance | Day 2 | All accounts balanced; no uncategorized lines |
| Data Collection | Apply cutoff rules to accrued revenue and expenses | Finance | Day 2 | Accruals worksheet fully populated |
| Reconciliations | Reconcile all bank accounts | Finance | Day 3 | Each account ticked and tied |
| Reconciliations | Reconcile accounts payable aging | Finance | Day 3 | AP aging matches subledger |
| Reconciliations | Reconcile accounts receivable aging | Finance | Day 3 | AR aging matches subledger |
| Reconciliations | Post accrued liabilities and prepaid schedules | Finance | Day 4 | Schedules updated; journal entries posted |
| Reconciliations | Review and release deferred revenue balances | Finance | Day 4 | Balance confirmed; release entries posted |
| Review and Close | Confirm all outstanding items resolved | Finance + Ops | Day 5 | No open flags on the checklist |
| Review and Close | Prepare draft financial statements | Finance | Day 5 | P&L, balance sheet, cash flow drafted |
| Review and Close | Controller review and adjusting entries | Controller | Day 6 | All entries reviewed; no open items remain |
| Review and Close | Controller sign-off and period lock | Controller | Day 7 | Period locked; statements finalized |
The ops manager’s active window is the Pre-Close phase. After Day 0, their role shifts to responding quickly if finance surfaces a question or a missing item.
How to Build Your Own Month-End Close Template
A month-end close template is not a one-size-fits-all download. It needs to reflect your actual transaction volume, team structure, and accounting systems. Here is how to build one that holds up every month:
- List every recurring close task. Start from your accounting system’s transaction history. What gets entered, approved, or reconciled every single month? Pull the actual list rather than guessing from memory.
- Assign a specific owner to every task. Every item needs a role or a name, not a department. “Finance” is not an owner. “Controller” or “AP Bookkeeper” is.
- Set due dates in business days, not calendar dates. Use Day 1, Day 2, Day 3 from the first of the month. This makes the template reusable every month without adjustment.
- Define what “done” looks like. “Bank reconciled” is better than “review bank.” “Controller-signed in QuickBooks” is better than “approved.” Vague checkboxes create disputes about whether a task is actually complete.
- Build the pre-close layer at Days -2 to 0. The ops manager finance checklist lives in this window. Expense submission cutoffs, invoice approvals, and payroll confirmations all need to close before accounting opens the books.
- Add a daily review during close week. A five-minute check on outstanding items each morning prevents a single stalled task from blocking everything behind it.
- Save it as a documented financial close SOP. A checklist that lives in one person’s head is not a system. Write it down, get sign-off from both the finance lead and the ops lead, and store it where both teams can find it.
How to Make the Financial Close SOP Stick
Building the checklist is the straightforward part. Getting a non-finance ops manager to follow a financial close SOP consistently, every single month, is harder. Most guides stop before they get to this section.
Three factors determine whether the SOP holds:
Visibility before accountability. If the ops manager cannot see their tasks until close week begins, they will always be reacting. Send a preview of the ops lane on the 25th of each month. Give them their tasks before the deadline pressure starts.
A clear escalation path. What happens when an ops task is blocked? Maybe a vendor has not responded with an invoice by Day 0. The ops manager needs to know who to notify, by which day, and when to escalate to the controller. Blocked items do not resolve on their own.
A monthly retrospective. After each close, spend 15 minutes noting what arrived late, what was missed, and why. A simple one-column log after each cycle turns the SOP from a static document into a living system. Most teams skip this step and repeat the same failure points every quarter.
Common Mistakes Teams Make with the Month-End Close
Waiting until Day 1 to collect pre-close data
Expense reports and vendor approvals that arrive on Day 2 push every downstream reconciliation by at least two business days. The cutoff must be enforced before month-end, not chased after it has passed.
No named owner on each task
A checklist that assigns tasks to “Finance” or “Operations” is a responsibility gap waiting to surface. Every item needs a specific role or a person’s name attached to it.
Missing the handoff confirmation step
When the ops team submits expense data or clears an invoice queue, there is usually no record that the handoff was completed. Finance then has to ask again to confirm. A simple acknowledgment at each ops-to-finance transition eliminates most of this close-week back-and-forth.
Treating the close as an accounting-only event
Department heads affect the close outcome even when they are not accountants. Payroll inputs, project cost allocations, inventory counts, and sales figures all feed the accounting layer. If those inputs are not part of the ops manager finance checklist, the close has an unowned dependency.
Not locking the period after sign-off
Posting transactions to a closed month undermines every reconciliation that was just completed. Period lock is a controller function, but the ops manager should know when it happens and what it means for any late expense submissions.
When to Bring In a Controller
A clear checklist and a documented SOP solve the process problem. But if the accounting layer underneath those processes is inconsistent, even a well-run checklist will produce unreliable numbers.
Signs that a controller belongs in the close:
- The close takes more than 10 business days with no clear explanation for why
- Reconciliations are completed but the numbers still do not agree with prior months
- Accruals and deferrals are applied inconsistently from month to month
- The ops manager is being asked to make judgment calls that require accounting expertise
- Financial statements are not available within two weeks of month-end
If any of those apply, the problem is not the checklist. It is the accounting infrastructure behind it.
For more on how a controller transforms the close from a task list into a repeatable reporting system, see How a Controller Turns Month-End Into a Management System.
How CoCountant Approaches the Month-End Close
CoCountant’s accounting services are built around a controller-and-bookkeeper pod. The controller designs the close workflow, owns every reconciliation and sign-off step, and produces GAAP-aligned financial statements on a 10 to 15 business day timeline.
The ops manager’s responsibilities are defined from the start of the engagement. CoCountant establishes a clear handoff protocol: what the operations team submits, by which day, and in which format. The controller handles everything that follows.
The engagement runs inside your existing QuickBooks instance, so there is no proprietary platform to migrate to. Response time is 2-4 hours on standard plans. Pricing is a flat monthly subscription with no hourly billing.
Colleen Rupp, COO at Hollywood.com, cut her close timeline from 20 days to 10 days after moving to this model. The change was not a new checklist. It was a controller who owned the system and held the deadline.
Controller oversight is standard on every plan. See the full range at the pricing page.
For a picture of what a controlled close delivers at the reporting layer, see What Should a Monthly Controller Report Include?.
Conclusion
A month-end close checklist that works is not the same as one that exists on paper. The difference is explicit owner assignment, confirmed handoffs at each stage, and a financial close SOP both the finance and ops teams have read and agreed to follow. The ops manager’s job is upstream: get the pre-close inputs in by Day 0, clear the approval queue, and respond quickly when finance has a question.
The accounting layer still requires a controller to reconcile, review, and sign. But when the ops side runs cleanly, the close lands on time and the numbers are reliable when they matter.
If your close is consistently running past 10 days, or the handoffs between ops and finance keep breaking down, talk to a controller about what a structured close looks like for your business size and transaction volume.
FAQs
What should a month-end close checklist include?
A complete month-end close checklist includes pre-close tasks (expense submissions, vendor invoice approvals, payroll confirmation), data collection steps, reconciliations for bank accounts, AP, AR, and inventory, adjusting journal entries, financial statement preparation, and controller sign-off. Each task should list a specific owner, a due day in business days, and a clear definition of done.
How long should the monthly accounting close process take?
Most finance teams complete the monthly accounting close process in 5 to 10 business days. High-performing teams close in 5 to 7 days. A close that regularly runs past 10 days usually signals a structural issue: missing pre-close inputs, unresolved reconciling items, or no controller with defined ownership over the timeline and sign-off.
What are the month-end close steps in order?
The month-end close steps follow four phases: pre-close preparation (Days -2 to 0), data collection (Days 1-2), reconciliations and adjusting journal entries (Days 2-4), and controller review with sign-off (Days 4-7). The ops manager’s primary window is the pre-close phase. Finance and the controller own everything that follows.
What is the ops manager’s role in the monthly close?
The ops manager owns the pre-close inputs: submitting and approving expense reports, clearing vendor invoices from the approval queue, confirming payroll figures, and completing any required inventory counts. All of these must be done by Day 0. After that, the ops manager’s job is to respond quickly to any questions finance raises during the reconciliation phases.
How do I create a financial close SOP that non-finance staff can follow?
Build the financial close SOP around role-specific task lists with due dates in business days, clear definitions of done, and written handoff confirmations at each ops-to-finance transition. Train non-finance staff only on their lane, not the full accounting workflow. Review the SOP after each close and log what broke or arrived late so the document improves over time.
