SWIFT MT940 field
MT940 field :21: Related Reference
Optional: the reference of the request this statement answers, when it was sent in reply to an MT920 (request message). Scheduled statements leave it out.
| :21: (optional) | Related Reference: Reference of the MT920 request this statement answers, if any. |
|---|---|
| Format | 16x |
| Message | MT940 customer statement (also used by MT942 where the field exists there) |
| In camt.053 | not mapped (noted) |
Format
The format is written in SWIFT notation: 16x. n digits; a capital letters; c capital letters and digits; x any character of the SWIFT set; d a decimal amount with a comma; 16x up to 16 of them; 6!n exactly 6; [ ] optional; 6*65x up to 6 lines of 65.
Annotated example
An illustration (the bundled samples have no such field):
:20:STMT301P1
:21:REQ20261028A| Part | Meaning |
|---|---|
:21: | The tag, right after :20:. |
REQ20261028A | The :20: reference of the MT920 that asked for the statement (16 characters at most). |
Where it goes in camt.053
The MT940 Viewer and the API convert MT940 to camt.053.001.08. For this field:
| MT940 | camt.053.001.08 | Note |
|---|---|---|
| :21: Related Reference | — | Not carried over (camt.053 has no place for the MT920 request reference). |
camt.053 has no element for it; the converter notes that it was left out. The ISO 20022 request for a statement is camt.060.
The whole mapping, field by field, is in camt.053 vs MT940.
Checks the viewer runs
mt.field.length: Field too long (SWIFT MT940/MT942 field lengths)mt.field.order: Field out of order (SWIFT MT940/MT942 field sequence)
Worth knowing
- The viewer shows :21: when it is there; the converter leaves it out and says so in its notes.
Read :21: from a script or an AI agent
Scripts and AI agents can do the same without a browser: POST /api/v1/parse or the MCP tool parse_mt940 returns every statement as JSON: balances, each :61: split into its subfields and each :86: with its structured parts. No key is needed, and the file is processed in memory and never stored (API and MCP docs).
curl -s --data-binary @statement.sta https://iso20022-navigator.com/api/v1/parse{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "parse_mt940",
"arguments": {
"content": "<the file text>"
}
}
}