Why bank statements are hard
Every US bank formats statements differently. Chase, Bank of America, Wells Fargo, Capital One, Citi, US Bank, and the regional banks each have their own layout, transaction formatting, and balance presentation. Add credit-card statements and the format space doubles. Cash-flow underwriting needs every transaction parsed; OCR-based parsers hit 70-80% transaction accuracy and miss balances on multi-page statements.
How Cogneris does it
Cogneris parses statements semantically: it identifies the institution, finds the statement period, walks every transaction, normalizes amounts and dates, and reconciles ending balance against the transaction sum. Multi-page statements are stitched automatically; credit-card statements are handled with the same schema as bank statements. Transaction categories (deposit, withdrawal, ACH, wire, fee, interest) are inferred from descriptors.
Sample extraction output
Bank statement to Excel in four steps
The extraction API returns JSON. Getting from there to a spreadsheet is a short, repeatable step rather than a separate product:
- Upload the statement — POST the PDF or scan to
/Document/extraction, attach it to a monitored inbox, or push it through your webhook integration. Multi-month bundles are stitched into one document. - Extract and reconcile — Cogneris identifies the bank, finds the statement period, parses every transaction with a per-line confidence score, and checks that opening balance + deposits − withdrawals = ending balance.
- Review what is flagged — transactions below your confidence threshold or failing balance-math come back with the source region they were read from. Add a review step and they wait in a review queue; the rest is auto-approved.
- Load it into Excel — the
transactionsarray is a flat table: date, description, amount, running balance, category, confidence. Write it to XLSX or CSV with a few lines of code, or push the JSON straight into your ledger.
Export formats
| Format | What you get | Best for |
|---|---|---|
| XLSX (Excel) | One row per transaction with typed columns, written from the JSON response as in the sample below. | Reconciliation, underwriting review, sharing a statement with a controller. |
| CSV | The same flat rows as plain text, one file per statement or one per account. | Google Sheets, accounting-software imports, data warehouses. |
| JSON | The full response: transactions, balances, the balance check, confidence, and source citations. | REST and webhook integrations, cash-flow models, the audit trail. |
From statement to spreadsheet in Python
No client library is needed — the call is a multipart POST with a bearer key, and each extracted cell carries its value and confidence:
import os, pandas as pd, requests
with open("statement.pdf", "rb") as f:
r = requests.post(os.environ["COGNERIS_BASE_URL"] + "/Document/extraction",
headers={"Authorization": "Bearer " + os.environ["COGNERIS_API_KEY"]},
files={"file": f})
envelope = r.json()
rows = [{col: cell["value"] for col, cell in tx.items()}
for tx in envelope["data"]["metadata"]["transactions"]]
pd.DataFrame(rows).to_excel("statement.xlsx", index=False) # or .to_csv("statement.csv")
What you get out of the box
Every US bank, every credit card
Chase, BoA, Wells, Capital One, Citi, US Bank, regionals, plus Visa / Mastercard / Amex statements.
Transaction-level confidence
Each transaction is returned with a confidence score, source page reference, and bounding box.
Multi-page stitching
30-page statements are stitched into one logical document with transaction continuity preserved.
Balance reconciliation
Opening + deposits − withdrawals = ending. Inconsistencies are flagged before they hit your underwriting model.
Integration patterns
For lenders, fintechs, and expense-automation platforms, Cogneris provides REST APIs and signed webhooks suitable for custom integrations with cash-flow models, lender CRMs, and other downstream systems. The bank statement converter API can also produce CSV-style transaction exports.
Bank statement OCR API evaluation
Benchmark bank statement extraction APIs on transaction row recall, balance reconciliation, duplicate transaction handling, statement-period detection, account-holder normalization, source citations, and whether the API can parse scanned PDFs as well as native PDFs. For lending and underwriting, auto-approval rate matters more than raw OCR accuracy.
Compliance & trust
Bank statements contain account numbers and transaction patterns. The Cogneris platform supports encryption at rest with per-tenant keys where configured. Document and audit retention are tenant-configurable and contract-specific. See our security page for the current control boundaries.
Get started
Pay-per-page pricing means you can start an evaluation today without an annual commit. Most teams ship their first bank-statement extraction into production within a week.
Related extractors
Cogneris extracts dozens of structured document types. The closest neighbors to bank-statement extraction:
- KYC document extraction — government IDs, proof of address, and beneficial ownership certifications for onboarding and CIP/CDD.
- Bank statement converter — turn statement PDFs into transaction JSON, balances, and CSV-ready exports.
- Financial spreading document AI — normalize bank statements, tax returns, and borrower financials for credit workflows.
- Payroll extraction — pay stubs, W-2s, and 1099s for income verification and YTD reconciliation.
- Tax return extraction — 1040s, K-1s, and schedules pulled into AGI, deductions, and refund workflows.
For broader context, see the IDP buyer's guide, the 2026 State of Document AI report, or estimate ROI at your volume.