Bank Statement PDF to CSV/Excel, Balance-Verified (MCP server)
Pricing
from $30.00 / 1,000 statement page processeds
Bank Statement PDF to CSV/Excel, Balance-Verified (MCP server)
Deterministic MCP tool for AI agents: bank statement PDF/scan to CSV + XLSX of transactions, with every row's running balance and opening + transactions = closing reconciled and a verified flag. No LLM inside.
Pricing
from $30.00 / 1,000 statement page processeds
Rating
0.0
(0)
Developer
Double AIgents
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
16 hours ago
Last modified
Categories
Features
Share
A deterministic bank statement converter for AI agents, served as an MCP server. There is no LLM inside, so the same file gives the same output every time. It runs on CPU and does not call any paid API.
Use it for: bookkeeping and accounts imports, affordability and lending checks, audit and reconciliation work, expense categorisation pipelines, and turning a year of PDF statements into one spreadsheet.
Why agents pick it: a statement converter that silently drops or mis-signs one row gives you a spreadsheet
that looks fine and is wrong. This tool proves it: every row is checked against the bank's own running balance
(previous balance + credit - debit = stated balance), and the whole statement is checked as opening + credits -
debits = closing. Your agent gets a plain verified flag, and the failing rows if there are any.
| Tool | What your agent gets back |
|---|---|
bank_statement_to_csv | transactions: date (ISO), date_raw, description (multi-line descriptions joined), debit, credit, signed amount, stated balance, computed balance and balance_ok per row. opening_balance, closing_balance, total_credits, total_debits, currency, checks and verified. Plus a CSV and an XLSX with Transactions and Checks sheets, failing rows in red. |
Handles separate Debit/Credit (Paid out/Paid in, Withdrawal/Deposit) columns, single signed Amount columns, sign from CR/DR suffixes or from the balance movement, US and UK date order (decided per statement), dates printed once per day, descriptions above or below the amount line, repeated headers on each page, and US-style statements split into Deposits / Withdrawals / Checks sections (each section total is checked too). Diagonal "SAMPLE"/"COPY" watermarks are ignored. Scanned statements are OCR'd with Tesseract.
Connect
MCP endpoint (streamable HTTP):
https://doubleaigents--bank-statement-to-csv-mcp.apify.actor/mcpAuthorization: Bearer <APIFY_TOKEN>
Claude Desktop / Cursor style config:
{ "mcpServers": { "bank-statements": {"url": "https://doubleaigents--bank-statement-to-csv-mcp.apify.actor/mcp","headers": { "Authorization": "Bearer <APIFY_TOKEN>" } } } }
Tool inputs
bank_statement_to_csv(file_url | file_base64, filename?, lang="eng")
- Send exactly one of
file_url(public http/https) orfile_base64. Supported files are PDF, PNG, JPG, TIFF, BMP and WEBP, up to 50 MB and 500 pages. - The CSV and XLSX come back as key-value store URLs. Files under 8 MB also come back inline as base64.
Pricing (pay per event)
| Event | USD |
|---|---|
page-processed: each page of the input statement, after extraction and reconciliation | 0.03 |
You are charged only after a call completes. If your run's maximum charge cannot cover the page count, the call is refused before any work is done.
Limits worth knowing
verified: falsemeans a figure does not tie out: a misread, a row the layout hid, or a statement that is itself inconsistent. The failing check is named inchecksandproblems.- The opening balance is read from the statement ("Opening/Beginning balance", "Balance brought forward"). If none is printed, it is derived from the first row and marked
derived-from-first-row. - Credit card statements without a running balance are checked on totals only.
- Handwriting is not supported. Poor scans lower OCR accuracy; the balance check is what flags it.
Batch mode
You can also run the Actor normally with fileUrl (or a list in fileUrls). It writes one dataset item per statement with the totals, checks, links to the CSV and XLSX, and the transactions.
Who runs it
Double AIgents Ltd, UK (company no. 17513072). Your input files are processed for the call. Outputs sit in the run's Apify storage, which Apify removes under its data-retention policy. Need volume pricing, a private deployment or a custom document pipeline? https://www.doubleaigents.com
More tools from Double AIgents
- PDF Tables to Excel + True PII Redaction — tables from PDFs and scans to XLSX with every figure double-read, and true redaction of personal data with a verification log.
- Invoice & Receipt to JSON + Excel — supplier, dates, VAT number, line items and net/VAT/gross, with the totals reconciled.
- PDF Compare — every added, removed, changed or moved passage between two PDF versions, plus an annotated diff PDF.