Home › MT940 to CAMT.053 mapping
MT940 to CAMT.053 field mapping
Every MT940 tag and where it goes in an ISO 20022 camt.053 bank statement: 31 rows, for camt.053.001.08 and the older .001.02, with balance type codes and the German :86: subfields. This is the exact mapping our free MT940 to CAMT.053 converter uses. Checked 2026-11-18.
Field mapping table
| MT940 | Meaning | camt.053.001.08 | Note |
|---|---|---|---|
| Statement | |||
:20: | Transaction reference number | BkToCstmrStmt/Stmt/Id | Cut to 35 characters. |
:21: | Related reference (optional) | (not carried) | CAMT.053 has no field for it. |
:25: | Account identification | Stmt/Acct/Id/IBAN | If the account is not a valid IBAN: Stmt/Acct/Id/Othr/Id. |
:28C: | Statement number / sequence number | Stmt/ElctrncSeqNb | The statement number before the slash. |
currency in :60F: | Account currency | Stmt/Acct/Ccy | Also the Ccy attribute of every Amt. |
| Balances | |||
:60F: | Opening balance | Stmt/Bal with Tp/CdOrPrtry/Cd = OPBD | Amt, CdtDbtInd (C = CRDT, D = DBIT) and Dt/Dt from the same line. |
:60M: | Intermediate opening balance (statement split over several messages) | Stmt/Bal with Cd = PRCD | PRCD = previously closed booked balance. |
:62F: | Closing balance (booked) | Stmt/Bal with Cd = CLBD | |
:62M: | Intermediate closing balance | Stmt/Bal with Cd = ITBD | ITBD = interim booked balance. |
:64: | Closing available balance | Stmt/Bal with Cd = CLAV | |
:65: | Forward available balance | (not carried) | Would be Bal Cd = FWAV; our converter does not write it. |
| Entry (:61:) | |||
:61: value date (YYMMDD) | Value date | Stmt/Ntry/ValDt/Dt | |
:61: entry date (MMDD) | Booking date (optional) | Stmt/Ntry/BookgDt/Dt | Missing entry date = the value date. The year is taken from the value date (also across new year). |
:61: mark C / D | Credit or debit | Stmt/Ntry/CdtDbtInd | C = CRDT, D = DBIT. |
:61: mark RC / RD | Reversal of credit / of debit | Stmt/Ntry/RvslInd = true | RC (reversal of a credit) = DBIT, RD (reversal of a debit) = CRDT. |
:61: amount | Amount (comma = decimal mark) | Stmt/Ntry/Amt | Written with a dot: 1250,00 -> 1250.00. |
(none) | Entry status | Stmt/Ntry/Sts/Cd = BOOK.001.02: Stmt/Ntry/Sts = BOOK | MT940 holds booked entries only. |
:61: transaction type (e.g. NTRF, NMSC) | Transaction type identification code | Stmt/Ntry/BkTxCd/Prtry/Cd | German GVC from :86: is added: NTRF+166. |
:61: customer reference (before //) | Reference for the account owner | Ntry/NtryDtls/TxDtls/Refs/EndToEndId | Used only when :86: has no EREF; NONREF becomes NOTPROVIDED. |
:61: bank reference (after //) | Reference of the account servicing institution | Stmt/Ntry/AcctSvcrRef | |
:61: second line | Supplementary details | Stmt/Ntry/AddtlNtryInf | Up to 500 characters. |
| Details (:86:) | |||
:86: EREF (or ?20 EREF+) | End-to-end reference | TxDtls/Refs/EndToEndId | |
:86: MREF (or MREF+) | SEPA mandate reference | TxDtls/Refs/MndtId | |
:86: NAME / ORDP / BENM, ?32 + ?33 | Name of the other party | TxDtls/RltdPties/Dbtr/Pty/Nm (money in) or Cdtr/Pty/Nm (money out).001.02: RltdPties/Dbtr/Nm or Cdtr/Nm (no Pty) | |
:86: IBAN / ACCW, ?31 | Account of the other party | TxDtls/RltdPties/DbtrAcct/Id/IBAN or CdtrAcct/Id/IBAN | Not a valid IBAN: .../Id/Othr/Id. |
:86: BIC, ?30 | Bank of the other party | TxDtls/RltdAgts/DbtrAgt/FinInstnId/BICFI or CdtrAgt/....001.02: FinInstnId/BIC (not BICFI) | Written only when it is a valid BIC. |
:86: REMI / SVWZ+, ?20-?29, ?60-?63 | Remittance information (purpose text) | TxDtls/RmtInf/Ustrd | Split into blocks of 140 characters. |
:86: first 3 digits (GVC) | German business transaction code (Geschäftsvorfallcode) | Stmt/Ntry/BkTxCd/Prtry/Cd (after the + sign) | Example: 166 = SEPA credit transfer. |
:86: ?00 | Booking text | TxDtls/RmtInf/Ustrd | Used only when there is no purpose text. |
| Message | |||
{1:} {2:} blocks | SWIFT envelope | (not carried) | Sender/receiver BIC of the message are not statement data. |
(none) | Message ID and creation time | BkToCstmrStmt/GrpHdr/MsgId + CreDtTm, Stmt/CreDtTm | Made by the converter (MT940 has no such fields). |
Example: one MT940 transaction in CAMT.053
MT940:
:61:2611131113C1250,00NTRFINV-2026-0042//BANKREF77 :86:166?00SEPA-UEBERWEISUNG?20EREF+INV-2026-0042?21SVWZ+Invoice 42 ?30COBADEFFXXX?31DE89370400440532013000?32Muster GmbH
camt.053.001.08 (the entry part):
<Ntry>
<Amt Ccy="EUR">1250.00</Amt> <CdtDbtInd>CRDT</CdtDbtInd> <RvslInd>false</RvslInd>
<Sts><Cd>BOOK</Cd></Sts>
<BookgDt><Dt>2026-11-13</Dt></BookgDt> <ValDt><Dt>2026-11-13</Dt></ValDt>
<AcctSvcrRef>BANKREF77</AcctSvcrRef>
<BkTxCd><Prtry><Cd>NTRF+166</Cd></Prtry></BkTxCd>
<NtryDtls><TxDtls>
<Refs><EndToEndId>INV-2026-0042</EndToEndId></Refs>
<RltdPties><Dbtr><Pty><Nm>Muster GmbH</Nm></Pty></Dbtr>
<DbtrAcct><Id><IBAN>DE89370400440532013000</IBAN></Id></DbtrAcct></RltdPties>
<RltdAgts><DbtrAgt><FinInstnId><BICFI>COBADEFFXXX</BICFI></FinInstnId></DbtrAgt></RltdAgts>
<RmtInf><Ustrd>Invoice 42</Ustrd></RmtInf>
</TxDtls></NtryDtls>
</Ntry>
This is the real output of our converter for the lines above (entry part only).
MT940 vs CAMT.053: the differences
| MT940 | CAMT.053 | |
|---|---|---|
| Format | SWIFT FIN text, lines with tags such as :61: | ISO 20022 XML (camt.053.001.02 to .13) |
| Text per transaction | :86: max 6 lines of 65 characters (390) | Structured fields; RmtInf/Ustrd 140 characters each, several allowed |
| Characters | SWIFT X set: no ä, ß, € or Cyrillic | UTF-8: every language |
| Payer / payee name, IBAN, BIC | Free text inside :86: (bank-specific, e.g. ?32 or /NAME/) | Own elements: RltdPties, RltdAgts |
| References | Customer ref + bank ref in :61:, EREF/MREF inside :86: | EndToEndId, MndtId, AcctSvcrRef, TxId ... each in its own element |
| Transaction type | 4-letter code (NTRF) + bank-specific GVC | Standard Domain/Family/SubFamily code (PMNT/RCDT/ESCT) or Prtry |
| Balances | :60F: :62F: :64: :65: | Bal with type codes OPBD, CLBD, CLAV, FWAV, PRCD, ITBD |
| Batch payments | One :61: line, details often lost | One Ntry with several TxDtls, one per payment |
Questions
What is the CAMT.053 equivalent of MT940?
camt.053 (BankToCustomerStatement) replaces MT940 (Customer Statement Message): both are the end-of-day account statement. camt.052 replaces MT942 (intraday report) and camt.054 replaces MT900/MT910 (debit and credit advice).
Which MT940 field becomes the EndToEndId in CAMT.053?
The EREF in the :86: field (/EREF/ or EREF+). When there is none, our converter uses the customer reference of the :61: line (the part before //); NONREF becomes NOTPROVIDED.
Where do the :60F: and :62F: balances go in CAMT.053?
Into Stmt/Bal elements: :60F: = OPBD (opening booked), :62F: = CLBD (closing booked), :64: = CLAV (closing available); intermediate :60M: and :62M: become PRCD and ITBD.
Is there an Excel version of this mapping?
Yes: download the CSV below (it opens in Excel, LibreOffice and Google Sheets). It has the same rows as the table.
What is lost when converting CAMT.053 back to MT940?
MT940 has less room: text over 6 x 65 characters is cut, letters outside the SWIFT character set are written in Latin letters, and several payments inside one batch entry are merged. The converter lists every cut in its notes.
Which camt.053 version should I write?
camt.053.001.08 unless your bank or accounting program asks for another one; camt.053.001.02 is the older version many older programs still read. The table shows where the two differ (Nm under Pty, BICFI vs BIC, Sts/Cd vs Sts).
Sources: SWIFT MT940 Customer Statement Message field layout; ISO 20022 camt.053 BankToCustomerStatement schema (versions 001.02 and 001.08); German :86: subfields from the DFÜ agreement (Deutsche Kreditwirtschaft). The table is what our converter does; your bank's own MT940 can use other :86: keywords. Checked 2026-11-18. See also SEPA return reason codes and IBAN format by country.