Requests information about, or an amendment to, a previous Category 1 message. It is the structured legacy query message; recurring payment investigations are migrating toward camt.110 through Swift Case Management.
DIRECTION: Sent by a financial institution to the counterparty expected to answer a query about a previous Category 1 message.
Version + profile: MT195 follows the applicable Standards MT release and service rules. This page is a curated field subset; bilateral practice and annual standards changes can alter permitted content and handling.
EVIDENCE AT ARM'S REACH
Start with the exact message version, then apply the scheme or network profile that governs your implementation.
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.
A fictional structured query about a previous MT103. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:426d155eInitiation, serial and cover context, cancellation and correspondence, advices, and statements.
crc32:8b3a20e4Field correspondence, transformation treatment, and data-loss notes for Legacy payment query compared with a structured investigation request.
crc32:cf0328edCurated field requirements, contexts, operational meaning, and implementation cautions.
crc32:793b29f1Curated teaching subset. The official Standards MT handbook and market-practice guidance define complete query codes, repetition rules, and response conventions.
| FIELD | NAME | PRESENCE | WHAT IT MEANS |
|---|---|---|---|
:20: | Query reference | MANDATORY | Unique case reference for this query. |
:21: | Related reference | MANDATORY | Reference of the original message being queried. |
:75: | Queries | MANDATORY | Coded question and any requested field clarification. |
:77A: | Narrative | OPTIONAL | Additional information needed to explain the query. |
Block 3 / field 121 | UETR | CONDITIONAL | Reference used to locate the original payment across the chain. |
:11S: | Original message details | CONDITIONAL | Message type and date of the transaction being queried. |
Swift Standards MT (annual standards releases) ↗ — Swift · Category 1 — MT195 Queries
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 · Exceptions and Investigations transformation
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 regulatory-information query is shown from a larger code set.
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…