'%3e%3c/rect%3e%3crect%20x='0.5'%20y='0.5'%20width='31'%20height='31'%20rx='7.5'%20stroke='oklch(1%200%200%20/%200.08)'%3e%3c/rect%3e%3crect%20x='9'%20y='9'%20width='14'%20height='2.4'%20rx='1.2'%20fill='oklch(0.995%200.003%2095%20/%200.85)'%3e%3c/rect%3e%3crect%20x='13'%20y='14.8'%20width='10'%20height='2.4'%20rx='1.2'%20fill='oklch(0.995%200.003%2095%20/%200.55)'%3e%3c/rect%3e%3crect%20x='6'%20y='20.6'%20width='17'%20height='2.4'%20rx='1.2'%20fill='oklch(0.52%200.120%20250)'%3e%3c/rect%3e%3c/svg%3e){kind=small}
Bank statement conversion for accountants
Every extracted row keeps a reference to the statement page it came from — so converted data arrives with its evidence attached, not detached from it. Review beside the source, check the balances, export with the checks recorded.
“Where did this number come from?” has a one-click answer.
Historical statement work — year-end catch-up, client onboarding, account reconstruction, a platform migration — ends with someone asking you to justify a number. Each extracted row keeps its statement page, shown side by side in review:
| Date | Description | Amount | Source page |
|---|---|---|---|
| 3 May 2026 | ATM WITHDRAWAL HIGH STREET CASH MACHINE REF 778221 | (£80.00) | 1 |
Provenance is page-level: the row tells you which page to look at, and the review workspace puts that page beside it. Sample data shown.
The workbook keeps the trail, not just the transactions.
The exported Excel workbook carries a source-page and review-status column on every row, plus a validation summary sheet recording the checks, warnings, and the balance-check outcome for the exported revision:
| Date | Description | Amount | Source page | Review status |
|---|---|---|---|---|
| 1 May 2026 | BACS SALARY ACME LTD MAY PAY | +£3,250.00 | 1 | valid |
| 6 May 2026 | CARD PURCHASE PRET A MANGER | (£6.75) | 1 | valid |
| 6 May 2026 | CARD PURCHASE PRET A MANGER | (£6.75) | 1 | needs_review |
| 14 May 2026 | FASTER PAYMENT FROM ALEX MORGAN | +£75.00 | 2 | valid |
| +11 more rows · opening 1250.75 · closing 2431.53 | ||||
Six months later, the spreadsheet still answers where each row came from and what was flagged at the time — without the PDF open beside it. Column details are on bank statement to Excel.
Corrections are counted, and checks re-run.
The balance check is decimal arithmetic against the opening, closing, and running balances the statement prints — on the sample: 1250.75 + 1180.78 = 2431.53. Edit a row and the check re-runs; the summary counts what was edited, so a corrected file never masquerades as an untouched one:
Edits are never overwritten by reprocessing, and no value is ever invented to fill a gap. What the check does — and the four outcomes it can report, including “insufficient data” — is documented on the reconciliation-check page.
What this is — and what it deliberately isn’t.
- It is
- A converter with a review workspace: digital bank-account statement PDFs in, source-linked and balance-checked rows out — as Excel, CSV, QuickBooks CSV, Xero CSV, Sage CSV, OFX, or QIF files you import manually.
- It is not
- Accounting software, a ledger-matching tool, or a bank feed. Nothing connects to your practice systems, and the balance check does not prove every field is correct — it proves the arithmetic is consistent.
- Current limits
- One digital PDF per job, up to 10 MiB and 20 pages. Scanned or photographed statements aren’t supported yet — a scan gets a clear answer, not a guess. Credit-card statements are rejected rather than converted wrongly.
- Not advice
- StatementStudio converts and checks statement data. How you treat the transactions in your engagement remains your professional judgement.
Accountants ask
How do I verify a converted row against the statement?
Every extracted row keeps a reference to the statement page it came from, and the review workspace shows the row beside that page. The exported files carry the source-page reference too.
What does the export carry besides the transactions?
The Excel workbook includes a validation summary — the checks that ran, the warnings, and the balance-check outcome for the exported revision — and each row keeps its review status and source page.
Are edits tracked?
Yes. The reconciliation summary counts edited and deleted rows, checks re-run after every committed edit, and edits are never overwritten by reprocessing.
Is there a live connection to QuickBooks, Xero, or Sage?
No. You download files — QuickBooks CSV, Xero CSV, Sage CSV, OFX, or QIF — and import them yourself. Nothing is linked, and nothing keeps running after you download.
What happens to a client statement after the work is done?
You delete the job. Its uploaded file, source preview, and exports are removed and cannot be recovered. Nothing requires an account or stores the statement beyond the job you control.
What are the current limits?
One digital bank-statement PDF per job, up to 10 MiB and 20 pages. Scanned or photographed statements aren’t supported yet — if a PDF is a scan, we’ll tell you rather than guess.