Purpose
What this converter does
The destination requires v2 evidence: booked status, value dates, dated opening and closing booked balances, a proven period and a completeness declaration.
BAI2 → MT940
Turn supported BAI2 v2 into MT940 with explicit accounting dates and statement reconciliation checks.
Purpose
The destination requires v2 evidence: booked status, value dates, dated opening and closing booked balances, a proven period and a completeness declaration.
Workflow fit
Useful for legacy treasury or accounting software that imports MT940 while the reporting bank supplies BAI2.
Implementation note
Do not substitute interim 03/030 for closing 03/015, default opening balance to zero or copy posting dates to value dates. Generated references may be technical, not original bank IDs.
BAI2 v2
MT940 needs actual booked entries, value dates, dated opening and closing booked balances, a proven period and reconciliation. A 03/030 current ledger is not a 03/015 closing ledger. Technical :20:/:28C: identifiers are not original bank references.
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.