CAMT · MT940 · OFX · TREASURY
Schema-validated CAMT / MT940 / PAIN parsers, OCR fallback for scanned PDFs, deterministic field mapping, SR 11-7-grade audit evidence — every transformation step recorded and reproducible.
Read case studySchema-validated CAMT / MT940 / PAIN parsers, OCR fallback for scanned PDFs, deterministic field mapping, SR 11-7-grade audit evidence — every transformation step recorded and reproducible.
Corporate treasury teams receive bank statements in CAMT, PAIN.001, MT940, OFX, CSV, and scanned PDFs from dozens of banks. Each format carries different field semantics, encodings, and ambiguities. Most teams hand-build brittle per-bank parsers, blocking real-time cash forecasting, fraud detection, and audit-ready reconciliation.
An open-source Python toolkit that unifies every common bank statement format into a single, normalised transaction stream. Schema-validated CAMT / MT940 / PAIN parsers, OCR fallback for scanned PDFs, deterministic field mapping, and SR 11-7-grade audit evidence for every transformation step.
Formats supported
CAMT (.052, .053, .054), MT940, OFX, CSV, scanned PDF (OCR)
Normalisation target
Single unified transaction record schema
Audit trail
Per-field provenance — source format + parser version logged per row
License
Apache-2.0 / MIT
NEXT
Architecture reviews, post-quantum migration plans, treasury-API programmes — all signed, all verifiable.
Get in touchMORE CASE STUDIES
MCP · ZERO-TRUST · DORA
TIER-1 BANK · TREASURY · BAAS
FIPS 203 · ML-KEM · BANKING MIGRATION
ISO 20022 · PAIN.001 · MT→MX MIGRATION
