Skip to content
FREE TOOL — NO EMAIL REQUIRED

MT ↔ ISO 20022 Message Equivalence Lookup

Look up any SWIFT MT message and find its ISO 20022 equivalent — or start from a pacs/camt/pain message and find the legacy MT it replaced. 21 pairs across payments, cover payments, investigations, returns, reporting, and cheque instructions.

CBPR+ migration is not message-for-message. Every pair below carries an explicit equivalence tier — some MTs map cleanly, some split across several ISO messages, and some have no single ISO replacement at all. Search works either direction and tolerates "pacs 008", "pacs.008", or "pacs008".

MT message(s) ISO 20022 message(s) Tier Business purpose Detail
MT103 pacs.008 Direct CBPR+ replacement The customer credit transfer — ordering a cross-border payment from a debtor to a creditor through the correspondent banking chain. This is the core SWIFT payment instruction. Full reference →
MT110 / MT111 / MT112 camt.107 / camt.108 / camt.109 Direct CBPR+ replacement The cheque lifecycle message set: MT110/camt.107 (Advice of Cheque / Cheque Presentment Notification) advises the drawee/collecting bank that a cheque has been drawn; MT111/camt.108 (Request for Stop Payment / Cheque Cancellation or Stop Request) asks the drawee's agent to stop payment on a specific cheque; MT112/camt.109 (Status of a Stop Payment Request / Cheque Cancellation or Stop Report) reports back the outcome. Read more →
MT191 / MT291 camt.106 Direct CBPR+ replacement Request for Payment of Charges, Interest and Other Expenses — a financial institution requests reimbursement of charges, interest, or other expenses (previously unknown to the receiver) arising from handling a prior transaction. MT191 is the category-1 (customer/FI-facing) variant, MT291 the category-2 (FI-to-FI) variant; both carry an identical official name and differ only in SWIFT message category. Read more →
MT200 pacs.009 Direct CBPR+ replacement Financial Institution Transfer for its Own Account — an FI moving funds between its own accounts held at another institution. Read more →
MT202 pacs.009 Direct CBPR+ replacement General Financial Institution Transfer — an interbank funds transfer where both the ordering and beneficiary parties are financial institutions, executed serially (each agent in the chain instructs the next). This is the non-cover variant; MT202 COV is a separate, owned pair. Read more →
MT202 COV pacs.009 COV Direct CBPR+ replacement The cover-payment settlement leg — moves the interbank funds for a cross-border transfer through reimbursement agents, carrying the Underlying Customer Credit Transfer block (originator/beneficiary data) so intermediary banks can screen for sanctions. Full reference →
MT205 pacs.009 Direct CBPR+ replacement Financial Institution Transfer Execution — sent by the receiver of a category-2 message (MT200/201/202/203/205 or its ISO equivalent) to further transmit the transfer domestically to the beneficiary institution. It is the next-leg execution message, not the initiating order. Read more →
MT210 camt.057 Direct CBPR+ replacement Notice to Receive — sent by an account owner (or a party acting for them) to their account-servicing institution as advance notice that funds will arrive for credit to the account, so the receiving bank can anticipate and match the incoming payment. Read more →
MT942 camt.052 Direct CBPR+ replacement The intraday account report — entries and/or balance information at a point in time during the business day, used for same-day cash position and liquidity sweeping. Full reference →
MT101 pain.001 Close functional match Request for Transfer — sent by an account owner (or a party authorised by the account owner) to a bank, requesting movement of funds from the account owner's account(s) to one or more beneficiaries. Also used in a distinct FI-to-FI 'relay' mode, where a corporate's primary bank forwards the instruction to secondary banks holding the corporate's other accounts. Full reference →
MT103 RETN pacs.004 Close functional match Returns a customer credit transfer that has already been forwarded or settled — for example, when the beneficiary account turns out to be closed. Sent by an agent back to the previous agent in the chain. Read more →
MT192 / MT292 camt.056 Close functional match Request for cancellation — the instructing side asking to recall or cancel a payment already sent. Full reference →
MT196 / MT296 camt.029 Close functional match The answer/response to a cancellation or investigation request — carries the outcome (cancelled, rejected, or partially actioned). Full reference →
MT202 RETN pacs.004 Close functional match Returns an interbank financial-institution transfer (or a cover payment) that has already settled or otherwise cannot be applied further down the chain. Read more →
MT204 pacs.010 Close functional match Financial Markets Direct Debit Message — sent by an exchange, clearing house, or FI to instruct the debtor's agent to move funds from one or more debtor accounts to one or more creditors, where both debtor and creditor are financial institutions. Most commonly used for CCP margin calls; SWIFT's own training material names the ISO module 'Interbank Direct Debit — Margin Collection (pacs.010)'. Read more →
MT195 / MT295 camt.026 / camt.027 / camt.087 Partial / scope split MT195 (category 1) and MT295 (category 2) are both officially named 'Queries' — a general-purpose enquiry message requesting information or clarification on a previous message or transaction, covering many investigation subtypes (missing funds, wrong beneficiary, value-date correction, general clarification) largely via free text and query-type codes. Read more →
MT900 / MT910 camt.054 Partial / scope split The debit/credit confirmation — a per-entry notification as a specific payment posts, with no balance information. Used to match an individual payment to an invoice without waiting for the end-of-day statement. Full reference →
MT940 / MT950 camt.053 Partial / scope split The end-of-day statement — booked entries only, for a closed reporting period. The reconciliation source of truth. Full reference →
MT199 / MT299 No single equivalent Workflow replacement MT199 (Category 1) and MT299 (Category 2) are free-format messages — an escape hatch for any correspondent-banking communication that did not fit a defined structured message type: investigation queries, cancellation requests, general remarks, gpi tracker notes, ad hoc clarifications. Read more →
MT201 / MT203 No ISO 20022 message Workflow replacement MT201 (Multiple Financial Institution Transfer for its Own Account) and MT203 (Multiple General Financial Institution Transfer) batched several FI-to-FI debits or credits into a single message. Read more →
No single MT equivalent pacs.002 Workflow replacement pacs.002 (FIToFIPaymentStatusReport) is sent by an instructed agent to the previous party in the payment chain to report the outcome of a payment instruction — a CBPR+-mandatory negative/rejection status (RJCT), plus an optional set of positive/interim status codes used bilaterally (RCVD, ACTC, ACCP, ACWC, ACSP, ACSC, ACWP, ACCC, PDNG). Read more →

What each equivalence tier means

Direct CBPR+ replacement

Designated CBPR+ replacement, same business function, message-for-message — but field-level fidelity is still not 1:1 (structured addresses, character truncation, party-identification changes).

Close functional match

Same business purpose, but scope or structure differ enough that the mapping isn't mechanical.

Partial / scope split

Scope split — one MT fans out to several ISO messages, or several MTs collapse into one.

Workflow replacement

No single equivalent — ISO 20022 handles the underlying need differently, and what replaces the MT depends on why you were using it.

A tool implying every MT has a clean one-to-one ISO replacement would actively mislead anyone planning a CBPR+ migration. Where a pair is genuinely owned by a full PaymentBrief reference — MT103/pacs.008 field mapping, MT202 COV cover payments, camt investigation messages, or camt account reporting — this table routes to that article rather than duplicating it.

Related references

Sourced from SWIFT's published standards material, iso20022.org message definitions, central-bank and market-infrastructure migration documentation, and bank ISO 20022 implementation guides. Field-level CBPR+ usage guidelines are gated on SWIFT MyStandards and are not the source for any equivalence claim here — where a mapping cannot be established from primary or near-primary sources, it is marked as market practice rather than a published designation. Verify against your bank or SWIFT MyStandards before building a migration process on any single row.