Skip to content

SWIFT Message Glossary: Key Terms Explained Clearly

A SWIFT message glossary is a reference list that explains the abbreviations, field names and technical terms found in messages sent across the SWIFT network. Banks use these messages to move money between countries, and the wording can look like a code to anyone outside the industry.

This guide walks through the most common terms in plain English. It is meant for everyday readers who receive or send international payments and want to understand what their bank statements and payment confirmations are describing.

Why Bank Messages Use So Much Shorthand

When a bank sends money abroad, it does not simply email a note. It sends a structured electronic message that other banks read automatically. Structure means every piece of information sits in a labeled slot, which keeps processing fast and reduces mistakes across many institutions.

The result is a language full of short labels, numbers and abbreviations. A single transfer can carry a sender name, a beneficiary account, an amount, a currency code and several routing identifiers, each marked by its own tag.

A glossary translates that shorthand into ordinary words. Once you know what the main labels mean, a payment record that once looked like noise becomes readable, and you can check whether the details match what you intended to send.

The Core Concepts Behind the Terminology

SWIFT stands for the Society for Worldwide Interbank Financial Telecommunication. It is a secure messaging network that financial institutions use to exchange payment and account instructions. SWIFT does not hold or move money itself; it carries the instructions that banks act upon.

A message type identifies the purpose of a communication. Each type begins with the letters MT followed by three digits, such as MT103 for a customer credit transfer. Many glossaries group message types first because every other term depends on knowing which kind of message you are reading.

Fields are the labeled slots inside a message. A field usually begins with a colon-number tag, for example :50K: for the ordering customer. Codes are short standardized values placed in those fields, such as currency codes that follow the three-letter ISO standard, including USD for US dollars and EUR for euros.

Common Terms You Will See on Payment Records

Several terms appear again and again in transfer records. Recognizing them is the fastest way to make sense of a typical international payment. The most frequently encountered entries include the following.

  • Ordering customer: the person or business whose account the money was sent from.
  • Beneficiary customer: the person or business who is meant to receive the funds.
  • Value date: the date on which the funds are considered settled and available for the parties involved.
  • Remittance information: free-text details the sender includes, such as an invoice number or purpose of payment.
  • Charges code: a short indicator showing who pays the transfer fees, often shown as OUR, SHA or BEN.
See also  SWIFT Message Security Measures: How Banks Protect Payments

These labels usually appear alongside the amount and currency. Checking that the ordering customer, beneficiary and value date match your own records is a simple first step when you review a payment you made or received. If something does not line up, contacting your bank with the message reference is the appropriate next move.

How Message Types Differ in Practice

Different message types serve different jobs, and a glossary helps you tell them apart. A transfer for a customer is handled differently from a movement between two banks, and each uses its own format and field set.

The MT103 is the message most people encounter, since it carries a single customer credit transfer from one institution to another. The MT202 is generally used for bank-to-bank transfers where the underlying customer details are not included in the same way.

Statement messages such as the MT940 and MT950 report account activity rather than instructing a payment. Knowing that a statement message reports past activity, while a transfer message initiates movement, helps you avoid confusing an incoming record with a new instruction.

Reading Codes and Identifiers Correctly

Many entries rely on identifiers rather than names. The BIC, which stands for Bank Identifier Code, identifies a financial institution. It is typically eight or eleven characters long and is used to route the message to the correct bank.

An IBAN, or International Bank Account Number, identifies an individual account in many countries. Its structure begins with a country code and check digits, followed by bank and account information. Because a mistyped identifier can delay or misdirect a payment, copying these values exactly matters.

Currency codes and country codes also follow international standards. A three-letter currency code and a two-letter country code are shorthand that stays consistent across banks, which is why a glossary entry for each one is so useful when records arrive from overseas.

Three Groups of Terms Worth Learning First

Not every term deserves equal attention on day one. Grouping the vocabulary by purpose makes it easier to build understanding gradually, starting with the terms that appear on almost every record.

Parties Involved in a Transfer

Every payment names the parties who are affected by it. The ordering customer is the sender, the beneficiary is the recipient, and intermediary or correspondent banks may sit in between to pass the funds along. Understanding these roles explains why a single transfer can pass through several institutions.

See also  SWIFT MT950 Account Statement: A Plain-English Guide

Institutions are usually identified by their BIC codes. When you see an intermediary listed, it does not mean the money has gone astray; it usually means the funds are being routed through a bank that has a working relationship with both sides. Your bank can explain the route for a specific payment.

Keeping the parties straight also helps when you need to trace a payment. The reference numbers linked to each party give your bank something concrete to search for, which often makes the difference between a quick answer and a long delay.

Dates, Amounts and Settlement Terms

The value date and the amount are the two most important data points in any transfer. The value date indicates when the transaction takes effect in the banking system, which may differ from the date you initiated it because of time zones and business day rules.

The amount is normally shown with the currency code and a decimal format that follows the currency’s conventions. A figure written with a comma or a period can mean different things in different countries, so the currency code is the reliable anchor for interpreting it.

Settlement terms describe how and when the money actually moves between institutions. Your account agreement and your bank’s published cutoff times set expectations for how long a transfer takes, and these can vary by destination and currency.

Status, Reference and Error Terms

Every message carries a reference that uniquely identifies it. Quoting this reference is the most efficient way to ask about a payment, because it lets the bank locate the exact message without searching by name and amount alone.

Status terms describe where a transfer stands, such as accepted, pending or returned. A returned payment has been sent back, often with a reason code. Reason codes are short and specific, so checking the glossary entry for the code explains what went wrong.

Error and rejection codes follow the same pattern. They are designed for systems to read, not for people to interpret quickly. Looking up the code and then contacting your bank with the reference is a practical way to resolve most issues without guessing.

Practical Ways to Use a Glossary When You Review a Transfer

Start with the reference and the message type. These two items tell you what kind of record you are reading and give you an anchor for any question you later raise with your bank. Writing them down before anything else keeps your review organized.

See also  How a SWIFT Message Lifecycle Moves Money Between Banks

Next, check each labeled field against your own records. Compare the ordering customer name, the beneficiary details, the amount and the currency, and the value date. A glossary entry for each label tells you exactly what that field is supposed to contain, which makes mismatches easier to spot.

Keep a short personal list of the terms you encounter most often. Over time this list becomes a faster reference than searching a full glossary each time, and it builds familiarity with the language banks use every day.

Common Misreadings and How to Avoid Them

One frequent mistake is assuming a field label means the same thing in every message. A given tag can carry different content depending on the message type, so always confirm the message type before interpreting a field.

Another misreading involves the charges code. Because it governs who pays transfer fees, it can explain why the amount received is smaller than the amount sent. Seeing a charges indicator and understanding it prevents a false assumption that money has been lost.

A third issue is treating a glossary as a substitute for your bank’s own information. A glossary explains the general meaning of a term, but how your bank applies a code, handles a rejection or sets a cutoff can be specific to the institution. The account agreement and your bank’s published guidance remain the authoritative sources.

What to Check When a Transfer Looks Wrong

If a payment record does not match what you expected, a short checklist can help you decide whether the issue is a simple misreading or something that needs attention from your bank. Work through these items before you contact anyone.

  • Confirm the message type and reference number, since these identify exactly which transfer you are examining.
  • Compare the amount, currency and value date against your original instruction or your own statement.
  • Look up any charges code, status term or reason code in the glossary to understand its meaning.
  • Check the beneficiary and intermediary identifiers, such as BIC and IBAN values, for typing errors.
  • Note any remittance text that might explain the purpose or an invoice reference connected to the payment.

If the record still does not make sense after these steps, contact your bank and provide the reference number and the message type. Describing the specific field that concerns you lets the bank respond quickly. For matters involving possible unauthorized activity, act promptly and follow the reporting steps described in your account agreement.

Building Confidence With Bank Messages Over Time

Reading international payment records becomes easier with repetition. The first few transfers may feel unfamiliar, but the same labels recur across most messages, and each one you decode strengthens your understanding of the system as a whole.

Looking ahead, banks continue to refine how they structure payment data, and newer message formats are gradually being adopted in many markets. A dependable glossary helps you bridge older and newer formats, because the core concepts of parties, amounts, dates and identifiers remain consistent even as the specifics change.

For practical next steps, keep your bank’s contact details and your payment references in one place, and revisit your personal term list whenever you encounter an unfamiliar label. Clear records and a basic vocabulary are among the most useful tools for managing international payments with confidence.