You have felt every one of these. We did too.
PDFs, Excels, CSVs — each bank with its own quirks. There is no standard.
Type your DOB or PAN every time you want to read your own statement. It is already leaked. But here we go again.
1 year max per fetch. 5 statements per day. Some banks force you to download month by month.
Your bank website is down. Again. Maintenance window. Random 500. Try again tomorrow.
Each bank app shows one bank. If you have three, you have three apps and no unified view.
Leave the bank, lose your history. People stay with banks they hate because the data is hostage.
And let's be honest — nobody actually files statements in well-named Drive folders.
One place that owns the truth of which statements exist, which transactions happened, and what they meant. Independent of any bank's portal, format, or policy.
Portal goes down? Data still here. Bank changes their format? Data still here. You leave the bank? Data still here.
Not 50 different PDF formats. One schema. Deduped. Reconciled against statement totals.
No vendor lock-in. Export everything. Pipe through API. Query from the CLI. It's your data.
Once your bank data is the source of truth, it's reachable however you want it.
Browse, search, and audit every statement and transaction in one place.
Daily balance, cashflow trends, category and entity breakdowns — for humans.
CSV, Excel, JSON. Take your data into any spreadsheet, ERP, or tool.
First-class programmatic access for workflows, integrations, and dashboards.
The fobs CLI for terminal-first users. Scripts, ad-hoc queries, pipelines.
Claude Code + the CLI + a skill = ask questions of your statements in natural language.
Statements is the bank-data layer beneath Zoho, YNAB, Actual, your spreadsheets, your ERP. Already using one of them? Great — we sit underneath.
Plaid covers US. Setu covers India. TrueLayer covers UK. None of them cover an NRI with all three. Statement extraction is bank-agnostic — and country-agnostic.
Works for any bank that emits a statement, anywhere.
No "this bank is not supported" walls. If it produces a statement, we read it.
As far back as the bank lets you export. No 90-day API ceiling.
Indian salary + US Stripe + UK invoicing — one unified ledger.
Statements isn't a chat app. Plug it into the AI you already use — through the fobs CLI, a skill, or the REST API — and ask whatever you want about your transactions.
Try a question
Plug Statements into your AI of choice via the fobs CLI or the REST API.