bai2 · us cash management · prior-day & intraday

BAI2 → CSV or Excel

US bank cash-management files parsed into a clean spreadsheet — all record types decoded, type codes labelled, multi-account groups split. Built for US corporate treasury, AR/AP, and ERP integration teams.

Browser-side
BAI2 never leaves your machine. SOX / GLBA friendly.
Record-aware
Decodes 01 file header, 02 group, 03 account, 16 transaction, 49/88/98/99 trailers.
Multi-account
Mixed-account BAI2 files split into one CSV per account number.

CSV output columns

One row per 16-record transaction — drop straight into Excel, SAP, Oracle, NetSuite, Sage Intacct, or Workday.

File ID (01)
Sender ID
Receiver ID
Group ID (02)
Account number (03)
Currency
As-of date
As-of time
Opening ledger
Closing ledger
Opening available
Closing available
Type code (16)
Type description
Amount
Funds type
Bank reference
Customer reference
Text / detail (88)
Record count (49)

Why BAI2 still rules US cash management

ERP bank reconciliation
SAP S/4HANA Cash Management, Oracle Cloud Cash Management, Workday Financials, and Sage Intacct all import BAI2 as a primary statement format.
Multi-bank treasury
US corporates pulling statements from 10–30 banks normalise to BAI2 first, then to CSV for daily cash positioning.
TMS feeds
Kyriba, GTreasury, Coupa Treasury, FIS Quantum, and ION Treasury consume BAI2 — converting to CSV lets you audit before posting.
Migration to ISO 20022
Mid-migration to CAMT.053? Run both formats through this site to verify the new feed matches the old BAI2.

Related tools

FAQ

What is a BAI2 file?+

BAI2 — Bank Administration Institute version 2 — is the dominant cash-management statement format in the United States. Every major US bank (JPMorgan, BofA, Citi, Wells Fargo, US Bank, PNC, BNY Mellon) delivers prior-day and intraday statements as BAI2 to corporate treasury and ERP systems.

What's the difference between BAI2 and MT940?+

BAI2 is the US standard, MT940 is the European/SWIFT standard. They carry the same information — opening/closing balances, summary totals, individual transactions — but use completely different syntax. BAI2 uses comma-delimited record types (01, 02, 03, 16, 49, 88, 98, 99); MT940 uses :tag: blocks. Both are being replaced by ISO 20022 CAMT.053.

Does it decode BAI2 type codes?+

Yes. The full BAI type-code table is built in — 100/400 series for credits, 200/300 series for debits, summary codes 010/015/040/045/100/400, and bank-specific extensions. Each transaction gets a human-readable label alongside the raw numeric code.

Will it work with BAI2 from my bank?+

Yes. JPMorgan Access, Bank of America CashPro, Citi CitiDirect, Wells Fargo CEO, US Bank SinglePoint, PNC PINACLE, BNY Mellon NEXEN, Truist, KeyBank, Fifth Third, M&T, Regions, Huntington, and Comerica BAI2 exports all parse with the same flow.

Is my BAI2 file uploaded?+

No. Parsing runs entirely in your browser — the BAI2 file never leaves your device. Important for treasury teams under SOX, GLBA, or internal data-residency policy.