Month-end is expensive because it is a reconstruction. Everything that was skipped for four weeks gets fixed in two days, and the person doing it is guessing at transactions nobody remembers.
A weekly close costs forty minutes and removes the guesswork. This is the checklist.
Why weekly, not monthly
Three reasons, in order of how much they save you:
Memory has a shelf life of about a week. An unexplained $1,340 payment can be identified on Friday. Three weeks later it is a mystery, and you are calling a client to ask what a payment was for — which is a small admission of disorder every time.
Errors are cheapest when they are one week old. A duplicate bill caught in week one is a deletion. Caught at month-end it is a correction, an amended payment run, and a conversation.
Month-end becomes review, not repair. The work that remains is judgement — is profit where it should be — instead of data entry.
The checklist
Run it the same day each week. Friday afternoon is the usual choice; Monday morning works if Friday is a delivery day.
1. Reconcile every account (15 minutes)
Every bank account, every card, every loan. Not one — every one.
For each, the target is that the statement balance and the ledger balance agree, with zero unreconciled items. Anything left unreconciled becomes permanent background noise, and once there are five items nobody looks at, there may as well be fifty.
2. Clear the suspense account (5 minutes)
Anything coded to suspense, uncategorised, or "ask my accountant" gets resolved or moved to a named holding account with a note.
Rule: nothing stays unclassified for two weeks. If it is genuinely unknown after that, it gets a holding category and a task with an owner.
3. Check the three accounts that go wrong
In most small businesses, errors cluster in the same three places:
- Merchant processor. Fees and payouts are easy to net off incorrectly. The gross should match sales; the fee is an expense. If you are booking net, your revenue is understated and your expense line is invisible.
- Payroll. Wages, taxes and net pay are three separate movements. A single lump entry hides errors until a filing is wrong.
- Owner draws and personal spend. These should never sit in an operating expense category. One account, clearly named, so it is visible.
4. Age the receivables and payables (10 minutes)
Two lists: who owes you, and who you owe. For each, note the age in 30-day buckets.
The deliverable is not the list — it is the two or three items that moved into a new bucket this week. Those are the only ones that need action.
5. Reconcile the sales tax position (5 minutes)
Sales tax collected is not income. It is a liability you are holding. Compare what the system says you collected against what you have set aside or remitted.
If those two numbers drift apart, you are spending tax money and will discover it at filing.
6. Write three lines the owner will read (5 minutes)
Not a report. Three lines:
- Cash in, cash out, cash at the end
- Anything that looked wrong and what happened to it
- What needs a decision next week
This is the step people skip, and it is the one that makes the other five worth doing. A close nobody reads is data hygiene; a close with three lines is management.
The failure mode to watch for
The checklist stops being run during a busy week, then two, then it is abandoned — and the month-end reconstruction returns.
Two defences:
Make it short enough to survive a bad week. Forty minutes will get done on a Friday where somebody is tired. Three hours will not.
Record whether it was done. A single line in a log — date, done or not. Six weeks of "not done" is the early warning that the books are drifting, and it is visible before the numbers look wrong.
What good looks like
- Every account reconciles to zero unreconciled items
- Nothing has been in suspense for more than two weeks
- The receivables ageing has no surprises in it
- Month-end takes an afternoon, and it is reviewing rather than fixing
The purpose of the weekly close is not tidiness. It is that the numbers you look at in the last week of the quarter are numbers you can act on, rather than numbers you are still assembling.