MT942 — Interim Transaction Report

The intraday mini-statement: sent periodically (typically every business hour) or on demand, MT942 summarises an account's activity since the previous cut. Pivot tool of real-time cash management in corporate treasury.

Purpose

MT942 delivers a partial intraday view of an account: list of operations since the previous cut (typically the prior day's MT940 or the previous MT942), plus cumulative debit / credit totals and the threshold above which transactions are included. Differences with MT940:

• no opening or closing balance (interim snapshot);
• filtered by threshold (tag :34F:) — ignores small amounts to reduce volume;
• multiple times per day vs MT940 = once per business day.

Typical usages:

• intraday cash pooling for a corporate group (consolidating subsidiary positions);
• intraday overdraft limit monitoring;
• automatic account sweeping triggers;
• short-term investment triggers (sweep excess cash into MMF).

Block 4 structure

:20:    Transaction Reference Number               (mandatory)
:21:    Related Reference                          (optional)
:25:    Account Identification                     (mandatory)
:28C:   Statement Number / Sequence Number         (mandatory)
:34F:   Floor Limit Indicator                      (mandatory — 1 or 2 occurrences)
:13D:   Date/Time Indication                       (mandatory)
[ :61: Statement Line                              (optional, repeatable)
  :86: Information to Account Owner                (optional, attached to preceding :61:) ]
:90D:   Number and Sum of Debit Entries            (mandatory)
:90C:   Number and Sum of Credit Entries           (mandatory)

Tags in detail

• :20:: MT942 message reference.
• :25:: account.
• :28C:: daily statement number / sequence number (incremented at every intraday cut). Example: 00134/003 = day 134, 3rd intraday cut.
• :34F:: amount threshold. Any transaction below this floor is omitted. One occurrence if same threshold for debit and credit, two if different (typical: D 1,000 / C 500).
• :13D:: date and time of MT942 generation with GMT offset (2605141400+0100 = 14 May 2026 14:00, GMT+01).
• :61:: statement line — one transaction. Dense format: value date, entry date, D/C, amount, transaction code (4!a like NTRF=transfer, NCHK=cheque, NFEE=fee, NMSC=miscellaneous), customer reference, bank reference, fund code.
• :86:: free information attached to the previous :61:. Max 6 lines × 65 chars. Holds payer/beneficiary/purpose details.
• :90D:: count + sum of cumulated debits over the period.
• :90C:: count + sum of cumulated credits over the period.

Real-world example

3rd MT942 of 14 May 2026 issued at 14:00 for ACME SARL: three operations since the previous cut (payroll 5,000, customer receipt 12,500, fee 850.75), threshold 50,000 (artificially low for example readability).

{1:F01BNPAFRPPAXXX0000000000}{2:O9421400260514ACMECORPXXXX12345678952605141400N}{4:
:20:STMT20260514F03
:25:FR7630006000011234567890189
:28C:00134/003
:34F:EUREUR50000,00
:13D:2605141400+0100
:61:2605141100D5000,00NTRFPMT20260514005//BNPP
:86:PAYROLL BATCH ACME FRANCE
:61:2605141315C12500,00NTRFREF20260515012//BNPP
:86:RECEIVED FROM CLIENT 0042 INVOICE 2026-220
:61:2605141345D850,75NFEEFEE20260514//BNPP
:86:BANKING FEE - WIRE TRANSFER
:90D:3F26653,75EUR
:90C:1F12500,00EUR
-}

• :28C:00134/003 — day 134, 3rd intraday sequence.
• :34F:EUREUR50000,00 — threshold 50,000 EUR for debits and credits.
• :13D:2605141400+0100 — generated 14 May 2026 14:00 (GMT+01).
• 3 :61: — one debit payroll, one credit customer, one debit fee.
• :90D:3F26653,75EUR — 3 debits totalling cumulated debits for the day (note: F in 3F is a separator; the example is deliberately simplified).
• :90C:1F12500,00EUR — 1 credit cumulated for the day.

Common errors

• Inconsistent :90D/:90C: totals vs message lines: totals are cumulative for the day, not the sum of lines in this message. A system that recomputes them from current lines is wrong.
• Too-low :34F: floor: an unfiltered MT942 becomes large and costly. Treasury must set a relevant threshold (granularity vs bandwidth trade-off).
• Non-incremented :28C:: sequence (XXX in YYYYY/XXX) must be strictly increasing intraday. Breaking the sequence prevents treasury integrity checks.
• Proprietary :61: transaction code instead of standard: the 4!a code (NTRF, NCHK…) is SWIFT-defined (Annex B). Custom codes (NACM…) without documentation break automated parsers.
• :86: too long or too short: the information block must fit in 6 × 65 chars. Truncating a business label is common in MT942 — hence the appeal of camt.052 (UTF-8, no limit).
• Character set x: same as MT103.

MX equivalent — camt.052

In ISO 20022, MT942 maps to camt.052.001.08 (Bank-to-Customer Account Report) — the intraday counterpart of camt.053 (EOD statement). Some mappings:

Related messages

• MT940 — EOD statement, complements intraday MT942.
• MT900 / MT910 — unit debit/credit tickets feeding the MT942 :61: lines.
• camt.053 — ISO 20022 counterpart of MT940.
• camt.052 — ISO 20022 counterpart of MT942 (Account Report).
• camt.054 — ISO 20022 counterpart of MT900/MT910.