The Statement · Issue #2
Apr 2026
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.
| Update | +/– |
|---|---|
Multiple statements Upload more than one statement in a session instead of converting PDFs one by one | + |
Dashboard organization Keep previous conversions, detected banks, dates, and exports in one place | + |
One-file-at-a-time busywork Less manual stitching after downloading a pile of separate CSVs | – |
| Update | +/– |
|---|---|
Multi-table detection Separate withdrawal, deposit, card, or summary tables can be detected and normalized | + |
Multi-account extraction Multiple accounts or cards in one PDF can stay separated instead of becoming mystery rows | + |
Language-aware parsing Support keeps expanding across non-Latin scripts, bilingual layouts, and local date formats | + |
More from the blog
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
Founder's letter: Revenue is flat, but we're getting better
Revenue is flat. Bing traffic tanked overnight. But Bankstatemently is actually getting better. Some reflections from the past 3 weeks.
By Michael Duyvesteijn
Your first statement from us
Close to 200 weekly visitors now rely on Bankstatemently, across 10+ countries. Here's what we've been building.
By Michael Duyvesteijn