SWIFT message types and ISO 20022 practice
Payment instructions and statements
A payment instruction and a bank statement describe different events. An instruction requests a transfer. A statement reports account entries and balances. Receiving a copy of an instruction doesn’t, by itself, establish that the beneficiary has been credited.
In the course, pacs.008 and legacy MT103 examples represent customer credit-transfer information. camt.053 and legacy MT940 examples represent statement information. These are related business functions, not a promise that every field converts one to one. The Swift reference guide maps customer and bank roles, and the ISO 20022 catalogue provides approved message definitions and versions.
A fictional MT103 excerpt
This shortened excerpt is for reading practice. It omits required message structure and cannot be submitted to a payment network.
:20:WGYM-PAY-0042
:32A:261113USD1250,00
:50K:/TRAINING-DEBTOR
NORTHHAVEN PAPER
:59:/TRAINING-CREDITOR
CEDAR QUAY TOOLS
:71A:SHA
The sender’s reference is WGYM-PAY-0042. Field 32A gives a value date of November 13, 2026, a currency of USD and an interbank settled amount of 1,250.00. The ordering customer and beneficiary customer are different roles; read their identifiers as well as their names. A training account label is deliberately not a bank-account number.
The Swift MT reference gives the official field specifications. Use the version and market practice required by the institution for production work.
An ISO 20022 reading task
Suppose an original training record identifies Northhaven Paper as debtor, Cedar Quay Tools as creditor, USD as currency and 1,250.00 as the settlement amount. Before matching it to a statement, compare its reference, currency and amount. A same-sized payment in another currency isn’t a match. Two entries with the same amount need more evidence than an amount-only join.
The simulator teaches a subset of the message shapes. It doesn’t validate a complete ISO schema, a network usage guideline or a bank’s production acceptance rules. It also doesn’t send money.
Reconciliation practice
Work through the customer credit transfer, the statement and statement reconciliation. For historical record reading, compare MT103 with MT940. Every case uses fictional names and amounts.
Keep a payment’s instruction, status evidence and statement entry separate until the records support your conclusion. The AML and KYC course gives you the customer and investigation context around those messages.