'%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}
Turn bank statements into spreadsheets you can check.
Review extracted transactions beside the source, correct anything flagged, and check the balances before you export to CSV or Excel.
| Date | Description | Amount | Balance |
|---|---|---|---|
| 1 May 2026 | BACS SALARY ACME LTD MAY PAY | +£3,250.00 | £4,500.75 |
| 2 May 2026 | CARD PURCHASE TESCO STORES 4381 | (£46.82) | £4,453.93 |
| 5 May 2026 | FASTER PAYMENT RENT 22 KING STREETEdited | (£1,450.00) | £2,799.53 |
| 6 May 2026 | CARD PURCHASE PRET A MANGER | (£6.75) | £2,792.78 |
| +11 more rows | |||
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.
Extract complete transaction rows
Every transaction is pulled into a structured table — dates, descriptions, debits, credits, and running balance.
Review anything uncertain
Ambiguous or duplicate-looking values are flagged for you to check, not silently guessed or removed.
Export balance-checked data
Download the reviewed revision as Excel or CSV once the balances and your edits line up.
A converter that looks right can still be wrong.
Plain PDF-to-spreadsheet tools can produce a clean-looking file with silent mistakes. StatementStudio shows its work so you can trust the result.
Where a plain conversion goes wrong
- A plausible row can still carry the wrong debit/credit sign.
- A hard-to-read page can be skipped without notice.
- Two legitimate identical payments can look like a duplicate.
- A missing transaction only shows up when the totals don’t add up.
How StatementStudio handles it
- Each row links back to the source page it came from.
- Deterministic checks flag duplicates and inconsistencies.
- Opening, closing, and running balances are checked where shown.
- You decide on every flag — nothing is auto-deleted.
Four steps from PDF to reviewed spreadsheet.
- 1
Upload a bank-statement PDF
Choose one statement, up to 10 MB and 20 pages.
- 2
It reads and checks the statement
Transactions are extracted and the balances are checked.
- 3
Review or correct anything flagged
Edit rows against the source; checks rerun after each change.
- 4
Download Excel or CSV
Export the reviewed revision, ready for your books.
See exactly where a statement stands.
One clear outcome sits above the data. Reconciliation compares the extracted amounts with the opening, closing, and running balances shown on the statement, where available.
- Each finding explains what it is and why it matters.
- Every row keeps a page-level reference to its source.
- Edits update the reconciliation result before you export.
A balance check is a strong consistency check — it does not prove every individual field is correct.
No unresolved issues remain.
Non-blocking findings to check before export.
Blocking issues must be resolved first.
Honest about what it does and doesn’t do.
StatementStudio focuses on bank statements. Limits and exclusions are shown before you upload so nothing is wasted effort.
What you can convert
Not supported in this version
Built for people who have to trust the numbers.
Catch-up and historical client statements
Convert months of client-provided PDFs into clean rows, with duplicates and gaps flagged before they reach the ledger.
Reviewable evidence and stable exports
Keep a clear link from each exported row to its source page, with consistent columns for import.
A spreadsheet without manual entry
Turn a statement into a usable Excel or CSV file without retyping every transaction by hand.
A sample conversion, end to end.
This is the actual review workspace running on a synthetic statement — not a live customer file. Source on the left, extracted rows on the right, one flagged duplicate, and a balance check.
- 2 pages · 15 transactions
- 1 row edited against the source
- 1 warning acknowledged
- Balances reconcile
| Date | Description | Amount | Balance |
|---|---|---|---|
| 1 May 2026 | BACS SALARY ACME LTD MAY PAY | +£3,250.00 | £4,500.75 |
| 2 May 2026 | CARD PURCHASE TESCO STORES 4381 | (£46.82) | £4,453.93 |
| 5 May 2026 | FASTER PAYMENT RENT 22 KING STREETEdited | (£1,450.00) | £2,799.53 |
| 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 |
| 29 May 2026 | INTEREST PAID | +£2.41 | £2,431.53 |
| +9 more rows | |||
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.
Clear about what happens to your file.
StatementStudio states only what it can stand behind today. Hosted retention, deletion, and security details are published after the evidence gates are met.
- Files are processed on hosted infrastructure during beta.
- No account, email, or payment is required during beta.
- Sample conversions use synthetic data, never a real customer file.
Built around validation before export.
StatementStudio combines document extraction with explicit accounting checks, so uncertain results are surfaced before export rather than silently guessed.
- Source-linked review keeps extracted rows beside the statement page they came from.
- Date, amount, sign, and balance checks highlight items that need attention.
- Bank-specific support is published only when it is backed by tested evidence.
Common questions
What statements are supported?
Bank-account statements as PDF files, up to 10 MB and 20 pages, with initial coverage for GBP/USD and UK/US layouts during beta.
What if the PDF is hard to read?
The review flow is designed to surface unreadable or low-confidence values rather than guess them.
Is a credit-card statement supported?
No. This version supports bank-account statements, not credit-card statements. A credit-card statement is detected and marked unsupported.
What does reconciliation check?
It compares the extracted transaction amounts with the opening, closing, and running balances shown on the statement, where available. It is a strong consistency check, not proof that every field is correct.
Can I edit a row?
Yes. You can edit, add, soft-delete, and restore rows against the source. Deterministic checks rerun after each committed edit.
What formats can I download?
Excel (XLSX) is the primary export, and CSV is fully supported. Exports are tied to the reviewed revision, so a later edit needs a new export.
Do I need an account?
No. There is no sign-up, email capture, or payment during beta.
How long is my file kept?
Retention and deletion details are published after the hosted file-handling evidence gates are met.
What happens when a value is unclear?
It is flagged for review with the reason, never silently filled in or removed. You decide what to do with each flag.