Skip to content

SWIFT Message Fields Explained: A Plain-English Guide

SWIFT message fields explained simply means understanding the labeled pieces of information that make up an international bank message. Each piece sits in a numbered box called a field, and each field carries one specific detail, such as the amount, the currency, or the beneficiary name.

Knowing what these fields mean can help you read a payment confirmation, spot an error, or ask your bank sharper questions. This guide walks through the common fields, how they are laid out, and what to check when something looks wrong.

Why Structured Fields Matter in International Transfers

When money moves between banks in different countries, the banks need a shared way to describe the payment. SWIFT, the Society for Worldwide Interbank Financial Telecommunication, provides a messaging network that banks use for this purpose. Each message is built from fields so that a receiving bank can process it automatically without retyping details.

A field is simply a labeled slot. One slot might hold the amount, another the date, and another the name of the person receiving the money. Because the labels are standard, a bank in one country can read a message sent by a bank in another country with little or no manual work.

Understanding fields gives everyday readers a practical advantage. When you receive a transfer notice or a statement line with codes on it, you can match each code to its meaning instead of guessing. That makes it easier to confirm that the payment is what you expected.

How a SWIFT Message Is Built

Most payment messages in the MT family, the older text-based format that is still widely used, follow a block structure. The message is divided into blocks, each with a number, and the main content sits in a block called the text block. Inside the text block, fields are listed one after another, each starting with a tag.

A tag is a short code wrapped in colons, such as :20: or :32A:. The tag tells the receiving system what kind of information follows. The text after the tag is the value, and it must follow the rules for that field, including the required length and allowed characters.

Fields may be mandatory or optional. A mandatory field must appear for the message to be valid, while an optional field can be left out. Some fields also allow several lines of text, which is why you may see a name and address spread across two or three rows in one field.

See also  SWIFT Message Troubleshooting: A Practical Guide for Banks

Common Fields You Are Likely to See

Several fields appear in most payment records. Knowing these will cover a large share of what you encounter on a transfer notice:

  • Field :20: holds the sender’s reference, a unique number the sending bank assigns to the transaction.
  • Field :32A: combines the value date, currency code and amount, so one line shows when and how much was sent.
  • Field :50K: identifies the ordering customer, meaning the person or business that started the payment.
  • Field :59: identifies the beneficiary, the person or company that is meant to receive the funds.
  • Field :70: carries remittance information, a short description such as an invoice number or purpose of payment.

These fields are not the only ones, but they are the most useful starting point. If you can locate the amount, the beneficiary and the reference, you can usually confirm whether a transfer matches what you arranged. Your bank’s documentation or account agreement can explain any additional fields used in your specific transactions.

Reading the Amount and Currency Field

The amount field is one of the most important parts of any payment record, and it is often the first place people look. In a field like :32A:, the value is written in a compact form: a six-digit date, a three-letter currency code, and the amount with a comma used as the decimal separator.

Consider a hypothetical example. Suppose a message contains :32A:250315USD1234,50. Read in parts, this means a value date of 15 March 2025, a currency of US dollars, and an amount of 1,234.50 dollars. The comma is the decimal mark, so the amount is not 1,234,50 but a little over one thousand two hundred dollars.

Misreading the comma is a common source of confusion, so it is worth checking this field carefully against the amount you expected. If the figures differ, contact the bank that issued the statement rather than assuming an error on either side.

Identifying Parties: Ordering Customer and Beneficiary

Two fields show who is involved in the payment. The ordering customer field, commonly tagged :50K:, names the party that instructed the transfer. The beneficiary field, tagged :59:, names the party meant to receive the funds. Both can include an account number and a name and address.

Some account numbers are shown in a format that begins with a slash, such as /123456789, followed by the name on the next line. This layout helps the receiving bank route the money to the right account. The name and address provide a human-readable check on whether the correct party is listed.

See also  SWIFT Message Codes List: A Plain-English Reference Guide

If the beneficiary details look incomplete or do not match the person you intended to pay, pause before taking any further action. Reviewing the account agreement or contacting your bank to confirm the details is a sensible step, since small differences can delay or redirect a transfer.

Field Codes, Options and Format Rules

Many fields have letter suffixes or option codes that change how the information should be read. These rules keep messages consistent across banks but can look confusing at first glance.

What the Letter Suffix Means

A letter after the field number, such as the A in :32A:, indicates a specific format option for that field. Different options can carry different combinations of information, so the same field number can appear in several forms across messages.

The suffix tells the receiving system how to parse the content. Without it, the system would not know whether it is reading a date, a currency, or a free-text description. This is why exact formatting matters so much in these records.

When reviewing a record, noting the suffix helps you understand what kind of detail the field contains. It is a small clue that makes the rest of the field easier to interpret.

Character Sets and Field Length

Each field has rules about which characters it can contain and how long its value may be. Most fields use a limited set of letters, digits and punctuation, and some restrict the number of lines allowed. These limits exist so that every system can read the message in the same way.

Length limits mean that long names or addresses may be shortened or split across lines. A shortened name can still identify a party, but it is worth checking that the abbreviation is not ambiguous. This is one reason why reference numbers and account identifiers are kept precise.

If a value is truncated or contains unexpected characters, it may be flagged during processing. Banks rely on these checks to protect the accuracy of payments.

Mandatory Versus Optional Fields

Some fields must always appear for a message to be considered complete. Others are included only when relevant. A payment message will normally require the amount, currency, value date and beneficiary, while a remittance description may be optional.

The distinction matters because a missing mandatory field can cause a message to be rejected or returned. Banks check for these requirements before forwarding instructions, which helps prevent incomplete transfers from moving through the network.

If you ever see a field marked as missing in a return notice, ask the bank which detail was absent and what it needs to resubmit the request. Clear questions usually produce a faster resolution.

Practical Steps for Checking a Payment Record

A simple checking routine can catch most problems early. Start by locating the amount and currency field and confirming they match the figure you expected. Next, verify the beneficiary name and account details, since these determine where the money is sent.

See also  SWIFT Message Integration With Banking Systems: A Guide

Then look at the sender’s reference and any remittance information. A clear reference makes it easier to trace the payment later and to match it with an invoice or statement entry. If anything is unclear, write down the field tag and the value before contacting your bank so the conversation is precise.

Keep a copy of the record for your files. If a dispute or question arises months later, a saved record with its reference number is far more useful than a memory of the transaction. Consult your account agreement for the bank’s procedures on questions and timeframes.

Limits of Field-Level Reading and When to Ask for Help

Understanding fields is useful, but it does not replace professional review of an unusual payment. Some records include technical codes, intermediary banks or correspondent details that depend on the specific banking chain. Reading these correctly often requires context from the bank that handled the transfer.

Field-level knowledge also cannot confirm that a payment is legitimate. Fraudsters sometimes change beneficiary details on invoices or send fake payment notices. If a request to pay a new account seems unexpected, verify it through a known phone number or in-person contact before sending any money.

Your bank can explain fields on a specific record, trace a payment, or correct a clear error. Reaching out early, with the reference number and the field you are concerned about, is usually the most efficient path.

Quick Checklist for Reading Any Payment Message

Use this short list whenever you review an international transfer record, so that the most important details are never overlooked:

  • Confirm the amount, currency and value date match what you agreed to pay or expect to receive.
  • Check that the beneficiary name and account number are the ones you intended to use.
  • Note the sender’s reference so you can trace the payment with your bank later.
  • Read any remittance text to confirm it describes the invoice or purpose correctly.
  • Save the record and contact your bank promptly if any field looks wrong or unfamiliar.

Working through these five points takes only a few minutes and covers the details that matter most. Over time, the field tags will become familiar, and reviewing a record will feel routine rather than puzzling.

Building Confidence With Payment Records in the Year Ahead

As international payments become more common for households and small businesses, understanding the structure behind each record is a practical skill. Learning a handful of core fields gives you a reliable way to check what you are sending or receiving without relying solely on a summary line.

A good next step is to pull a recent transfer record from your bank, or ask the bank for a sample explanation, and locate the fields described here. Matching real data to these definitions makes the terms concrete and easier to remember.

Treat your bank as a resource. Its staff can explain the fields used on your records, confirm how your account handles international transfers, and guide you through any correction. Asking questions is a normal part of managing money across borders.