MX vs MT corporate payment lifecycle
Compare the same cross-border corporate payment by business phase: initiation, execution, status, cancellation, return, investigation, and account reporting.
| DIMENSION | ISO 20022 / CBPR+ lifecycle | Legacy MT and transition lifecycle |
|---|---|---|
| Corporate instructionThe business intent aligns, but grouping, structure, and channel rules differ. | pain.001 carries a structured customer credit-transfer initiation. | MT101 requests one or more transfers, including relay use cases. |
| Customer-side status | pain.002 reports group, payment-information, or transaction status with structured reasons. | No exact MT twin; banks used channel status, proprietary reporting, or bilateral free-format messages. |
| Interbank payment and statusA network ACK is not a substitute for either business status model. | pacs.008 carries the customer credit transfer; pacs.002 reports FI-to-FI business status. | MT103 carries the payment. Negative progress was often represented with /REJT/ conventions rather than a standalone status type. |
| Customer cancellation | camt.055 gives the corporate a structured request to its debtor bank. | No exact customer-side MT equivalent; the corporate used an agreed channel or free-format communication. |
| FI cancellation and answer | camt.056 requests cancellation; camt.029 resolves the case. | MT192/292 requests cancellation; MT196/296 carries the answer. |
| Return of settled valueCase acceptance and actual value return remain separate in both operational models. | pacs.004 is a dedicated, linked payment return. | MT103/202 with /RETN/ conventions carried returned value. |
| Investigations | camt.110 and camt.111 provide structured request/response case data. | MT195/198 and MT199 query families, with MT196/198 and MT199 answers, relied more heavily on narrative and bilateral practice. |
| Entry notification | camt.054 can notify debit and credit entries with structured references and parties. | MT900 advises a debit; MT910 advises a credit. |
| Intraday and statement reporting | camt.052 reports intraday balances/entries; camt.053 carries the statement. | MT941/942 cover balance and interim entry reporting; MT940/950 carry customer and interbank statements. |
Sources for this comparison4
- Official requirement
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login. Coexistence for in-scope FI-to-FI payment instructions ended on 22 November 2025, but treatment differs by MT: some instructions are NAKed and selected messages can enter temporary, chargeable contingency conversion. Reporting, initiation, investigations and correspondence follow separate roadmaps.
- Market practice
ISO 20022 Standards (Swift ISO 20022 adoption programme) ↗ — Swift
Do not generalise the payment-instruction deadline to every FIN message. Swift publishes differentiated NAK, contingency-conversion, reporting, initiation and exceptions-and-investigations treatment.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: Comparison is organised by business phase and omits message-version and service-specific conditionals.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.