Close the Books in Five Days, Not Fifteen
Why your close takes three weeks
Most slow closes are not slow because the team is slow. They are slow because the work has no fixed order, so everyone waits on everyone else. The accounts payable person cannot finish until the credit card statement posts. The person doing reconciliations cannot start until AP is done. And the one who builds the reporting package cannot begin until reconciliations clear. When each step waits on the one before it, and nobody knows who owns which handoff, a close that should take a week stretches to fifteen working days.
I have spent about ten years running university finance operations, including managing a budget north of $30 million, and the closes that ran late almost never failed on the hard accounting. They failed on sequencing and ownership. Someone was waiting on a number that a colleague did not know was blocking them. The fix is not new software. It is a written order of operations, a named owner for each line, and the discipline to do the easy work before the period even ends.
This is general educational information, not formal accounting, tax, or legal advice. I work non-attest, alongside your CPA, not in place of them.
Start before the month ends
The single biggest compression you can make is to move work out of the close window. A surprising amount of the close does not depend on the final day's transactions, and you can do it on the 28th or 29th just as well as the 3rd.
Three things belong in this pre-close bucket. First, recurring journal entries that do not change month to month, like depreciation, prepaid amortization, and standard accruals. Build them as templates once and post them on a schedule. Second, vendor and payroll accruals you can already estimate, since you usually know the big ones before the calendar flips. Third, any reconciliation on an account that barely moves, like a deposit or a long-term loan. If the balance did not change, reconcile it early and leave it alone.
Do this and you walk into day one of the close with a third of the work already behind you.
A five-day order of operations
Here is the sequence I hand to small teams. The point is not the exact day count, it is that each task has a fixed slot and a named owner, so nothing waits in silence.
Day one: cutoff and capture. Lock the prior period so no new transactions slip in. Confirm all bank feeds and credit card statements have posted. Chase the last few outstanding invoices and expense reports. The goal of day one is simply that every transaction for the month is in the system. You cannot reconcile a moving target.
Day two: subledgers and accruals. Close accounts payable and accounts receivable. Post the accruals you did not pre-stage. Run payroll allocations. By the end of day two, the detail ledgers should tie to the general ledger control accounts.
Day three: reconciliations. Reconcile cash, credit cards, and any balance sheet account that moved. This is where a slow close usually hides, so protect the time. A reconciliation that someone other than the preparer can follow is the one that holds up under review. If you cannot explain a balance in two sentences, it is not reconciled, it is just matched.
Day four: review and adjust. Run a preliminary profit and loss and balance sheet. Look for the obvious tells: a negative balance where there should not be one, an expense line that doubled, a revenue account sitting at zero. Post correcting entries. This review catches the errors before they reach a leader's inbox, which is the whole point.
Day five: report and lock. Finalize the reporting package, write the short variance narrative, and lock the period. Done.
One list keeps it honest
The mechanism that makes this work is boring on purpose: a single shared close checklist with three columns, the task, the owner, and the status. It can live in a spreadsheet. You do not need a close-management product to get most of the benefit.
What matters is that the list is the same every month, that every line has one name next to it (not a team, a person), and that anyone can open it and see what is done and what is blocking the next step. The first month you run it, you will find tasks nobody thought they owned and tasks two people were quietly both doing. Fixing those overlaps alone often takes days off the close.
I keep the checklist visible to the whole team during the close window. When the AP owner marks their line done, the reconciliation owner can see it and start, without an email asking whether it is safe to go. That visibility is what turns a chain of people waiting into a relay where each person knows exactly when to run.
What to do this week
You do not need to redesign anything to start. Pull up your last close and write down, in order, every task that happened and who did it. That list, ugly as it is, is your first checklist. Then mark which of those tasks could have happened before the month ended, and move them. Most teams find three or four.
Run that for one cycle before you change anything else. A close gets faster when the work is ordered and owned, not when you buy a tool to manage the disorder.
If your close keeps slipping and you are not sure where the time goes, that is exactly the kind of thing a Financial Operations Assessment is built to find. It maps your current process, names the bottlenecks, and hands you the ordered checklist to fix them.