Client Bank Data Collection Guide

The collection step is where most of the pain in a bookkeeping job is decided. Get clean, complete files at the start and the rest is quick. Accept whatever a client throws at you and you'll be chasing a missing fortnight in week three of the close.

Decide what you're actually asking for

Before you email the client, be clear on the format you want. They will send the path of least resistance unless you tell them otherwise, and that's usually a screenshot.

Here's the order of preference, best first:

• Official PDF from online banking. Downloaded straight from the bank's portal, these carry clean text under the surface. The dates, descriptions and amounts sit in real columns, so extraction is accurate and the running balance is intact.
• CSV from online banking, if it's a full export. A genuine CSV is already structured data. The catch: many banks cap CSV exports at 90 days or strip the running balance, so you lose the one column that lets you prove completeness. For older periods, the PDF is often the more reliable source.
• Scanned paper statement. A clear scan of a posted statement is fine — it runs through OCR. Ask for 300 dpi, flat, the whole page in frame.
• Phone photo of a statement. Last resort, but it works. OCR will read a sharp, well-lit photo. Blurry, angled or shadowed shots are where misreads creep in.

If a client only has access to one of these, take it — the tool reads all of them. But asking for the official PDF up front saves a round trip. For the trade-offs in detail, our note on PDF vs CSV bank statements covers when each one wins.

Cover the full period — and every account

The single most common gap isn't a misread figure. It's a missing account.

Clients think of "the bank" as their main current account. They forget the savings pot, the second trading account, the card that clears separately, the PayPal balance that funds a chunk of sales. For a VAT quarter or a year-end, you need a continuous run with nothing dropped:

1. List every account the business uses, not just the one the client volunteers. A quick look at last year's file usually surfaces one they didn't mention.
2. Ask for the exact date range — first of the period to the last day — for each account, with no gaps between statements.
3. Check the statements run consecutively. The closing balance on one month should be the opening balance on the next. If they don't line up, a month is missing.
4. Confirm the period brackets cleanly. A statement that starts mid-month on one account and on the 1st for another makes reconciliation harder than it needs to be.

That continuity check is worth doing by eye before you convert anything. If month three closes at 6,884.12 and month four opens at 6,512.00, you're missing a statement, and no amount of clever extraction will fix data you don't have.

Handle password-protected files without friction

Most banks now send statement PDFs encrypted, locked with the client's date of birth, part of their postcode, or the last few digits of an account number. A locked file you can't open is a job that stalls.

Build the unlock into your request. When you ask for statements, ask in the same message whether the files are password-protected and, if so, how to open them — without the client emailing you the raw password in plain text alongside the file. A quick phone call for the password is safer than a paper trail of credentials in your inbox.

Once you have it, you can remove the protection so the file opens cleanly for conversion. We walk through that in converting password-protected bank statements. The point for collection: flag it early. Discovering ten locked PDFs the night before a filing deadline is a bad evening.

Handle the data like it's not yours — because it isn't

Client bank data is about as sensitive as records get. You're holding account numbers, balances, every payee the business deals with. The duty of care sits with you, and clients increasingly ask where their data ends up.

A few habits that hold up:

• Use a secure channel for collection. A client portal or encrypted upload, not a statement PDF as a reply-all email attachment.
• Don't let credentials travel with the file. Passwords for protected PDFs go through a separate channel from the documents themselves.
• Keep the working copy only as long as you need it. The fewer places a client's statements live, the smaller the surface if something goes wrong.
• Know what your tools do with the file. Export Bank Statement processes the statement and then deletes it immediately, and files are never used to train AI. That's the answer you want ready when a client asks what happened to their upload.

None of this is exotic. It's the same care you'd apply to any client record — it just matters more when the document is a full map of someone's finances.

Turn the collected files into reconciled data

Once you've got clean, complete files, the conversion is the easy part — provided you don't stop at "it looks right". A converted statement can read perfectly and still be wrong: a faint figure on a scan gets dropped, a 1,180.00 reads as 1,180.0, two same-day transactions merge into one. The spreadsheet still looks tidy.

This is the wedge worth building your process around. Export Bank Statement runs the arithmetic the bank already ran — opening balance, plus every credit, minus every debit, should equal the closing balance the bank printed. If a line is missing or a figure is misread, the running balance drifts and the statement gets flagged. You catch the gap in seconds, at collection time, instead of during a reconciliation when the client can't remember what the 180 was for.

Be honest with yourself and the client about what happens next. The tool converts the statement and exports a CSV in Xero, QuickBooks or Zoho Books' native bank-import format, so the lines come in as reconcilable bank entries. You then import that CSV. It does not push transactions into the ledger through a live bank-feed API — that needs partner certification and is a different product. The workflow is collect, convert, check it reconciles, then import. For catch-up and year-end work that's exactly the control you want anyway. If you handle a portfolio, our guide on how bookkeepers process bank statements shows where this fits in a monthly close.

A short request template you can adapt

When you ask a client for their statements, vague requests get vague results. Be specific:

"Could you send official PDF statements downloaded from online banking for [account names], covering [start date] to [end date], with no months missing? If any files are password-protected, let me know separately how to open them. A scan or clear photo is fine if you can't download the PDF."

That one message sets the format, the period, every account, and the password question in advance. It cuts the back-and-forth that eats the first few days of most jobs.