Monthly close slips because time disappears in file queues, matching, exceptions, and approvals, not in the closing journals. A useful diagnosis maps working minutes to process stages, then cuts the stages that wait without a decision.
Lateness is a symptom, not a team personality
The line in the meeting is usually that the team is too slow or the data is too messy. Neither sentence points at the work that actually eats the calendar. Close is a chain, and the chain stops at the step with no owner.
Bank rec, receivables rec, tax rec, and accrual review wait on one another. If one bank statement arrives late, everything behind it shifts. If exceptions are not classified, the close meeting becomes a guessing session.
What you need to measure is not overtime spirit. You need to measure minutes waiting, minutes matching, minutes investigating, and minutes approving.
A map of where time goes
Waiting for files everyone assumes exist
Most delay is not work. It is a queue. The bank statement is not final. The ERP export is still open because accounting is posting journals. The gateway settlement file is still being downloaded by operations staff who do not know the finance cutoff.
Make a required-file list per entity: each bank statement, the ledger export, cash and receivables subledgers, gateway reports, and the cut-off journal list. Every file needs an owner, a final hour, and an escalation path. A file that is not on the required list must not hold the close.
Matching without a sequence
Starting with the strangest row is a trap. The team spends the morning on one hard break while hundreds of rows that could match cleanly sit untouched. A healthy sequence is totals first, batches first, exceptions last.
If matching keys change every month, time will be spent rewriting formulas. Stable keys are value date, amount, reference, and account. Description is only a fallback.
Exceptions without categories
An unmatched list dumped into one column is where time evaporates. Settlement timing, bank fees, wrong-period journals, and duplicates need different paths. Mixing them forces every row to be reviewed from scratch.
Clear categories cut review time. Timing items only need an expected date. Mapping items need one source correction. Fraud or duplicate items need investigation, and they must not queue behind admin-fee differences.
Approvals with no service level
Many closes stall on the desk of someone who does not know they are being waited on. Material adjustments wait for the CFO. Customer clarifications wait for sales. Tax corrections wait for an adviser who replies when free.
Define what a reconciler may close, what the accounting lead must approve, and what needs a director. Without authority limits, every break becomes a meeting.
How to diagnose a close week
Record the calendar, not the vibe
For one cycle, write down when files arrived, when matching started, when the first exception list was complete, and when the last journal posted. Do not trust meeting memory. Meeting memory blames the most dramatic task, not the longest queue.
A simple map is enough: a time axis by day, a row per stage, and a mark whenever a person was waiting on another person. The pattern shows up without an expensive dashboard.
Separate valuable work from rework
Valuable work is matching, tracing, and deciding. Rework is re-exporting, cleaning columns, copying into a new sheet, and hunting the right file version. If rework dominates, the problem is not reconciliation skill. It is file governance.
Keep one period folder that locks after cutoff. A new version after lock must be recorded as a replacement, with a reason. A close that lives on loose chat attachments will always slip.
Measure exception age, not row count
A long exception list on day two is not always bad. The same exceptions still open on day seven almost always are. Age tells you whether the process is closing, or only stacking.
Set an age limit per category. Timing may live until the next settle date. Mapping should die inside the current cycle. Ownerless items should escalate the same day.
Fixes that actually shorten the calendar
Lock cutoff earlier than the close meeting
A meeting on day five will not save a cutoff that was never written down. Lock cash date, recognition date, and settlement date before the period ends. Anyone posting after lock must use an adjustment path, not a silent edit.
Normalise files before matching
Time spent reshaping every bank statement is close time in disguise. Date, amount, and reference columns should be normalised before matching, and the steps should be repeatable. If each bank needs a new formula every month, the calendar will lose.
Do not mix daily rec with month-end rec
Daily rec catches timing and duplicates while the trail is still warm. Month-end rec closes items that cross cutoff and reviews clearing accounts. Mixing both at month-end compresses a fortnight of work into three late nights.
Ship an evidence pack, not a slide deck
Close is done when the pack is complete: working papers, open items, adjusting journals, and an approval log. A management summary may exist, but the slide must not be the definition of done. If done means a presentation, the process will wait on the meeting calendar.
What not to fix first
Do not start by replacing the ERP. Do not start with a prettier report template. Do not start by hiring people to copy columns. Start with late files, vague exception categories, and approvals without authority.
Once those three are tidy, a matching engine starts to matter. Before that, automation only delivers the mess to a cleaner screen, faster.
FAQ
Why does monthly close still slip when the team works late?
Overtime does not cut file queues or approval queues. Time disappears while people wait for files, wait for clarifications, or reshape columns again. Measure those queues before adding hours.
What is the most useful first diagnostic step?
Log one cycle: file arrival time, matching start, first complete exception list, last journal. That map names the blocked link more honestly than meeting impressions.
Is bank reconciliation always the bottleneck?
Often, but not always. Receivables, tax, and accruals can hold the same books. If statements already match and clearing accounts are still dirty, the delay is recognition, not cash.
How long may an exception stay open?
It depends on category. Timing waits for the next settlement. Mapping should finish in the current cycle. Ownerless items should not overnight without escalation.
Must we wait for every bank before starting?
No. Start with accounts whose files are final. Waiting for a complete pack before touching the first row only moves the whole job to the end of the calendar.
What does a controlled monthly close look like?
Required files arrive on time, matching runs in layers, exceptions age out quickly, and adjusting journals carry an approval trail. The meeting becomes a review, not a hunt for files.