Why the request gets ignored
“Could you send me your bank statements when you get a chance?” is a reasonable sentence and a terrible request. Look at what it actually asks the client to work out before they can act:
- Which accounts? All of them, or the main one?
- What period? Last month, last quarter, since you last asked?
- What format? A PDF download, a CSV export, a photo of the app?
- By when? “When you get a chance” means never, and both of you know it.
- Where do they send it? Reply to this email, or the thing you mentioned in March?
Five decisions, each small, and every one of them a reason to deal with it later. The request is not ignored because your client is disorganised. It is ignored because you moved the work of specifying the task onto the person least equipped to do it. Every template below is built on one principle: make the decisions for them.
The one-line version
The six specifics every request needs
| Specify | Bad | Good |
|---|---|---|
| The accounts, by name | Your bank statements | Barclays current account ending 4471, and the Amex card |
| The exact period | For last month | 1 to 31 August, the full month including both end dates |
| The format | Whatever's easiest | The PDF download from online banking, not a screenshot |
| A real deadline | When you get a chance | By Friday the 5th, so your accounts are ready on the 15th |
| One destination | Send them over | Upload them here: [one link] |
| The consequence, stated calmly | (omitted) | If they arrive after the 5th your August figures move to the following month |
The last row is the one most practices leave out, and it is the one that does the work. Not as a threat — as information. A client who does not know that late statements delay their own numbers has no reason to prioritise it over anything else in their inbox. A client who does know will usually act, because the deadline is now theirs rather than yours.
PDF or CSV — ask for the right one
Ask for the wrong one and you get to have this conversation twice, which costs you more than getting it right first time.
- PDF for reconciliation, verification and anything that will be shown to a third party. It carries the bank’s own formatting, the running balance and the statement period, which is what makes it evidence. This is the default ask.
- CSV when you are importing transactions because a feed is missing or broken. Faster to work with, but it is an export rather than a statement, so it does not prove the closing balance.
- Both for a catch-up or clean-up engagement covering many months. The CSV to load the data, the PDF to check you loaded it correctly. Say that you want both and why, or you will get one and have to ask again.
Never accept a screenshot or a photo of a phone screen as a bank statement. It has no statement period, no running balance, and no way to show the page you were not sent. There is a template below for redirecting that politely.
Template 1: the first request
For a new client, or the first time you ask a particular client. Longer than the others because it sets the pattern for every month afterwards.
The click path is worth including the first time. It costs you two lines and removes the most common genuine reason for delay, which is that the client does not know where the statements live in their banking app. Drop it from later months.
Template 2: the standing month-end request
Once the pattern is established, shorter is better. Same accounts, same format, same day every month. If this email is not identical each month, you are re-teaching the client the process every time.
The closing question earns its place. It costs nothing, it frequently surfaces the asset purchase or the loan drawdown you would otherwise find on the 14th, and it gives the client a low-effort way to reply — which makes them more likely to also do the high-effort part.
Template 3: the chaser
Send this once, on the day after the deadline. Not three days later, when the delay has already cost you the slot in your own schedule.
Three things make this chaser work. It shows what has already been received, so the client sees credit for the part they did. It names one specific outstanding item rather than repeating the whole list. And the last line gives them a way to respond that is not compliance — a client who is embarrassed about being late will often reply to “tell me what is going on” when they would ignore “please send the statement”.
If you are on the third chaser rather than the first, the problem has stopped being the wording. The escalation for a client who never sends anything covers what to do at that point, including the version where you change the engagement rather than the email.
Template 4: the client who keeps sending screenshots
Frequent, and annoying to correct without sounding ungrateful — they did do the thing you asked, just wrong. Lead with why, not with the rule.
“You have the bank feed — why do you need statements?”
A fair question and worth having a straight answer ready, because a client who thinks the request is busywork will deprioritise it forever.
The feed shows me the transactions. The statement proves the list is complete. Feeds drop transactions, duplicate them, and silently stop when the bank’s authorisation expires — often for weeks before anyone notices. Reconciling the feed against the statement balance is the check that catches it. It is the difference between books that look right and books that are right.
That answer is also a small piece of positioning for your own practice. A client who understands that you verify rather than assume is a client who values the work more, and argues about the fee less.
How to stop asking every month
The templates above are a patch on a structural problem. If you send twelve near-identical statement requests a year per client, and you have thirty clients, that is 360 emails you are composing, sending and tracking by hand — plus the chasers, which is where the real time goes.
Three ways out, in order of how much they help:
- Fix the feed first. A working feed plus a monthly statement for the reconciliation check is far less work than importing everything by hand. Some of what you chase is a symptom of a connection that broke in February.
- Make the request identical every month. Same day, same subject line, same accounts, same wording. Clients learn patterns. They do not learn one-off emails.
- Stop composing it at all. The request is the same every month, so it should be set up once and then repeat on its own, with the reminders going out without you deciding to send them.
That third one is the job ClientVault does. You build the item list once — accounts named, instruction attached to each, format specified — set it to repeat monthly or quarterly, and it goes out on schedule. The client opens a link with no account and no password, uploads as many files as they want against each item, and the reminders for whatever is still missing go automatically at day 3, 7 and 14. You see what is outstanding without reading back through an email thread.
It is free for three clients, and the comparison page is honest about where the established alternative in this category is better — including its security certification, which we do not have. If you want the document list itself rather than the wording, the free month-end close checklist builds one for your client’s industry and cadence.