Skip to content

Understanding the SWIFT MT940 Bank Statement Message

The SWIFT MT940 bank statement message is a standardized electronic report that banks send to account holders, listing the opening balance, individual transactions and closing balance for a given day. It lets companies pull statements straight into accounting software rather than retyping figures from paper or PDF documents.

For everyday readers, this matters because the same format underlies many business reconciliations you may never see directly. This article explains what the message contains, how its parts fit together, and why finance teams rely on it to keep records accurate.

Why Banks and Businesses Rely on Machine-Readable Statements

Imagine a small manufacturer that receives payments from dozens of customers each day. Someone must check every incoming amount against open invoices, and that work is slow if the bank report is a scanned page. A structured message solves this by giving software a predictable layout it can read without human interpretation.

The MT940 format is one of the older and most widely supported statement types in international banking. Because it follows a fixed pattern, a company’s treasury system can process statements from many banks in the same way, which reduces manual data entry and the chance of copying errors.

Banks usually produce these messages at the end of a business day, sometimes with intraday updates. The exact delivery schedule, cut-off times and available channels depend on the bank and the agreement in place, so the account terms are the place to confirm what your institution provides.

What a SWIFT MT940 Message Actually Contains

SWIFT is the Society for Worldwide Interbank Financial Telecommunication, a network that banks use to exchange standardized financial messages. The MT prefix means a message type in that system, and 940 identifies this one as a customer statement. Each message covers a single account for a specific statement date.

The message is built from tagged fields, each beginning with a two-character code in colons such as :20: for a reference or :60F: for the opening balance. The tags tell software exactly what each piece of data means, so the same account information can be read identically by any compliant system.

See also  SWIFT Message Deadlines: Key Cutoff Times Explained

A typical statement includes the account identifier, a statement number, the opening balance with its date and debit or credit indicator, one or more transaction lines, and the closing balance. Together these fields let a reader verify that the starting balance plus all movements equals the ending balance.

Key Fields Inside the Statement

Each transaction line in an MT940 message follows a consistent structure. Understanding the main elements helps readers interpret what their bank has sent and what their accounting software will display.

  • Value date, showing when the amount is considered effective for interest and balance purposes
  • Entry date, which may differ from the value date when funds post after the transaction day
  • Debit or credit indicator, showing whether money left or entered the account
  • Amount and currency code, using the ISO standard three-letter currency identifier
  • Transaction type code and a free-text description that often includes the payer or payee reference

These fields are the building blocks of automated reconciliation. When the value date, amount and reference are consistent, matching software can link a bank line to an invoice or ledger entry with little human effort. Gaps or unusual codes often signal a line that needs manual review, which is why reading the field definitions is useful for anyone checking statements.

How Statements Fit Into Daily Reconciliation

Reconciliation means confirming that the bank’s record of an account matches the company’s own books. An MT940 message supplies the bank side of that comparison in a form software can process directly, so the finance team can focus on exceptions rather than every line.

A practical routine looks like this: the statement is received, the opening balance is checked against yesterday’s closing figure, each transaction is matched to a ledger entry, and any unmatched items are investigated. Discrepancies commonly come from timing differences, bank charges that were not recorded, or payments that arrived with incomplete references.

Keeping the statement file as an unaltered record also supports audits and internal reviews, since the original message shows exactly what the bank reported on that date. Many organizations archive these files according to their own retention policies and any applicable record-keeping requirements.

Common Misunderstandings About the Format

One frequent misunderstanding is that the MT940 message is a payment instruction. It is not. It is a report of activity that has already occurred or is being posted, and it does not move money. Payment instructions use different message types within the same network family.

See also  SWIFT Message Types: A Plain-English Guide for Readers

Another misconception is that the statement shows every balance in real time. Many banks generate the message at fixed times, so a statement may not reflect transactions that were initiated later that day. Readers who need live figures usually rely on the bank’s online banking screens or intraday reporting services instead.

Some people assume all banks format statements identically. While the core standard is shared, individual institutions may use optional fields, different description conventions or varied delivery methods. Confirming those details with your bank helps avoid confusion during reconciliation.

Working With the Message Step by Step

Turning a raw statement into usable records involves a sequence of checks that most finance teams follow. The steps below describe a general approach that can be adapted to different accounting systems and bank relationships.

Receiving and Validating the File

Begin by confirming that the file arrived from the expected source and covers the correct account and date. Compare the account identifier and statement sequence against your records to rule out misdirected or duplicated files.

Next, check that the opening balance matches the prior closing balance. A mismatch can point to a missed statement, a corrupted file or a timing issue that should be raised with the bank before posting any entries.

Matching Transactions to Your Ledger

Import the transaction lines into your reconciliation tool and apply matching rules based on amount, date and reference. Exact matches can usually be cleared automatically, freeing staff to review the remaining items more carefully.

For unmatched lines, look at the free-text description and any invoice or remittance numbers it contains. Bank charges, interest and returned payments often appear without a clear counterpart and should be recorded as separate ledger entries.

Closing the Period and Keeping Records

Once every line is matched or explained, confirm that the closing balance in the statement agrees with the balance in your general ledger, after accounting for any outstanding items such as checks not yet presented or deposits in transit.

Store the original message file with your reconciliation workpapers. Keeping the unchanged source document makes it easier to answer questions from auditors, colleagues or the bank if a figure is later disputed.

Troubleshooting Common Statement Problems

When a statement does not reconcile, the first step is to isolate the source of the difference rather than adjusting balances to force agreement. Start by checking whether the opening balance is correct, because an error carried forward will affect every later figure.

See also  SWIFT Message Codes Explained for Everyday Banking Users

Duplicate transactions are another frequent cause. If the same statement was imported twice, or a payment appears in two consecutive files, the totals will drift. Comparing statement sequence numbers and dates usually reveals the duplication quickly.

If an error cannot be explained internally, contact your bank with the statement date, account identifier and the specific line in question. Banks can often provide a copy of the original posting record, which is usually more reliable than guessing at the cause.

Operational and Governance Considerations

Organizations that process statements at scale typically define who may import files, who approves reconciliations and how exceptions are escalated. Clear segregation of these duties reduces the risk that a single person can alter both the bank data and the internal records without review.

Access to statement files should also be controlled, because they contain account numbers, balances and payee details. Restricting storage locations, using encrypted transfer channels and logging who downloads or edits files all support better data protection.

Periodic reviews of your reconciliation process help catch drift before it becomes significant. Sampling a few statements each quarter and checking them against bank confirmations is a simple way to confirm the controls are working as intended.

Checklist for Reviewing a Statement

Before closing a reconciliation period, a short checklist helps confirm that nothing important was overlooked. The points below are commonly used by finance staff reviewing bank data.

  • Confirm the account number and statement date match the expected account and period
  • Verify the opening balance equals the previous period’s closing balance
  • Check that every debit and credit line is either matched or documented with an explanation
  • Recalculate the closing balance from the opening balance and all transaction lines
  • Retain the original message file and any supporting correspondence with the bank

Working through this list each period builds a consistent habit that makes problems easier to spot. Over time, the checklist can be expanded to reflect the particular account types, currencies and payment flows your organization handles, while keeping the core checks in place.

Planning Ahead With Better Statement Data

As finance operations evolve, many organizations are looking at richer statement formats and more frequent reporting. Understanding the current MT940 structure gives you a solid baseline for evaluating those options and for judging whether new reports contain the information you need.

If you are responsible for reconciliation, consider documenting your matching rules, exception handling steps and contact points at the bank. Written procedures make the process easier to hand over and easier to review during audits or internal assessments.

Review your bank agreements periodically to confirm which statement formats, delivery channels and cut-off times apply to your accounts. Terms can change, and checking them with your institution ensures your reconciliation process continues to reflect how the service actually works.