Context: Legacy answer compared with a structured investigation response.
EVIDENCE AT ARM'S REACH
Use the official definitions for both sides of the translation and inspect the original teaching samples before implementing a mapping.
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.
Choose the exact message definition in the official catalogue. The base XSD checks XML structure; it does not prove compliance with a scheme profile.
The annual MT standard and release information. Full field specifications may require an authenticated Swift account.
The network profile that restricts how ISO 20022 payment and reporting messages are used for cross-border traffic.
Adds the November 2026 validation and structured-address changes; implement against the final SR2026 usage guidelines.
Final usage guidelines are published through MyStandards; the public release page gives the implementation timeline.
Open version sourceFedwire message versions, usage guidelines, implementation guidance, testing material, and the controlled route to proprietary schemas.
A fictional structured answer confirming that an investigated payment was credited. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:c322c0c4A fictional answer to an MT192 or MT195; the response is not proof that return value settled. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:ee0ddb7fCustomer and FI cancellation, resolution, return, reversal, and structured investigation messages.
crc32:f4772381Initiation, serial and cover context, cancellation and correspondence, advices, and statements.
crc32:8b3a20e4Field 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 answer compared with a structured investigation response.
crc32:efa3234eField 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 Category 2 query answer compared with a structured Case Management investigation response.
crc32:8d3c9dc6Field correspondence, transformation treatment, and data-loss notes for Residual Category 2 free-format answer compared with a structured investigation response.
crc32:59866077Curated field requirements, contexts, operational meaning, and implementation cautions.
crc32:04c55911Curated field requirements, contexts, operational meaning, and implementation cautions.
crc32:8d2c6383Positive 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:50787584Verified profile constraints with versioned evidence and explicit operating conditions.
crc32:6f8b5902Positive and negative lifecycle tests linked to verified profile rules.
crc32:3b72999aDiscovery, controls, testing and operational-readiness checks for the profile.
crc32:d31e7e73Outcome-focused profile acceptance criteria with honest release gates.
crc32:0bf84f8fVersion, transformation, cutover and reconciliation controls.
crc32:e22fb314Evidence that must be obtained from the owner before production readiness can be claimed.
crc32:3955f552Generated mapping, field-matrix, test, checklist, acceptance-criteria, migration, manifest, checksum, and source-inventory bundle.
crc32:9d2559edGenerated mapping, field-matrix, test, checklist, acceptance-criteria, migration, manifest, checksum, and source-inventory bundle.
crc32:b811f27b| MT196 | camt.111 | CORRESPONDENCE | NOTE |
|---|---|---|---|
:20: | Assgnmt/Id | PARTIAL | The answer reference becomes the response assignment id. |
:21: | OrgnlAssgnmt/Id | PARTIAL | The related query becomes an explicit original-assignment link. |
Block 3 / field 121 | Undrlyg/OrgnlUETR | DIRECT | The original payment UETR carries unchanged. |
:76: answer status | InvstgtnSts | TRANSFORMED | Narrative disposition becomes a structured investigation status. |
:76: answer details | Rspn | TRANSFORMED | The substantive answer is structured and scoped to the requested information. |
:76: requested follow-up | NxtActn | TRANSFORMED | The next action can be represented explicitly. |
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.
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.
Payments Signal editorial teaching models — Payments Signal
What this simplifies: Curated lifecycle-level mapping.
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…