Skip to content

SWIFT MT950 Account Statement: A Plain-English Guide

A SWIFT MT950 account statement is a standardized message that a bank sends to report the balance and transactions on an account, in a format designed for machine processing. Many businesses and finance teams receive these messages without knowing exactly what they show or why they matter.

This guide explains the purpose of the MT950, the fields it typically carries, how it differs from related messages, and how organizations use it to reconcile accounts. Practices vary by bank and agreement, so the account terms and the sending institution’s documentation remain the authoritative reference.

Why a Standardized Account Report Matters for Everyday Finance

Every day, banks move money on behalf of companies, and those companies need a reliable record of what happened to their balances. Imagine a small importer that receives several payments and makes a few supplier transfers in a single day. Without a structured report, its accountant would have to log into an online portal and copy figures by hand.

A standardized message solves this problem by giving every bank and every receiving system the same layout. When the format is consistent, software can read the balances and transactions automatically, which reduces typing errors and speeds up the close of the books.

The MT950 belongs to the family of SWIFT messages, a messaging network that banks worldwide use to exchange financial instructions. Its job is narrow: to report account activity from the bank that holds the account to the customer or to a party that has been authorized to receive it.

What an MT950 Message Actually Is

The MT950 is a statement message, and its name follows the SWIFT convention in which the first digit identifies a category and the rest identifies the message type. Category 9 covers cash management and status messages, which is why account statements sit in that group rather than with payment instructions.

Unlike a payment message that tells a bank to move money, the MT950 is purely informational. It does not instruct anything. It records what already occurred, such as incoming credits, outgoing debits, and the balance at the start and end of the reporting period.

Because it reports history rather than requesting action, the MT950 is often paired with other messages in a treasury workflow. A company may send payment messages through the network, then later receive an MT950 that confirms those payments cleared.

See also  SWIFT Message Standards Evolution: From MT to ISO 20022

Key Fields Found in a Typical MT950

Each MT950 is built from numbered fields, and each field carries a specific piece of information. The exact fields a bank includes can vary, but the following elements are commonly found and are worth understanding before you read a statement.

  • Field 20 holds the transaction reference, a unique identifier the sender assigns to the statement.
  • Field 25 identifies the account the statement relates to, usually an account number or IBAN.
  • Field 28C gives the statement number and sequence, which helps you detect missing reports.
  • Field 60F shows the opening balance, including the debit or credit indicator and the currency.
  • Field 62F shows the closing balance, so you can confirm where the account stood at period end.

Transaction lines appear between the opening and closing balances, typically in field 61, with descriptive detail in supporting fields. Reading the opening balance, the transaction lines, and the closing balance together lets you verify that the arithmetic works out. If the figures do not reconcile, that is a signal to contact the bank promptly.

How to Read the Balance Lines Correctly

Balance lines are where many readers make mistakes, mainly because the debit and credit indicators are easy to misread. A balance marked as credit means the account is in positive territory, while a debit balance means the account is overdrawn or owes money to the bank, depending on the account type.

Consider a hypothetical example with round numbers. Suppose the opening balance is a credit of $10,000. During the day there are two incoming payments of $2,000 each and one outgoing payment of $3,000. The closing balance should therefore be a credit of $11,000, since $10,000 plus $4,000 minus $3,000 equals $11,000.

If your own records show a different closing figure, check each transaction line against your ledger before assuming the bank is wrong. Timing differences, such as payments that were initiated but not yet settled, often explain the gap.

Using the MT950 for Account Reconciliation

Reconciliation means matching the bank’s record of activity against your internal books. The MT950 provides the bank side of that comparison. Finance teams typically run each transaction line against their accounting entries and flag anything that appears on one side but not the other.

Reconciliation is most effective when it happens regularly rather than once a month. Daily or near-daily matching makes it easier to spot duplicate payments, missed receipts, or unexpected debits while the underlying details are still fresh.

See also  Benefits of SWIFT Messaging Automation for Banks Today

Many organizations import the MT950 directly into reconciliation software. Where that is done, it is good practice to periodically check a sample of automated matches manually, since no import process is free of mapping errors.

Related Messages and How They Differ

The MT950 is one of several statement and reporting formats, and confusing them can lead to misreading a bank’s report. The following three subsections describe the main related messages and where each fits.

MT940 Customer Statement Message

The MT940 is the customer statement message and is probably the most widely used account report in the SWIFT family. Like the MT950, it reports balances and transactions, but it is typically sent to the account holder itself rather than to a third party.

The practical difference matters when you are setting up feeds. Some banks send MT940 to customers and MT950 to authorized financial institutions. Check which message your bank actually delivers before you configure your system to expect it.

In day-to-day use, the two messages share much of their structure, so many field descriptions apply to both. Reading the field tags carefully will help you confirm which report you are looking at.

MT942 Interim Transaction Report

The MT942 is an interim transaction report, meaning it reports transactions posted during the day before the end-of-day statement is produced. It helps treasury teams see activity as it happens rather than waiting for the closing report.

Because interim reports can show items that later change or reverse, they are best used for monitoring rather than final accounting. Treat the MT942 as a preview and rely on the end-of-day statement for the official record.

When both an interim report and a final statement are available, comparing them can highlight late postings. That comparison is a useful habit for catching problems early in the day.

Choosing the Right Message for Your Needs

Selecting the correct report depends on who needs the information and when. A business that wants a single end-of-day record for its own books will usually prefer a customer statement. A team that needs intraday visibility will look for interim reporting.

Your bank’s service documentation and your account agreement determine which messages you can receive and how they are delivered. These details can differ between institutions, so confirm them directly with your bank instead of assuming a standard setup.

When in doubt, ask the bank to provide a sample of each message type. Seeing real examples from your own account is the fastest way to understand what you will be working with.

Common Problems When Working With Account Statements

Even well-formed messages can cause confusion. One frequent issue is a mismatch between the statement date and the value date of a transaction, where a payment appears on one day’s report but was dated differently in the sender’s system. Checking both dates usually resolves the discrepancy.

See also  SWIFT Message Authentication: How Banks Verify Payments

Another common problem is missing statements. If the statement sequence number skips a value, the message may have been lost or delayed in transit. Field 28C helps you spot such gaps, and a quick request to the bank can recover the missing report.

Character encoding and formatting errors can make a statement difficult to parse. If your software rejects a message, compare it against the expected field structure and ask your bank or technical support team to confirm the format version in use.

Security and Access Considerations for Statement Data

Account statements contain sensitive financial information, so access to them should be limited to people who need it. Organizations commonly restrict who can view or import MT950 files and keep an audit trail that records who accessed them and when.

Protect the channels that deliver statements as well. Use the security controls your bank provides, keep credentials confidential, and report any unexpected change in how messages arrive. A sudden new sender or an unusual message pattern deserves prompt verification with the bank before anyone acts on it.

Keep archived statements in a secure location for as long as your record-keeping policy and applicable regulations require. Consistent retention also makes future audits and disputes much easier to handle, and it gives your team a dependable history to compare against.

Practical Steps for Reviewing an MT950

A simple, repeatable routine makes account statements easier to manage and reduces the chance of overlooked errors. The following steps are a reasonable starting point for most finance teams.

  • Confirm that the account number in field 25 matches the account you expected to receive.
  • Verify the opening balance against the closing balance from the previous period.
  • Check each transaction line against your internal records and note any unmatched items.
  • Recalculate the closing balance from the opening balance and transaction totals.
  • Record the review, including the date and the reviewer, to maintain an audit trail.

Documenting these steps also helps when you train new staff or hand over responsibilities. If you notice persistent differences, raise them with your bank through the channel named in your account agreement, and keep copies of the statements involved.

Looking Ahead: Building a Dependable Statement Process

As payment systems continue to modernize, the way account statements are delivered and consumed is likely to keep changing. Many institutions are exploring richer data formats and faster reporting, so it helps to build a process that can adapt rather than one tied to a single file layout.

A practical next step is to document your current statement workflow, including which messages you receive, who reviews them, and how discrepancies are resolved. That documentation becomes the baseline for any future upgrade or change in banking partner.

Schedule periodic reviews of your statement process with both finance and technology staff. Regular conversations with your bank about message formats and service options can prevent surprises and keep your reconciliation running smoothly.