SWIFT MT942 field
MT942 field :13D: Date/Time Indication
Mandatory in an MT942: when the report was produced, with the offset from UTC. An intraday report is a snapshot, so the time matters.
| :13D: (mandatory) | Date/Time Indication: When the report was produced: YYMMDD, HHMM and the UTC offset. |
|---|---|
| Format | 6!n4!n1!x4!n |
| Message | MT942 interim transaction report |
| In camt.053 | Not converted (MT942) |
Format
The format is written in SWIFT notation: 6!n4!n1!x4!n. 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
From the sample MT942 the viewer opens with “Try a sample”:
:13D:2610291130+0100| Part | Meaning |
|---|---|
261029 | Date, YYMMDD: 29 October 2026. |
1130 | Time, HHMM: 11:30. |
+0100 | Offset from UTC: one hour ahead (central European time). |
In ISO 20022
MT942 corresponds to camt.052, which the converter on this site does not produce. The viewer shows the time with its offset.
Checks the viewer runs
mt.field.required: Mandatory field missing (SWIFT MT940/MT942 field specifications)mt.date: Invalid date (SWIFT dates YYMMDD / MMDD)mt.field.format: Field format (SWIFT MT940/MT942 field specifications)
Worth knowing
- Several MT942s a day are normal; the latest one, by :13D:, is the current picture.
Read :13D: 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>"
}
}
}