Financial Document Engineering · Open Source

Parse any bank statement in milliseconds.
Zero cloud dependencies. Zero telemetry.

An open-source, high-throughput financial document parsing engine engineered in Rust with native Python bindings. Converts CAMT, PAIN.001, MT940, MT942, OFX/QFX, BAI2, CSV, and PDF bank statements into validated JSON, Apache Parquet, and ISO 20022 transaction streams entirely on your own infrastructure.

Install CLI & SDK Explore Supported Formats

Deterministic Rust Core
Zero Cloud Dependencies
100% Air-Gapped Privacy

10,000+ Pages/Min Deterministic multi-threaded streaming throughput with zero lock contention.
< 0.8 ms Latency Zero-copy tokenization designed for real-time ledger reconciliation.
100% Zero Telemetry Runs fully air-gapped on your private VPC or local host with zero network calls.
8 Banking Standards Unified extraction across CAMT (052/053/054), PAIN.001, MT940, MT942, OFX/QFX, BAI2, CSV, and PDF.

Developer Quickstart

Install via Cargo, Pip, or Homebrew in Seconds

Deploy as a standalone CLI tool, embed as a high-assurance Rust crate in your microservices, or integrate into Python data pipelines with zero external runtime overhead.

Full Documentation → API Reference

bash — bankstatementparser

# 1. Install standalone CLI or Python library

$cargo install bankstatementparser

$pip install bankstatementparser

# 2. Parse statement with arithmetic balance verification

$bankstatementparser --input statement.pdf --format json

# 3. Deterministic output verification (< 0.8 ms)

{ "status": "VALIDATED", "duration_ms": 0.72, "balance_proof": "EXACT_MATCH" }

Engine Architecture

Engineered for absolute accuracy.

Industrial-grade financial parsing combining memory-safe Rust execution, native Python bindings, and dual Apache/MIT licensing.

Multi-Format Dialect Engine

Deterministic state machines parse digital and scanned PDFs, irregular CSV layouts, SGML OFX/QFX, BAI2 cash management, and SWIFT MT940/MT942 messages without brittle regex or external cloud OCR.

Arithmetic Balance Verification

Strict mathematical balance validation ensures opening balance plus net credits and debits precisely equals closing balance to the penny before record emission.

ISO 20022 Harmonization

Normalize disparate bank statements directly into canonical ISO 20022 CAMT.053 XML envelopes, Apache Parquet streams, or strongly-typed JSON schemas ready for ERP, GL, and accounting ingestion.

The Processing Pipeline

From raw bank document to validated ledger transactions.

Ingest

Stream PDF bytes, CSV feeds, BAI2 files, or SWIFT MT940/MT942 messages into memory-safe zero-copy buffers.

Sub-millisecond stream loading

Tokenize

Deterministic lexical analysis identifies account metadata, booking dates, line items, and structured :86: sub-tags.

Deterministic layout analysis

Verify

Arithmetic balance reconciliation confirms credit/debit integrity, checks PDF forensics, and validates IBAN checksums.

Mod-97 and balance proofs

Emit

Output strongly-typed JSON, streaming Apache Parquet, Plain-Text Ledgers (hledger, beancount), or ISO 20022 messages.

Ready for ERP, Lakehouse & GL

Corporate treasury and real-time financial ledger analytics dashboard in modern banking operations

Corporate Treasury Automation

Automated Reconciliation for Modern Treasury

Eliminate manual statement keying, error-prone spreadsheets, and expensive cloud OCR APIs. Normalize multi-bank statements directly into your general ledger, ERP, and treasury management workflows with sub-second turnaround.

View Treasury Playbook

Iconic financial architecture of London at night, highlighting high-assurance parsing infrastructure

High-Performance Pipeline

Deterministic Execution at Enterprise Scale

Engineered for high-frequency financial platforms requiring bounded latency, zero-allocation loops, and strict ISO 20022 data models.

View Architecture Blueprint

Zero-Telemetry Privacy

Your financial data never leaves your infrastructure.

Bank Statement Parser is 100% self-contained and operates entirely on your local machine, private VPC, or air-gapped on-premise servers. Zero analytics, zero telemetry, and zero outbound network calls—guaranteeing complete GDPR, GLBA, and banking confidentiality compliance.

Read Security & Privacy Architecture

Clear Answers

Frequently Asked Questions

Does Bank Statement Parser send data to the cloud or external servers?

No. Bank Statement Parser is 100% self-contained and operates entirely on your local machine or private cloud server. It contains zero analytics, zero telemetry, and zero outbound network calls, ensuring complete compliance with GDPR, HIPAA, GLBA, and banking confidentiality regulations.

Which bank statement file formats are supported?

Bank Statement Parser natively supports eight primary banking formats: ISO 20022 CAMT (camt.052, camt.053, camt.054), ISO 20022 PAIN.001 (Credit Transfer), SWIFT MT940 and MT942 messages, BAI2 (Bank Administration Institute), Open Financial Exchange (OFX 1.x/2.x and QFX), CSV files (with automatic delimiter and date detection), and digital/scanned PDF statements.

How does the parser handle scanned or image-based statements?

For digital and vector PDFs, the engine extracts structured text streams directly with zero loss. For scanned image statements, an optional local OCR module performs deterministic optical layout parsing with zero external cloud API dependencies.

Is the project open source and available for commercial use?

Yes. Bank Statement Parser is dual-licensed under the Apache-2.0 and MIT open-source licenses. You can freely integrate it into commercial SaaS products, enterprise backends, and internal financial pipelines.