MT195 — Queries
Structured investigation request on a prior customer payment. More formal than MT199, MT195 structures questions via tag :75: and triggers an MT196 in reply.
Purpose
MT195 investigates an issue on a past payment: amount mismatch, wrong value date, beneficiary not credited, etc. The structured format (tag :75: with paragraph numbering) enables automated processing on the receiver side.
Block 4 structure
| Tag | Name | Status |
|---|---|---|
:20: | Transaction Reference Number | Mandatory |
:21: | Related Reference (original MT103) | Mandatory |
:75: | Queries (structured questions) | Mandatory |
:11R: | MT and Date of Original Message | Optional |
:11S: | MT and Date Reference | Optional |
:79: | Narrative (additional free text) | Optional |
Real-world example
BNP Paribas asks Deutsche Bank why the beneficiary received 12150 EUR instead of 12500:
{1:F01BNPAFRPPAXXX0000000000}{2:I195DEUTDEFFXXXXN}{4:
:20:QRY260518001
:21:REF20260514001
:75:/1/AMOUNT DOES NOT MATCH BENEFICIARY EXPECTATION
/2/PLEASE CONFIRM AMOUNT IN EUR ACTUALLY CREDITED
/3/AMOUNT EXPECTED: 12500,00 EUR
/4/AMOUNT REPORTED BY BENEFICIARY: 12150,00 EUR
:11R:103
260514
-}{5:{CHK:MNO345678901}}Common pitfalls
- Unnumbered :75: — the spec expects
/N/numbering for each question (used by MT196). - No :11R: or :11S: — on complex chains, without explicitly pointing to the original message, the receiver may be ambiguous.
- :75: too long — max 35 lines of 50 characters.
MX equivalent
Depending on investigation type:
- camt.027 — Claim Non Receipt (beneficiary did not receive).
- camt.087 — Request to Modify Payment.
- camt.029 — Resolution of Investigation (case closure).