To request missing bank statements from a client, send one message that names the bank, the account's last four digits and the exact statement months still needed. Ask for the bank's own PDF statements, say where in online banking to find them and where to upload them, then check each returned file against the gap before closing the request.
What should a bank statement request name?
A bank statement request should name four things for every missing statement: the bank, the account type, the last four digits of the account number, and the statement period. "Please send your missing bank statements" names none of them. "Cedar Valley Bank business checking ending 3317, the April and May 2026 statements" names all four.
Each detail closes a different door to a wrong answer:
- The bank. Clients with accounts at two banks will send whichever is easier to reach.
- The account type and last four digits. Many clients hold checking and savings at the same bank. Without the suffix, a client may resend a checking statement the firm already has and believe the savings gap is closed.
- The period. Use month names and the year, and add the cycle dates when the bank does not cycle on calendar months, such as "the statement covering March 14 to April 13, 2026".
- The format. Say "the bank's PDF statement". The section on transaction exports below explains why.
Give a reason in one short line. Clients respond better when they know the statement is needed to finish the books or the return, and a missing month is easier to take seriously when it is named as the thing holding up the work.
Keep the list to what is missing. If the firm has eleven of twelve statements, ask for one, not "all of 2026". A request for the whole year invites the client to resend everything, which adds duplicates to review and may still omit the month that mattered.
The list of gaps comes from the statements already in hand. The guide to reading statement period dates to find missing bank statements explains how to build it account by account.
Where clients download past bank statements
Clients download past bank statements from the statements or documents area of their bank's website or app, usually inside each account. The menu name varies by bank, so a request works best when it describes what to look for, such as a list of monthly statements by date, instead of naming one button.
Point the client at the website rather than the phone app when you can. Many clients only ever use the app's transaction list and do not know a separate statement archive exists. A short line such as "sign in on a computer, open the account, and look for Statements or Documents" is usually enough to send them to the right place.
For a fuller set of instructions, a numbered step list is worth sending with the first request of the year. The post on how to collect bank statements from clients includes an example step list a firm can adapt for its own clients.
Name the year as well as the month. Archives usually open on the current year, and a client looking for "April" may download April of this year rather than the year the firm needs.
Ask the client to save each statement as its own PDF. One file per statement is easier to check against the request than a single combined download, and it avoids a client printing to paper and scanning the pages back in.
Statement request email template for one or several gaps
A statement request email template gives the client one ready list of what is missing, account by account, with a clear place to send it and a date. Use the template below for a single gap or several; add one bullet per missing statement and leave out anything the firm already has.
Example request email with placeholders
The firm, client, bank and dates below are fictional placeholders for the example. Replace each bracketed field before sending.
Subject: [Client name]: [number] bank statements still needed for [year]
Hi [first name],
We have most of your [year] bank statements and need [number] more to finish your [books / return]:
- [Bank name] [account type] ending [last four digits]: [month and year] statement
- [Bank name] [account type] ending [last four digits]: statement covering [start date] to [end date]
Please download each one as the bank's PDF statement, not a transaction export or screenshot, from the Statements or Documents area of online banking. Upload them to your link: [upload link].
If a month does not appear online, reply and tell us which one, and we will help you ask the bank for a copy.
We need these by [date] to stay on schedule.
Thank you, [Preparer name], [Firm name]
Filled in, the list for a fictional client, Okafor Design Studio, might read: "Cedar Valley Bank business checking ending 3317: April 2026 statement" and "Cedar Valley Bank savings ending 6604: statement covering September 1 to November 30, 2026".
Keep the subject line specific. A count and a year tell the client this is a short task, which helps the message get opened.
When the request is one of several follow-ups across the season, the timing and tone of each reminder matter as much as the list. The post on the tax document reminder email template for each stage covers the sequence from first nudge to final notice. Schema CPA drafts a reminder that lists the statements it found missing in a client's run; a preparer adds any download guidance, edits the draft and sends it from the firm.
Why a transaction export is not a bank statement
A transaction export is a list of account activity that the client generates on demand, usually as a CSV file, a spreadsheet or a screen of recent transactions. A bank statement is the bank's own record for a fixed period, with a beginning balance, an ending balance and every transaction between them. Only the statement closes a gap.
The difference shows up in three ways. First, an export has whatever date range the client chose, which may start a day late or end a day early. Second, many exports carry no beginning or ending balance, so the firm cannot prove the period connects to the statements on either side. Third, an export can be filtered, sorted or edited before it is sent, and nothing on it shows whether that happened.
Screenshots have the same problems and add new ones. They often cut off the account number, the period or the last few transactions, and a phone screenshot of a scrolling list may skip rows between captures.
The balance test is what makes a statement useful. The firm checks that each statement's beginning balance equals the previous statement's ending balance. The method is set out in how to tie out bank statements month to month, and it only works with documents that print both balances for a defined period.
A transaction export can still be useful for other work, such as importing activity into a spreadsheet. It is a supplement to the statement, not a substitute for it.
When the client's bank no longer shows old statements?
A client's online banking may stop short of the period a firm needs. When a statement is older than the online archive reaches, the client has to ask the bank for a copy of the statement directly, by phone, by secure message or at a branch.
Ask the client to tell you as soon as they find the gap in the archive, not after a week of silence. The template above includes a line for this. A reply that says "April is not there" is useful; a request that goes unanswered is not.
Give the client the words to use with the bank. A request for "copies of the monthly statements for checking ending 3317 for April and May 2026" is easy for a bank employee to act on. Ask them to request PDFs if the bank can provide them, so the firm does not receive paper that has to be scanned.
Set expectations on timing. A copy request can take longer than a download. Ask the client to find out from the bank how long the copies will take and whether there is any charge, and to pass that on.
A copy request is not a dispute. In the CFPB's text of Regulation E, section 1005.11, the list of things that are not errors includes a request for information for tax or other recordkeeping purposes. For consumer accounts, the regulation's error-resolution steps therefore do not govern an ordinary request for old statements for tax records, so the client should treat it as a normal service request.
Accounts that have since closed are often the hardest. The client may no longer have online access at all, and a call to the bank is the only route.
Checking the returned bank statements before closing the request
Checking the returned bank statements means confirming that each new PDF is the right document for the right account and actually fills the gap, before the request is marked closed. A file arriving is not the same as the gap closing. Five quick checks on each statement settle it.
Five-point check for each returned PDF
- Bank and account. The bank name and the last four digits match the line in the request.
- Statement period. The period printed on the statement covers the missing days. It should start the day after the previous statement ended and end the day before the next one starts.
- Beginning balance. The beginning balance equals the ending balance on the previous statement in the file.
- Ending balance. The ending balance equals the beginning balance on the next statement in the file.
- Complete pages. Every page is present, usually shown as "Page 1 of 4" through "Page 4 of 4", and nothing is cropped or blank.
If any check fails, reply about that statement only, saying what came back and what is still needed. "We received the March statement for savings ending 6604; we still need April for checking ending 3317" keeps the list short and accurate.
Once all five checks pass, the account's run is continuous across that period. Proving the run connects is not the same as reconciling the account to the books, which compares each statement line with the ledger. The guide on what a bank reconciliation is explains that next step. For how Schema CPA tracks every client's received and missing items in one place, see the client tracker demo.