It's 10pm. A client's self-assessment is due tomorrow. You've asked three times for bank statements — twice by email, once by WhatsApp. The attachment finally lands in your inbox. You open it. And your stomach drops.
It's the wrong account. Or three months instead of twelve. Or — somehow — a photo of a laptop screen taken at an angle that defies physics.
Every UK bookkeeper knows this moment. You've cleared your evening for this client. You've planned your workflow. And now you're staring at a file that's about as useful as a chocolate teapot. The deadline hasn't moved, but your usable data just vanished.
This happens to every bookkeeper. You are not alone. In conversations with UK accounting professionals — on forums, at conferences, in day-to-day practice — wrong or incomplete bank statements from clients comes up again and again as one of the top three workflow-killers. The difference between a stressful evening and a manageable one isn't whether mistakes happen. It's what you do next.
This guide gives you exactly that: what to do next. How to spot the problem in 30 seconds. How to talk to your client about it without damaging the relationship. When to fix the statement yourself and when to push back. And how to prevent these situations from recurring — because processing the wrong statement means redoing the work — or worse, filing incorrect figures with HMRC.
The 6 Most Common Client Bank Statement Mistakes (And How to Spot Them Immediately)
Before you can fix a problem, you need to identify it. These six mistakes account for the overwhelming majority of "wrong statement" situations. Learn to spot each one in under a minute, and you'll save yourself hours of wasted processing time.
1. Wrong Date Range
The client sends 3 months when you need 12. Or January–March instead of April–June. Spot it: Look at the statement period header on page 1. Compare it to the tax year or reporting period you requested. Don't skip this check — even if the file name says "Full Year.pdf".
2. Wrong Account
Personal account instead of business. Savings account instead of current. Or an old closed account they forgot about. Spot it: Check the account name, sort code, and last four digits against your records. A client with three accounts will send the wrong one roughly 40% of the time.
3. Missing Pages
The statement cuts off mid-month. Pages 4–7 of a 12-page statement are absent. Spot it: Check the page numbering (e.g., "Page 3 of 12"). If your PDF has pages 1, 2, 3, 8, 9 — you're missing a chunk. Also scan the final page for a closing balance — no closing balance usually means missing pages.
4. Photo Instead of PDF
Client opens their banking app on their phone, takes a photo of the screen with another phone, and emails it. Blurry reflections, cropped edges, text at an angle. Spot it: You'll know immediately — but the damage is time lost. These are almost never usable for straight data entry.
5. Wrong Format
A CSV where all columns are merged into one. A password-protected PDF with no password. A screenshot pasted into a Word document (yes, this happens). Spot it: Open the file and try to work with the data. If you can't select individual columns or rows, or if the file demands a password the client hasn't provided, you've got a format problem.
6. Duplicate Statements
The same January–March period sent twice — once as a bank download, once as a paper scan. Spot it: Compare opening balances, date ranges, and file sizes. If two files cover the same dates with identical transactions, one is a duplicate. This is the easiest mistake to miss because both files "look right" individually.
How to Communicate with Clients About Bank Statement Errors — Professional Scripts
The hardest part of receiving a wrong statement isn't the technical fix — it's the conversation. You don't want to sound frustrated or accusatory. You don't want to make the client feel incompetent. And you definitely don't want to damage a relationship you've spent years building.
Here are professional, ready-to-use scripts for the four most common scenarios. Copy and adapt these — they're designed to be direct enough to solve the problem, warm enough to preserve the relationship.
Script 1: Wrong Date Range
Subject: Quick clarification on the bank statements you sent
Hi [Name],
Thanks for sending these over so quickly — really appreciate it.
I've just checked the statement dates, and they cover January to March 2026. For your self-assessment we need the full tax year — that's April 2025 through to March 2026. It's a 12-month window, not the calendar year, which catches a lot of people out.
Could I ask you to download the full 12 months from your online banking? It's usually just a date range selector in the statements section — select 6 April 2025 to 5 April 2026 and it should generate the full PDF. Should take about 2 minutes.
If you get stuck, I'm happy to talk you through it over the phone.
Thanks,
[Your name]
Script 2: Wrong Account
Subject: Statement check — can we confirm the account?
Hi [Name],
Thank you for sending your statements through.
I've noticed the statements appear to be from your [savings/personal] account (sort code ending [XXX]). For the bookkeeping I need the [business/current] account — that's the one ending [last 4 digits].
It's an easy mix-up — especially if you have multiple accounts showing on your banking app. Could you resend from the [name of correct account] when you have a moment?
No rush — but the sooner I get it, the sooner I can get your figures ready.
Best,
[Your name]
Script 3: Photo Instead of a Proper Statement
Subject: Bank statements — can we go digital?
Hi [Name],
Thanks for sending the photo of your banking screen.
Unfortunately, photos don't give me the level of detail HMRC needs — the text needs to be machine-readable for accurate data entry, and photos tend to blur or distort the figures. It would take me several hours to retype everything manually, and even then there's a risk of transcription errors.
Could you download the actual PDF from your banking app instead? On most UK banking apps, you tap 'Statements', select the date range, and choose 'Download as PDF'. It usually takes under a minute and gives us exactly what we need.
If your app doesn't offer PDF downloads, a CSV export works too — or you can log in on a computer browser where the download option is usually more visible.
Let me know if you need a hand — happy to walk you through it.
Cheers,
[Your name]
Script 4: Missing Pages / Incomplete Statement
Subject: Your bank statements — looks like a few pages are missing
Hi [Name],
Hope you're well. I've been going through the statements you sent, and it looks like a few pages might not have come through.
The PDF shows transactions from January through to mid-February, but then it cuts off. I'm missing the second half of February and all of March. This sometimes happens if the download is interrupted or if the PDF didn't fully generate on the bank's side.
Could you try downloading the statement again for the full period? The page count should show on the bank's download screen — if it says something like '12 pages', make sure all 12 come through before you hit send.
If you're emailing from a phone, switching to a computer browser sometimes helps with larger statement files.
Thanks for sorting this — I know it's a faff, but getting the full set means I can give you accurate figures without having to chase you again later.
All the best,
[Your name]
When You Can Rescue a Bad Statement (And When You Should Push Back)
Not every problematic statement needs to be sent straight back to the client. Some issues can be fixed on your end — especially with the right tools. Others genuinely require the client to resend, and pushing through with bad data is worse than asking again.
Here's a practical decision framework for the six most common scenarios:
Rescue or Request: A Decision Framework
✅ Rescue (fix it yourself)
Scanned PDFs — AI tools with OCR can extract data from properly scanned statements.
CSV with formatting issues — Merged columns or odd date formats can be cleaned with bank-specific AI converters.
Unusual bank formats — Credit unions, building societies, and challenger banks. Many AI converters handle these.
Duplicate statements — Quick to identify and discard. No client action needed.
❌ Request (client must resend)
Wrong date range — No tool can conjure data that isn't in the file.
Wrong account entirely — You need transactions from account A, not account B. Resend required.
Missing pages — If 4 pages out of 12 are absent, the data is incomplete. No amount of AI fixes that.
Photos of screens — In almost all cases, unusable. Push back and request the digital original.
The acid test: Is the right transaction data physically present in the file? If yes — even if it's hard to read — a good AI conversion tool can probably extract it. If no — the wrong period, wrong account, or physically missing pages — no tool can help. Push back.
How to Set Up a Bank Statement Request System That Prevents Client Errors
Prevention beats cure — and most client statement errors aren't caused by carelessness. They're caused by vague instructions. When you say "send me your bank statements", a client hears "send me something that looks like a bank statement" — and they'll interpret that in ways you'd never predict.
Here's a system that dramatically reduces errors by removing ambiguity at every step:
1. Create a Standardised Request Template
Stop writing fresh requests every time. Create one email template with blanks you fill in per client. It should specify:
- Exact date range: "I need statements covering 6 April 2025 to 5 April 2026" (not "last year's statements")
- Account identifier: "Your business current account ending 4821" (not "your bank statements")
- Acceptable formats: "PDF download from your banking app or website" (not "whatever you've got")
- Deadline: "Please send by Friday 15th" with a brief note on why (tax deadline, month-end close)
2. Give Clients a One-Page Visual Guide
Most clients don't know what a "statement period" is. Create a simple one-page PDF — annotated screenshot of a typical bank statement — with arrows pointing to: the statement period, the account number, the page count, and the download button. Send this once, and refer to it every time. It takes 20 minutes to make and saves dozens of back-and-forth emails per year.
3. Use a Pre-Send Checklist
Add this to your request email:
- Does this cover the full date range I asked for? Check the dates on page 1.
- Is this the correct account? Check the account name and last 4 digits.
- Have I included all pages? Check the page count at the bottom of each page.
- Did I send it as a PDF? Please don't send photos of your screen.
4. Enforce a File Naming Convention
Ask clients to name files like this: ClientName_AccountType_YYYYMMDD_to_YYYYMMDD.pdf. For example: JSmith_BusinessCurrent_20250406_to_20260405.pdf. This forces the client to actively check what they're sending — the act of typing the date range makes them verify it. And it gives you instant visual confirmation when the file arrives.
5. Bake It Into Your Engagement Letter
Add a short clause to your engagement letter: "To ensure timely and accurate processing, please provide bank statements as PDF downloads covering the full requested period. Statements provided in alternative formats (photos, incomplete date ranges, or incorrect accounts) may delay processing and may incur additional charges for rework." This sets expectations from day one and gives you a professional reference point if you need to push back.
6. Use Pre-Deadline Reminders for Repeat Offenders
For clients who've sent wrong statements before, send a gentle nudge a week before the deadline: "Just a quick note — when you send this month's statements, the period I need is [dates]. The correct account is [account]. PDF format please. Let me know if you need help finding them." This 30-second email prevents the 30-minute fix later.
5 Common Mistakes Bookkeepers Make When Handling Problem Statements
It's not just clients who make mistakes. When you're under pressure — deadline looming, half a dozen clients waiting — it's easy to cut corners you'll later regret. Here are the five most common bookkeeper errors when dealing with problem statements:
1. Assuming the Data is Correct Because the File Opened
The PDF opened. The numbers look plausible. You start processing. Two hours later, the closing balance doesn't reconcile — because you were working from a statement that covered the wrong period. The fix: Always do a 30-second opening balance/closing balance/period check before you process a single transaction. It's the cheapest quality control you'll ever implement.
2. Manually Retyping Instead of Using Conversion Tools
You receive a scanned statement or a poorly formatted CSV. Instead of running it through a conversion tool, you open Excel and start typing. An hour later, your wrist hurts and you've probably made three transcription errors. The fix: Use an AI bank statement converter. Modern tools like BankScan AI process statements in under 30 seconds — PDF, CSV, or scanned — and output clean, formula-ready Excel. The time-cost equation is brutal here: 30 seconds of upload vs. 45 minutes of typing.
3. Not Checking the Statement Period Against the Tax Year
The client sends "last year's statements." You process them. Only later do you realise they meant the calendar year (January–December) and you needed the tax year (April–April). Now the figures are wrong and you're unpicking work. The fix: Never assume "last year" means the tax year. Always specify the exact dates and verify them on receipt.
4. Accepting Photos of Statements as Usable Records
A client emails a phone photo of their laptop screen showing their banking app. You squint, type out what you can read, and file the return. This creates three problems: (1) transcription errors are almost guaranteed, (2) there's no audit trail — you can't prove the statement wasn't altered, and (3) MTD rules require digital records. A photo of a screen is not a digital record. The fix: Always push back on photos. If the client genuinely can't access online banking, ask them to visit a branch and request printed statements — then scan them properly.
5. Not Documenting the Error for the Client File
You resolve the issue — the client sends the correct statement, you process it, you file the return. But you never recorded that the first submission was wrong. Six months later, HMRC queries a figure and you can't explain why the books were updated after the initial filing deadline. The fix: Always note in your working papers: "Client initially provided statements for [wrong period/account]. Corrected statements received [date]. Processing completed [date]." This is a 20-second note that could save you a lot of explaining later — and it's good compliance practice under MTD record-keeping requirements.
What to Do Step by Step When You Receive a Problem Statement
When a statement lands in your inbox and something feels off, run through this checklist. It turns the moment of frustration into a systematic, professional process:
- Open the file immediately — Don't save it for later and assume it's correct. Open it within minutes of receipt. The faster you spot an issue, the faster you can resolve it — and the less pressure you're under.
- Scan for the obvious — Check the statement period on page 1. Check the account name and number. Glance at the final page for a closing balance and correct page count. This takes 30 seconds.
- Spot the specific error — Is it the wrong date range? Wrong account? Missing pages? Format problem? Refer to the six common mistakes above and categorise what you're dealing with.
- Decide: rescue or request — Can an AI tool fix this? Or does the client genuinely need to resend? Use the decision framework above. If it's a quick fix, process it. If not, move to step 5.
- Communicate clearly — Use one of the script templates above. Be specific about what's wrong and what you need. Give a clear, one-step action for the client. Don't make them guess.
- Document the interaction — Note in your working papers that the initial submission was incorrect, what the issue was, and when the corrected version arrived. This protects you if HMRC or the client queries the timeline later.
- Process the corrected statement — Once you have the right file, use your normal workflow. If you're processing multiple clients' statements, consider a tool that handles bulk uploads and auto-detects bank formats — it removes another layer of potential error.
This entire process — from opening the file to sending the client email — should take under five minutes. The goal isn't to eliminate errors (you can't control what clients send). The goal is to catch them fast, resolve them professionally, and keep your workflow moving.
When You Do Have the Right File — Process It in Seconds
BankScan AI processes 16+ UK bank formats — PDFs, CSVs, and scanned statements — in under 30 seconds. Our colour-coded confidence system highlights transactions that need your attention, so you can spot problematic data at a glance. Upload, review, export to Excel. No manual typing. No format headaches. Just clean data, ready for Xero, QuickBooks, Sage, or your working papers.
Try BankScan AI Free →Frequently Asked Questions
What do I do if my client sends bank statements for the wrong tax year?
First, don't process the statements — even partially. HMRC requires transaction-level data for the correct tax year, and mixing periods means you'll have to unpick everything later. Send your client a clear, specific request: state the exact date range you need (e.g., "6 April 2025 to 5 April 2026"), the account name or last four digits of the account number, and the format you require (PDF preferred). If the client struggles to locate the right statements, guide them to their online banking archive — most UK banks keep 7 years of statements. For clients who are repeatedly confused about tax years, send them a simple one-page PDF showing which calendar months map to which tax year. You'd be surprised how many sole traders think the tax year matches the calendar year.
Can I use a photo of a bank statement for bookkeeping?
In almost all cases, no — at least not directly. A smartphone photo of a bank statement introduces several problems: (1) poor lighting, angles, and blur make manual data entry error-prone; (2) standard OCR tools struggle with smartphone photos because of lens distortion and uneven text; (3) photos have no digital audit trail — you can't prove the statement hasn't been edited; (4) HMRC expects "accurate and complete" records under MTD rules, and a blurry photo of a screen doesn't meet that standard. That said, AI-powered tools with advanced OCR — like BankScan AI — can sometimes process clear, well-lit photos of printed statements if the text is legible and the full page is captured. But even then, it should be a last resort. Always ask the client for the original PDF or a CSV export from their banking app first. If they genuinely can't access online banking, ask them to visit a branch and request printed statements, then scan them properly.
How do I tell a client their bank statements are unusable?
Be direct, specific, and helpful — never accusatory. Start by acknowledging their effort ("Thanks for sending these over so quickly"), then state the problem clearly and neutrally ("I've noticed the statements cover January to March 2026, but we need April 2025 to March 2026 for the tax year"). Explain why it matters in plain language ("HMRC needs the full 12 months, so I can't submit with only 3 months of data"). Then give them a clear, one-step action ("Could you download the full 12-month statement from your online banking and send it as a PDF? It usually takes about 2 minutes"). End by offering help ("If you're unsure how to find it, I'm happy to talk you through it"). The key is making it feel like a minor fix, not a major failing — you're solving a problem together, not assigning blame.
What's the fastest way to check if a bank statement covers the right period?
Before doing any processing work, do a 30-second "period check": open the PDF, scroll to the first page, and look at the statement header. Every UK bank statement prints a "Statement Period" or date range at the top of page one — usually something like "1 January 2026 to 31 March 2026". Compare this against the tax year or reporting period you need. Then scroll to the last page and check the final transaction date and closing balance date — these should match the end date of the stated period. If anything looks off, flag it immediately. A second fast check: scan the first and last dates of the actual transactions listed. If the first transaction is 15 March but the period starts 1 January, you're missing two and a half months. This 30-second check saves you hours of rework and is the single highest-return habit you can build into your bookkeeping workflow.
Can AI tools handle partially corrupted bank statement PDFs?
It depends on the type of corruption. AI-powered bank statement converters like BankScan AI can handle: scanned PDFs where the original digital text layer is missing (using OCR), PDFs with watermarks or stamps overlaid on transactions, statements where pages are out of order, and PDFs exported from mobile banking apps with unusual formatting. What AI tools generally cannot fix: PDFs where pages are physically missing (e.g., page 3 of 12 is a blank error page), statements where the text is genuinely illegible even to a human eye, and encrypted or password-protected PDFs without the password. For password-protected PDFs, if the client has emailed the password separately, BankScan AI and similar tools can process them once unlocked. If the corruption means data is genuinely absent — as opposed to just hard to read — there's no software fix. You need the client to resend.
Should I still process a statement if one month is missing?
It depends on the purpose. For internal management accounts, processing a partial statement with a clear note that one month is outstanding is acceptable — you can update the figures when the missing month arrives. For VAT returns, the answer is no — you need a complete quarter of data. Filing a VAT return with missing data risks underpayment and potential penalties from HMRC. For self-assessment tax returns, definitely no — HMRC expects complete annual records, and a missing month means your figures won't reconcile to the closing balance. For mortgage or loan applications, partial statements may raise red flags with underwriters. If you do process a partial statement internally, always: (1) clearly mark it as "incomplete — [month] outstanding", (2) enter a placeholder journal for the expected transactions, (3) set a reminder to follow up with the client, and (4) never submit partial data to HMRC or external parties without explicit qualification.
How do I prevent clients from sending the wrong statements in future?
Prevention is about setting clear expectations upfront — most client errors come from vague instructions, not carelessness. Here's a practical system: (1) Send a standardised "bank statement request" template that specifies the exact date range, account name, and acceptable formats (PDF, CSV). (2) Give clients a one-page visual guide showing where to find the statement period on a typical bank statement header — many clients genuinely don't know. (3) Include a simple checklist: "Before you send, check: Does this cover the full date range I asked for? Is this the correct account? Have you included all pages?". (4) Set a naming convention: "ClientName_AccountName_YYYYMMDD_to_YYYYMMDD.pdf" — this forces the client to actively check what they're sending. (5) Bake these requirements into your engagement letter so they're part of the professional relationship from day one. (6) For repeat offenders, send a polite reminder template before each deadline: "Just a quick note — when you send this month's statements, the period I need is [dates]. Let me know if you need help finding them." Most clients improve dramatically once expectations are explicit.
Last updated: 11 August 2026. BankScan AI supports 16+ UK bank formats — read our UK bank statement formats guide, see our guide on handling duplicate bank statements, or browse all blog posts for UK accountants and bookkeepers.