The symptom
We chase clients for the same documents every single month
The short answer
The chasing exists because nobody has automated the comparison, not because clients are difficult. Somewhere there is a list of what a complete month looks like, and somewhere else there is a pile of what actually arrived. A person compares the two, writes an email about the difference, and does it again next week. The comparison is mechanical, it happens dozens of times a month, and it is the only part that needs to stop being human.
The shape of the fix is: a required-items checklist per client, an intake channel where arrivals are matched against it automatically, a gap list produced on a schedule, and precise reminders that name the specific missing items. Critically, the reminders must stop the moment the item arrives. Nearly every team that automates this without that rule ends up chasing clients for documents they already sent, which costs more goodwill than the original delay.
It is also worth being clear about why this is permanent work rather than a one-off tidy-up. The records businesses are expected to keep are set out publicly by the IRS, and they recur every period, for every client, forever. This is not a backlog to clear; it is a monthly cycle to instrument.
Why the same clients are late every month
Usually because your request is vague and theirs is not urgent. Send me your statements is a request that requires the client to do the thinking; send the November statement for account ending 4471, which is the only item still outstanding, is a request that takes them ninety seconds. Specificity is the single biggest lever here, and it is free.
The other reason is that the request arrives at the wrong time. A reminder sent when the bookkeeper is not at their desk is a reminder that will be read and forgotten. Once the gap list is automated, sending the same reminder consistently on a predictable day costs nothing and outperforms sending better-written ones at random.
What has to exist before automation helps
A per-client required-items list that is genuinely correct. Most firms have a standard checklist and a set of undocumented per-client exceptions that live in a senior person's memory. Automating against the standard list produces confident, wrong reminders, which is worse than the status quo.
And one intake channel. If documents arrive by portal, email attachment, text photo and paper, then matching arrivals to requirements has to happen four times in four places. Narrowing intake to one or two channels before automating anything is unglamorous and does more for the problem than any software.
Before and after — yours to use, nothing to buy
Before and after: the monthly chase
The comparison we would put in front of a firm before scoping anything. Note how much of the improvement is in the first three rows, which are process rather than software.
| Step | Today | After |
|---|---|---|
| What complete looks like | A standard checklist, plus per-client exceptions held in one senior person's memory. | A per-client required-items list, written down, including the exceptions. Reviewed once a quarter. |
| How documents arrive | Portal, email attachments, photographed pages by text, and occasionally paper. | One or two channels only. Anything arriving elsewhere is forwarded into them by rule. |
| Matching arrivals to requirements | A person opens each file, works out what it is and which client it belongs to, and ticks a list. | Built: incoming files are identified and matched against the checklist, with anything ambiguous queued for a person rather than guessed. |
| Knowing what is missing | Someone reviews each client near the deadline, which is when there is least time to react. | A gap list regenerates on a schedule. The status is available on any day of the month, not just at the end. |
| The reminder | A general nudge, written from scratch, asking for outstanding items. | Built: a reminder naming the exact missing items for that client, sent on a predictable schedule. |
| When the document arrives | The next reminder goes anyway, because it was already drafted or the sender did not check. | Reminders stop automatically on receipt. This rule is not optional — it is the difference between helpful and irritating. |
For scale, an illustrative three people spending four hours a week each on chasing, at a fully loaded $40 an hour with 65 percent of it rules-based, is 7.8 hours a week and 374 hours a year — around $14,976 of annual capacity against an illustrative $8,000 build, a payback of roughly 6.4 months. Those numbers come from Soxoa's public estimate_automation_roi tool on those inputs and are illustrative, not a quote.
Terminology bridge
What consultants call this
This is a well-worn problem with established vocabulary, mostly borrowed from accounting operations.
PBC means prepared by client — the standard name for the list of items you are waiting on.
The automated comparison of what arrived against what was required. The core build.
The route documents travel to reach you. Fewer is better, and narrowing them is free.
The per-period list of everything that must exist before work can complete.
The logic that stops a reminder once the item arrives. Ask about it explicitly; it is the most commonly missing piece.
Say PBC list and missing-document detection to any accounting-technology vendor and you will get straight to whether their product does the comparison or just stores the files.
Common questions
Fair questions
Will clients resent automated reminders?
Not if the reminders are more specific than what you send now and stop the moment they comply. Clients generally dislike vagueness and repetition, and automation done properly reduces both. Done badly it amplifies both, which is why the suppression rule matters more than the reminder copy.
Can the system tell what a document is?
For common, well-formed documents, usually. For a photograph of a statement taken at an angle, sometimes. The right design routes low-confidence matches to a person with the file attached rather than filing them under a guess, and the vendor documentation linked below is candid about what degrades that confidence.
We only have thirty clients. Is this worth it?
At thirty clients with two reminder cycles each, this is one of the more clearly justified small builds we see — it was the highest-confidence opportunity in our published accounting assessment example. Below about ten clients, a well-kept shared checklist and a recurring calendar block will do the job for free.
Sources
Where this comes from
- What kind of records should I keep
Internal Revenue Service
The federal list of records a business is expected to retain — the reason document collection is a recurring obligation, not a one-off.
- Enterprise Document OCR
Google Cloud, Document AI documentation
Vendor documentation for the read-and-extract step, including which document qualities affect accuracy.
- Manage Gmail filters
Google Workspace developer documentation
The rules layer that routes mail before a person sees it.
- AI Risk Management Framework (AI RMF 1.0)
National Institute of Standards and Technology
The public reference for deciding where a human checkpoint belongs in an automated process.
- Occupational Employment and Wage Statistics
U.S. Bureau of Labor Statistics
Free wage data by occupation and metro area — the honest starting point for the hourly rate in any of the worksheets below.
Last reviewed: September 1, 2026 · every source link checked on that date
Where to go next
Three useful next reads
How accounting firms sequence this work, and which parts they deliberately keep manual.
Read it →See the evidenceAccounting assessment exampleMissing-document detection assessed end to end, including the pilot scope and what would make it fail.
Read it →What it costsHow we workThe research-first process, and the written success gate a pilot has to clear.
Read it →Free · No strings
See whether your document chase is worth automating
Share your company, website, and email. We research your operations, show the sources and assumptions, and send a private assessment link when it is ready — no call required to read it.
Other things owners tell us