Skip to content

SWIFT Message Fields and Codes: A Plain-English Guide

SWIFT message fields and codes are the labeled pieces of information that banks use to describe a payment, from the sender and recipient to the amount and purpose. Each field sits under a numeric tag, and many values are short codes that follow standard formats.

Most people never see the raw message behind a transfer, yet it determines how quickly funds arrive and whether they reach the right account. This guide explains the structure, walks through common tags, and shows what the codes mean in practice. It also describes where errors usually occur, so readers know what to ask their bank about.

Why Fields and Codes Matter When You Send Money Abroad

When you send an international wire, the instruction travels between banks as a structured text message. The bank that handles your request turns your details into fields, each with a specific meaning, so that every institution along the route reads the same information in the same way.

Think of the message as a filled-in form. The sender name occupies one box, the beneficiary account another, and the amount a third. Because the form has fixed boxes, a receiving bank can process thousands of payments without guessing what each piece of text is supposed to represent.

Small mistakes in these boxes can cause delays. A misplaced account number or a missing identifier may force the receiving bank to pause the payment and ask questions. Knowing what each field expects helps you review your transfer request with more confidence before you submit it.

What a SWIFT Message Looks Like

SWIFT messages are built from blocks, which are sections separated by braces and labeled with numbers. Block 1 identifies the sending institution, Block 2 identifies the receiving institution and the message type, Block 3 holds optional reference data, Block 4 contains the main body of the payment, and Block 5 holds trailer information such as security checks.

The body in Block 4 is where most payment details appear. It is organized as a list of tags, where each tag starts with a colon, a number, and a letter, followed by the value. A tag might introduce the amount, the currency, or the beneficiary, and the content after it follows the rules for that tag.

Not every bank displays this raw structure to customers. Your bank may show you a simplified summary instead. If you want to understand the full message, you can ask the bank for a copy of the transfer details, which typically lists the same information in a readable format.

Common Fields You Will See in a Payment Message

Several fields appear in nearly every customer payment. Recognizing them makes it easier to check your own transfer details and to understand what your bank is asking for when it requests more information.

  • Field 32A, which shows the value date, the currency, and the amount of the payment
  • Field 50K, which identifies the ordering customer, meaning the person or company sending the money
  • Field 59, which identifies the beneficiary, including the account number and name of the recipient
  • Field 70, which holds remittance information such as an invoice number or a short description
  • Field 71A, which states who pays the transfer charges, such as OUR, BEN, or SHA
See also  SWIFT Message Fees: What Customers Should Know About Costs

These fields cover the core of most transfers. Other tags appear for special cases, such as intermediary banks or regulatory reporting. The exact fields a bank uses can vary by the type of message and by local rules, so the account agreement or the bank’s transfer form is the best reference for your own payment.

How Codes Work Inside a Message

Many values inside a SWIFT message are codes rather than free text. Currency codes follow the three-letter ISO 4217 standard, so USD stands for US dollars and EUR for euros. Country codes use two letters, such as US for the United States. Using standard codes lets banks in different countries read the same information without translation.

Some codes describe the bank itself. A BIC, or Bank Identifier Code, is an eight or eleven character identifier that points to a specific financial institution.

It typically includes a four-letter bank code, a two-letter country code, a location code, and an optional branch code. An IBAN, used mainly in Europe and some other regions, identifies a bank account and includes check digits to catch typing errors.

Codes also control how charges and instructions are handled. For example, a charge code in field 71A tells the receiving banks who should pay fees. Because these codes carry specific meanings, using the wrong one can change the cost or the speed of a payment, so it is worth confirming the choice with your bank before sending.

Mistakes That Commonly Delay Payments

Most delays come from data that does not match the expected format. An account number entered without required prefixes, a BIC with the wrong length, or a currency code that does not match the account can cause a receiving bank to hold the funds for review. These problems are usually simple to fix once identified.

Another frequent issue is incomplete beneficiary information. If the name, address, or account details are unclear, a bank may need to contact the sender or the recipient before releasing the money. Providing complete and consistent details at the outset generally reduces these back-and-forth requests.

Remittance information can also cause confusion. A long or unclear reference in field 70 may not be passed along correctly by every institution. Keeping references short and specific, such as an invoice number, typically makes the purpose easier for the recipient to match to a payment.

See also  SWIFT Message Deadlines: Key Cutoff Times Explained

Reading Messages Across Different Message Types

SWIFT uses many message types, and the fields and codes you see depend on the category of the message. Payment messages, statement messages, and trade finance messages each have their own structure, though many tags are shared across categories.

Customer Payment Messages

Customer payment messages, often labeled in the MT103 family, carry the details of a transfer sent on behalf of an individual or business. They include the ordering customer, the beneficiary, the amount, and the charge instructions. These are the messages most US readers will encounter when sending an international wire.

Because these messages move money on behalf of customers, banks apply strict validation to them. Each required field must be present and correctly formatted, and the message must pass checks before it is released. This strictness is one reason why incomplete wire requests are often returned for correction.

If you receive a payment and want to understand the details, your bank’s statement or transfer advice usually shows the relevant fields in plain language. Matching those details to your own records can help you confirm that the sender and amount are correct.

Bank-to-Bank Transfer Messages

Bank-to-bank transfer messages move funds between financial institutions rather than on behalf of individuals. They use a similar tag structure but focus on the institutions involved, including the sending and receiving banks and any intermediary banks in the chain. These messages are generally not used directly by consumers.

Intermediary and correspondent banks often appear in these messages because funds may pass through several institutions. Each one adds or reads fields that identify the next step. Understanding this chain helps explain why a payment can take more than one business day to complete.

Consumers typically interact with this process only indirectly. If a payment is delayed, your bank can often tell you which institution is holding the transfer and what information it needs to proceed.

Statement and Reporting Messages

Statement messages summarize account activity and are commonly used by businesses to reconcile their books. They include fields for opening and closing balances, transaction lines, and reference numbers that match individual entries. Many of the codes in these messages describe whether an entry is a credit or a debit.

Reading these fields carefully can help with bookkeeping. A transaction line often includes a code that indicates the type of entry, such as a transfer or a charge, along with a reference that links it to the original instruction. Matching these references is a practical way to trace a payment.

If the statement does not match your records, contact your bank and ask for a breakdown of the entries and the references they use. This approach usually resolves differences more quickly than trying to interpret the raw codes alone.

How to Check Your Own Transfer Details

Before you approve a wire transfer, review the details your bank shows you. Confirm the beneficiary name, the account number or IBAN, the bank identifier, the currency, and the amount. A quick comparison with the invoice or agreement you are paying against can catch errors before they cause problems.

See also  SWIFT Message Processing Automation for Banks Explained

Be cautious about changes to payment instructions you receive by email or phone. Fraudsters sometimes send altered account details that look legitimate. If you receive a request to change where money should go, verify it through a separate, trusted channel, such as calling the recipient at a number you already have on file.

If something in your transfer details looks unfamiliar, pause and ask your bank before submitting. Banks can explain what each field means for your specific payment and whether any information needs correction. Checking the account agreement for the bank’s transfer rules is also a useful step.

Limits of What Codes Can Tell You

Field and code knowledge helps you read a payment, but it does not replace the bank’s review process. Banks run their own validation, sanctions screening, and compliance checks, and these may hold a payment for reasons unrelated to the codes you entered. A clean message can still be delayed for review.

Also keep in mind that rules and formats can change over time. SWIFT has updated some message standards in recent years, and banks may support different formats during transition periods. The details in older guides may not reflect current requirements, so treat any reference as a starting point rather than a final authority.

This guide is educational and does not describe the specific rules of any single institution. Costs, cutoff times, and required fields differ between banks, so the account agreement and the bank’s own transfer instructions remain the definitive source for your payments.

Questions to Ask Before You Send a Wire

A short checklist can prevent many common problems. Asking the right questions before you submit a transfer helps ensure that the fields and codes match what the receiving bank expects.

  • Is the beneficiary name exactly as it appears on the recipient’s bank account?
  • Does the account number or IBAN follow the format required by the destination country?
  • Is the bank identifier correct, and does it match the receiving institution?
  • Which party will pay the transfer charges, and does that match what the recipient expects?
  • Is the remittance reference short, clear, and linked to a specific invoice or purpose?

Working through these questions takes only a few minutes and can save days of delay. If you are unsure about any answer, ask your bank before submitting. A bank representative can usually confirm the required fields and explain any unfamiliar codes that appear on the transfer form.

Building Confidence With Payment Details Going Forward

Learning the basics of SWIFT message fields and codes gives you a clearer view of how international payments move. Over time, you will recognize the common tags and understand why banks ask for specific information. This knowledge makes conversations with your bank more productive and helps you spot inconsistencies early.

Consider keeping a record of the details for recurring payments, such as the beneficiary name, account format, and reference style that work well. Reusing verified information reduces the chance of new errors, though you should still confirm details whenever a recipient’s account changes.

As payment technology continues to evolve, the core ideas of labeled fields and standard codes are likely to remain. Staying curious about how your transfers are structured, and asking your bank when something is unclear, is a practical habit that supports safer and more predictable international payments.