Bank Statement BAI2 Conversion Platform
Partner banks deliver statements in mixed formats; manual BAI2 conversion makes reconciliation unreliable and peak-season import status was opaque. We built a bank transaction platform with multi-bank import, reconciliation queries, and tagged BAI2 output—consolidating import, audit, and account mapping in one admin UI.
Reference
- Client
- Professional services operations unit
- Industry
- Financial services
- Services
- Enterprise operations systems
Relevant if you need to consolidate multi-bank statements into BAI2 or similar standard formats.
Outcomes
14 banks unified
- Banks supported 14
- Output format BAI2
Scenarios & highlights
- — Operations staff drop statements in inbound folders and run import plus BAI2 generation from the home screen
- — Reconciliation staff select a bank and review imported, unexported transactions before export
- — Parameter maintainers update GL and transaction-type mapping so export tags stay accurate
- — System admins filter execution logs by bank and level, and clear unexported staging when needed
Challenge
1. Partner banks deliver xls/xlsx/csv statements with inconsistent columns and encodings (e.g. Big5)—manual prep is slow and error-prone. 2. Downstream systems require BAI2; manual conversion makes amount and count reconciliation unreliable. 3. On busy days, staff cannot easily see which files are imported and which transactions remain unexported. 4. Transaction summary-to-GL mapping varies by bank and debit/credit type; without a central maintenance UI, export mapping errors are common.
Solution
Built an ASP.NET MVC bank transaction platform: scan per-bank inbound folders, parse Excel/CSV (including Big5) via NPOI, archive sources on success; aggregate unexported rows and emit BAI2-tagged text (01/02/03/16/49/98/99); list unexported details, query execution logs, maintain GL mapping, and clear staging data.
Results
Multi-bank format handling moved from scattered prep to centralized NPOI import—14 banks share one workflow, reducing duplicate data entry. BAI2 generation shifted from manual conversion to tagged output with opening/closing balances per account group; export status updates prevent duplicate runs. Reconciliation and parameter maintenance live in the admin UI: unexported details, filtered execution logs, GL mapping, and staging reset for re-import.