Choose a BAI2 report
Open a UTF-8 .bai, .bai2 or .txt export up to 2 MB.
Download structured JSON from a BAI2 file with accounts, groups, exact amounts, raw transaction codes, references and source descriptions.
The JSON model keeps semantic values without CSV formula escaping or inferred bank-specific type descriptions.
Choose a file, then use Download JSON to save the result.
Also with this file: View report · Download CSV · Download Excel
Open a UTF-8 .bai, .bai2 or .txt export up to 2 MB.
Review groups, account balances, transactions, dates and raw type codes.
Download transaction CSV, a two-sheet Excel workbook or the normalized JSON document.
Understand account and transaction records without reading delimited BAI2 lines.
Prepare type codes, references and exact amounts for spreadsheet review.
Export structured JSON while retaining group and account context.
The details that matter before you use BAI2 Viewer.
This version reads complete 01, 02, 03, 16, transaction-text 88, 49, 98 and 99 records. Other continuation placements and bank-specific extensions fail closed.
Raw three-digit codes remain visible. Credit and debit are classified only for standard 100–399 and 400–699 ranges; other monetary codes remain unclassified.
The tested decimal scales are USD, CAD, EUR and GBP with two places, plus JPY with zero. Other currencies are rejected rather than guessed.
No. The parser displays supported records but does not certify account, group or file control totals, or reconcile balances.
A type 88 line after a supported type 16 transaction extends its description. Other continuation forms are rejected in this version.
CSV has one row per monetary transaction. Type 890 non-monetary detail is omitted with an explicit warning; Excel also has an account statement sheet.
No. Parsing and exports are local. Account numbers, references, filenames and report content are excluded from analytics.