GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX
PAYMENTSSIGNAL

The interactive academy for the standards, messages, and rails that move money.

PROGRESS
MT295SWIFT MT

MT295 — Queries

Raises a structured query about a previous Category 2 transfer. It is the category-2 counterpart to MT195, not a value-moving message.

DIRECTION: Sent to the institution expected to answer a query about the earlier Category 2 transfer.

Version + profile: MT295 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.

Contributor Shubham Mathure

DOMAIN + EDITORIAL AUDITAudited 2026-07-18 for payment logic, source scope, technical writing, and Payments Signal voice — see the method.

EVIDENCE AT ARM'S REACH

IMPLEMENTATION RESOURCES

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.

MappingCBPR+current

MT295 → camt.110 implementation mapping

Field correspondence, transformation treatment, and data-loss notes for Category 2 query compared with a structured Case Management investigation request.

Owner
Payments Signal
Checked
2026-07-19
Integrity
crc32:c5b42c10
Access
Payments Signal download · Original, source-backed teaching asset; no login required.
DOWNLOAD
Field matrixBase ISO 20022current

MT295 field matrix

Curated field requirements, contexts, operational meaning, and implementation cautions.

Owner
Payments Signal
Checked
2026-07-19
Integrity
crc32:52f48461
Access
Payments Signal download · Original, source-backed teaching asset; no login required.
DOWNLOAD

WHO IS INVOLVED

  • Query senderIdentifies the original transfer and asks a specific question.
  • Query receiverInvestigates the transfer and answers through MT296 or the applicable service.

KEY FIELDS

Curated teaching subset; complete codes and current migration treatment come from the Standards MT handbook and Swift roadmap.

Key fields of MT295
FIELDNAMEPRESENCEWHAT IT MEANS
:20:Query referenceMANDATORYUnique reference for the query.
:21:Related referenceMANDATORYReference of the original transfer.
:11S:Original message detailsCONDITIONALMessage type and date being queried.
:75:QueryMANDATORYStructured question about the original transfer.
:77A:Additional narrativeOPTIONALSupporting detail needed to answer the query.
Block 3 / field 121UETRCONDITIONALNetwork reference used to locate the original transfer.

COMMON ERRORS

  • Using MT295 without the original references.Consequence: The receiver cannot locate the transfer.Avoid it: Populate the query from the stored original message and UETR.
  • Using a vague query where a cancellation is required.Consequence: The value continues while teams exchange narrative.Avoid it: Choose MT292 when the requested business action is cancellation.

USAGE CONTEXTS

  • Cover investigationUsed to ask about a missing or unmatched Category 2 cover leg.
  • MigrationModern investigation services use structured camt messages under their current reachability rules.
MT295 → CAMT.110

SEE IT IN A PLAYABLE FLOW

LEARN THE CONTEXT

Sources for this reference2
  1. Official requirement

    Swift Standards MT (annual standards releases) ↗ — Swift · Category 2 — MT295 Queries

    Defines the MT message standards (including MT101, MT103, MT202/202 COV, and the MT9xx statement messages) exchanged over the Swift FIN network, maintained through annual standards releases. · Checked 2026-07-18

    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.

  2. Simplified educational illustration

    Payments Signal editorial teaching models — Payments Signal

    This site's own simplified teaching models. · Checked 2026-07-12

    What this simplifies: One cover-payment query pattern 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.

COMMUNITY SIGNAL

Discuss this learning page

Share an operational observation or ask a concrete payments question. Your name and message are public; your email remains private.

NEXT QUESTION REVIEWMonday, 27 Jul, 8:00 amMonday answer runs use source-supported educational material. Some questions may need owner review.
WHAT ARE YOU SHARING?

Publish only lawful, relevant content. Never include confidential payment or personal data.

Public discussion

LOADING

Loading the discussion…