Ask any bookkeeper what actually delays the close and it's rarely the accounting. It's the wait: the missing bank statement, the payroll report nobody downloaded, the merchant processor statement the client swears they'll send "right after lunch." The books are ready. The documents aren't.
So firms buy tools to chase better — request lists, automated reminders, client portals with upload links. The asking gets politer and more persistent. But the close still stalls, because the client is still the bottleneck. And here's the part worth stopping on: for most of what's on that missing list, the client was never the right target in the first place.
Request-list tools do one thing well: they nag on schedule. That's genuinely useful for things only a client can produce. But look at what a typical month-end missing list is actually made of:
None of these documents is missing. Every one of them is sitting in a portal that either your firm or your client can already log into. When you send a reminder for one of these, you're asking a human to be a download robot — and waiting on their lunch break to end.
A document behind a login isn't missing — it's unpulled. Reminders manage people. A close needs something that manages portals.
The reframe that changes month-end: split the missing list in two.
List A — pullable. Anything that exists in a portal on a predictable schedule. This is usually the large majority of a recurring close: statements, reports, payouts, invoices.
List B — genuinely human. Paper receipts, a new signed lease, the one-off invoice that only exists in the client's inbox, anything requiring a decision. This is what reminder tools are actually for.
List A doesn't need a reminder. It needs a dispatch list: for each client × portal × document, is it in, missing, or stuck — and for everything missing, a pull that runs on its own. The chase you're used to shrinks to List B plus a short triage of whatever got stuck.
| Option | What it costs you |
|---|---|
| Remind the client and wait | The close runs at the speed of the slowest client's inbox |
| Log into every portal yourself | Real hours: 20 clients across 30+ portals is 30+ logins, every single close |
| Record each pull once; replay it monthly on your own machine | One-time setup per portal; then the documents land themselves |
The first two are where most firms are. The third is the one worth understanding — and as with statement pulls, there's a right way and a wrong way to build it.
Each portal gets one recorded workflow: log in (on the session you already have), navigate, download the month's document, drop it in the client's folder. Recorded once, it's a fixed program — no AI improvising clicks inside a live bank account — so it does exactly the same thing every month and leaves a log of what it did.
On the first of the month, the whole list runs. What you look at is the roll-up:
# month-end pull list — July close ✓ acme-co / first-citizens checking statement in ✓ acme-co / amex business card statement in ✓ acme-co / gusto payroll journal in ✓ blue-fox / square payouts report in ⚠ blue-fox / regional-cu statement stuck: session expired — log in once, re-run — cedar-llc / signed lease list B → reminder sent
Three states, one glance. In means filed. Stuck means a human moment — usually a fresh login or an MFA prompt — after which the pull resumes. And because each recorded pull replays without any per-run AI, running the whole list every month costs nothing beyond the electricity: the setup effort is paid once and amortized across every close after it.
To pull from a portal, something has to be logged in. Cloud fetchers solve that by storing your clients' credentials on their servers and logging in from a datacenter — which is precisely the pattern banks and processors now device-block, and, more to the point, a liability decision most engagement letters never contemplated. "We keep client banking credentials on a third party's cloud" is a sentence nobody wants to write to a client — or an insurer.
The local version inverts it: the automation runs in your own browser, on your own machine, riding the login session you already hold. To the bank it looks like you, because it is. The credential never leaves your computer — that's architecture, not a promise. For a firm that holds other people's logins, that one sentence is the difference between a tool you can adopt and a tool you have to clear with a lawyer.
The month-end document chase feels like a client-communication problem, so firms keep buying better ways to ask. But most of the missing list was never a communication problem — it's a logistics problem, and the documents are behind logins someone already has. Put those on a dispatch list that pulls them on schedule, on your own machine, and the chase collapses to a ten-minute triage: a couple of stuck logins, and the short human list that reminders were always meant for.
We run done-for-you document pulls for bookkeepers — your machine, your logins, nothing in any cloud, no AI. You watch every recording get made. First client free.
How do bookkeepers stop chasing clients for documents at month-end?
Split the missing list in two. Most recurring close documents — bank and card statements, payroll reports, processor statements, loan statements — live in portals the firm or client can already log into, so they can be pulled on a schedule instead of requested. Only the remainder (receipts, contracts, one-offs) genuinely needs the client.
Don't request-list tools like Content Snare or Keeper already solve this?
They automate the asking — reminders, checklists, upload links — which is right for things only a client can produce. For documents sitting behind a portal login, the client is an unnecessary middleman: pull the document directly and save the reminders for List B.
Is it safe to give a cloud tool my clients' portal passwords?
Storing client banking or payroll credentials on a third party's servers is a liability decision — many engagement letters and bank terms don't allow it, and banks device-block datacenter logins anyway. A local automation rides the login session in your own browser, so no credential ever leaves your machine.
Which documents can be pulled automatically, and which still need the client?
Pullable: bank/card statement PDFs, payroll journals, merchant processor statements and payouts, loan statements, recurring vendor invoices. Still human: paper receipts, signed contracts, one-off emailed bills, anything needing a decision. The dispatch list separates the two.