Purpose
What this converter does
The source must prove BOOKED transactions, real posting dates and reconciled, dated opening/closing balances. OFX account metadata must be genuine and consistent.
All converters
CODA 2 → OFX
CODA 2 → OFX
Export eligible CODA 2 statements to OFX Banking XML 221 without inventing bank account identities, posting dates or balances.
Workflow fit
When this route is useful
For banking or bookkeeping software that imports OFX XML from compatible Belgian CODA 2 statements.
Implementation note
What to expect
Strict ASCII CODA 2 only. You may supply account metadata only when you know the exact 1-based sourceAccountIndex; no CODA inspection endpoint identifies it. Incompatible files are rejected safely.
CODA 2
CODA 2: scope and limitations
What CODA data can be converted?
Only the supported CODA 2 subset in strict ASCII. Source validation and the destination writer run on the server. We never fill in missing balances, transactions or dates.
Is CODA inspection available before conversion?
No public or authenticated CODA inspection endpoint exists. Local byte checks are advisory only; a file may be rejected by the server after a conversion attempt.
Can CODA 2 always be converted to OFX, and can missing account data be repaired?
No. OFX Banking XML 221 requires a real posting date, booked transactions, reconciled balances and valid account metadata. You may supply known details with an explicitly identified 1-based sourceAccountIndex. ValidConvert cannot infer that index or diagnose missing fields from a generic CODA 422 response. No financial values are fabricated.
Related converters
Keep the same source or continue the workflow
Explore other production-ready routes connected to this format.
CODA 2CSV
View converterCODA 2XLSX
View converterCODA 2CAMT.053
View converterCODA 2MT940
View converterOFXCSV
View converterOFXXLSX
View converterOFXCAMT.053
View converterOFXMT940
View converterOFXQIF
View converterOFXQuickBooks Desktop US (IIF General Journal)
View converter