About

StatementProof is built and maintained by Tarun Vashishth, independently — no company, no VC funding, no data-monetization business model behind it. The source is public at https://github.com/tarunvashishth/bank-statement-to-csv: the PDF parser, the reconciliation checks, and every export format are readable, not a black box you're asked to trust.

Why this exists

Every bank statement converter online makes two claims: your file is handled safely, and the numbers come out right. Neither claim is usually checkable — the file goes to a server you can't inspect, and "99% accurate" has no methodology behind it. StatementProof was built to make both of those claims verifiable instead of asserted: a strict Content-Security-Policy that makes network requests physically impossible, and reconciliation checks that verify the output against the numbers already printed on your statement. See how the privacy claim is enforced andwhat the reconciliation checks actually do.

How it's funded

It isn't, currently. There's no signup, no paywall, no ads, and — because of theconnect-src 'none'Content-Security-Policy — no analytics beacon either. That's a deliberate trade: the privacy guarantee is the point, and weakening it to add tracking or a paid tier would undercut the reason to use this tool over a competitor's.

Limitations, stated plainly

• Text-based (native) PDFs only — scanned or image-only statements aren't supported; there's no OCR step.
• Five banks have dedicated parsing profiles. Others still run through the geometric parser, without bank-specific hints.
• One person builds and maintains this. See the changelog for what's actually shipped and when.

Get in touch

Found a bank statement that doesn't parse correctly, or a bug in a reconciliation check? Open an issue on GitHub — ideally with the statement's layout described (not the statement itself; don't attach a real one).