What is SWIFT Field 57A? Definition & Formatting Guide

What Is SWIFT 57A?

To understand SWIFT field 57A, you first need to understand how SWIFT messages are structured.

Take the MT103, the standard SWIFT message used for international customer payments. Each MT103 is composed of a series of fields, each identified by a colon-enclosed tag (for example, :20:, :32A:, :57A:). Field :57A: represents the "Account with Institution" — the financial institution where the beneficiary holds their account, and where the funds should ultimately be credited.

You may also encounter :57B:, :57C:, or :57D: in some messages. All four variants identify the beneficiary's bank, but each uses a different format. The "A" suffix in 57A specifically means the field uses a BIC (Bank Identifier Code) — also known as a SWIFT Code — to identify the bank. This is the most precise, most automated, and most universally recommended format.

Here is how the four variants compare:

[Table:1]

For the overwhelming majority of international wire transfers, 57A is the correct field to use. The other variants exist to accommodate edge cases — smaller regional banks, credit unions, or institutions in markets with limited SWIFT connectivity.

What Does SWIFT Field 57A Actually Do?

In most international transfers, the sending bank and the beneficiary's bank have no direct account relationship. This means funds cannot be transferred directly — they must travel through one or more intermediary (correspondent) banks to reach the destination.

The BIC code provided in field :57A: identifies the final destination bank — the institution where the beneficiary actually holds their account. Think of it as the terminal postcode on a parcel: it is the last critical routing instruction before the money enters the recipient's account.

Correspondent banks use the :57A: BIC to route funds automatically through their systems — quickly and with minimal manual intervention. This precision is what keeps large-value cross-border transfers moving without human touchpoints at every hop.

In a multi-tier correspondent structure, funds typically flow from the intermediary bank (identified in field :56A:) to the final beneficiary bank (identified in :57A:). As long as the :57A: BIC is accurate, the correspondent bank can instruct the next bank in the chain to route the foreign currency funds correctly to the destination — avoiding errors or delays in a complex correspondent network. Understanding how intermediary banks function in international payments is key to anticipating where in the chain a transfer might stall.

Field 57A also serves as a compliance checkpoint. Correspondent banks use the BIC to verify the identity of the receiving institution and confirm that the transaction complies with AML (Anti-Money Laundering) requirements and international sanctions regulations before releasing the funds.

How to Fill In SWIFT Field 57A Correctly

The :57A: field requires a valid 8-digit or 11-digit SWIFT/BIC Code. The BIC structure breaks down as follows:

Characters 1–4 (letters): Bank code — e.g. HSBC represents HSBC

Characters 5–6 (letters): Country/territory code — e.g. HK represents Hong Kong

Characters 7–8 (letters or digits): Location code

Characters 9–11 (letters or digits, optional): Branch code — if omitted, the code defaults to the bank's head office (represented as XXX)

The standard format for the :57A: field requires you to enter :57A:/ followed by the correspondent bank's SWIFT Code, then on the next line the bank's full name and address (split across multiple lines if needed). For example, if the beneficiary bank is HSBC Hong Kong:

:57A:/HSBCHKHHXXX

THE HONGKONG AND SHANGHAI BANKING CORPORATION LIMITED

1 QUEEN'S ROAD CENTRAL

HONG KONG

If you only need to supply the SWIFT Code itself, it can also be simplified to :57A: followed directly by HSBCHKHHXXX.

Always obtain the BIC directly from the beneficiary — either from a formal bank payment instruction or an invoice. Never type it from memory, and never search online for a bank's name and assume the first BIC result is correct.

SWIFT 57A Requirements by Country: What Else You Need Besides a BIC Code

While :57A: is the primary field for identifying the beneficiary bank in international SWIFT transfers, certain countries require additional identifiers alongside the BIC. Here is what Hong Kong SMEs sending to major markets need to know:

United States

US banks typically require a 9-digit ABA Routing Number (also called a Fedwire number) in addition to a SWIFT Code. If it cannot be accommodated within the 57A field, it is generally entered in the :57C: field with the prefix //FW, or noted in the payment narrative field. For a detailed walkthrough of the cost and process of sending money from Hong Kong to the US, our dedicated guide covers the full picture.

Europe

European countries make extensive use of the IBAN (International Bank Account Number), which encodes both the bank identifier and the account number in a single string. However, when conducting cross-border wire transfers to Europe, you still need to provide the corresponding SWIFT/BIC Code in the :57A: field to ensure correct cross-border routing — the IBAN alone is insufficient for international transfers originating outside the SEPA zone. For a full breakdown of the distinction between these two identifiers, see our guide to IBAN vs SWIFT codes.

Australia

Australian wire transfers typically require a 6-digit BSB Code (Bank State Branch Code) to identify the specific branch. This is usually entered alongside the beneficiary account number in the final beneficiary field, or in the local clearing field, rather than in the :57A: field itself.

United Kingdom

UK domestic payments use Sort Codes — 6-digit branch identifiers — to route funds within the UK clearing system. For international SWIFT transfers arriving into a UK bank, the SWIFT BIC in :57A: handles the cross-border routing, while the Sort Code ensures correct branch-level delivery. For more detail on how UK payment methods work, including CHAPS, BACS, and FPS, our guide explains the distinctions. For the costs associated with sending money from Hong Kong to the UK, the fee comparison is worth reviewing before you send.

Common Mistakes When Filling In SWIFT Field 57A

These are the errors that most frequently cause wire transfers to be delayed, mis-routed, or returned — often with intermediary fees already deducted.

Confusing the Letter "O" with the Number "0"

SWIFT BIC codes use only letters and digits, and the distinction between the letter "O" and the number "0" is invisible in certain fonts. A single character error renders the BIC invalid and prevents automated routing. Always copy-paste the BIC from an official source rather than typing it manually.

Using the Head Office Code When a Branch Code Is Required

Appending "XXX" to a BIC defaults to the bank's head office. However, in certain countries and for certain account types, funds must be routed to a specific branch BIC — and the head office code will cause the transfer to fail or require manual rerouting. Confirm with your beneficiary whether a specific branch code is required.

Mismatch Between Field 57A and Field 59 (Beneficiary)

The bank identified in :57A: must be the actual bank where the beneficiary holds their account (as specified in field :59:). If these two fields reference different institutions, the correspondent bank cannot complete the routing — the funds will be returned, typically after deducting handling and return fees. This is one of the most expensive mistakes to make on a large B2B payment.

The rule is simple: before sending any international wire, ask the beneficiary for their official bank payment instructions or invoice, and copy the SWIFT Code directly from that document. Do not search for BIC codes independently online or rely on what you remember from a previous transaction.

Beyond 57A: Key MT103 Fields You Need to Know

To read and verify a complete SWIFT MT103 message — whether for a payment you have sent or one you are chasing — you need to understand the full field structure. Here are the core fields alongside :57A::

[Table:2]

For a complete walkthrough of how to execute a SWIFT payment end-to-end as a business — including what to enter in each field — see our step-by-step guide to making SWIFT payments. For a comparison of when SWIFT wire transfers make sense versus local bank transfer alternatives, including cost and speed trade-offs, our guide covers the key decision points.

Aspire: Send International Payments Without the SWIFT Complexity

Every time a :57A: field is filled in incorrectly, or a SWIFT transfer gets held at a correspondent bank, it costs your business time, money, and — if a supplier is waiting for cleared funds before shipping — operational momentum.

Aspire is built to eliminate exactly these friction points for Hong Kong SMEs.

• Global reach, local simplicity. With Aspire multi-currency account, your business can send and receive payments across 130+ countries in 40+ currencies — with FX spreads from just 0.18%, up to 3x cheaper than a traditional bank wire. Where possible, Aspire routes transfers through local payment rails rather than multi-hop SWIFT chains, which means fewer intermediary fees, faster settlement, and less risk of funds being held at a correspondent bank for compliance review. This is particularly valuable when sending to markets like the UK, the US, or Southeast Asia, where local payment networks can significantly reduce costs and settlement times versus SWIFT.
  
• SWIFT transfers with instant confirmation. When SWIFT is the right rail for your payment, Aspire processes it with full SWIFT GPI tracking enabled. Once your transfer completes, you can download your payment confirmation instantly from the app — no calls to the bank, no admin fees, no waiting for an MT103 copy to be emailed over.
  
• Full financial control in one platform. Issue corporate cards with configurable spending limits, automate invoice and bill management, and sync every transaction with Xero or QuickBooks in real time. For Hong Kong SMEs managing payroll, free FPS and CHATS are both natively supported — ensuring domestic payments clear on time, every time.
  
• 1.2% unlimited cashback. Every eligible transaction on your Aspire corporate card earns 1.2% cashback. Combined with over USD 500,000 in partner rewards included with your account, Aspire turns your operating costs into working capital from day one.
  

Open your account free. Approved in as little as one business day. No branch visits, no stacks of paper forms, no waiting weeks for a relationship manager to call you back.

Frequently Asked Questions

Q: What happens if I enter the wrong or missing :57A: field?

If the :57A: BIC is missing or incorrect, the funds are highly likely to stall at the correspondent bank rather than reaching the beneficiary bank. You will need to contact your sending bank immediately to request an Amendment — providing the correct :57A: details — or to initiate a Recall to have the funds returned. Both processes take time and may incur fees. This is why accuracy at the point of input is critical.

Q: Can I use field 57A for a bank that has no SWIFT Code?

No. The :57A: field format strictly requires a valid 8 or 11-character SWIFT/BIC Code. If the beneficiary bank is a smaller regional institution or credit union that is not connected to the SWIFT network, you cannot use 57A. Instead, use :57C: with the relevant country clearing code (such as the US ABA Routing Number or Australia BSB Code), or :57D: with the bank's full name and physical address. Note that 57D requires manual processing and is significantly more prone to delays.

Q: When should a beneficiary request the MT103 document from the sender?

There are three situations where a beneficiary should proactively request the MT103:

First, if funds have not arrived within a reasonable timeframe — international wire transfers typically take 1–5 business days. If payment has not landed after that window, the beneficiary should request the MT103 and use the UETR code (or the :57A: and :56A: field information) to ask their own bank whether funds have been held by a compliance team.

Second, if the amount received is less than expected — checking fields :71A: (charge allocation) and :32A: (original amount) on the MT103 reveals whether the shortfall is due to intermediary fees or a currency conversion issue.

Third, for B2B invoice settlement and shipping authorisation — in larger commercial transactions, suppliers often require formal MT103 confirmation that funds have been dispatched through the SWIFT network before releasing goods, as it constitutes verifiable proof of payment.