Parses
Bank account statements (checking, savings, current) and credit-card statements, digital or scanned, multi-page when signed in.
Bank statement parser
Every bank lays out its statement differently, and half of them arrive as scans. Templates break on the next bank. This parser reads each page as it is, turns every line into a transaction, then checks the running balance so you can see what to verify.
Goes in
Bank and credit-card statement PDFs, digital or scanned, up to 20 MB
Comes out
Transactions as CSV, Excel or JSON, from the web app or the API
10/07/2026 CHK 1043 RENT - OAK STREET 500.00 4,766.61
{
"date": "2026-10-07",
"description": "Rent - Oak Street",
"credit": null,
"debit": 500,
"balance": 4766.61,
"reference": "CHK 1043",
"classification": "OAK STREET RENTALS"
}An illustrative line as it might appear on a statement, and the transaction the parser returns for it. Column hints from the page decide which side the amount goes on.
Statement line (illustrative)
10/07/2026 CHK 1043 RENT - OAK STREET 500.00 4,766.61
Parsed transaction
{
"date": "2026-10-07",
"description": "Rent - Oak Street",
"credit": null,
"debit": 500,
"balance": 4766.61,
"reference": "CHK 1043",
"classification": "OAK STREET RENTALS"
}The full statement comes back in the same shape as the JSON export, or as CSV and Excel.
Sample data from a made-up statement, not a real account.
Step 1
Digital pages are read as positioned text, keeping columns aligned. Pages with no text layer go to OCR.
Step 2
A language model turns the page text into transactions: date, description, credit or debit, balance, reference, payee.
Step 3
Each running balance is recomputed from the previous row. Mismatches are reported, not hidden.
Step 4
Preview, then download CSV, Excel or JSON, or fetch JSON and CSV from the API.
It is a statement parser, not a general document parser. Knowing the edges saves you a test upload.
Bank account statements (checking, savings, current) and credit-card statements, digital or scanned, multi-page when signed in.
Financial statements such as balance sheets, income or cash-flow statements, and it does not read photos directly. Other account statements (brokerage, loan, utility) are not what it is built or tested for.
It is not template-based, so there is no list of supported banks to check. The quickest test is a free upload of your own statement, no account needed.
A tool that reads a bank statement, usually a PDF, and returns its transactions as structured data: one row per transaction with date, description, amount and balance, ready for a spreadsheet, accounting tool or code.
It is not template-based, so it does not keep a bank list; it reads each page's layout. Our ground-truth benchmark covers three hand-checked statements, so test yours with a free upload.
No. It parses bank and credit-card statements. Balance sheets, income statements and cash-flow statements are a different document and are not supported.
Yes. Pages without a text layer are sent to OCR first. Photos (JPG, PNG) are not accepted; save them as a PDF.
Two checks: the preview on the page before you download, and balance_check in the JSON, which lists the rows whose running balance does not add up.
Yes. Create a key at /developers and send PDFs to /api/v1/developer/uploads; results come back as JSON and CSV. See /docs/api.
Rows for QuickBooks, Xero or a spreadsheet.
An .xlsx workbook with a summary sheet.
Structured output and the API.
Keys, upload, poll and fetch.
Scanned statements into rows.
How AI OCR tools compare on bank statements.