Purpose
What this converter does
The BAI2 reader validates US-ASCII, record structure and control totals before writing the common generic-v1 CSV layout.
BAI2 → CSV
Export supported BAI2 v2 monetary transactions to predictable CSV rows for analysis and import.
Purpose
The BAI2 reader validates US-ASCII, record structure and control totals before writing the common generic-v1 CSV layout.
Workflow fit
Useful for reconciliation scripts and accounting imports that consume transaction-level rows rather than BAI2 files.
Implementation note
BAI2 record 03 balances and summaries are not turned into transactions. A file with no exportable monetary transactions cannot produce a billable empty CSV.
BAI2 v2
No. CSV exports eligible monetary transactions to the fixed generic-v1 64-column layout. BAI2 record 03 summaries and balances are not fabricated as movements; files with no exportable monetary transactions are rejected.
Only supported BAI Cash Management Balance Reporting v2 (2005) in strict US-ASCII is accepted. File extensions .bai2, .bai and .txt are hints, not proof of validity. BAI1, BAI3 and proprietary bank variants are not promised.
No. For CAMT.053, OFX and MT940 outputs you may need to confirm BOOKED status, dates, balances or statement completeness from genuine evidence. Never attest a value you cannot verify. The backend checks the file again when converting.
Authenticated BAI2 inspection for CAMT.053, OFX or MT940 preparation is free; a successful conversion follows the usual trial or prepaid-credit rules. Inspection readiness does not guarantee a successful output.
Related converters
Explore other production-ready routes connected to this format.