Why it exists
A lender approves a loan on a bank statement. A landlord, a visa agent and an accountant do the same. The statement is a PDF, every bank prints it differently, and reading it by hand is slow and easy to get wrong. Tools that extract the rows leave one question open: are these numbers right?
Sumproof answers that question in the same call. A bank statement is an arithmetic puzzle that checks itself, because each balance must equal the one before it plus credits minus debits. We use that to prove the rows, and we hand you the proof, not just the data.
What it does today
- Reads bank statement PDFs, including password-locked files, scans and several months stapled into one PDF.
- Returns typed transactions, a cash-flow summary and insights, with the checks that show whether the balances add up.
- Answers questions in English and over GraphQL, computed from the checked rows.
- Starts with Nigerian banks and fintechs. See which are confirmed on real statements.
The rules we build by
- Prove it or flag it. If a number cannot be checked, the response says so. A repair is reported, never silent.
- Cheapest reliable reader first. Free readers on our own servers go first. A language model reads only the pages they cannot prove, and the model's answers are matched against the page before we trust them.
- Keep nothing you did not ask us to keep. Read the exact list on the security page.
- Only claim what we have measured. We say how many banks are confirmed on real statements, and how many are not.
Where it is going
Bank statements are the first document type, not the whole product. The same idea, proving the arithmetic of a document, applies to other documents whose numbers must add up, such as invoices and payslips. They are planned; none is available yet, and we will announce them in the changelog when they are.
Talk to us
Questions, a statement that did not parse, or an idea for a document type you need read: see contact.