MT940 vs CAMT.053 vs MT942: Format Comparison for Indian Bank Statement Reconciliation

The SWIFT CBPR+ programme completed its cross-border ISO 20022 cutover on 22 November 2025. Cross-border payments now flow on ISO 20022 natively, ending the coexistence window that began in March 2023. For Indian treasury teams, the practical consequence is not the cross-border rail itself — that is the banks’ problem — but the corporate-side delivery of statements. Each major bank is independently deciding when to migrate its corporate customers from MT940 end-of-day statements to ISO 20022 CAMT.053. The result is a multi-year window where reconciliation parsers must consume both formats, plus the intraday MT942 statement, on the same ingestion pipeline. This guide compares MT940, CAMT.053, and MT942 on structure, content, delivery cadence, and reconciliation implications, with specific notes for the major Indian banks.

The Three Formats at a Glance

MT940 is the SWIFT MT (Message Type) end-of-day customer statement, in use since the 1990s. It is a flat text file with fixed tags and semi-structured content. It carries opening balance, all transactions for the period, closing balance, and forward-available balance.

CAMT.053 is the ISO 20022 XML equivalent of MT940, defined under message identifier camt.053.001.xx. It carries the same information as MT940 but in an XML schema with named elements, supporting richer structured remittance information.

MT942 is the SWIFT MT intraday statement, used for partial activity reporting between end-of-day MT940s. It carries transactions since the last MT940 or MT942 plus a forward-available balance, but does not close out the day’s position. The ISO 20022 equivalent is CAMT.052.

Quick-Reference Format Comparison

MT940 Structure

MT940 uses SWIFT block format with field tags. The body of the statement uses six core tags:

• :20: Transaction reference number — sender’s reference for the statement message
• :25: Account identification — the corporate’s account number with the bank
• :28C: Statement number / sequence number — page numbering for multi-page statements
• :60F: Opening balance — debit or credit indicator, date, currency, amount
• :61: Statement line — one per transaction, carrying value date, entry date, debit/credit, amount, transaction type, and bank reference
• :86: Information to account owner — free-text narration linked to the preceding :61: line
• :62F: Closing balance — final balance for the period
• :64: Closing available balance — forward-available balance for next-day position

The :61: tag contains the structured transaction data: value date (YYMMDD), entry date (MMDD), debit/credit code (C, D, RC, RD for credit, debit, reverse credit, reverse debit), amount, transaction type code (N for normal, F for first, S for SWIFT, etc.), and bank reference.

The :86: tag carries the free-text narration. This is where Indian banks place the UTR, counterparty name, and reference number — and where bank-specific narration parsing is required. HDFC prefixes the content with /INF/. ICICI uses a pipe-delimited structure. SBI uses dashes. Each requires a separate parser profile in the reconciliation engine. The narration patterns are documented in companion bank-specific guides.

MT940 file structure for a typical Indian corporate account:

{1:F01HDFCINBBXXXX0000000000}{2:I940...}{4:
:20:STMT260612
:25:50100123456789
:28C:163/1
:60F:C260611INR15234567,89
:61:2606120612C50000,00NTRFNONREF
:86:/INF/NEFT CR:HDFC2616312345678/ABC LTD/INV-001
:61:2606120612D2500,00NCHGNONREF
:86:HDFC CHRG NEFT JUN2026
:62F:C260612INR15282067,89
:64:C260612INR15282067,89
-}

CAMT.053 Structure

CAMT.053 wraps the same information in ISO 20022 XML. The document root is BkToCstmrStmt (Bank to Customer Statement), containing one or more Stmt (statement) elements. Each statement has a header, opening balance, transaction entries, and closing balance. Transaction entries (Ntry) carry amount, credit/debit indicator, status (booked, pending, information), and a transaction details block.

The transaction details block is where CAMT.053 materially exceeds MT940. It includes:

• Structured remittance information (creditor reference, structured invoice references)
• Original ordering customer, ordering bank, intermediary banks as separate named elements
• End-to-end identification and transaction identification as separate fields
• Bank transaction codes following the ISO 20022 BankTxCd standard
• Charges and exchange rate information as structured sub-elements

For Indian banks, the most material advantage is that the UTR (carried as end-to-end identification or as a structured creditor reference) lives in a named field, not embedded in narration free text. Reconciliation engines consuming CAMT.053 can map directly to the UTR without bank-specific regex extraction.

A simplified CAMT.053 transaction entry, shown in code block form:

<Stmt>
  <Id>STMT260612</Id>
  <ElctrncSeqNb>163</ElctrncSeqNb>
  <CreDtTm>2026-06-12T18:30:00+05:30</CreDtTm>
  <Acct><Id><Othr><Id>50100123456789</Id></Othr></Id><Ccy>INR</Ccy></Acct>
  <Bal>
    <Tp><CdOrPrtry><Cd>OPBD</Cd></CdOrPrtry></Tp>
    <Amt Ccy="INR">15234567.89</Amt>
    <CdtDbtInd>CRDT</CdtDbtInd>
  </Bal>
  <Ntry>
    <Amt Ccy="INR">50000.00</Amt>
    <CdtDbtInd>CRDT</CdtDbtInd>
    <Sts><Cd>BOOK</Cd></Sts>
    <BookgDt><Dt>2026-06-12</Dt></BookgDt>
    <NtryDtls>
      <TxDtls>
        <Refs><EndToEndId>HDFC2616312345678</EndToEndId></Refs>
        <RltdPties><Dbtr><Nm>ABC LTD</Nm></Dbtr></RltdPties>
        <RmtInf><Strd><CdtrRefInf><Ref>INV-001</Ref></CdtrRefInf></Strd></RmtInf>
      </TxDtls>
    </NtryDtls>
  </Ntry>
</Stmt>

The same NEFT credit that required /INF/ prefix stripping and slash-delimited parsing in MT940 is available as three named fields in CAMT.053: end-to-end identification (the UTR), debtor name (the counterparty), and creditor reference (the invoice number).

MT942 Intraday Structure

MT942 follows the same SWIFT MT block structure as MT940 but with two key differences. First, there is no closing balance tag (:62F:) — MT942 reports partial activity, not end-of-day closure. Second, the :34F: tag carries a floor limit indicator: transactions below a configurable amount are typically aggregated rather than individually reported, reducing message size for high-volume accounts.

MT942 sequence numbering uses the same :28C: tag as MT940 but increments multiple times per day. A typical daily sequence at HDFC CMS:

• 09:00 — MT940 for previous business day (sequence 162)
• 11:00 — MT942 intraday partial (sequence 163/1)
• 13:00 — MT942 intraday partial (sequence 163/2)
• 15:00 — MT942 intraday partial (sequence 163/3)
• 17:00 — MT942 intraday partial (sequence 163/4)
• 19:00 — MT940 end-of-day for current business day (sequence 163)

The reconciliation engine should treat MT942 files as position updates only — feeding the live cash position dashboard but not closing out the matching cycle. Final closure runs against the 19:00 MT940 (or its CAMT.053 equivalent).

ISO 20022 defines CAMT.052 as the intraday equivalent of MT942. CAMT.052 is structurally similar to CAMT.053 but omits the closing balance element. As Indian banks migrate to ISO 20022, MT942 deliveries are expected to transition to CAMT.052 on the same timeline as MT940 to CAMT.053.

CBPR+ Migration Timeline

SWIFT’s CBPR+ (Cross-Border Payments and Reporting Plus) programme defined the migration timeline for cross-border payments and reporting:

• March 2023 — Coexistence window opens; banks can send and receive both MT and MX (ISO 20022) for cross-border payments
• November 2025 — Coexistence window closes; cross-border MT decommissioned for payment instruction messages (pacs.008, pacs.009, pacs.004)
• Beyond November 2025 — Customer-facing statements (camt.053, camt.052) and reporting messages continue rolling out at each bank’s own pace

The November 2025 cutover applies to the cross-border interbank rail, not to corporate customer statement delivery. Banks make independent decisions about when to migrate their corporate customers from MT940 to CAMT.053. For most Indian corporates, the practical horizon is:

• 2026 — Major private banks (HDFC, ICICI, Axis, Kotak) offer CAMT.053 as an opt-in alongside MT940. Most corporates remain on MT940 because their ERP integrations are MT940-based
• 2027-2028 — ERP vendors complete CAMT.053 connector rollout; corporate adoption accelerates
• 2029+ — Bank-side MT940 deprecation; CAMT.053 becomes the default and MT940 is delivered only for legacy contracts

Reconciliation parsers built today should accept both formats on the same ingestion pipeline rather than betting on a single format winning quickly.

Worked Rupee Example

A treasury team at a mid-market manufacturer consumes statements from five banks: HDFC and ICICI (CMS clients, MT940 + MT942 available), Axis (CMS client, MT940 only currently, CAMT.053 in pilot), Yes Bank (NetBanking CSV only), and Bank of Baroda (PSU, MT940 via SFTP, no MT942). The team processes 18,500 statement lines per month.

Current setup uses a single MT940 parser. Yes Bank CSV is hand-loaded by an analyst (4 hours per month). Axis CAMT.053 pilot output is discarded because the parser does not support XML. End-of-day cash position is visible at 19:00 each business day; intraday visibility is manual via NetBanking screens.

Format-aware setup: ingestion accepts MT940, MT942, CAMT.053, and CSV. MT942 feeds an intraday cash position dashboard refreshing every two hours. Axis CAMT.053 is consumed in parallel with MT940 (same data, different format) — the team starts validating the CAMT.053 mapping against MT940 today so the eventual MT940 deprecation is a clean cutover. Yes Bank CSV ingestion is automated. Intraday visibility improves from 19:00-only to every two hours. Manual analyst time on Yes Bank falls from 4 hours per month to under 30 minutes.

The format-aware setup also de-risks the MT940-to-CAMT.053 transition. When Axis or any other bank deprecates MT940, the only work required is flipping the format selection — the canonical statement model and downstream matching are unchanged.

To model the analyst time and exception cost of your current versus target format setup, use the Three-Way Match Exception Cost Calculator — input your monthly statement volumes, current exception rate, and analyst cost to size the saving.

Indian Bank Specifics

HDFC CMS delivers MT940 end-of-day and MT942 intraday on configurable cadences. CAMT.053 is available for select corporate customers on request. The :86: free-text format uses the /INF/ prefix described in companion guides.

ICICI Bank similarly delivers MT940 end-of-day and MT942 intraday for CMS clients. ICICI’s :86: format uses pipe-delimited structured fields. CAMT.053 rollout is in pilot as of mid-2026.

SBI delivers MT940 end-of-day for corporate clients on SFTP. MT942 intraday is available for top-tier corporate relationships. SBI’s narration formats follow the TRANSFER FROM and TRANSFER TO convention with dash separators. CAMT.053 is on the bank’s published roadmap but no firm date is in the public domain.

Axis Bank delivers MT940 plus MT942 for CMS clients with CAMT.053 in active pilot. Several corporates already receive parallel MT940 and CAMT.053 to validate the new format.

PSU banks (Bank of Baroda, Canara, Union Bank, PNB) have variable MT942 support and slower CAMT.053 timelines. For corporates with significant PSU bank balances, plan to consume MT940 end-of-day for the foreseeable horizon and seek MT942 only where the bank explicitly supports it.

The Reserve Bank of India publishes payment system and settlement guidance that frames the underlying domestic rails (NEFT, RTGS, NACH) feeding all three formats — bookmark its master directions on payment and settlement systems for the regulatory backdrop.

For enterprise teams scoping a new reconciliation deployment, bank reconciliation software India should accept MT940, MT942, CAMT.053, and bank-specific CSV on the same ingestion pipeline, with a single canonical statement model that downstream matching consumes. A full reconciliation software India implementation also covers ledger, statutory, and platform settlement reconciliation alongside bank reconciliation. See MT940 bank statement reconciliation India for the deep dive on MT940 itself, HDFC bank reconciliation India for HDFC-specific narration and CMS notes, and multi-bank reconciliation India for unifying multiple banks and formats under a single reconciliation cycle.