The legacy MT path from MT101 and MT103 through cancellation, investigations, returns, confirmations, and statements — with explicit no-equivalent and migration notes.
Asha Traders treasury → Bank Alfa (ordering bank) · MT101
Asha Traders asks Bank Alfa to execute the supplier payment with an MT101. It is the legacy initiation request, not the bank-to-bank customer payment and not proof of execution.
Step 1 of 15: Treasury sends a request for transfer
The bank checks the mandate, message fields, funds, cut-off, routing, and sanctions-screening results. A FIN ACK only confirms network acceptance; pain.002-style business status has no MT equivalent.
Once it accepts the request for execution, Bank Alfa books the customer debit under the account agreement before it releases the interbank MT103.
The correspondent validates FIN fields, checks Bank Alfa's account, screens the parties and narrative data, and decides whether it can book and forward the payment.
Meridian debits Bank Alfa's USD account and credits Nordbank's USD account. The ledger movement is the settlement; the MT103 is the instruction.
Nordbank checks the beneficiary account, screens the payment, and matches the instruction to the credited nostro entry before paying its customer.
Nordbank books the credit to Northstar Components. A later cancellation is now a recovery request; the original credit cannot be erased by sending another message.
What this simplifies: A legacy teaching composite, not a recommendation to start new MT implementations. It joins corporate initiation, serial correspondent settlement, investigations, returns, and two account-reporting perspectives; bilateral services and migration dates vary.
EVIDENCE AT ARM'S REACH
These resources cover the message conversations explicitly authored in this flow. Scheme-neutral teaching files still require validation against the profile used in production.
An XSD checks XML structure. A usage guideline adds profile rules, conditional fields, code restrictions, and business controls. XSD-valid does not mean scheme-compliant.
The annual MT standard and release information. Full field specifications may require an authenticated Swift account.
Non-binding market practice for structured party data, cover payments, investigations, and the transition between MT and ISO 20022 reporting.
A compact FIN-style customer payment with fictional parties and account data. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:bd8c51c4A fictional corporate request for transfer — the customer-side instruction that precedes the interbank MT103. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:0005a988A fictional single-entry debit advice. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:30dc40c8A fictional single-entry credit advice. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:a6674afcA fictional end-of-day account statement. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:08d809ddA fictional intraday balance report. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:840c7d82A fictional intraday entry report. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:d5f49743A fictional interbank account statement. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:1f1aadc4A fictional legacy MT103 carrying a /REJT/ convention in field 72. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:00d34508A fictional legacy MT103 carrying a /RETN/ convention in field 72. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:21271c74A fictional structured request to cancel an earlier MT103. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:b9a5eb01A fictional structured query about a previous MT103. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:426d155eA fictional answer to an MT192 or MT195; the response is not proof that return value settled. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:ee0ddb7fA fictional free-format payment investigation used only where no more specific structured message fits. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:6379a2cfInitiation, serial and cover context, cancellation and correspondence, advices, and statements.
crc32:8b3a20e4Field correspondence, transformation treatment, and data-loss notes for Cross-border customer credit transfer translation, in the spirit of public CBPR+ and PMPG translation guidance. Educational summary — the applicable usage guideline is the rule.
crc32:47a46ccbField correspondence, transformation treatment, and data-loss notes for Request-for-transfer to customer credit transfer initiation. Corporates migrating channel formats meet this mapping first.
crc32:52591871Field correspondence, transformation treatment, and data-loss notes for Legacy negative-status convention compared with a structured FI-to-FI status report. This is a business-semantic comparison, not a claim that pacs.002 has a standalone MT equivalent.
crc32:a90c5f46Field correspondence, transformation treatment, and data-loss notes for Legacy return-payment convention compared with the structured ISO 20022 payment return.
crc32:a221a68dField correspondence, transformation treatment, and data-loss notes for Bank-to-bank request for cancellation of a previously sent payment instruction.
crc32:cac48d1aField correspondence, transformation treatment, and data-loss notes for Legacy answer to a cancellation/query compared with a structured resolution of investigation.
crc32:6cd3cfd2Field correspondence, transformation treatment, and data-loss notes for Legacy payment query compared with a structured investigation request.
crc32:cf0328edField correspondence, transformation treatment, and data-loss notes for Legacy answer compared with a structured investigation response.
crc32:efa3234eField correspondence, transformation treatment, and data-loss notes for Free-format category-1 query compared with a structured investigation request.
crc32:4f8da59eField correspondence, transformation treatment, and data-loss notes for Free-format category-1 answer compared with a structured investigation response.
crc32:f2fa44acField correspondence, transformation treatment, and data-loss notes for Single debit advice compared with a structured bank-to-customer debit/credit notification.
crc32:96b16a98Field correspondence, transformation treatment, and data-loss notes for Single credit advice compared with a structured bank-to-customer debit/credit notification.
crc32:baee9a30Field correspondence, transformation treatment, and data-loss notes for Intraday balance reporting migration.
crc32:739da5e8Field correspondence, transformation treatment, and data-loss notes for Interim transaction reporting migration.
crc32:6c2b3d52Field correspondence, transformation treatment, and data-loss notes for Customer statement migration from compact FIN lines to structured ISO 20022 entries.
crc32:6bcf9eecField correspondence, transformation treatment, and data-loss notes for Interbank statement migration to a structured bank-to-customer statement.
crc32:5c7c7b44Curated field requirements, contexts, operational meaning, and implementation cautions.
crc32:2acadbd0Curated field requirements, contexts, operational meaning, and implementation cautions.
crc32:843abd95Curated field requirements, contexts, operational meaning, and implementation cautions.
crc32:c04ea1baCurated field requirements, contexts, operational meaning, and implementation cautions.
crc32:793b29f1Curated field requirements, contexts, operational meaning, and implementation cautions.
crc32:04c55911Curated field requirements, contexts, operational meaning, and implementation cautions.
crc32:21dbbb94Curated field requirements, contexts, operational meaning, and implementation cautions.
crc32:d7a561d5Curated field requirements, contexts, operational meaning, and implementation cautions.
crc32:ee953655Curated field requirements, contexts, operational meaning, and implementation cautions.
crc32:cbc473d4Curated field requirements, contexts, operational meaning, and implementation cautions.
crc32:04be2398Curated field requirements, contexts, operational meaning, and implementation cautions.
crc32:28b44d2aCurated field requirements, contexts, operational meaning, and implementation cautions.
crc32:ced8839aPositive and negative test cases across validation, rejection, return, recall, reversal, investigation, reconciliation, migration, instant payments, and screening.
crc32:98c48cc7A practical control list for semantic transformation and coexistence risk.
crc32:50787584Swift 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.
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.
Payments Signal editorial teaching models — Payments Signal
What this simplifies: One serial correspondent chain and one set of bilateral reporting services. MT usage is presented as legacy/transition context; availability and retirement dates vary by message purpose and Swift programme milestone.
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.
Share an operational observation or ask a concrete payments question. Your name and message are public; your email remains private.
Loading the discussion…