Most month-end close checklists are written for a controller closing one company's books. A firm closing books for clients has a different problem. Every client wants the same short window, the person preparing the entries is usually not the person whose judgment the client is paying for, and the statements that leave the office carry the firm's name.
That changes what belongs on the checklist, where the review sits, and what the last step actually is.
What a Firm's Month-End Close Has to Produce
The month-end close is the recurring process of cutting off a period, reconciling every account to an outside record, posting the adjustments that make the period complete, and producing statements someone can act on.
Cutoff is the term doing the work in that sentence. It means the point after which a transaction belongs to the next period rather than this one, and in a firm setting the cutoff you can enforce is rarely the calendar date. A client's last supplier invoice for March may not reach anyone until the second week of April.
So a firm's close runs on two clocks. The client's operational cutoff decides when the underlying data stops moving. Your delivery date decides when reviewed statements go out. The gap between them is the whole close, and it is the only part of the process your firm controls.
The output is also bigger than the statements. What has to exist at the end is a reviewable file: the reconciliations, the support behind every adjusting entry, the questions asked of the client and the answers received. A close that produces correct numbers and no file can only be reviewed by the person who did it, and that shows up later as a capacity problem rather than an accuracy one.
Before the Month Ends: The Pre-Close Checklist
Pre-close work is what stops the first days of the close from being a document chase. Five items, all of them finished before the period is over.
Send the cutoff request to a named person. Not to a shared mailbox. The request names the specific documents you already know are missing and the date you need them by.
Confirm every feed and integration is live. Bank feeds, card feeds, payment processors, payroll, point of sale, and any application writing into the ledger. A broken feed found on day one of the close costs a day. Found in the pre-close, it costs a message.
Confirm payroll dates, including off-cycle runs. Payroll tends to be the accrual that moves after everyone has assumed it was settled, and a bonus run or a correction posted late lands squarely in the close.
Write the client's known-late list. Clients tend to be reliably late on the same things, and after two closes you know what those are. That list is the real pre-close checklist for that client, and it belongs in their file rather than in a manager's memory.
Lock the prior period. If last month can still be posted to, this month's opening balances are not fixed, and every reconciliation you are about to perform sits on sand.
The Seven-Step Month-End Close Checklist
Work these in order, because each step produces something the next one depends on. Each one also needs a named preparer and a named reviewer agreed before the month starts, not assigned while it is running.
- Confirm the period's transactions are complete.
- Reconcile every account that has an outside statement behind it.
- Close the sub-ledgers and tie each one back to its control account.
- Post accruals, deferrals and adjusting entries.
- Walk the balance sheet account by account.
- Explain every variance above the client's threshold, in writing.
- Issue the statements, lock the period, and log what broke.
1. Confirm the Period's Transactions Are Complete
Completeness comes first, because every later step is arithmetic performed on whatever happens to be in the ledger, gaps included. Post or import payroll, confirm supplier invoices dated in the period have been entered, capture employee expenses and card spend, and record revenue earned but not yet billed.
The firm version of this step is a source list rather than a task list. For each client, write down where transactions come from, then confirm each source has been drawn down for the period. A source nobody remembers is how a whole revenue stream goes missing for a month and turns up in the next one.
2. Reconcile Every Account With an Outside Statement
Reconcile everything with an external record behind it: bank accounts, credit cards, merchant processors, loans, and payroll liability accounts. Nothing in the result needs a judgment call, which is why this is often the first work a firm hands to someone else, and the test for what else moves and what stays is the same one.
What decides whether a reconciliation is finished is the unexplained difference. A reconciliation carrying one is not complete, it is postponed, and postponed differences compound across months until somebody has to rebuild a year of a client's books to find the original error.
3. Close the Sub-Ledgers
A sub-ledger is a detailed record that rolls up into a single control account in the general ledger. Accounts receivable, accounts payable, fixed assets, inventory and payroll each have one.
Close each sub-ledger and tie its total back to the control account before looking at the balance sheet. Aged receivables and payables get reviewed at this point rather than at the end, because a receivable nobody has chased since last summer is a conversation with the client, not a journal entry, and that conversation takes days the delivery date does not have.
Fixed assets and inventory come last in this step, since additions, disposals and counts usually arrive from people outside the accounting function.
4. Post Accruals, Deferrals and Adjusting Entries
Here the close stops being data entry.
An accrual records an expense incurred but not yet invoiced, or revenue earned but not yet billed. A deferral does the reverse, holding back amounts already invoiced or paid that belong to a later period. Prepaid insurance, deferred revenue, accrued payroll and accrued interest are the usual candidates, and each deserves a standing schedule the preparer updates rather than recalculates from scratch.
For a client reporting on an accrual method for tax, the book accrual and the deductible amount are not automatically the same number. Under the accrual method described in IRS Publication 538, a business expense is generally deducted or capitalized only when two things are both true. The all-events test has been met, which happens when all events have occurred that fix the fact of liability and the liability can be determined with reasonable accuracy. And economic performance has occurred.
Economic performance is the extra hurdle, and it is the one a book accrual does not test for. Where the expense is for property or services provided to the business, economic performance occurs as the property or services are provided (Publication 538). For an accrual covering work already performed, that test is already satisfied on the day the entry is posted. The items worth flagging are the ones where it is not.
The recurring item exception loosens that timing for the items a monthly close produces most often, and it carries four conditions rather than one. The all-events test has to be met. Economic performance has to occur by the earlier of 8½ months after the close of the year or the date a timely return, including extensions, is filed. The item has to be recurring in nature, with similar items consistently treated as incurred in the year the all-events test is met. And either the item is not material, or accruing it in that year produces a better match against income than accruing it in the year of economic performance. The exception does not apply to workers' compensation or tort liabilities (Publication 538).
The instruction this leaves the close with is narrow. Flag the accruals whose tax treatment may differ, keep the schedule that supports them, and leave the determination to whoever signs the return. A close records a position. It does not decide one.
5. Review the Balance Sheet Account by Account
Every journal entry has two sides, and the side nobody was checking is often a balance sheet account. That is why an income statement can read plausibly while the error sits in a clearing account. Walk every balance sheet account and answer one question for each: what is this balance made of, and where is the support?
Suspense and clearing accounts should be zero or explained. Negative balances in asset accounts, credit balances in receivables, and payables older than the client's own payment terms usually point at coding rather than at anything happening in the client's business.
This is also where a preparer's work becomes reviewable or does not. An account with a schedule behind it can be checked in minutes. An account with only a number behind it has to be rebuilt by the reviewer, which is the same as not delegating it at all.
6. Run the Variance Review Before Anything Leaves
Compare the period against the prior month and against the same month a year earlier, and against budget where the client keeps one. Then explain every variance above the threshold you set for that client, in writing, before anything is sent.
Set the threshold per client and write it into the file. A threshold that catches everything produces a review nobody finishes. One that catches nothing produces the call where the client finds the error first.
Variance review costs little and catches what reconciliations structurally cannot. An account coded to the wrong expense line still reconciles perfectly and is still wrong.
7. Issue the Statements, Then Lock the Period
The final step is the one absent from checklists written for in-house teams, because an in-house team is not an accountant in public practice.
Where an accountant in public practice is engaged to prepare a client's financial statements, and is not engaged to audit, review or compile those same statements, AR-C section 70 applies. If your firm performs the audit, review or compilation for that client, the statements it prepares sit outside the preparation standard. The section also names engagements it need not be applied to, among them statements prepared solely for submission to taxing authorities and the personal financial planning, litigation and valuation work a monthly close rarely produces (AICPA Statements on Standards for Accounting and Review Services).
Where it does apply, among its requirements is a legend on each page of the financial statements, including any note disclosures, clearly indicating that "no assurance is provided" on the statements (Journal of Accountancy). A firm that cannot get that statement onto every page has three routes named in the standard itself. It can issue a disclaimer that makes the same point, perform a compilation engagement under AR-C section 80 instead, or withdraw from the engagement and tell management why (AICPA Statements on Standards for Accounting and Review Services). The engagement letter has to address that choice up front, because the standard requires it to record either management's agreement to the statement on each page or the accountant's obligation to issue a disclaimer instead.
Whether a firm is engaged to prepare them is a question about the engagement rather than about the volume of work behind it. Michael Westervelt, then chair of the AICPA's Accounting and Review Services Committee, put it directly in 2023: the amount of bookkeeping or accounting work done for a client has no bearing on the level of service provided, and the standard is not required unless the practitioner is engaged or hired to prepare financial statements (Journal of Accountancy).
A firm merely assisting a client in preparing statements, by posting journal entries into the client's own system or drafting certain note disclosures, is providing an accounting or bookkeeping service that the preparation standard does not reach. The distinction turns on what the client expects next. Where the client's understanding is that the accountant will then prepare the financial statements from those inputs, the standard applies after all (Journal of Accountancy). For a firm that runs the close and then sends the statements out, the client's understanding is usually exactly that, so read your own engagement letter against what your close actually delivers each month.
There is a prior question underneath that one, which is which professional standard the engagement runs under at all. SSARS No. 27 amends the scope of AR-C section 70 so that the section is not required to be applied, though applying it is not precluded, where the statements come out of a consulting services engagement under CS section 100 in which preparing them is not the primary objective. That amendment takes effect for the preparation of financial statements for periods ending on or after December 15, 2026 (AICPA Statements on Standards for Accounting and Review Services).
For firms whose financial statements are a by-product of the work rather than its point, that turns a given into a choice, and the conditions are set out in what a client accounting services practice requires. Settle it before the close rather than during one.
Then lock the period, archive the file with the statements, and write down what broke. The note takes a minute and it is the only input the next close gets.
Where a Multi-Client Close Actually Breaks
Those seven steps are not the hard part. Running them across a book of clients is.
Every client's close lands in the same window. Nothing in the checklist fixes this, because it is a calendar problem rather than a process problem. Firms that solve it stagger clients by delivery date, using the client's own reporting needs to justify the spread, and treat the schedule as part of capacity planning rather than as a scheduling favor.
The reviewer is the bottleneck, and adding preparers makes it worse. More prepared work arriving at the same reviewer lengthens the queue. The first move is to make the preparation reviewable, through schedules and standard workpapers, so review time drops per client.
Cleanup is billed as close. Books that arrive in poor condition turn a fixed-fee close into an open-ended remediation. Price and scope cleanup separately, and say so before the first month rather than after the third.
Judgments live in one person's head. The accrual estimate nobody documented, the allocation that has always been done that way, the client's odd revenue timing. Each of these is fine until that person is unavailable in the delivery week.
No two clients are set up the same way. Different chart of accounts logic, different file naming, different report packs. Standardizing that is dull work, and it is what lets one reviewer cover more clients without quality drifting.
Month-End Close Versus Year-End Close
A monthly close finishes a period. A year-end close finishes the same period and then has to support something outside the firm: the tax return, a lender, a valuation, sometimes an attest engagement performed by a different firm.
For a firm serving clients, the more useful distinction is contractual rather than technical. The monthly service and the year-end deliverable can be separate engagements with separate terms, and treating them as one recurring service is how year-end work ends up unbilled. Decide which is which when the engagement letter is written.
Making the Close Something You Can Hand Off
A checklist that only its author can run is a personal habit, not a process. Three changes make it transferable.
Give every line an owner, an input and an output. The line reads as who does it, what they need before they can start, and what exists when it is done. A line that cannot be written that way is not a task, it is a judgment, and judgments stay with the reviewer.
Standardize the workpaper structure and the file naming across clients, even where the accounting differs. Review speed comes from a reviewer knowing where to look before they open the file.
Keep an exception log per client. Every rejected item, every rework, every question that should not have been necessary. Expand what you delegate when the log stops surprising you.
If your firm is carrying monthly closes and the review queue is what slips, don't trust us, test us. Run a Free 40-Hour Proof Pilot on a block of your own representative work, graded by your own reviewer, before any client file moves.
What Makes the Checklist Hold
A month-end close checklist is only as good as the calendar it runs on and the file it leaves behind. The steps are stable across every client you serve. What varies is when the data stops moving, who is late with what, and how much of the work a reviewer has to redo because the support was never built.
Start with one client and one month. Write the seven steps into a shared file with an owner against each line, add that client's known-late list, and record the exceptions as they happen. The second month tells you whether the checklist is real or whether it was a description of what one person already knew.