SWIFT MT message
MT942 format: SWIFT interim transaction report
MT942 is the SWIFT intraday report: the entries booked (and sometimes expected) since the last report, above a floor limit, with their count and totals. It is the MT counterpart of camt.052. Unlike the MT940 it has no opening or closing balance fields.
| Message | MT942 |
|---|---|
| Name | SWIFT interim transaction report |
| Read by | MT940 Viewer |
Who sends it, and when
The account-holding bank sends it to the account owner during the day, at agreed times or after bookings, over the same channels as the MT940.
The structure of an MT942
:20: Transaction reference
:21: Related reference (optional)
:25: Account identification
:28C: Statement number / sequence number
:34F: Floor limit (one, or one for debits and one for credits)
:13D: Date and time of the report, with UTC offset
:61: Statement line ┐ repeated
:86: Details ┘
:90D: Number and sum of debit entries (optional)
:90C: Number and sum of credit entries (optional)
:86: Information about the report (optional)Versions in use
A SWIFT FIN message type, maintained in SWIFT’s yearly standards releases. The viewer reads it with or without SWIFT headers; the converter on this site does not convert it (its ISO counterpart is camt.052).
An annotated MT942
An excerpt of the sample the viewer opens (fictitious companies, published test account numbers):
:20:INTRA261029-11
:25:NL91ABNA0417164300
:28C:89/3
:34F:EURD0,
:34F:EURC0,
:13D:2610291130+0100
:61:261029C1250,00NTRFNONREF//ABN261029B1
:86:/TRTP/SEPA OVERBOEKING/IBAN/BE68539007547034/BIC/GKCCBEBB/NAME/Br
asserie du Parc/REMI/Invoice 7790
…
:90D:1EUR99,00
:90C:1EUR1250,00“…” marks lines left out.
| In the file | What it says |
|---|---|
:28C:89/3 | Report 89, the third of the day. |
:34F:EURD0, / :34F:EURC0, | Floor limits of zero for debits and for credits: every entry is reported. |
:13D:2610291130+0100 | Produced 29 October 2026 at 11:30, UTC+1. |
:86:/TRTP/…/NAME/…/REMI/… | Details in /CODE/ style: type, counterparty IBAN, BIC and name, remittance. |
:90D: / :90C: | One debit of 99.00 and one credit of 1,250.00: the viewer recounts them. |
Common validation errors
What most often goes wrong in an MT942, and the rule that reports it in the viewer and the API:
mt.summary(Entry totals differ): :90D: or :90C: totals that differ from the :61: lines.mt.field.required(Mandatory field missing): A missing :34F: or :13D:.mt.date(Invalid date): An impossible date or time.mt.field.format(Field format): A field that does not follow its format.
Check an MT942 from a script or an AI agent
Scripts and AI agents can do the same without a browser: POST /api/v1/validate or the MCP tool validate_payment_file returns every issue with its rule id, severity, line and path, and whether the file is valid. No key is needed, and the file is processed in memory and never stored (API and MCP docs).
curl -s --data-binary @mt942-intraday.sta https://iso20022-navigator.com/api/v1/validate{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "validate_payment_file",
"arguments": {
"content": "<the file text>"
}
}
}