It's the 3rd, and you're trying to remember a Tuesday from four weeks back.
One card purchase, no receipt anywhere, and four weeks of bank feed behind it that nobody has looked at.
Ten minutes of that feed sorts itself out. Then you hit the rest. A transfer that's either an owner draw or a loan payment. A run of charges from a vendor you don't recognize. A deposit that doesn't match any invoice you've got.
So you write to the client. They answer part of it four days later. You ask again. On the 11th you get the last piece, and by then you've been in and out of that one file six separate times.
The ten minutes was bookkeeping. The eight days were you reassembling a month out of a bank feed and your own memory of it.
You can't review a month you're still assembling.
Every one of those unknowns had a cheaper version of itself. On the day it happened, the client could have told you what that transfer was in about eight seconds, because they'd just done it. Four weeks later the same question costs you a message, a reminder, a guess, a follow-up, and a re-open of a file you'd already finished twice.
The problem is the 1st, not the 15th.
The 1st is thirty days long, and most of those days you're already in the file.
What is a good bookkeeping workflow?
A bookkeeping workflow is where in the month each decision gets made. Three layers do the whole job. Capture: documents arrive on the day of the spend, through one route the client never has to learn. Triage: one twenty-minute pass a week where you ask about anything you can't identify, while the person who knows still remembers. Standing rules and a written definition of done: the recurring judgment calls get decided once, in writing, so they stop routing through your head. Build all three and the close becomes a check against a list. The work moved to the days where it costs a fraction of what it costs on the 3rd.
Key Takeaways
A long close is a measurement of the month behind it - the days at the front of your month count what nobody captured or decided in the thirty before.
Four things repeat in every painful close - a transaction nobody can identify, a document that doesn't exist yet, something only the client knows, and a judgment call somebody skipped.
Two of those are capture failures and two are decision failures - fixing how documents arrive only reaches the first pair.
Set up the document route first - an address, a sentence, and an autoresponder change what arrives next month.
Twenty minutes a week beats the front of the month - and the twenty minutes is spent asking questions, which is why it survives a busy week.
Done has to be tickable by a stranger - a close that can't finish without you in the room is a job you'll still be doing at fifty clients.
The four things a rebuild is made of
Pull up the last three closes that hurt. Nearly everything in them is one of four items, and it tends to be the same four. Each one has a version that costs seconds and a version that costs a week.
Start with the transaction nobody can identify. On the day, that's a one-line question: what was that charge to the processor this morning? On the 3rd it's three messages, a guess, and a correcting entry next month.
A document that doesn't exist yet. On the day it's a photo of a paper receipt taken in the parking lot. On the 3rd there's nothing to go find, so you're deciding how much documentation you're willing to live without.
The question only the client can answer. On the day: was that personal, and a yes. On the 3rd it's a client squinting at a date four weeks back, which is a coin flip you then post to the books.
The judgment call you skipped. On the day it's thirty seconds of thought while you still have the whole context. On the 3rd it's the same thirty seconds with less context, and no memory of what you decided the last time you saw it.
They split in half. The first two are capture problems, and capture is wiring you install once. The last two are decision problems, and no route you set up will touch them. Fix only the capture side and the answering still gets batched into one shift at the start of the next month, which is the rhythm nobody ever taught anybody to change.
The bookkeeping workflow starts with capture
The workflow is three layers, and capture goes first because it shrinks everything downstream.
One email address that lands wherever your documents live. One sentence to the client: forward it when it happens, photos are fine, don't write anything in the email. An autoresponder on that address, so they get a reply and learn the thing worked. No app, no portal, no password they'll reset twice and then stop using.
You've probably tried a version of this and watched it die by week three. It dies because sending you a receipt is your problem and nothing about it feels urgent to somebody running a restaurant.
So attach it to something they want. The unresolved-items list goes out on a fixed schedule, names the specific transactions you can't finish without, and their statements genuinely wait on it. That's the first time the receipt has been their problem.
For the client who will never comply, stop trying. Ask at the moment the transaction shows up in your weekly pass, one question at a time, and put the chasing on the invoice.
Twenty minutes, three questions, same order
Once a week, same slot, all clients. Twenty minutes.
What came in this week that I can't identify?
What's identified but has no document behind it?
What did I decide not to decide?
Then you send. All of it, one message per client, once a week. Five messages across five days teaches the client to skim you.
The list is fixed at three. That's what stops it growing into a second close, which is the part that breaks first.
Write down the decisions you keep re-making
"What did I decide not to decide" is the decision half, and it's where the capacity is.
Owner draws versus distributions. Personal spend on the business card. The vendor that's half cost of sales and half equipment. You've decided each of these before. Nobody writes it down, so it gets decided again, slightly differently, and every one routes through your memory.
Write them down. One file per client, one line per rule, in whatever plain words you'd use with a staff member. "Anything at the fuel station under our documented threshold goes to vehicle expense, statement line only." "Transfers to the second account are draws unless the owner tells us otherwise the same week." For a client you've had a couple of years it's one sitting.
Done is a list somebody else could tick
A close checklist that needs you in the room is a set of reminders for one person. The tell is any step that reads "check the usual things." The rest of it never got written down, so it stays with you.
Put on it the steps that fail silently. Every account reconciled to a statement. Zero uncategorized. Nothing parked in Ask My Accountant or whatever your holding account is called. AR and AP agings tie to the balance sheet. Suspense and clearing accounts at zero or explained. Payroll cleared to the payroll report. Prior period locked with a closing date set. And the item you've already had to fix twice for this client. Those are the ones that fail without telling you. You'd never forget to open the file.
Same list for every client, one row per month. A client who needs something extra gets a note in the last column.
What the client owes you, and when
The client has a job in the close and nobody ever told them what it was. Nobody told them in the engagement letter, and nobody told them across all the months the statements arrived late.
The issue on what to charge made the case for saying the scope sentence in week one, before anyone has a reason to be annoyed. The month map is that same move on the delivery side. In week one you tell them what you need, by when, and what happens when it's missing: you close what you can, their numbers are wrong for a month, and you tell them which numbers.
Week one, this is just how you work. Left until the third bad close, it sounds like you're building a case.
The system that fills a firm only helps if there's room for what it brings you. My own firm, SDO CPA, has had a waitlist since June, and the constraint there has never been demand. The front of your month, spent reassembling the same handful of accounts, is the room.
Do this before Friday: pick the client whose close hurts most and write down the four things you re-derive for them every single month. Then start that client's rules file, one line per decision you know you've made twice.
Open last month's close for that client. What was the last thing to clear, and who were you waiting on? Both answers, in a reply, would be genuinely useful to me. The capacity issue is out now and it still needs a wider sample than my own client list.
Operator annex
None of this needs a new app. A sheet, an email address, and two text files.
The close checklist
One sheet, one row per client per month. Column headers first:
Client, Month, Feed categorized, Docs complete, Questions sent, Questions answered, Reconciled, Agings tie, Payroll cleared, Prior period locked, Repeat-fix check, Sent to client, Notes for next monthRepeat-fix check is the column that usually gets left out, and it's the one that compounds. It's a yes or no on whether you looked at the specific thing you've already fixed twice for this client. Notes for next month is where you write the sentence that stops you working the same problem out from scratch in thirty days.
The definition of done, written once and kept where the person doing the close can see it:
This month is closed when:
- Every bank, card, and merchant account is reconciled to a statement
- Zero uncategorized transactions, not just zero over your review threshold
- Nothing is sitting in Ask My Accountant or an equivalent holding account
- AR and AP agings tie to the balance sheet
- Suspense, undeposited funds, and any clearing account are at zero or explained in Notes
- Payroll is cleared to the payroll report and posted to the period it belongs to
- Every question sent this month has an answer in writing, or a rule that made it unnecessary
- The prior period is locked and the closing date is set
- The repeat-fix check for this client is done
- The statements are with the clientThe rule for a box you can't tick: the close still ships. You mark the row done, write the unticked item and the reason in Notes for next month, and tell the client which number is affected. A close that waits for one missing receipt just arrives later, and then it's two closes.
The month map you give the client
Send this in week one, in the onboarding email or right after the kickoff call. Fill in your own dates and cut anything that doesn't apply.
Here's the monthly rhythm, so you know what to expect from us and what we need from you.
From you, every month:
- Bank and card statements by the [5th], if we don't pull them automatically
- Receipts as they happen, forwarded to the address below. Not saved up for the end of the month.
- Answers to our monthly questions within two business days. There are usually a handful and they're short.
From us, every month:
- One message with all of our questions, sent the same week each month
- Your closed financials by the [Nth], once the questions above are answered
If something's still outstanding on your side after the [Nth], we close the month without it. Your statements go out on time and we'll tell you exactly which numbers are affected and what would fix them. It carries to the following month.The closing paragraph is what makes the deadline real without anyone having to charge a late fee. If the which-numbers-are-affected pass turns into real work on a late month, it belongs in your scope sentence and on the invoice.
The capture address
An address, and then two sentences you write once.
Set up a dedicated address that lands wherever your documents live. Then give the client this, once, in writing:
Forward receipts and bills to [receipts@yourfirm.com] as they come in. Photos are fine. You don't need to write anything in the email. If it's a card purchase with no email receipt, take a picture of the paper one and send it from your phone before you leave.That sentence goes in three places: the onboarding email, the bottom of every message you send them for the first month, and a contact card you ask them to save under your firm's name. The contact card is the one that gets it onto the phone, and the phone is where the receipt is.
Then the autoresponder:
Got it, thanks. This is filed for [Firm]'s bookkeeping.
If this one needs an explanation (personal, a new vendor, a job it belongs to), just reply to this email with a few words and we'll attach it.
No reply needed otherwise.Keep a note of who never uses it. Two months of chasing hours next to their name makes the pricing case better than any reminder you could send them.
The weekly pass
Twenty minutes. Same slot. Keep this where you'll see it when the slot fires:
Weekly pass. 20 minutes. Do not close anything.
1. What came in this week that I can't identify? Note it, don't solve it.
2. What's identified but has no document behind it? Note it.
3. What did I decide not to decide? Note it, and mark whether it's a repeat.
4. Send one message per client with everything from 1-3. One message.
5. File anything that came back from last week's message, now, while you're in here.
6. Anything from 3 that's marked a repeat goes in that client's rules file before you stop.
If a client has nothing this week, send nothing. A week with no message is what makes the weeks with one worth opening.The last two steps are the ones that get dropped in a busy week, and an answered question that never got filed still shows up on the 3rd.
The standing rules file
One file per client. One line per decision. Plain words, because the point is that somebody else can read it and act.
[Client] - standing rules
Last updated: [date]
- Fuel station charges under [your documented threshold]: vehicle expense, statement line only
- Transfers to the second operating account: owner draw, unless the owner tells us otherwise in the same month
- [Vendor]: split [70/30] cost of sales / equipment unless the invoice says otherwise
- Anything from [platform]: revenue, gross, with the platform fee booked separately
- Personal charges on the business card: due from owner, and flagged in the monthly message
Anything not on this list that comes up twice gets added here the second time.One line does the work there: anything that comes up twice gets written down the second time.
One prompt (review before you apply anything)
One warning before you paste anything into this. It sees a client's account list, so scrub the names first, every time. And what comes back is somebody else's guesses about your accounts. Edit it into your own standard before anybody works a close from it.
The capture instruction above doesn't get a prompt. It's one sentence and you already have it.
The close checklist is where a prompt earns its keep. Its value is in the done-conditions, and those depend on accounts you actually have:
I run a bookkeeping firm. I'm writing a definition of done for our monthly close, so a staff member can complete a close without asking me anything.
Below is a chart of accounts for one client. Read it and propose the done-conditions that this specific client's close needs, on top of the standard ones: all accounts reconciled to a statement, zero uncategorized, nothing in a holding account, agings tie to the balance sheet, payroll cleared, prior period locked.
I want you to look for accounts that go wrong quietly: clearing and suspense accounts, intercompany, owner accounts, inventory, deferred revenue, anything that should net to zero and won't announce it when it doesn't.
[paste chart of accounts]
Give me a plain checklist a person can tick, in the order they'd work it. Say which items you're unsure about and why. Don't connect to any accounting system, don't pull data from anywhere, and don't write anything to a file. This is a draft for me to edit.House ad. I build this one.
Growthy is bookkeeping software I build. It connects to QuickBooks Online, or you import bank statements, or you upload a CSV. It categorizes the routine transactions automatically and hands the rest to you to review and approve. About 85 percent lands right on a first import. Running my own firm's books on it took our month-end close from about four hours to about 30 minutes, on our own books, covering the categorizing half of the job. It doesn't build your checklist or ask your clients anything. Every judgment in this issue is still yours. See what Growthy does.
Two of these hold their value past this month. The address, because documents keep arriving through it while you're doing something else. The rules file, because a decision written down doesn't come back a third time.