| Field | Meaning | Required |
|---|---|---|
:20: | A unique reference assigned by the sending bank for this statement message. It identifies the statement for tracking and duplicate detection. The customer uses | M |
:21: | The related reference linking this statement to a prior request or agreement, when the statement was sent on request. It helps the customer match the statement | O |
:25: | The account the statement covers, identified by account number with the account owner name. It tells the customer system which ledger account to reconcile. A st | M |
:28C: | The statement number and sequence number that identify this statement in a series. They let the customer detect a missing or duplicate statement. The numbers mu | M |
:60F: | The opening balance of the account for the statement period, with the credit or debit mark, value date, currency and amount. It is the closing balance of the pr | M |
:60M: | An additional opening balance when the statement covers an intraday period or a balance was corrected. It carries the same format as the first opening balance. | O |
:61: | One entry in the statement, representing a single debit or credit with value date, entry date, amount, funds code and narrative. A statement can hold many entri | O |
:86: | Supplementary details for a statement line, giving extra information such as the end to end reference or a narrative description. It can carry the beneficiary n | O |
:62F: | The closing balance of the account for the statement period, with the credit or debit mark, value date, currency and amount. It is the opening balance plus all | M |
:62M: | An additional closing balance when the statement covers an intraday period or a balance was corrected. It carries the same format as the first closing balance. | O |
:64: | A forward available balance showing funds expected to be available on a future date, with the credit or debit mark, date, currency and amount. It helps the cust | O |
:65: | A forward available balance for a later date, with the same format as the first available balance. It shows the expected balance after future dated entries are | O |
Meridian Bank sends an MT940 to a corporate customer for account 77012345 covering 5 November 2026, opening balance EUR 120,000.00, with 14 entries including a credit of EUR 48,250.00 for a supplier receipt. The closing balance is EUR 168,250.00, the control totals agree, and the customer reconciles every entry to its ledger.
Valid example from the message catalogue. Scheme rules: MT940 follows the SWIFT statement rules and remains widely used for customer account reporting, even where ISO 20022 reporting is available. Many banks still send MT940 daily because corporate reconci
Reconciling Statements: MT940, MT950 and camt.053
What you will learn
Your objective. By the end of this lesson, you will be able to explain reconciling statements: MT940, MT950 and camt.053. Reconciliation of an MT940 starts with three control checks before any transaction is matched.
Why it matters. This matters because the message is the payment instruction. A wrong field, a missing element or a misunderstood format is a failed payment, a return, or a compliance breach.
Chapter objective: Learner explains MT940 and MT950 statements, MT910 confirmations, and how opening, closing booked, closing available and forward balances are calculated. Learner uses real examples with amounts, banks and message names to show how the topic works in practice.
Key learning points
- Reconciliation of an MT940
- MT950 reconciliation
- Camt.053 Bank to Customer Statement
- Richer structure
- Break one day old
- Duplicate break
Key terms
Remittance information: Information that explains what a payment is for, such as invoice numbers, contract references or salary month.
Nostro reconciliation: Reconciliation of a bank nostro account against the statement received from the correspondent bank. Operations teams match each nostro entry to a statement entry, investigate breaks, and confirm the...
Reconciliation: The process of comparing records from two sources, such as a bank statement and an internal ledger, to confirm they agree.
SWIFT MT message viewer showing Reconciling Statements: MT940, MT950 and camt.053.
Practise this lesson
Exercise
Read the MT940 starts message described in this lesson and identify its key parts.
Use the message structure, fields and example in this lesson.
- What to do. List the main blocks of the message, name the field that carries the amount, and name the field that identifies the payment.
Correct result. The message is made of blocks, each carrying a part of the payment instruction. The amount field and the identification field are the two a receiving bank checks first, because without them it cannot process or reconcile the payment.
Why. A message is only useful if you can read it. The blocks tell the receiving bank what to do, and the amount and identification fields are what it checks first.
Check your understanding
Practice question
Which of the following best describes reconciling statements: MT940, MT950 and camt.053?
Takeaway and next step
What to remember
The key discipline is the same in every format, namely match on reference, amount, currency and value date, check the balances, and investigate every break by age.
Open the message type from this lesson and inspect its fields, then find the field that carries the amount.
Open the ISO 20022 Message Explorer →
Builds on "MT940 Balances: F60a Opening Balance, F62a Closing Balance (Booked Funds), F64 Closing Available Balance (Available Funds), F65 Forward Available Balance".
Transcript and full text
Show transcript
Reconciliation of an MT940 starts with three control checks before any transaction is matched. First, the statement number in Field 28C must follow the previous statement without a gap, so statement 143 must follow statement 142. Second, the opening balance in Field 60a must equal the previous closing balance in Field 62a. Third, the calculated closing balance, opening plus credits minus debits, must equal Field 62a. Only when those three checks pass does the system match each Field 61 line to an expected entry in the accounting system, using the reference, the amount, the currency and the value date. A line for EUR 320,000 with reference pacs.008 DE 88412 and value date 3 November 2026 should match exactly one expected receipt. The MT950 reconciliation follows the same logic, but the matching is against the bank own nostro ledger rather than a customer accounting system. The receiving bank checks the sequence number, checks that the opening balance equals its own previous closing balance for that nostro account, and checks that the calculated closing balance equals Field 62a. Each Field 61 line is then matched to a payment the bank sent or received through that correspondent. A USD 950,000 debit on the MT950 should match a pacs.009 the bank sent to Singapore on the same value date. If the MT950 shows a debit the bank did not send, or omits a credit the bank expected, the nostro reconciliation team raises a break and contacts the correspondent bank the same day. The camt.053 Bank to Customer Statement is the ISO 20022 equivalent of the MT940, and it carries the same statement information in XML form with richer structured data. A camt.053 has a group header, a statement element with the account, the opening balance, the closing balance and the available balance, and a series of entry elements, each with an amount, a credit or debit indicator, a value date, a booking date and structured remittance information. The same EUR 320,000 credit that appears as a Field 61 line and a Field 86 narrative in an MT940 appears in a camt.053 as an entry with a structured creditor name, a structured invoice reference and a bank transaction code. The richer structure means fewer unmatched items. The three formats coexist because banks and corporates migrate at different speeds. A corporate that has used MT940 for twenty years may keep it for its main operating accounts, while a new subsidiary with a modern treasury system receives camt.053 for the same bank. A bank reconciling nostro accounts may receive MT950 from one correspondent and camt.053 from another, and its reconciliation system must handle both. The key discipline is the same in every format, namely match on reference, amount, currency and value date, check the balances, and investigate every break by age. A break that is one day old may be a timing difference, while a break that is thirty days old is a real error. Common breaks fall into a small set of patterns, and recognising them speeds up resolution. A timing break occurs when a payment is booked on 3 November in the bank system but on 4 November in the customer system, so the amounts match but the dates differ by one day. A value break occurs when the amounts differ, for example a EUR 320,000 payment arrives as EUR 319,850 after EUR 150 in charges, and the system must decide whether the difference is a charge or an error. A missing item break occurs when a line appears on the statement but not in the ledger, or the reverse, often because a payment was made by a different channel. A duplicate break occurs when the same reference appears twice. Each break needs an owner, an age and a resolution, and the reconciliation report must show the ageing every day.
Reconciliation of an MT940 starts with three control checks before any transaction is matched. First, the statement number in Field 28C must follow the previous statement without a gap, so statement 143 must follow statement 142. Second, the opening balance in Field 60a must equal the previous closing balance in Field 62a. Third, the calculated closing balance, opening plus credits minus debits, must equal Field 62a. Only when those three checks pass does the system match each Field 61 line to an expected entry in the accounting system, using the reference, the amount, the currency and the value date. A line for EUR 320,000 with reference pacs.008 DE 88412 and value date 3 November 2026 should match exactly one expected receipt.
The MT950 reconciliation follows the same logic, but the matching is against the bank own nostro ledger rather than a customer accounting system. The receiving bank checks the sequence number, checks that the opening balance equals its own previous closing balance for that nostro account, and checks that the calculated closing balance equals Field 62a. Each Field 61 line is then matched to a payment the bank sent or received through that correspondent. A USD 950,000 debit on the MT950 should match a pacs.009 the bank sent to Singapore on the same value date. If the MT950 shows a debit the bank did not send, or omits a credit the bank expected, the nostro reconciliation team raises a break and contacts the correspondent bank the same day.
The camt.053 Bank to Customer Statement is the ISO 20022 equivalent of the MT940, and it carries the same statement information in XML form with richer structured data. A camt.053 has a group header, a statement element with the account, the opening balance, the closing balance and the available balance, and a series of entry elements, each with an amount, a credit or debit indicator, a value date, a booking date and structured remittance information. The same EUR 320,000 credit that appears as a Field 61 line and a Field 86 narrative in an MT940 appears in a camt.053 as an entry with a structured creditor name, a structured invoice reference and a bank transaction code. The richer structure means fewer unmatched items.
The three formats coexist because banks and corporates migrate at different speeds. A corporate that has used MT940 for twenty years may keep it for its main operating accounts, while a new subsidiary with a modern treasury system receives camt.053 for the same bank. A bank reconciling nostro accounts may receive MT950 from one correspondent and camt.053 from another, and its reconciliation system must handle both. The key discipline is the same in every format, namely match on reference, amount, currency and value date, check the balances, and investigate every break by age. A break that is one day old may be a timing difference, while a break that is thirty days old is a real error.
Common breaks fall into a small set of patterns, and recognising them speeds up resolution. A timing break occurs when a payment is booked on 3 November in the bank system but on 4 November in the customer system, so the amounts match but the dates differ by one day. A value break occurs when the amounts differ, for example a EUR 320,000 payment arrives as EUR 319,850 after EUR 150 in charges, and the system must decide whether the difference is a charge or an error. A missing item break occurs when a line appears on the statement but not in the ledger, or the reverse, often because a payment was made by a different channel. A duplicate break occurs when the same reference appears twice. Each break needs an owner, an age and a resolution, and the reconciliation report must show the ageing every day.
Full lesson text (all scenes)
Completing a lesson updates your progress dashboard on the homepage.
Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.