To collect bank statements from clients every month, send one short request on the same day each month, tell them exactly which files you need and how to send them, and follow up on a fixed schedule. Pick a method each client can actually do, and make replying a one-step task.
Which statement collection method suits each client?
The right collection method is the one a client will use without help every month. Match it to the client's habits: some will forward an email, some will upload to a shared folder, and some will do neither and need you to access the statements yourself.
The main options, with what each asks of the client:
| Method | What the client does | Best for | Watch out for |
|---|---|---|---|
| Forward by email | Forwards the bank's statement email or attaches the PDF | Clients who already get statements by email | Attachments sent as photos; wrong account |
| Shared folder upload | Drops the PDF into a folder you set up | Clients comfortable with a cloud drive | Files in the wrong folder; no reminder when empty |
| Upload link or portal | Opens a link and picks files | Clients who need one obvious place | Forgotten links; links shared beyond the client |
| Client grants view access at the bank | Nothing monthly, after one setup | Clients with a business bank that supports it | Access rules differ by bank; see the last section |
| You download them | Nothing; you log in | Clients who will not do any step | Credential handling; confidentiality terms |
Pick per client, not per practice. A practice can run three methods at once so long as each client's method is written in their record. What breaks is the unwritten method: you remember that one client always sends them by text, and then you take a week of leave.
Think about the client's real environment. A restaurant owner reading email on a phone between shifts will forward a message faster than they will log in anywhere. An office manager may prefer a shared folder because she already works in one. Ask during onboarding; the answer is usually a sentence long. The bookkeeping client onboarding checklist places that question in the first week.
Whatever the method, ask for the bank's own PDF download, not a printout or a photo. A downloaded PDF holds the exact text the bank printed, which is much easier to read reliably than an image.
If you use AutoBankConvert, you can upload the files yourself or forward them to your firm's inbox, and each file is matched to its client. Clients do not need an account; they never log in unless you invite them.
A statement request email clients actually answer
A statement request email that clients answer is short, names the month and accounts, says exactly what to send, and gives one way to reply. Clients ignore long emails and vague asks. A message they can answer in under a minute gets answered.
Four things raise the reply rate:
- A subject line with the month. "March bank statements needed by the 8th" beats "Quick question."
- The account list. Name each account by bank and last four digits, so the client does not guess.
- One action. "Reply to this email with the PDFs attached" is one action. "Log in, download, rename, upload" is four.
- A date. A date gives the client permission to act now.
Request email template
Copy this and change the example values.
Subject: March bank statements needed by April 8
Hi Dana,
To finish March for Example Bakery LLC, I need the March statements for these accounts:
- Example Bank business checking ending 4417
- Example Bank business savings ending 9082
- Example Card business credit card ending 1203
Please reply to this email with the PDF statements attached, downloaded from your bank's website or app. Photos and screenshots take longer to read, so the PDF is better if you can get it.
I need them by April 8 so your books are ready on the 12th. If a statement is not available yet, tell me and I will check back.
Thanks, Sam
The same text works as a monthly template. Send it on the same day each month, so clients learn the pattern, and replace only the month, the date and the account list. If a client has an account that closed, update the list rather than let them ask.
Do not bury the request in a newsletter or add unrelated questions. A separate email for questions about transactions gets those questions answered faster, and keeps the statement request clean.
For a client who prefers calls or texts, send the same details by their preferred channel. The wording stays short. What matters is that the month, accounts, format and date are all there.
Reminder timing for late client statements
Reminder timing for late client statements works best as a fixed schedule written down in advance: a first reminder a few days after the request, a second a few days later, and a direct contact after that. A fixed schedule removes the awkwardness of deciding when to nag.
The table below is an example schedule. Adjust the days to your own close calendar.
| Day | Action | Tone | Example line |
|---|---|---|---|
| Day 1 | Send the request email | Neutral | "I need the March statements by April 8." |
| Day 5 | First reminder, same thread | Friendly | "Checking that the March statements reached you. Reply with the PDFs when you can." |
| Day 10 | Second reminder, plus a call or text | Direct | "March is still open. I can finish as soon as I have these three files." |
| Day 14 | Tell the client what slips | Plain | "Without the statements I cannot close March, so your report will be late." |
Keep reminders in the same email thread, so the client sees the original request and the account list below the new note. Replying to the thread also means you do not repeat yourself.
Two refinements help. Start reminders from the due date you gave, not from the day you sent the request, if the due date is the one the client sees. And log the dates somewhere shared. If a team member sends day 5, the person who sends day 10 should be able to see it.
What if a client is slow every month? Look at the method before the person. A client who never replies to email may answer a text. A client who forgets may do better with a standing monthly reminder in their calendar. If nothing works, move them to a method where you do the download, with clear terms on access.
Capacity affects this too. The more clients you carry, the more reminders you send; see how many clients a bookkeeper can handle for how that load grows.
Clients who send screenshots instead of statements
Clients who send screenshots usually do so because it is the fastest thing they can do on a phone. A screenshot is an image of part of a page, which means it often misses opening balances, account details or whole days of activity. Ask for the full PDF.
Reasons a screenshot falls short:
- It shows only the part of the page that fit on the screen.
- It rarely includes the statement period, the account number or the closing balance.
- Text in an image must be read optically, which can misread digits.
- It cannot be checked against opening and closing balances if those are missing.
Reply the same day, politely, with a short how-to for their bank. "In the app, open Statements, choose March, and tap Download PDF" saves a round trip. Many clients simply do not know the PDF exists. If you serve several clients at one bank, write the steps once and reuse them.
If the screenshot is all you will get this month, record what is missing and tell the client. Use the shot to start, then ask for the PDF to confirm balances. Do not guess at missing lines.
Software handles images differently from PDFs. AutoBankConvert reads scanned and digital PDFs, and a statement that fails its balance check is flagged instead of exported. For what happens to image-only pages and phone photos in a flagging system, see why screenshots get flagged.
Should clients download statements or give you access?
Clients should download statements when they are comfortable doing so, and give you access only when a monthly request keeps failing. Downloading keeps their bank credentials with them. Access saves effort but moves risk to you, and it needs clear written terms.
Compare the two on what matters:
- Credentials. If you log in as the client, you hold or use their password. Some banks provide separate, limited access for accountants. Check what your client's bank offers rather than assuming, and read the bank's own help pages.
- Control. A client who downloads decides which accounts you see. Access shows everything on the login, including accounts you may not need.
- Reliability. Access removes the monthly dependency on the client. Downloads depend on their memory.
- Responsibility. If something goes wrong while you hold access, you are the person who had it.
A reasonable default: ask for downloads, offer view-only bank access to clients who prefer it and whose bank supports it, and avoid keeping client passwords at all. Whatever you choose, write it into the engagement letter, including who can access what and for how long.
Whichever method a client uses, collect the statements into one place per client, then process them as a batch. A month of files from every client is the input AutoBankConvert is built for: you upload or forward them, and each file is matched to its client for conversion, categorization and export.