Purpose
What this converter does
The source must prove BOOKED movements, booking/value dates, reconciled dated opening and closing booked balances. The target writer never invents missing values.
CODA 2 → CAMT.053
For eligible source files, confirm real bank facts before creating the requested CAMT.053 version.
Purpose
The source must prove BOOKED movements, booking/value dates, reconciled dated opening and closing booked balances. The target writer never invents missing values.
Workflow fit
For treasury or accounting workflows that need a supported CODA 2 statement imported into a CAMT.053-capable system.
Implementation note
Strict ASCII CODA 2 only. Records with unknown value dates or missing balances may be rejected without a final debit. No CODA inspection endpoint is available.
CAMT.053 conversion details
For eligible source files, confirm real bank facts before creating the requested CAMT.053 version.
Transform a valid CODA 2 bank statement into representable CAMT.053 XML with original statement identity and balances.
Choose the original source, map or verify its account and statement facts as required, select a backend-supported CAMT.053 version and review the preflight before converting.
CODA-specific codes and document details may not fit the target; unsupported semantics are not silently discarded.
CAMT.053 .001.01 through .001.14 are not interchangeable: acceptance depends on the actual XML schema, bank semantics, balances and target representability. Neither a successful parse nor a ZIP proves bank certification.
A verified account has three successful trial conversions. Paid conversions use prepaid credits without a subscription; failed conversions do not use credits. Input limits depend on the route and the current commercial contract. Original financial contents are not published in these pages.
Will every file in this format convert?
No. A valid source file is not enough when real statement dates, balances, status or account identity are missing. The backend can reject an unsupported CAMT.053 version or an unrepresentable source.
Is the output certified by the bank or guaranteed to import?
CODA-specific codes and document details may not fit the target; unsupported semantics are not silently discarded.
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.
Only when the source proves BOOKED status, real booking and value dates, dated opening/closing booked balances and reconciliation for the chosen CAMT.053 .001.02–.001.14 version. Unknown dates and missing balances are never filled in automatically.
Related converters
Explore other production-ready routes connected to this format.