BAI2 Viewer & Converter → camt.053
Open a BAI2 statement, see balances and transactions, and export camt.053 — entirely in your browser, nothing uploaded.
What is BAI2 and how does it relate to camt.053?
BAI2 is the "Cash Management Balance Reporting" format published by the Bank Administration Institute (BAI) in 1987 — the dominant bank-statement format in the United States and Canada, and the North American counterpart of Europe's SWIFT MT940. Its modern ISO 20022 replacement is camt.053, a richer XML format. This free tool reads a BAI2 file locally, extracts the account, balances and transactions, and converts it to a camt.053 statement — no data ever leaves your browser.
About the BAI2 viewer & converter
BAI2 is the Bank Administration Institute's version 2 "Cash Management Balance Reporting" specification, published in 1987 and still the workhorse bank-statement format across the United States and Canada — the North American equivalent of the European SWIFT MT940. A BAI2 file is a hierarchy of comma-delimited numeric records, each terminated by a slash ("/"): 01 (File Header) → 02 (Group Header) → 03 (Account Identifier) → 16 (Transaction Detail) → 88 (Continuation), closed by matching trailers 49 (Account), 98 (Group) and 99 (File). It is compact and machine-friendly, but far less structured than the modern ISO 20022 XML statement, camt.053.
ValidateFin parses every record locally in your browser. Amounts are integers in the currency's minor units with no decimal separator — "10000" means 100.00 in a two-decimal currency, while the number of decimals depends on the currency (JPY has 0, KWD has 3). The debit/credit direction is carried by a numeric type code, not a sign or flag: codes 100–399 are credits and 400–699 are debits. The tool reads the key balance codes — 010 (opening ledger), 015 (closing ledger) and 040/045 (available) — reconciles that opening ledger plus the sum of movements equals the closing ledger, then exports a valid camt.053.001.02 statement carrying the real balances and mixed debit/credit entries. No BAI2 file is ever uploaded to a server.
Why the BAI2 to camt.053 migration matters
- BAI2 remains the default statement format for US and Canadian banks, but ISO 20022 camt.053 is the modern, globally standardised replacement.
- ERP and treasury systems — SAP, Kyriba and others — increasingly consume camt.053, pushing finance teams to convert their legacy BAI2 feeds.
- camt.053 carries far richer structured data than BAI2's numeric records, with an official ISO 20022 XSD to validate against.
- A converter is only useful if the camt.053 keeps the real balances and both debit and credit entries — BAI2 encodes direction through 100–399 (credit) and 400–699 (debit) type codes, not a sign.
- Because a bank statement is sensitive data, converting locally in the browser avoids emailing account numbers and counterparties to a third-party service.
Frequently asked questions
What is a BAI2 file?
BAI2 is the "Cash Management Balance Reporting" format published by the Bank Administration Institute in 1987, the dominant bank-statement format in the US and Canada. It is a hierarchy of comma-delimited numeric records (01 file header, 02 group, 03 account, 16 transaction detail, 88 continuation) each terminated by a slash.
What replaces BAI2?
The ISO 20022 XML statement camt.053 is the modern replacement for BAI2. It carries richer structured data and an official XSD, and most ERP and treasury systems now prefer to import camt.053.
Can I convert BAI2 to camt.053 here?
Yes. After reading the file, click "Export camt.053" to download a valid camt.053.001.02 statement generated from the BAI2, with the real balances and debit/credit entries. Everything runs in your browser.
Is my bank statement uploaded anywhere?
No. The BAI2 file is read, parsed and converted entirely in your browser using JavaScript. No statement data is ever sent to a server.
How does the tool know the file is consistent?
The integrity check is arithmetic: the opening ledger balance (type code 010) plus the net of all transaction movements must equal the closing ledger balance (type code 015). A mismatch is flagged as a warning.
How are amounts and debit/credit encoded in BAI2?
Amounts are integers in the currency's minor units with no decimal separator (so "10000" is 100.00 in a two-decimal currency; JPY uses 0 decimals, KWD uses 3). Debit or credit is not a flag but a numeric type code: 100–399 are credits and 400–699 are debits.