Bank statement conversion for bookkeepers
Convert a client’s statement, resolve what’s flagged, check the balances, and hand over a spreadsheet you’ve actually reviewed — not just downloaded. One digital bank-statement PDF at a time, up to 10 MiB and 20 pages.
Months of client PDFs, and the feed doesn’t go back that far.
Catch-up work rarely arrives as clean data. It arrives as statement PDFs — because the bank feed starts too late, the account is closed, the books are being reconstructed, or the client switched platforms. The job is turning that pile into data you can stand behind.
- Convert one statement per job — a month at a time keeps each balance check meaningful.
- Work through the flags, not the whole file: rows the checks trust stay quiet, and anything uncertain is flagged with a plain-language reason beside its source page.
- Let the balance check close the month: opening balance plus the extracted rows must equal the closing balance — the same arithmetic your reconciliation habit expects.
- Export in the shape your software imports, then delete the job.
No account, no email, no per-seat procurement — a single statement works without setting anything up.
Two identical purchases, same day: duplicate, or just lunch twice?
The worst converter mistake in bookkeeping isn’t a misread digit — it’s a tool silently deleting a legitimate repeat because it looked like a duplicate. Here’s the real behaviour, on the sample statement:
| Date | Description | Amount | Balance |
|---|---|---|---|
| 6 May 2026 | CARD PURCHASE PRET A MANGER | (£6.75) | £2,792.78 |
| 6 May 2026 | CARD PURCHASE PRET A MANGERPossible duplicate | (£6.75) | £2,786.03 |
This row has the same date and amount as another transaction, with a similar description. Both are kept — compare the source pages before deleting either one.
Both rows stay in the data. Nothing is auto-deleted — the running balances show whether the statement really charged twice. Sample data shown.
Export for the books you keep — after the review, not instead of it.
Every export is generated from the rows as you reviewed them. The Excel workbook carries a validation summary and source-page references; the destination files match each product's manual import.
- Excel / CSV
- The full documented output — dates, debits, credits, balances, review notes, source pages. See bank statement to Excel and to CSV.
- QuickBooks CSV
- The 3-column shape QuickBooks Online’s manual upload expects. Bank statement to QuickBooks CSV
- Xero / Sage CSV
- Xero’s four-column CSV and Sage’s money-in/money-out CSV, generated from the same reviewed rows.
These are files you import yourself — StatementStudio never connects to your or your client’s accounting system.
Client files deserve a shorter life than your working papers.
A bookkeeper uploading someone else's bank statement needs more than a privacy policy — it needs an off switch you control.
- No account trail
- No sign-up, no email, no client data tied to an identity. The job is private to your session.
- Delete means delete
- One action removes the job: the uploaded PDF, the source preview, and every export — immediately, and they cannot be recovered.
- Nothing is altered
- The source PDF is read, never modified — and no value is ever invented to fill a gap in it.
- Details in writing
- The Security page states the current data-handling facts in plain language.
Bookkeepers ask
Can I use it for client statements?
Yes — that is the core use. No account is needed, the job stays private to your session, and you can delete it — the uploaded file, source preview, and exports — the moment you have downloaded your file.
How does it fit catch-up or historical work?
One statement at a time — a month per job works well. Each export is built from rows you have reviewed, so a backlog becomes a set of files you have actually checked, not a pile you still have to verify.
What happens with duplicate-looking transactions?
They are flagged, never auto-deleted. A legitimate repeat — two identical card purchases on the same day — looks exactly like an extraction duplicate, so the call stays with you, with the source page beside both rows.
Which files can I move into accounting software?
Excel and CSV with documented columns, plus QuickBooks CSV, Xero CSV, Sage CSV, OFX, and QIF files that you import manually. There is no direct connection to any accounting product.
Do scanned client statements work?
Not yet. StatementStudio currently reads digital bank-statement PDFs. If a client sends a scan, we’ll tell you rather than guess.
Is there a batch upload?
Not during beta — one PDF per job, up to 10 MiB and 20 pages, with a daily limit on new conversions.