Chasing clients for records is a recurring task
Chasing clients for records eats hours every month and sits on no task list. Give it a calendar rule, an owner, a script and a log.

Ask anyone in a bookkeeping firm where the month goes and chasing clients for records comes up within a minute. Bank statements that have not arrived, receipts in a shoebox, a payroll change mentioned on a call but never confirmed. Yet chasing almost never appears on the firm's task list. It is treated as noise around the real work: a few emails here, a phone call there, done by whoever notices the gap. This post argues the opposite. Chasing is a recurring task like any other, it runs on a predictable calendar, and it deserves an owner, a rule, a script and a log.
Why chasing stays invisible
Most task lists are built from deliverables. The VAT return, the payroll run, the management accounts. Chasing sits in front of all of them, so it gets folded into each one and never written down on its own.
That has three costs. First, nobody owns it, so it starts late. The person doing the reconciliation discovers the missing statement on the day they sit down to reconcile, which is the worst possible day to ask for it. Second, everyone chases differently. One bookkeeper sends a polite email and waits a week, another phones the same afternoon, and the client gets a different experience depending on who is on shift. Third, nobody can see how much time it takes. When we costed a single bank reconciliation step by step, the matching was the cheap part. The hours sat in the waiting and the asking.
Chasing has a calendar
The useful thing about chasing is that it is predictable. You know which records each client sends, roughly when they are due, and which clients are usually late. That is everything a calendar rule needs.
Take a hypothetical firm with 60 monthly bookkeeping clients. Most send bank statements and purchase invoices for the month just ended. A reasonable set of rules might look like this:
- Working day 1 after month end: a standard reminder goes to every client whose records are not yet in.
- Working day 4: a second, more specific message to anyone still missing items, listing exactly what is outstanding.
- Working day 7: a phone call from the client's named contact at the firm.
- Working day 10: escalation to the manager or partner, with a note on the file of what the delay will mean for the deadline.
The exact days will differ by firm and by client, and some clients will need their own rule. The point is that the sequence exists before the month starts, so chasing begins on day one rather than on the day someone runs out of other work.
Give it an owner, and a backup
A task with no owner is done by whoever feels guilty first. Name one person per client who owns the chase, and a backup for when they are away. Often this is the bookkeeper who will use the records, which keeps the context in one place. In some firms it works better as a single coordinator role across many clients, freeing the bookkeepers to do the bookkeeping.
Either can work. What does not work is "the team". If three people can see that a client is late, each one assumes another has asked.
Write the script
Chasing feels like a personal skill, and some of it is. Knowing that one client's finance director responds better to a phone call than to email is genuine know-how. But most of the content of a chase is the same every time, and it can be written down.
A short chasing script per stage covers:
- What to ask for, exactly. "Your March bank statements for both current accounts" beats "your records for March".
- Where to send it. The upload link, the shared folder, or the email address, so the client does not have to reply asking.
- Why it matters now. A plain sentence on the deadline it feeds, without threats.
- Client-specific notes. Who to contact, the best channel, and anything that has gone wrong before.
That last line is where the real know-how lives, so it belongs on the client's record rather than in someone's memory. When the usual contact is on holiday, the backup should be able to read it and chase the same way. Our post on client onboarding as a recurring task suggests capturing these preferences on day one, when the client is easiest to ask.
Keep a chase log
Each chase should leave a line: the date, the client, what was outstanding, how they were contacted, and when the records arrived. It sounds like admin, and it is. It is also the only way to answer questions that otherwise run on gut feel:
- Which clients are late every single month?
- How many working days does the average client take to send everything?
- Which stage of the sequence actually produces the records: the first email, the second, or the phone call?
- How many hours a month does the firm spend asking for things?
Say, for illustration, that each chase takes ten minutes to write or make, and an average client needs three chases a month. Across 60 clients that is 30 hours a month, close to a working week, before anyone opens a ledger. Your own figures will be different. The log is how you find them out, and once you have them you can have a sensible conversation with the clients who drive most of it, about their deadlines or their fees.
A natural place for drafts
Chasing is also one of the more sensible places to try an AI agent in a finance team, carefully. The rules are written, the inputs are known (what has arrived and what has not), and the output is a message a person can read in seconds before it goes. An agent that drafts the day four message for every late client, listing exactly what is missing, and leaves a person to approve and send, removes the dullest half of the job without taking the client relationship away from the people who hold it.
That only works if the calendar rule, the script and the client notes exist first. An agent cannot chase well from "you know what that client is like". This is the pattern behind everything Beaks is built around: name the recurring work, write down how it is done, and only then decide what to hand over and how far to trust it.
One thing to do this week
Pick the five clients your team chases most often. For each one, write down which records you wait for, when you usually ask, who asks, and what finally works. That half page is the start of a chasing calendar, and it will probably show you that the same records are late for the same reasons every month.

