James Allman | JA Technology Solutions LLC
BAI2 File Explorer
Parse BAI2 bank statement files into structured views with type code lookup, transaction details, a duplicate Bank Reference # audit, and CSV export.
BAI2 File Explorer
Parse BAI2 (Bank Administration Institute Version 2) bank statement files into structured views used by corporate treasury departments for bank reconciliation and cash management. Navigate groups, accounts, and transactions in a collapsible tree with opening and closing balances, currency codes, and account identifiers at each level; click any transaction for its type-code description, reference numbers, and addenda text records. File-level control totals are verified against computed sums so hash mismatches surface immediately instead of silently breaking downstream reconciliation. A Reference Audit flags duplicate, blank, and bank-padded all-zeros Bank Reference numbers, per account and across the whole file, the kind of repeated reference that ERP bank-feed imports silently skip. Bank Reference # positions are read per the BAI2 funds-type rules, with a layout override (a simple wizard or a visual field mapper) for banks whose records deviate. Export transactions or the audit as CSV or Excel. All parsing happens client-side. Your statements never leave your browser.
Learn more ↓
Loading interactive explorer...
What Is the BAI2 Format?
BAI2 (Bank Administration Institute Version 2) is the standard file format used by banks to deliver account statements electronically to corporate customers. Each file contains a hierarchy of records: file headers (01), group headers (02), account headers (03), transaction details (16), and corresponding trailer records with control totals. Treasury teams, accounts payable departments, and ERP systems rely on BAI2 files for automated bank reconciliation and cash position reporting.
Why BAI2 Files Are Difficult to Read
BAI2 files are comma-delimited with numeric type codes instead of readable labels. A transaction coded 16,142,125000 means “wire credit of $1,250.00”, but only if you know that type code 142 is “Miscellaneous ACH Credit.” This tool decodes every type code, formats amounts, and groups transactions under their accounts so you can read the statement without a reference manual. To look up a code on its own, see the BAI2 Type Code Reference.
Duplicate Bank References and Silent Import Skips
Many ERP bank-feed imports (Acumatica among them) deduplicate transactions on the Bank Reference # in the Type 16 record. When a bank reuses the same reference for more than one transaction, or pads the field with zeros because the originator supplied none, the import keeps the first and silently skips the rest, often with no warning and no error log, so a deposit or payment simply goes missing from the feed. The Reference Audit in this tool groups duplicate Bank Reference numbers per account and across the whole file and flags blank and all-zeros references, so you can catch the problem before importing rather than hunting a missing transaction afterward. Because the reference does not sit at a fixed column (value-dated and distributed funds-type records carry extra sub-fields, and some banks deviate further), a layout override lets you correct the field positions with a guided wizard or a visual field mapper.
Automating Bank Reconciliation
Manually reviewing BAI2 files is feasible for occasional troubleshooting but not for daily operations. I build automated reconciliation pipelines that ingest BAI2 files from bank SFTP servers, match transactions against ERP records, flag exceptions, and produce reconciliation reports, all without manual file handling. When an automated bank feed misbehaves, a fallback that exports clean per-account files (see the OFX/QFX Explorer) keeps the books moving. Learn about integration services or get in touch to discuss automating your bank reconciliation.
All tools run entirely in your browser. Your data never leaves your machine. Need help? Ask James.