This reads a PDF bank or credit-card statement and turns it into a clean spreadsheet, checking every transaction against the statement's own balance before you see the result. It runs entirely in your browser: the file never leaves your device, and you can prove that by turning off your internet connection before you convert one. Free, no account, no subscription.
These layouts are matched from text inside the PDF itself (the bank's name, domain, or a phrase specific to that statement family), never by asking you to pick a bank first. Anything that doesn't match falls to a general reader built for the row-and-column shapes most PDF bank statements share.
| United States | Chase, Bank of America, Wells Fargo, Citi, Capital One, American Express, Discover |
| Canada | RBC, TD |
| United Kingdom | Barclays, HSBC |
| Germany | Sparkasse, Deutsche Bank |
| Any other bank | The general reader handles most PDF statements. You review the results and balance check before exporting, just like any other statement |
Detection isn't infallible: a scan, unfamiliar branding, or a layout variant it hasn't seen yet can throw it off. When that happens, a dropdown above the results lets you pick the bank yourself, or force the general reader, and the statement re-parses in place.
Most checking-account statements print a running balance next to every transaction, so the app can confirm each row's balance really is the one before it plus that row's amount. RBC prints it sparingly, once per day's block of transactions and not every line, so the check skips those gaps instead of flagging rows that were never wrong. Amex, Discover, and Capital One's credit-card statements print no running balance at all; the check instead reads the page's own summary box, where previous balance minus payments plus purchases, fees, and interest should land on the new balance. Bank of America and Wells Fargo checking statements have neither shape, so for those two the app says plainly that no arithmetic check is possible instead of pretending to have verified something it didn't.
A CSV that a US spreadsheet reads correctly can look scrambled in a German copy of Excel, and a plain CSV lacks the columns a budgeting app expects. Beyond a plain ISO-dated CSV, there's an Excel preset for the US/UK/Canada (M/D/Y dates), a German Excel preset (semicolon-delimited, D.M.Y dates, comma decimals, what German Excel expects), and ready-made column layouts for YNAB (Payee/Memo/Outflow/Inflow) and QuickBooks. Pick whichever matches where the file is going, and you can switch presets and re-export as many times as you like.
Pick a PDF bank or credit-card statement using your device's normal file picker, the same one you'd use to open any file.
The app matches your bank's statement layout when it can, or falls back to the general reader. Either way, every row gets whichever reconciliation check applies to that statement (see above) before you see it.
Anything that doesn't add up is surfaced first, next to the original statement text, so you can fix it in seconds. For a stubborn row, an optional on-device AI double-check can judge whether a flagged line reads like a real transaction. It only ever confirms or flags; it never invents a date or amount, and every value you see always comes straight from the PDF's own text.