Is camt.053 replacing MT940?

camt.053 is the ISO 20022 equivalent and banks increasingly offer it, but the MT940 was not part of the November 2025 cut-over for payment instructions: reporting messages remain supported on Swift FIN until an end date is set. Check with your bank which formats it will keep.

What is the difference between camt.052, camt.053 and camt.054?

camt.053 is the end-of-period statement (like MT940), camt.052 the intraday account report (like MT942) and camt.054 a debit or credit notification for individual entries (like MT900 and MT910).

Where is the UETR in a camt.053?

In Stmt/Ntry/NtryDtls/TxDtls/Refs/UETR, next to the end-to-end and instruction references. MT940 has no field for it.

What do PMNT, RCDT and XBCT mean?

They are the domain, family and sub-family of the ISO bank transaction code: payments, received credit transfers, cross-border credit transfer. Together they replace the four-character transaction type of MT940 field 61.

What is lost when a camt.053 is converted to MT940?

The UETR and end-to-end reference (unless copied into field 86), references longer than 16 characters, the individual payments inside batch bookings, structured names, addresses and remittance data beyond the 6 lines of field 86, and the detailed bank transaction code.

Statements

What is the difference between camt.053 and MT940?

Written and maintained by ZagTrader. Last reviewed 21 October 2026. How this page is sourced and checked

Both are end-of-day account statements: the MT940 in Swift FIN format and camt.053 (Bank to Customer Statement) in ISO 20022 XML. camt.053 carries the same balances and booked entries, but adds structured references (end-to-end reference, UETR), a three-level bank transaction code, full party and remittance details and the individual transactions inside a batch. Converting camt.053 to MT940 loses most of that extra detail.

What it means

An MT940 is a flat list: header fields (20, 25, 28C), an opening balance (60a), one field 61 per entry with up to six lines of field 86 text, a closing balance (62a) and optional available balances (64, 65). Everything about the underlying payment that is not in the 61 line has to fit in field 86 as free text, at most 6 lines of 65 characters.

A camt.053 is a tree. Stmt holds the account (Acct), the balances (Bal, each with a type such as OPBD opening booked, CLBD closing booked or CLAV closing available), an optional summary (TxsSummry) and the entries (Ntry). Each entry has its amount, CdtDbtInd (CRDT or DBIT), status (Sts, BOOK for booked), booking and value dates, the bank’s reference and a bank transaction code. Under it, NtryDtls/TxDtls repeats once per underlying transaction, each with its own references, amounts, related parties, agents, purpose and remittance information.

References are where the two differ most. MT940 field 61 has one 16-character reference for the account owner and one for the bank. camt.053 has a Refs block per transaction with separate elements for the message, payment information, instruction and end-to-end identifications (up to 35 characters each), the UETR and others. Reconciliation by end-to-end reference or UETR is only possible from the camt.053.

Transaction codes are structured differently. MT940 uses four characters in field 61 subfield 6: S plus an MT number, or N or F plus a code such as TRF or CHG. camt.053 uses the ISO bank transaction code in BkTxCd/Domn: a domain (PMNT payments), a family (RCDT received credit transfers, ICDT issued credit transfers) and a sub-family (XBCT cross-border credit transfer, ESCT SEPA credit transfer), with an optional proprietary code beside it.

Reversals are expressed differently too. MT940 uses the marks RC and RD in field 61. camt.053 gives the booking direction in CdtDbtInd and sets RvslInd to true: CRDT with a reversal means a debit was reversed, DBIT with a reversal means a credit was reversed.

Multi-page statements work the same way. Where MT940 uses 28C page numbers with 60M and 62M intermediate balances, camt.053 uses StmtPgntn/PgNb and LastPgInd, with the balance sub-type INTM on intermediate opening and closing balances. Under the CBPR+ guidelines for camt.053.001.08, page 1 must carry exactly one OPBD without INTM, and a last page exactly one CLBD without INTM.

For statements, the November 2025 end of MT/MX coexistence for payment instructions did not switch off the MT940: reporting messages remain supported on FIN beyond that date.

Common causes

Reconciliation by end-to-end reference or UETR fails on MT940 because those references only appear, if at all, as free text in field 86.
A batch booking shows as one 61 line in MT940 with one total amount; the individual payments inside it are only listed in camt.053 (NtryDtls/Btch plus one TxDtls per payment).
Bank transaction codes do not map one to one: one MT940 code such as NTRF covers many ISO sub-families, so a rule built on MT940 codes cannot tell a SEPA transfer from a cross-border one.
Names, addresses and remittance text are cut at the field 86 limit when a camt.053 is turned into an MT940.
Reversals booked with the wrong sign after conversion, because RvslInd was ignored or RC and RD were swapped.
Names and addresses in camt.053 can use characters that the narrower FIN character set of the MT940 cannot carry.

How to fix it

Decide what you reconcile on. If you match by end-to-end reference, UETR or invoice number, use camt.053; MT940 gives you only the 16-character references and free text.
Map balances by type, not by position: OPBD to 60F or 60M, CLBD to 62F or 62M (use INTM and the page fields to tell them apart), CLAV to 64.
Map each Ntry to one field 61: ValDt to subfield 1, BookgDt to subfield 2, CdtDbtInd plus RvslInd to subfield 3, Amt to subfield 5, AcctSvcrRef to subfield 8.
Translate the bank transaction code with your bank’s published mapping table; banks publish their own lists of ISO codes against MT940 codes.
For batch entries, read every TxDtls under the entry; in MT940 ask the bank for a separate batch breakdown if you need it.
Run both formats in parallel for a period and compare the totals per day before switching your reconciliation from MT940 to camt.053.

MT940 fields and their camt.053.001.08 elements. Paths are relative to the `BkToCstmrStmt` root and checked against the ISO 20022 schema; balance rules from the CBPR+ camt.053 usage guideline.

MT940	camt.053	Note
20 Transaction Reference Number	`GrpHdr/MsgId`, `Stmt/Id`	camt.053 identifies the message and each statement separately.
25a Account Identification	`Stmt/Acct/Id` (`IBAN` or `Othr/Id`), `Stmt/Acct/Ccy`	Currency is an element of its own in camt.053.
28C Statement/Sequence Number	`Stmt/ElctrncSeqNb` or `Stmt/LglSeqNb`, `Stmt/StmtPgntn/PgNb`, `Stmt/StmtPgntn/LastPgInd`	camt.053 says explicitly which page is the last.
60F / 60M Opening Balance	`Stmt/Bal` with `Tp/CdOrPrtry/Cd` = `OPBD` (`Tp/SubTp/Cd` = `INTM` on later pages)	Amount in `Bal/Amt`, sign in `Bal/CdtDbtInd`, date in `Bal/Dt`.
62F / 62M Closing Balance	`Stmt/Bal` with `CLBD` (`INTM` on pages before the last)
64 Closing Available Balance	`Stmt/Bal` with `CLAV`
61 subfield 1 Value Date	`Stmt/Ntry/ValDt`	Full date (or date and time) instead of YYMMDD.
61 subfield 2 Entry Date	`Stmt/Ntry/BookgDt`	Always a full date; MT940 gives only MMDD.
61 subfield 3 D/C Mark (C, D, RC, RD)	`Stmt/Ntry/CdtDbtInd` and `Stmt/Ntry/RvslInd`	`RD` becomes `CRDT` with `RvslInd` true; `RC` becomes `DBIT` with `RvslInd` true.
61 subfield 5 Amount	`Stmt/Ntry/Amt` with `Ccy`	Dot as decimal mark in XML.
61 subfield 6 Transaction Type	`Stmt/Ntry/BkTxCd/Domn` (domain, family, sub-family) or `BkTxCd/Prtry`	Not a one-to-one mapping; use the bank’s table.
61 subfield 7 Reference for the Account Owner	`NtryDtls/TxDtls/Refs` (`InstrId`, `EndToEndId`, `AcctOwnrTxId` and others)	Several references of up to 35 characters instead of one of 16.
61 subfield 8 Account Servicing Institution Reference	`Stmt/Ntry/AcctSvcrRef`
(no MT940 field)	`NtryDtls/TxDtls/Refs/UETR`	Only in camt.053.
(no MT940 field)	`NtryDtls/Btch` and repeated `TxDtls`	Batch details: number of transactions, total and each payment.
61 subfield 9 and 86 (per entry)	`TxDtls/RltdPties`, `TxDtls/RltdAgts`, `TxDtls/RmtInf`, `TxDtls/AddtlTxInf`, `Ntry/AddtlNtryInf`	Structured parties and remittance instead of 6 lines of free text.
86 (statement level)	`Stmt/AddtlStmtInf`

Example

BANKGB2LXXX reports to ZagTrader Test Bank on GBP account 12345678 for 23 October 2026: one incoming cross-border credit with its end-to-end reference, UETR, payer address and remittance text, and one batch debit of two outgoing payments booked as a single entry. In MT940 the batch would be one field 61 line of 9,000.00, and the payer’s address and the 90-character remittance text would have to be squeezed into field 86.

<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.053.001.08">
  <BkToCstmrStmt>
    <GrpHdr>
      <MsgId>BKGB-STMT-26102300236</MsgId>
      <CreDtTm>2026-10-23T22:05:00+01:00</CreDtTm>
    </GrpHdr>
    <Stmt>
      <Id>ST261023GBP0236</Id>
      <StmtPgntn>
        <PgNb>1</PgNb>
        <LastPgInd>true</LastPgInd>
      </StmtPgntn>
      <ElctrncSeqNb>236</ElctrncSeqNb>
      <CreDtTm>2026-10-23T22:05:00+01:00</CreDtTm>
      <Acct>
        <Id>
          <Othr>
            <Id>12345678</Id>
          </Othr>
        </Id>
        <Ccy>GBP</Ccy>
        <Svcr>
          <FinInstnId>
            <BICFI>BANKGB2LXXX</BICFI>
          </FinInstnId>
        </Svcr>
      </Acct>
      <Bal>
        <Tp>
          <CdOrPrtry>
            <Cd>OPBD</Cd>
          </CdOrPrtry>
        </Tp>
        <Amt Ccy="GBP">150000.00</Amt>
        <CdtDbtInd>CRDT</CdtDbtInd>
        <Dt>
          <Dt>2026-10-22</Dt>
        </Dt>
      </Bal>
      <Bal>
        <Tp>
          <CdOrPrtry>
            <Cd>CLBD</Cd>
          </CdOrPrtry>
        </Tp>
        <Amt Ccy="GBP">166000.00</Amt>
        <CdtDbtInd>CRDT</CdtDbtInd>
        <Dt>
          <Dt>2026-10-23</Dt>
        </Dt>
      </Bal>
      <Ntry>
        <Amt Ccy="GBP">25000.00</Amt>
        <CdtDbtInd>CRDT</CdtDbtInd>
        <Sts>
          <Cd>BOOK</Cd>
        </Sts>
        <BookgDt>
          <Dt>2026-10-23</Dt>
        </BookgDt>
        <ValDt>
          <Dt>2026-10-23</Dt>
        </ValDt>
        <AcctSvcrRef>BKGB2610230077</AcctSvcrRef>
        <BkTxCd>
          <Domn>
            <Cd>PMNT</Cd>
            <Fmly>
              <Cd>RCDT</Cd>
              <SubFmlyCd>XBCT</SubFmlyCd>
            </Fmly>
          </Domn>
        </BkTxCd>
        <NtryDtls>
          <TxDtls>
            <Refs>
              <InstrId>ZT2610200021</InstrId>
              <EndToEndId>INV-2026-0457</EndToEndId>
              <UETR>1529a461-c90a-466b-8b0a-0a709f59ad39</UETR>
            </Refs>
            <Amt Ccy="GBP">25000.00</Amt>
            <CdtDbtInd>CRDT</CdtDbtInd>
            <RltdPties>
              <Dbtr>
                <Pty>
                  <Nm>GULF TRADING LLC</Nm>
                  <PstlAdr>
                    <StrtNm>BUSINESS BAY</StrtNm>
                    <BldgNm>BUSINESS BAY TOWER</BldgNm>
                    <Room>1204</Room>
                    <TwnNm>DUBAI</TwnNm>
                    <Ctry>AE</Ctry>
                  </PstlAdr>
                </Pty>
              </Dbtr>
            </RltdPties>
            <RmtInf>
              <Ustrd>/INV/2026-0457 COMPONENTS ORDER 7781 DELIVERED 15 OCTOBER 2026, SECOND INSTALMENT OF THREE</Ustrd>
            </RmtInf>
          </TxDtls>
        </NtryDtls>
      </Ntry>
      <Ntry>
        <Amt Ccy="GBP">9000.00</Amt>
        <CdtDbtInd>DBIT</CdtDbtInd>
        <Sts>
          <Cd>BOOK</Cd>
        </Sts>
        <BookgDt>
          <Dt>2026-10-23</Dt>
        </BookgDt>
        <ValDt>
          <Dt>2026-10-23</Dt>
        </ValDt>
        <AcctSvcrRef>BKGB2610230131</AcctSvcrRef>
        <BkTxCd>
          <Domn>
            <Cd>PMNT</Cd>
            <Fmly>
              <Cd>ICDT</Cd>
              <SubFmlyCd>XBCT</SubFmlyCd>
            </Fmly>
          </Domn>
        </BkTxCd>
        <NtryDtls>
          <Btch>
            <PmtInfId>ZT-BATCH-261023-01</PmtInfId>
            <NbOfTxs>2</NbOfTxs>
            <TtlAmt Ccy="GBP">9000.00</TtlAmt>
            <CdtDbtInd>DBIT</CdtDbtInd>
          </Btch>
          <TxDtls>
            <Refs>
              <EndToEndId>SUP-2026-1101</EndToEndId>
              <UETR>78b40e10-0683-4470-9eea-33fc85bd0704</UETR>
            </Refs>
            <Amt Ccy="GBP">5500.00</Amt>
            <CdtDbtInd>DBIT</CdtDbtInd>
          </TxDtls>
          <TxDtls>
            <Refs>
              <EndToEndId>SUP-2026-1102</EndToEndId>
              <UETR>c03cb0c0-56a6-43fb-9e60-588700c7a22b</UETR>
            </Refs>
            <Amt Ccy="GBP">3500.00</Amt>
            <CdtDbtInd>DBIT</CdtDbtInd>
          </TxDtls>
        </NtryDtls>
      </Ntry>
    </Stmt>
  </BkToCstmrStmt>
</Document>

Open this example in the parser

Balances: OPBD 150,000.00 + 25,000.00 - 9,000.00 = CLBD 166,000.00. LastPgInd true on page 1 means a one-page statement.

BkTxCd PMNT / RCDT / XBCT is a received cross-border credit transfer; PMNT / ICDT / XBCT an issued one.

The batch entry carries Btch/NbOfTxs 2 and one TxDtls per payment, each with its own EndToEndId and UETR.

Account, references, BICs and UETRs are made up.

Questions

Is camt.053 replacing MT940?: camt.053 is the ISO 20022 equivalent and banks increasingly offer it, but the MT940 was not part of the November 2025 cut-over for payment instructions: reporting messages remain supported on Swift FIN until an end date is set. Check with your bank which formats it will keep.
What is the difference between camt.052, camt.053 and camt.054?: camt.053 is the end-of-period statement (like MT940), camt.052 the intraday account report (like MT942) and camt.054 a debit or credit notification for individual entries (like MT900 and MT910).
Where is the UETR in a camt.053?: In Stmt/Ntry/NtryDtls/TxDtls/Refs/UETR, next to the end-to-end and instruction references. MT940 has no field for it.
What do PMNT, RCDT and XBCT mean?: They are the domain, family and sub-family of the ISO bank transaction code: payments, received credit transfers, cross-border credit transfer. Together they replace the four-character transaction type of MT940 field 61.
What is lost when a camt.053 is converted to MT940?: The UETR and end-to-end reference (unless copied into field 86), references longer than 16 characters, the individual payments inside batch bookings, structured names, addresses and remittance data beyond the 6 lines of field 86, and the detailed bank transaction code.

Messages involved

All troubleshooting · Guides · Codes