Why Accountants Still Chase Clients for Bank Statements (And How to Stop)
If you work in an accounting or bookkeeping firm, you already know what the last week of every month looks like. Somewhere in your inbox is a chain of emails asking a client for their bank statements — sent once, chased twice, and still waiting on day eight. Multiply that across 40 clients and a three-person team, and you have a firm that's administratively overwhelmed before the real accounting work even begins.
This guide is for practice managers, senior bookkeepers, and client-facing accountants who want a reliable, repeatable way to collect bank and credit card statements from clients — without the weekly chasing cycle.
Why Collecting Bank and Credit Card Statements Goes Wrong
The problem isn't that clients are uncooperative. Most of them genuinely intend to send their statements. The problem is the system — or rather, the absence of one.
Here's what the typical broken process looks like in practice:
The "reply when I remember" trap
You send a casual email asking for last month's statements. The client reads it, thinks "I'll do that later," and forgets. Three days pass. You follow up. They reply apologising and promise to send it that evening. Two more days pass.
The wrong file problem
When clients finally do send something, it's frequently the wrong document — a payment summary instead of a full statement, a partial export missing the last five days of the period, or a screenshot from their banking app that's too small to read. Now you're back to square one, explaining what you actually need.
The fragmented inbox
Statements for four different accounts arrive across six different emails, sent by two different people at the client's business, over a span of nine days. By the time everything has arrived, you've spent more time managing the correspondence than reviewing the numbers.
The missing account
You reconcile what was sent, raise a query — and only then does the client mention they also have a second business credit card that wasn't included. The period has to be reopened.
Research from Dext found that accountants and bookkeepers spend nearly 5 hours per week just detecting and correcting client data errors — before factoring in the time spent chasing the missing documents that cause those errors in the first place.
A separate survey by CPA Practice Advisor found accounting firms spend an average of 9.3 hours per week on client communication, with document follow-up as one of the primary drivers. The US accounting workforce shrank by more than 17% between 2020 and 2024. Fewer staff, more clients, tighter margins — and the same informal, email-based document collection process that's been in place for a decade. Something has to change.
How to Collect Bank & Credit Card Statements: Step by Step
The fix isn't asking clients more nicely. It's restructuring how you ask, what you ask for, and when the request goes out.
Define every account upfront — at onboarding, not monthly
The root cause of most missing accounts is that nobody ever established a definitive list. At client onboarding, build a complete account register: every bank account, every business credit card, every merchant processor that feeds into the books. Get account nicknames, the last four digits, and the issuing bank for each. Store this list somewhere your whole team can see it. From this point forward, every monthly request references this list explicitly — not "please send your statements," but "please send statements for the three accounts listed below."
Send a structured request, not a casual email
A structured request specifies the exact accounts required, the exact statement period (e.g. 1 June – 30 June 2025), the accepted file formats (PDF, OFX, CSV), and the deadline. It also explains why you need each item — enough to make the client feel they're being asked for something specific rather than pestered. Structured requests get higher completion rates because they remove ambiguity.
Send the request early, with enough lead time
Most firms send document requests too late — five days before the deadline is already a scramble. Send the request at the start of the new period (or on the first working day of the month for monthly bookkeeping). Clients who receive requests early tend to batch-upload everything at once. Clients who receive requests late tend to send documents piecemeal over days.
Use a form or portal, not an email thread
Emailed requests encourage emailed replies — attachments buried in threads, files labelled "scan001.pdf," multiple partial submissions. A dedicated collection form or client portal changes the dynamic: the client can see exactly what's been requested, upload directly to the right fields, and the form won't let them submit until each required file is attached. Your team gets a single clean submission rather than a scattered inbox.
Set automated reminders, not manual follow-ups
Manual follow-up is where the time goes. If a client hasn't submitted by day three after your initial request, an automatic reminder should go out — from the system, not from a person. A second reminder at day six. A team alert at day eight. This keeps the process moving without anyone on your team having to track 40 outstanding requests in a spreadsheet.
Acknowledge receipt and confirm completeness before you close
The most overlooked step. When statements arrive, check them against the account register immediately — not at the point of reconciliation. A 30-second check now prevents a full restart later. Send the client a brief confirmation that everything has arrived and the period is closed for collection.
Review the process quarterly
Clients open new accounts. Credit cards get cancelled. Business structures change. Your account register needs a quarterly review — not an annual one. Add this to your standard quarterly client communication.
Bank & Credit Card Statement Collection Checklist
Use this checklist when setting up a collection request for any client:
- Full list of business current accounts (bank name, last 4 digits, nickname)
- Full list of business savings or deposit accounts
- All business credit card statements (each card separately)
- Merchant processor reports (Stripe, Square, PayPal, etc.)
- Payment processing summaries if used for high-volume retail
- Foreign currency account statements if applicable
- Loan or overdraft account statements if applicable
- Statement period clearly stated (start date to end date)
- File format specified (PDF preferred; OFX or CSV accepted for digital exports)
- Instructions on how to download from online banking (for clients who send screenshots)
- Confirmation from client that all accounts have been included
- Receipt confirmed by your team against the account register
This checklist maps directly to the fields in the GatherMonk bank & credit card statement collection template.
A Real Example of What Good Collection Looks Like
Scenario: Meridian Bookkeeping handles monthly accounts for a retail client running two trading companies under the same ownership. Each company has a business current account, a company credit card, and a Stripe account.
In the old process, the owner would email statements sporadically throughout the month — sometimes sending one company's documents a week before the other, attaching wrong periods, or forgetting the Stripe CSV entirely. Meridian's team typically spent two to three hours per client per month chasing and consolidating.
After switching to a structured collection form, Meridian sends a single request on the first working day of each month. The form lists all six required items explicitly, with the period pre-filled. The owner submits everything in one session. If they miss the deadline, one automated reminder arrives at day four. Average completion time dropped from eleven days to three. Meridian's team recovered approximately six hours of admin time per month across their client base.
Common Mistakes That Keep the Chasing Cycle Going
Asking for "last month's bank statements" without specifying which accounts
Clients with multiple accounts don't know which ones you mean. Always list every account by name.
Accepting partial submissions without flagging the gap
If three of four required accounts arrive, don't file the request as "received." Mark it incomplete and send a targeted follow-up for the missing item only.
Sending requests too close to deadlines
A request sent five days before close leaves no room for the client to gather documents. Two to three weeks of lead time is realistic.
Not having an account register on file
If your team doesn't know exactly which accounts each client operates, you can't send accurate requests. Build the register at onboarding and keep it current.
Treating the monthly request as a one-person job
When only one person on your team knows the client's account structure, holiday cover or staff turnover means the process breaks immediately. Document the account register in a shared system.
Use the Ready-Made Template Instead of Starting From Scratch
You could build a bank and credit card statement collection workflow from emails and spreadsheets — and spend weeks iterating on it. Or you can start from the ready-made template in GatherMonk. The account register fields, statement period selection, format instructions, and automated reminders are already built in. Preview it, adjust the account list for each client, and your first structured request goes out in minutes.
→ See the bank & credit card statement collection template
Frequently Asked Questions
What is the most common reason clients send incomplete bank statements?
Clients send incomplete statements because they do not know which accounts you expect. Without a named account list, most clients send only their main current account. Specifying every account by name in the request is the single most effective change accounting firms can make to their collection process.
How often should I request bank and credit card statements from clients?
For monthly bookkeeping, request statements at the start of each new month for the previous month. For quarterly accounts, request at the start of each new quarter. For annual accounts, send the request six to eight weeks before your preparation deadline to allow time for chasing.
Can clients send screenshots of their online banking instead of PDF statements?
No. Screenshots may be cropped, may not show the full period, and do not carry the same audit trail as a downloaded statement. Always specify downloaded PDF or digital export (OFX or CSV) in every request, not screenshots.
What should I do if a client refuses to use a client portal or form?
Use a structured email template that lists every required document by name with a named attachment convention. Document collection tools like GatherMonk also support email-based submission workflows where clients do not need to log in to a portal.
How does structured bank statement collection help with AML compliance?
A documented, structured collection process creates an audit trail showing that client financial data was obtained systematically and completely — essential for firms with Anti-Money Laundering obligations. An informal email chain does not provide the same audit evidence.
For accounting and finance firms looking to systematise document collection across all client types, see GatherMonk for Accounting & Finance and the Practice Manager resource hub.