Common group, all categories
MT n95 Queries (MT295 to MT995)
Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked
MT n95 is the common group message used to ask a question about an earlier message, or about a transaction in it: a missing payment, a figure that does not match, a confirmation that needs checking. The first digit is the category of the message being queried, so an MT395 goes to the treasury team and an MT595 to securities operations. The answer always comes back as an MT n96 in the same category.
- Message type
- MTn95
- Category
- All (n = category digit)
- Structure
- 7 fields listed
- ISO 20022
- camt.110
Message types that use this layout
When MTn95 is used
The query is one of the common group messages that every category shares (see MTn92 for the whole group of n90 to n99). It can be sent from one financial institution to another, from a corporate customer to its bank, or from a bank to a corporate customer, and it can relate to a Swift message or to something that arrived by other means.
The category digit routes the query: 1 Category 1 customer payments (MT195); 2 Category 2 financial institution transfers (MT295); 3 Category 3 treasury markets (MT395); 4 Category 4 collections (MT495); 5 Category 5 securities (MT595); 6 Category 6 precious metals, commodities and syndications (MT695); 7 Category 7 documentary credits and guarantees (MT795); 8 Category 8 travellers cheques (MT895); 9 Category 9 cash management (MT995).
If the query relates to a Swift message, use that message’s category digit: an MT395 about an MT300, an MT995 about an MT950 statement entry. If it relates to nothing on Swift, pick the category that best describes the business.
The question goes in field 75 (six lines of 35 characters), with more room in field 77A. Fields 11a and 79, or a copy of the original fields, identify the message being queried. Swift’s usage guidelines also define numbered standard queries that can be quoted in field 75 instead of free wording.
A query may also ask for an earlier message to be amended, but not where the category has its own way to amend. An FX confirmation is corrected with a new MT300 carrying AMND in field 22A, a documentary credit with an MT707: a query asking for those changes is answered, not acted on.
MTn95 format: sequences and fields
Message text (block 4)Mandatory
Same layout in every category. Field 79 and the copy of the original fields are alternatives: at most one of them.
| Tag | Name | Status | Format | Meaning |
|---|---|---|---|---|
| 20 | Transaction Reference Number | M | 16x | The Sender’s reference for this query. The answering MT n96 quotes it in field 21. No leading or trailing slash and no double slash (T26). |
| 21 | Related Reference | M | 16x | The reference of the original message the query is about, normally its field 20 (or the reference the other side gave it). |
| 75 | Queries | M | 6*35x | The question or questions, up to six lines of 35 characters. Free text or one of the numbered standard queries from Swift’s usage guidelines. |
| 77A | Narrative | O | 20*35x | More text for the query when six lines in field 75 are not enough. |
| 11a | MT and Date of the Original MessageOptions R or S | O | R: 3!n 6!n [4!n6!n] S: 3!n 6!n [4!n6!n] | Type and send date (YYMMDD) of the message being queried, with session number and ISN if known. Option R when the querying party received that message, option S when it sent it. The type must be 100 to 999 (T18). |
| 79 | Narrative Description of the Message to Which the Query Relates | C | 35*50x | A description of the queried message detailed enough for the Receiver to identify it. Not allowed together with the copy of fields (C31). |
| (no tag) | Copy of at least the Mandatory Fields of the Original Message | C | Copy of fields | The fields of the queried message, or of the single transaction in a multiple message, instead of a description. Not allowed together with field 79 (C31); 77F and 77T may not be copied. |
Format notation: n digits, a upper-case letters, c upper-case letters and digits, x any character of the Swift character set, d a decimal number with a comma, ! fixed length, [ ] optional, 4*35x up to 4 lines of 35 characters. M mandatory, O optional, C conditional (a rule decides).
Rules worth knowing
- Either field 79 or a copy of fields of the original message, but not both, may be present (network rule C1, error C31). Swift does not check that copied fields match the original.
- Use the category digit of the queried message; when it was not a Swift message, use the category that best describes the business.
- In field 11a the message type must be from 100 to 999 (T18) and the date a valid YYMMDD date (T50). Option R refers to a message the Sender received, option S to one it sent.
- A query asking for an amendment is not used where the category has a specific message or function for it, for example the MT707 for documentary credits or the amendment function of the MT300.
- In MT195 and MT295, a field 79 whose first line starts with /REJT/ or /RETN/ must follow the payments reject and return guidelines (T80).
- The network accepts a UETR in field 121 of the user header of the MT195, MT295 and MT995, so a query about a tracked payment can quote its UETR.
MTn95 example
On 20 October 2026 ZagTrader Test Bank, Dubai (ZAGTAEADXXX), bought USD 1,000,000.00 against AED from BANKGB2LXXX. BANKGB2L’s MT300 confirmation (reference BGL3002610200011) shows a rate of 3.6730, but ZagTrader’s deal ticket says 3.6725. ZagTrader’s treasury back office queries the confirmation with an MT395.
{1:F01ZAGTAEADAXXX0000000000}{2:I395BANKGB2LXXXXN}{4:
:20:ZTQ2610200004
:21:BGL3002610200011
:75:YOUR MT300 SHOWS RATE 3,6730.
OUR DEAL TICKET SHOWS 3,6725.
PLEASE CHECK AND AMEND OR CONFIRM.
:11R:300
261020
:79:FX DEAL TRADE DATE 261020 VALUE 261022
WE BOUGHT USD1000000,00 AGAINST AED
-}Decode this example in the parserLine by line
| Line | What it says |
|---|---|
| {1:F01ZAGTAEADAXXX0000000000}{2:I395BANKGB2LXXXXN}{4: | Sender ZAGTAEADXXX, input MT395 to BANKGB2LXXX: category 3 because the queried message is an MT300. |
| :20:ZTQ2610200004 | Reference of this query. BANKGB2L will quote it in field 21 of its MT396. |
| :21:BGL3002610200011 | The reference of BANKGB2L’s MT300 being queried. |
| :75:YOUR MT300 SHOWS RATE 3,6730. | The question, at most 6 lines of 35 characters. |
| OUR DEAL TICKET SHOWS 3,6725. | |
| PLEASE CHECK AND AMEND OR CONFIRM. | |
| :11R:300 | Field 11a, option R: ZagTrader received the MT300... |
| 261020 | ...on 20 October 2026. |
| :79:FX DEAL TRADE DATE 261020 VALUE 261022 | Description of the queried confirmation. No copy of fields, because 79 and the copy may not both be present. |
| WE BOUGHT USD1000000,00 AGAINST AED | |
| -} | End of block 4. |
An MT295 or MT995 has exactly the same fields; only the category digit changes. For a customer payment, see the MT195.
BICs, rates and references are made up.
Common errors and rejects
Both field 79 and copied fields (C31)
A query may describe the original in field 79 or copy its fields, not both. Keep the one your system fills reliably.
Field 21 does not identify the original
Field 21 should carry the reference of the queried message. Putting your own internal reference there leaves the Receiver searching, and the query waits.
Line too long in field 75
Field 75 holds six lines of 35 characters. Put the rest of the question in field 77A (20 lines of 35 characters).
Wrong option in 11a
Option R is for a message you received, option S for one you sent. Querying an incoming confirmation with 11S points the Receiver at a message it never received from you.
Query sent in the wrong category
An MT195 about an MT300 reaches the payments team, not the treasury back office. Use the category of the queried message.
Query used instead of a cancellation or amendment message
Asking the Receiver to cancel a message is an MT n92, not a query; correcting a confirmation or a credit uses the amendment mechanism of its category. A query only asks.
MTn95 in ISO 20022
For payments, Clearstream’s ISO 20022 adoption schedule maps MT n95 (and n99) messages to camt.110 Investigation Request, answered by camt.111 Investigation Response. These case management messages are part of the cross-border payments (CBPR+) plan; according to J.P. Morgan, Swift deferred the enquiry and investigation changes from November 2026 to a partial release planned for Q1 2027.
Queries about treasury (category 3), collections (category 4), trade finance (category 7) and securities (category 5) messages were not part of the CBPR+ migration, and the MT395, MT495, MT595 and MT795 remain the queries of those business areas on FIN.
MTn95 questions
- What is an MT n95?
- The common group query: a structured question about an earlier message or transaction, with the same fields in every category from MT195 to MT995.
- Which category digit should a query use?
- The category of the message being queried: MT295 for an MT202, MT395 for an MT300, MT595 for a securities message, MT995 for a statement. If it relates to no Swift message, the category that best fits the business.
- What is the difference between MT n95 and MT n99?
- The n95 is a query about a specific earlier message: it identifies the original by reference, type and date and expects an MT n96 answer. The MTn99 free format message carries any information that has no other message type.
- How is an MT n95 answered?
- With an MT n96 in the same category, quoting the query’s field 20 in field 21 and the answer in field 76. See MTn96.
- Can a query ask for an amendment?
- Yes, except where the category has its own amendment message or function, such as the MT707 for documentary credits or AMND in field 22A of an MT300.
- What is the ISO 20022 equivalent of MT n95?
- For payments,
camt.110Investigation Request, answered bycamt.111. Queries in treasury, collections, trade finance and securities were not part of that migration and stay on MT.
All MT messages · ISO 20022 messages · Codes · Troubleshooting