Purpose
What this converter does
The route inspects the BAI2 source and requires v2 evidence for booked entries, posting dates and a dated ledger closing balance.
BAI2 → OFX
Prepare OFX Banking XML 2.3 from supported BAI2 v2 without inventing dates, balances or account indices.
Purpose
The route inspects the BAI2 source and requires v2 evidence for booked entries, posting dates and a dated ledger closing balance.
Workflow fit
Useful when receiving software imports OFX Banking but the available bank export is BAI2 v2.
Implementation note
Not QFX or investments. OFX account overrides can provide permitted technical identifiers only for an authentic server-provided account index; they never change amounts or transaction dates.
BAI2 v2
OFX Banking XML 2.3 requires actual BOOKED status, justified DTPOSTED dates, a dated closing LEDGERBAL and representable account routing. Account metadata is requested only for a server-identified account index, never guessed from the statement index.
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.