8 Formats. One Upload. Every Transaction Extracted.
Drop a bank statement in PDF, CSV, XLSX, XLS, OFX, QFX, MT940, or BAI2 format. The AI-powered extraction engine parses every transaction — date, description, amount, balance — regardless of which bank issued the statement or how the file is structured. SHA-256 hashing prevents duplicate uploads.
Key Bank Statement Upload & Parser Capabilities
Built-in functionality that eliminates repetitive document tasks
Eight Formats, Zero Column Mapping
PDF, CSV, XLSX, XLS, OFX, QFX, MT940, and BAI2 are all accepted. The engine reads each format natively — no template selection, no column headers to configure, no bank-specific setup.
AI-Powered Transaction Extraction
An AI model with Structured Outputs reads the full statement and returns every transaction with date, description, amount, running balance, and transaction type in a consistent schema.
Format-Aware Routing
Each file takes the optimal path: Excel files are converted to tabular text via SheetJS, PDFs are sent as base64, and text formats (CSV, OFX, QFX, MT940, BAI2) are parsed as raw content.
SHA-256 Duplicate Prevention
Every uploaded file is hashed with SHA-256 on arrival. If the same file is uploaded again, the duplicate is rejected instantly — preventing double-counted transactions.
Background Worker Processing
Parsing runs asynchronously after upload. You can continue working in the dashboard while the worker extracts transactions and delivers results to your reconciliation view.
Structured, Reconciliation-Ready Output
Each transaction includes date, description, amount (debit or credit), running balance, and reference. The output feeds directly into the AI Transaction Matcher.
Supported Statement Formats
AI identifies and extracts data from every supported format
PDF Bank Statements
Downloaded from online banking portals. The AI reads table layouts, multi-page statements, and varying column arrangements without templates.
CSV and Excel (XLSX/XLS)
Exported spreadsheets from any bank. Excel files are auto-converted before extraction — no manual column mapping or header configuration required.
OFX and QFX
Open Financial Exchange files used by US and international banks. QFX (Quicken-compatible) files follow the same standard and are handled identically.
MT940 (SWIFT)
The international SWIFT standard for electronic statement delivery. Multi-statement and multi-account files are parsed into individual transaction records.
BAI2
Bank Administration Institute format used by US commercial banks for treasury and cash management. Complex multi-account structures are fully supported.
Mixed Bank Uploads
Upload statements from different banks in different formats in the same session. Each file is detected and routed through the correct pipeline independently.
How It Works
From connection to first extracted invoice in under five minutes
Upload Your Statement
Drag and drop or browse for the file. PDF, CSV, XLSX, XLS, OFX, QFX, MT940, and BAI2 are all accepted without additional configuration.
Automatic Format Detection
MIME type and file extension determine the format. The system routes the file to the correct pipeline — AI for PDFs and text, SheetJS conversion for Excel.
AI Parses Transactions
The extraction engine reads every transaction in the statement and returns structured data: date, description, amount, balance, and type. Processing runs in the background.
Transactions Are Ready for Matching
Parsed transactions appear in your Reconciliation dashboard, where the AI Transaction Matcher can compare them against your invoices automatically.
Who Benefits Most
Designed for finance professionals and teams managing high-volume documents
AP and Accounting Teams
Upload monthly statements and receive structured transaction data without manual entry or CSV wrangling. One upload replaces hours of spreadsheet work.
Treasury and Finance Operations
Process statements from multiple banks — each in a different format — through a single interface. All transactions are normalized for consistent downstream reconciliation.
Bookkeepers with Multiple Clients
Each client uses a different bank with a different export format. Upload them all and let the parser handle format detection, saving 8+ hours per week on statement processing.
See Bank Statement Upload & Parser in Action
Set up in under 5 minutes and let AI handle the busywork.
Frequently Asked Questions
Eight formats: PDF, CSV, XLSX, XLS, OFX, QFX, MT940, and BAI2. This covers statements from virtually every bank worldwide, whether downloaded from online banking portals or received via electronic delivery.
The PDF is sent to an AI model as a base64-encoded document. The model reads tables, headers, and multi-page layouts, then returns structured transaction data — date, description, amount, balance — via Structured Outputs.
No. The AI reads the CSV content and identifies date, description, amount, and balance columns automatically, regardless of your bank's specific column naming or ordering.
Every uploaded file is hashed with SHA-256. If you upload the same file twice, the duplicate is detected and rejected instantly — preventing the same transactions from being processed twice.
Yes. Upload statements from any number of banks in any combination of supported formats. Each file is parsed independently, and all transactions are consolidated in your reconciliation view.
Typical statements are processed in 30 to 90 seconds depending on length. Processing runs in the background — you can continue using the dashboard while it completes.
Yes. Each statement upload uses one credit, which covers AI extraction of every transaction in the file regardless of transaction count.
Statements are kept in your private workspace and only your team members can access them. Files are encrypted at rest.
You Might Also Need
Complementary tools that extend this capability