LucadenFree online toolsBrowse toolsZero-upload treasury utility
Convert local MT940 and CAMT.053 bank statements to mapped CSV, XLSX, and JSON with balance reconciliation.
Bank statements and payment files expose account numbers, counterparties, balances, and references. This workspace reads them only in browser memory and creates downloads locally, so none of that bank data is sent to Lucaden or a third party.
Loading tool workspace…
How it works
Important
A local validator can prove structural checks, but it cannot confirm a bank's implementation rules, account status, sanctions controls, or settlement. Keep the source file, review every result, and test generated output with the receiving bank before production use.
These tools provide local technical checks and transformations, not banking, legal, compliance, or accounting advice. Formats and bank usage rules vary. Always verify output with your bank before submitting, keep the original file, and use a bank test or sandbox channel where available.
Deep explainer
MT940 is a tagged SWIFT customer statement; CAMT.053 is its richer ISO 20022 XML counterpart. Both carry account, balance, booking, amount, and reference data.
Treasury, accounting, cash-management, ERP integration, and audit teams moving bank statements into spreadsheets or data pipelines.
For opening 1,000.00, a +250.00 credit and −100.00 debit, the calculated close is 1,150.00. A declared 1,149.99 close produces a loud 0.01 reconciliation failure.
Practical details
Convert local MT940 and CAMT.053 bank statements to mapped CSV, XLSX, and JSON with balance reconciliation.
Every byte of input is parsed in this browser tab. Downloads are created with Blob URLs; the suite has no upload endpoint, server action, edge parser, or content-bearing telemetry.
Questions
No. These treasury routes read local files through browser ArrayBuffers, parse them in this tab, and create downloads with local Blob URLs. There is no file upload request.
No. A base-format check cannot cover every bank implementation guide, bilateral agreement, local scheme rule, or compliance control. Always test and confirm the output with the receiving bank.
Keep the original, use the reported row, tag, line, or path to correct the source system, and run the complete file again. Lucaden does not silently drop malformed financial records.
Open-source foundations
Lucaden documents its standards sources, architectural references, and permissive runtime dependencies while keeping this workspace consistent with the Lucaden interface.