SWIFT MT942 field
MT942 field :90D: / :90C: Number and Sum of Entries
Optional in an MT942: how many debit entries (:90D:) and credit entries (:90C:) the report holds, and their totals.
| :90D: (optional) | Number and Sum of Entries (debits): How many debit entries the report holds and their total. |
|---|---|
| :90C: (optional) | Number and Sum of Entries (credits): How many credit entries the report holds and their total. |
| Format | 5n3!a15d |
| Message | MT942 interim transaction report |
| In camt.053 | Not converted (MT942) |
Format
The format is written in SWIFT notation: 5n3!a15d. 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”:
:90D:1EUR99,00
:90C:1EUR1250,00| Part | Meaning |
|---|---|
:90D:1 | One debit entry … |
EUR99,00 | … totalling 99.00 EUR. |
:90C:1EUR1250,00 | One credit entry totalling 1,250.00 EUR. |
In ISO 20022
MT942 is not converted on this site. The same check exists in camt: the transaction summary (TxsSummry) of a camt.052 or camt.053 counts and sums the entries too.
Checks the viewer runs
mt.summary: Entry totals differ (MT942 :90D: / :90C: number and sum of entries)
Worth knowing
- The validator recounts the :61: lines and reports totals that differ (mt.summary).
Read :90D: / :90C: 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>"
}
}
}