Reports all entries booked to an account over a statement period in a compact bank-to-bank statement format. It is widely used for financial-institution account reconciliation.
DIRECTION: Sent by an account servicing institution to the financial institution that owns the serviced account.
Version + profile: MT950 follows the applicable Standards MT release and service rules. This page is a curated field subset; bilateral practice and annual standards changes can alter permitted content and handling.
EVIDENCE AT ARM'S REACH
Start with the exact message version, then apply the scheme or network profile that governs your implementation.
An XSD checks XML structure. A usage guideline adds profile rules, conditional fields, code restrictions, and business controls. XSD-valid does not mean scheme-compliant.
The annual MT standard and release information. Full field specifications may require an authenticated Swift account.
A fictional interbank account statement. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:1f1aadc4Initiation, serial and cover context, cancellation and correspondence, advices, and statements.
crc32:8b3a20e4Field correspondence, transformation treatment, and data-loss notes for Interbank statement migration to a structured bank-to-customer statement.
crc32:5c7c7b44Curated field requirements, contexts, operational meaning, and implementation cautions.
crc32:ced8839aCurated teaching subset. The complete MT950 specification defines field options, repetition, pagination, and balance rules.
| FIELD | NAME | PRESENCE | WHAT IT MEANS |
|---|---|---|---|
:20: | Transaction reference | MANDATORY | Reference assigned to the statement message. |
:25: | Account identification | MANDATORY | Account covered by the statement. |
:28C: | Statement and sequence number | MANDATORY | Number and page sequence of the statement. |
:60F: | Opening balance | MANDATORY | Booked balance before the reported entries. |
:61: | Statement line | OPTIONAL | One booked debit or credit with date, amount, and references. |
:62F: | Closing balance | MANDATORY | Booked balance after the reported entries. |
The whole MT950 laid out as a parent-child tree: every field in its nesting, with a sample value and what it means. Expand a branch to drill in. Values are fictional (SYNTHETIC / TRAINING ONLY); this is a curated practitioner view, not the full schema.
Block 1F01DEMOGB2LAXXX0000000000MandatoryBasic header — identifies the sender and the session (application id, service id, the sender's logical-terminal address built on its BIC, session and sequence numbers).Block 2I950DEMODEFFXXXXNMandatoryApplication header — the message type, the counterparty address, whether it is input or output, and the priority.Block 4—MandatoryText — the business content, as numbered :tag: fields. The only block whose shape changes by message type.:20:DEMO-MT950-001MandatoryReference assigned to the statement message.:20:DEMO20260712:25:DE02120300000000202051MandatoryAccount covered by the statement.:28C:198/1MandatoryNumber and page sequence of the statement.:60F:C260718EUR50000,00MandatoryBooked balance before the reported entries.:61:2607180718D1250,00NTRFDEMOE2E001//DEMOREF001OptionalOne booked debit or credit with date, amount, and references.:62F:C260718EUR48750,00MandatoryBooked balance after the reported entries.ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · pain/pacs/camt message-definition elements
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group) · cross-border agent chain and structured-data usage
Full guidelines require MyStandards access. Public guidance states that after 14 November 2026 fully unstructured addresses are removed for in-scope CBPR+ traffic, with explicit message exceptions including admi.024, camt.025, camt.052, camt.053, camt.054 and camt.060.
Swift Standards MT (annual standards releases) ↗ — Swift · FIN block structure
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login. Coexistence for in-scope FI-to-FI payment instructions ended on 22 November 2025, but treatment differs by MT: some instructions are NAKed and selected messages can enter temporary, chargeable contingency conversion. Reporting, initiation, investigations and correspondence follow separate roadmaps.
Payments Signal editorial teaching models — Payments Signal
What this simplifies: One-line plain-language descriptions of the commonly-populated elements — a practitioner view, not the authoritative ISO 20022 / MT schema, which defines many more optional elements.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Swift Standards MT (annual standards releases) ↗ — Swift · Category 9 — MT950 Statement Message
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login. Coexistence for in-scope FI-to-FI payment instructions ended on 22 November 2025, but treatment differs by MT: some instructions are NAKed and selected messages can enter temporary, chargeable contingency conversion. Reporting, initiation, investigations and correspondence follow separate roadmaps.
Payments Signal editorial teaching models — Payments Signal
What this simplifies: One-page correspondent statement is shown.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Share an operational observation or ask a concrete payments question. Your name and message are public; your email remains private.
Loading the discussion…