When a Bank Statement Doesn’t Reconcile

TL;DR: Don’t blame the client and don’t get technical. Say you’ve started, explain that PDFs sometimes don’t convert perfectly (especially scans), ask for a fresh portal download if possible, and set the expectation that you’ll send back a reconciled export.

When a bank statement export doesn’t match, the hard part usually isn’t the math. It’s the messaging.

You don’t want to sound accusatory. You don’t want to overload them with jargon. And you definitely don’t want to create a long email thread where everyone is “just checking one thing” while the deadline gets closer.

Most clients aren’t doing anything wrong. They’ve just downloaded a PDF, sent it over, and assumed a converter would handle it. They can’t see the difference between a clean, digital statement and a scanned one. They don’t realize that one tiny formatting issue can disrupt an export. And frankly, they shouldn’t have to.

So here’s a practical way to handle it: stay calm, clear, and professional.

Start with reassurance, not the problem

Your first line sets the tone. The goal is to convey that you’ve got this without pretending the file is perfect.

Something like:

Thanks, I’ve started processing the statement. There’s a small mismatch in the extracted totals that I’m going to correct before finalizing.

This removes blame and eases anxiety.

Explain the issue in plain English

Clients don’t care about “OCR” or “row-level validation.” They care about whether their books will be accurate.

A simple explanation that works is:

The statement PDF doesn’t convert into a spreadsheet perfectly every time, especially when the layout changes in the document or when the PDF is a scan. A single misread amount can throw off the running balance.

Notice what this does: it frames it as a normal limitation of PDFs, not as a problem with their PDF.

If you want a simple explanation of why “almost correct” exports can still waste hours, this breaks it down without jargon: Why 99% Accuracy Isn’t Enough in Bank Statement Extraction.

Be specific about what you need and why

Vague requests create confusion. Give them a clear, short checklist.

Usually, you’ll need one of these:

• A fresh download of the statement (not a screenshot or print-to-PDF)
• The statement for the full date range (no missing pages)
• A second copy of the same statement (some banks generate different PDF versions)
• Confirmation of opening/closing balance if the statement is unclear

You can write:

To make sure the ledger matches properly, could you please send one of the following?

1. The original downloaded PDF directly from the bank portal (not a scanned copy), if available, or
2. A second download of the same statement, in case the first file is a scan version.”

It’s polite and gives them options.

Set expectations on time without sounding dramatic.

Don’t say “this is going to be a nightmare.” Don’t say “your PDF is unreadable.”

Just set a normal expectation:

Once I have that, I’ll be able to finalize the reconciled transaction list and import it cleanly.

That’s what they care about: final and reconciled.

And if you’re already staring at an export that won’t tie out, this is the fastest way to pinpoint where it breaks: How to find the exact row that breaks reconciliation (and fix it fast).

Copy-paste templates you can actually use

Below are a few templates. Pick the one that fits your situation and your relationship with the client.

Template 1: Short and professional (works 80% of the time)

Hi [Client Name],

Thanks, I’ve started processing the statement. There’s a small mismatch between the statement totals and the extracted transaction list, which can happen with certain PDF layouts/scans.

Could you please resend the statement as the original downloaded PDF directly from the bank portal (not a scanned copy), if available? A fresh download of the same statement also works.

Once I have that, I’ll finalize a reconciled export ready for import.

Thanks,

[Your Name]

Template 2: When they sent a photo/scan/screenshot PDF

Hi [Client Name],

Thanks for sending this over. Just a quick note: this appears to be a scanned/photographed statement PDF, which can sometimes cause small conversion errors (for example, a digit or decimal getting misread).

If you’re able to download the statement directly from the bank portal as a native PDF, please send that version instead. It’ll let me produce a clean, reconciled export much faster.

If that’s not possible, no problem—I can still work with this; it just may take a bit longer to verify.

Thanks,

[Your Name]

Template 3: When pages or date range might be missing

Hi [Client Name],

I’m seeing a mismatch in the running balance, which usually happens when a page is missing or the statement date range isn’t complete.

Could you confirm this PDF includes all pages for [Start Date] to [End Date], including any “continued” pages? If you can resend a full download from the bank portal, that’s ideal.

Once confirmed, I’ll finalize the reconciled transaction list.

Thanks,

[Your Name]

Template 4: When you want to avoid any “your fault” vibe (high-touch clients)

Hi [Client Name],

Thanks, I’m reviewing the statement now. One small item: the extracted totals aren’t matching up yet, which is common with bank statement PDFs when formatting shifts or the file is a scan.

To keep everything accurate, could you send a fresh download of the same statement from the bank portal if possible? That usually resolves it quickly.

I’ll take it from there and send you the reconciled result once it’s ready.

Thanks,

[Your Name]

If you’re having this conversation often, it’s usually because the “conversion” step is producing exports that don’t reconcile cleanly. Tools like SmartBankStatement are built around reconciliation checks and quick review, so you spend less time chasing mismatches and more time finishing the work.

A small trick that saves you time

If you often receive messy statement PDFs, add one sentence to your onboarding email or checklist:

Please send bank statements as the original downloaded PDFs from the bank portal (not photos, screenshots, or scanned printouts).

That single line prevents many issues later.

The whole point: keep trust high

Clients don’t mind small issues. They mind uncertainty.

If clients ask about safety, here’s a plain-English overview of how statement data should be handled: Data security for bank statements: what matters (and what doesn’t).

Your message should clearly communicate three things:

• You’ve started.
• You’ve spotted the mismatch early.
• You’re taking steps to ensure the final numbers are correct.

That’s what a professional sounds like.