What you get
- One row per transaction: date, narration, debit, credit and running balance, in one schema whatever the bank. Dates are ISO, amounts are numbers.
- CSV for Excel or Google Sheets, or JSON for your own code. The CSV opens directly in Excel.
- Proof, not just rows. Every balance is checked against the one before it. Any row that does not chain is flagged with its page and row.
- The statement's own details: account holder, account number, period, opening and closing balance, and the bank, where printed.
Convert one in a single call
For a CSV you can open in Excel:
curl "https://api.sumproof.dev/v1/statements/parse?format=csv" \
-H "Authorization: Bearer sp_test_YOUR_KEY" \
-F "file=@statement.pdf" \
-o statement.csvFor JSON, with the checks, summary and insights:
curl https://api.sumproof.dev/v1/statements/parse \
-H "Authorization: Bearer sp_test_YOUR_KEY" \
-F "file=@statement.pdf"You need a free test key: sign up (no card), then copy the key from the dashboard. Add -F "password=..." if the bank locked the PDF. Test keys read documents up to 10 pages; live keys up to 300. Full details are in the docs.
Why the check matters
Most converters give you rows and stop. A single misread digit then flows into your spreadsheet unnoticed. A bank statement has a built-in test: each balance must equal the previous balance plus credits minus debits. Sumproof runs that test on every row, to the kobo, and reports each break. Rows a bank printed twice are removed and listed, never hidden. The response ends with a quality grade, high, medium or low, so you know when to look.
The files people really have
- Password-locked PDFs. Send the password with the file. It is used in memory and never stored or logged.
- Scanned statements. Pages without a text layer are read by free OCR on our own servers first, then checked the same way.
- Several months in one PDF. Each month is found and balanced on its own.
- Long statements. Over 60 pages are read in the background and returned as a job.
Works with Nigerian bank statements. See which banks are confirmed on real statements.
What it does not do
It returns JSON or CSV, not a formatted .xlsx workbook, and it reads PDFs and page images, not other file types. Your statement is read in memory and dropped; see what we store.
Frequently asked questions
- Can I convert a bank statement PDF to Excel?
- Yes. Ask for CSV and open it in Excel or Google Sheets, or take the JSON and load it into your own tables. Sumproof returns one row per transaction with a date, narration, debit, credit and balance, and checks that the balances add up before you rely on them.
- Does it work on scanned statements and password-protected PDFs?
- Yes to both. Send the password with a locked PDF and it is used in memory only. Pages without a text layer are read by free OCR on our own servers first, and the balance chain still checks every row, so a misread number shows up as a flagged row, not a silent error.
- How do I know the numbers are right?
- Each row's balance must equal the previous balance plus credit minus debit. If a row does not chain, the response lists the page and row, and the quality grade drops from high. Rows a bank printed twice are removed and listed, never hidden.
- Is there a spreadsheet file (.xlsx) download?
- Not yet. The API returns JSON or CSV, and a CSV opens directly in Excel. A ready-made .xlsx export is not part of the product today.
- Is it free to try?
- Yes. Every account gets 100 free pages a month and a free test key, with no card. Test keys read documents up to 10 pages.