ValidConvert
All converters

MT940 → CODA 2

MT940 → CODA 2

Convert an original MT940 (.mt940/.sta/.txt) to derived CODA 2 .cod with explicit financial review and strict Java validation.

Open MT940 to CODA converterBrowse converters

Purpose

What this converter does

Upload the unchanged MT940; confirm actual :20:, :25:, :28C:, :60F: and :62F: balances and the original :61: entries. Java verifies the source and all financial claims before producing CODA.

Workflow fit

When this route is useful

For treasury and bookkeeping imports accepting derived CODA 2 from complete, representable MT940 statements.

Implementation note

What to expect

Only SIMPLE ASCII output is supported. Annex IV maps four middle digits only and cannot establish an eight-digit CODA code. No guessed data, bank issuance or third-party import guarantee.

CODA 2

MT940 → derived CODA 2: original-source checks

Which MT940 files can be converted?

Submit the original .mt940, .sta or .txt. The source must contain true :20:, :25:, :28C:, dated :60F:/:62F: balances and complete :61: entries. Java rejects cases that cannot become SIMPLE ASCII CODA without losing meaning.

Can annex IV classify all eight digits?

No. Annex IV maps only the four central digits; it cannot establish a complete eight-digit CODA code. You must provide an authentic full code where needed, along with the real IBAN, currency, entries and statement sequence.

Is the CODA official, and what does it cost?

No. Output is technically validated derived CODA 2, not bank-issued, with no guarantee of third-party acceptance. Paid conversion uses one credit per started 10,000,000 input bytes; rejected files do not count as successful conversions.

Related converters

Explore other production-ready routes connected to this format.

MT940DATEV EXTF Buchungsstapel 700/13
Production readydatev-buchungsstapel-700-13-v1
View converter