The Statement · Issue #4
Jul 2026
Longer statements, scanned checks, and a Claude Code plugin
This month is about the statements we could not handle cleanly before. Bankstatemently now recognizes when a PDF holds several statements and converts every transaction accurately, reads the scanned checks and deposit slips that plain text leaves blank, takes files up to 50 pages (up from 20), and ships a Claude Code plugin you install in one command.
| Update | +/– |
|---|---|
Several statements in one PDF When a file holds several statements, Bankstatemently recognizes each one and converts its transactions accurately, each with its own tabs, totals, and export. | + |
Scanned checks, slips, and forms It now reads imaged checks, deposit slips, and debit forms inside your statement to fill in transaction detail that plain text leaves blank. | + |
Longer statements A single upload now handles up to 50 pages, up from 20. Available on the Pro plan (US$50/month). | + |
| Update | +/– |
|---|---|
A Claude Code plugin Install the plugin in one command and convert statements straight from Claude Code. MCP and a REST API are there for everything else. | + |
More from the blog
Introducing Bankstatemently Workspace
Converting one PDF was never the whole job. Bankstatemently is now introducing its Workspace: The place where your statements live. Bulk upload them, find any conversion later, and export it all together.
By Michael Duyvesteijn
Convert a folder of statements, not just one PDF
The homepage has been refreshed around what Bankstatemently is becoming: not a one-off PDF demo, but a workflow for messy, real-world bank statements.
By Michael Duyvesteijn
Bankstatemently Open Benchmark for Bank Statement Parsing
Everybody can now build a bank statement converter. Any vision model can look at a PDF and extract transactions. So how do you know if your parser is actually good? I built a benchmark to find out.
By Michael Duyvesteijn