Purpose
What this converter does
The CSV export contains a fixed 64-column transaction layout. CODA continuation records and non-monetary information are not turned into extra transactions.
CODA 2 → CSV
Export eligible monetary postings from a supported CODA 2 file to CSV. The original file is transmitted unchanged.
Purpose
The CSV export contains a fixed 64-column transaction layout. CODA continuation records and non-monetary information are not turned into extra transactions.
Workflow fit
For accountants importing actual bank movements into a spreadsheet or a downstream CSV workflow.
Implementation note
A valid CODA statement without exportable monetary postings cannot produce a billable CSV output. Strict ASCII input only; non-exported source context may trigger warnings.
CODA 2
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.
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.
CSV requires genuine exportable monetary postings. XLSX can contain useful real account balances even when there are no postings.
Related converters
Explore other production-ready routes connected to this format.