Bank statement collection checklist for bookkeeping firms

Every close has that moment. The books are ready, the reconciliations are queued, and two bank statements are nowhere to be found. Nobody can say whether they were never requested, requested and forgotten, or sitting in an inbox under the wrong subject line. Our own close stalled waiting on statements more months than we care to admit, and collecting documents is literally part of our job.

A checklist fixes more of this than you might expect. Statement collection involves a dozen small decisions per client, and unless those decisions get written down once, your team re-makes them every month, differently each time. Below are the two checklists we use at Scale CPA: one you run once per client at onboarding, and one you run every month. Both work with a spreadsheet and a shared drive. The complete guide to collecting client bank statements covers the surrounding process; this post is just the artifact.

Part 1: the per-client onboarding checklist

Run this once when a client signs, and again whenever they open an account.

1. Inventory every account. List every checking, savings, and money market account, every credit card, every line of credit, and any loan that issues its own statement. Then the payment platforms: Stripe, PayPal, Square, Shopify, wherever the client actually sells. Send the list back to the client and get written confirmation that it is complete. The account nobody mentioned at onboarding is always the one that derails a reconciliation in month four.

2. Record the real statement cycle for each account. Banks do not all cut statements on the last day of the month, and credit cards almost never do. For each account, note the cycle closing date and the date the PDF usually becomes available. Skip this and you will spend the first week of every month chasing statements that do not exist yet. The mechanics are in bank statements do not follow calendar months.

3. Pick one access method per account. The realistic options, roughly in order of durability: view-only online access for the firm, an automated retrieval connection through an aggregator, the bank’s accountant-access feature, or the client forwarding PDFs each month. Any of these can work. Leaving it undecided cannot, because then every month opens with a small investigation into how this account gets collected.

4. Get consent in writing. If the firm will log into the account or connect it through an aggregator, get written authorization first and store it with the engagement letter. It protects the client, it protects you, and it makes the security conversation much shorter when a new controller arrives and asks why the firm has bank access. More in client consent for bank connections.

5. Fix the storage location. One firm-controlled drive. One structure: client, then year, then month. Email is a delivery channel; the drive is the record. For US firms, the FTC Safeguards Rule expects access controls around exactly this kind of client financial data, and a pile of statements in a shared inbox fails that test.

6. Set a naming convention and enforce it from file one. Sortable date first, then client, then account.

That is the whole onboarding pass. Thirty minutes per client, once.

Part 2: the monthly ops checklist

Run this on a fixed day each week during close. Fifteen minutes if part 1 was done honestly.

1. Mark what arrived. Keep a grid: one row per account, one column per month. Each cell is received, pending, or missing. A spreadsheet is fine. The format matters less than the habit of looking at the whole book at once instead of client by client.

2. Separate missing from not-posted-yet. Check the cycle dates from onboarding before chasing anyone. A statement that posts on the 12th is not late on the 5th. Chasing clients for documents that do not exist yet burns goodwill you will need for the real gaps.

3. Check connections and logins before you need them. If any account uses online access or an automated connection, verify it still works early in the cycle. Connections break for predictable reasons: changed passwords, expired multi-factor enrollment, and bank-side security reviews. Most large banks, including Chase and Wells Fargo, have security-review flows that can quietly pause third-party access until the client takes action. The failure modes are catalogued in why bank statement connections break.

4. Run an escalation day. Pick one date, say the 10th. On that day, every cell still marked missing becomes a personal ask: a named person, a specific account, a specific statement month. Blanket reminders to the whole client list get ignored. A message that says “the June statement for the Chase operating account” gets answered.

5. File and verify the same day. Every statement that arrives goes into the fixed folder with the fixed name before end of day. Then the one-minute test: can a teammate who did not file it find last March’s statement for any account in under a minute? If not, the filing step is failing and the archive is quietly rotting.

Rolling it out

Notes from running this on our own client book:

Month one is inventory correction. Expect the account list to be wrong for a surprising share of clients. A card nobody mentioned, a dormant savings account, a second Stripe account for a side product. Treat discoveries as normal. Update the list, adjust the grid, move on.

Client-side handoffs decay first. Forwarded-PDF arrangements fail fastest: the person doing the forwarding changes roles, or the bank redesigns its notification emails and the client stops noticing them. Automated connections decay second, usually at a bank security review. Direct view-only access tends to last longest where the bank offers it.

Revisit on a schedule, not after a failure. Quarterly is enough. Re-check access methods, prune closed accounts, correct cycle dates that drifted. Once a year, send the full account inventory back to the client for fresh written confirmation. A new account, a new bank, or a new bookkeeper on the client side triggers an immediate pass through part 1.

Where automation fits

Everything above runs fine on a spreadsheet, and doing it manually at least once teaches you your client book. It is also, nearly line for line, what we automated in StatementFlow after running the manual version ourselves: it learns each account’s actual posting cycle, retrieves the official PDF through Plaid or Mastercard Open Banking when the bank publishes it, files it into the firm’s own Google Drive by client, year, and month, and shows the account-by-month grid with gaps and needed reconnects. It does not extract data from the PDFs; tools like Dext or AutoEntry still do that job. If the monthly checklist is where your close loses days, join the early access list and run the automated version against your own book.