BAI2 to QBO Converter

QuickBooks does not know what a BAI2 record is — it expects OFX SGML wrapped in a .qbo file. A BAI2 statement is a sequence of coded lines: 01/02 headers, 03 account identifiers with balances, 16 transaction detail records, and 88 continuation lines, with amounts stored in cents and direction implied by a three digit type code (100–399 credit, 400–699 debit). None of that means anything to QuickBooks's import screen, which is why banks that only offer BAI2 downloads leave QuickBooks users stuck.

This converter parses the BAI2 file the same way the Excel version does — decoding type codes like 195 (Incoming Money Transfer) and 475 (Check Paid), joining 88 continuation text back onto its transaction, and converting cents to decimal amounts — then builds a proper OFX <STMTTRN> block per transaction with a mapped TRNTYPE and a unique FITID.

• FITID deduplication — every transaction needs a unique financial institution transaction ID, or QuickBooks silently drops it as a repeat. FITIDs here are built from the BAI2 bank reference or customer reference, falling back to date+amount when neither is present.
• TRNTYPE mapping — BAI type codes and descriptions are mapped to OFX types (CHECK, XFER, DIRECTDEBIT, DEP, FEE, INT) so QuickBooks categorizes transactions sensibly instead of dumping everything as generic debits/credits.
• <INTU.BID> caveat — QuickBooks Desktop only accepts a .qbo file when INTU.BID matches a financial institution it recognizes. If you don't have your bank's value, use the .ofx download instead, which has no such requirement and imports into Quicken, Xero, Wave, MoneyMoney and most accounting tools.