How to Fill Out a SWIFT Form for International Transfers

Filling out a SWIFT form for international transfers means completing an MT103 message, the standard instruction banks use to send a single customer payment abroad. You will not usually see the raw MT103 on your screen. Instead, your bank’s wire form asks you for the pieces that populate it: the recipient’s legal name, their account number or IBAN, their bank’s BIC (SWIFT code), the currency and amount, a purpose of payment, and a choice about who pays the fees. Get those right and the transfer moves. Get one wrong and it stalls, costs extra, or bounces back.

What to Gather Before You Start

Have every piece of information in front of you before you open the wire form. Guessing at a field is what causes most delays.

  • The recipient’s full legal name, exactly as it appears on their bank account. A nickname, an abbreviation, or a missing middle initial can trigger a compliance hold.
  • The recipient’s account number or IBAN. Many countries, particularly across Europe and the Middle East, require an International Bank Account Number, and a transfer sent without one to those destinations will likely be rejected.
  • The recipient bank’s BIC, an 8- or 11-character alphanumeric code governed by ISO 9362. The first four characters identify the institution, the next two the country, the next two the location, and an optional three-character suffix identifies a specific branch.1International Organization for Standardization. ISO 9362 – Banking Telecommunication Messages – Business Identifier Code
  • Intermediary bank details, if the receiving bank does not have a direct relationship with yours. Smaller banks often route through a larger correspondent, and you may need that correspondent’s BIC.
  • The purpose of payment. Many banks require a short explanation, and some countries mandate one for regulatory screening.
  • The three-letter ISO currency code for the payout (USD, EUR, GBP, and so on). The wrong code can cause the transfer to bounce.

Ask the recipient for these details in writing, ideally from a source you can verify independently. Do not rely on numbers pasted into an email you were not expecting.

The Fields You Actually Fill In

Whether you are using an online banking portal or a paper form at a branch, the inputs map to numbered fields inside the MT103. Knowing what each one is for makes the on-screen labels easier to read.

  • Field 20 (Sender’s Reference) is a unique code your bank assigns to identify the transfer. You will see it on your receipt and can quote it if you ever need to trace the payment.2Goldman Sachs Developer. Swift Payments
  • Field 32A (Value Date, Currency, and Amount) is the settlement date, the three-letter currency code, and the amount.
  • Field 50 (Ordering Customer) is your legal name and address as sender, and it must match what your bank has on file.3Swift. Standards MT Usage Guidelines
  • Field 56 (Intermediary Institution) is where the correspondent bank’s details go, if one is needed to reach the recipient.
  • Field 57 (Account with Institution) is the specific branch or bank holding the recipient’s account.
  • Field 59 (Beneficiary Customer) is the recipient’s name and account number, exactly as registered at their bank.3Swift. Standards MT Usage Guidelines
  • Field 70 (Remittance Information) is a free-text field for the purpose of payment, such as an invoice number or a contract reference. Some countries require a specific purpose-of-payment code here, and a vague description can cause the receiving bank to reject the transfer.2Goldman Sachs Developer. Swift Payments
  • Field 71A (Details of Charges) is a three-letter code that sets who pays the fees.

On your bank’s form these show up as ordinary labels: “beneficiary name,” “beneficiary account/IBAN,” “beneficiary bank SWIFT/BIC,” “amount,” “currency,” “purpose of payment,” and “charge type.” The underlying structure is what your bank sends onward.

Choosing Who Pays the Fees: OUR, SHA, or BEN

Field 71A is the choice most senders overlook, and it changes how much money the recipient actually receives. You pick one of three codes.

  • OUR: you pay every fee in the chain. Your bank charges its outgoing fee, and any intermediary or receiving bank fees are billed back to you. The recipient gets the full amount.
  • SHA (shared): you pay your own bank’s outgoing fee. The recipient absorbs intermediary and receiving fees, which come out of the amount before it arrives. Most banks default to SHA if you do not specify.
  • BEN (beneficiary): the recipient pays every fee. All charges are deducted from the transfer, so they receive noticeably less than you sent.

If you owe an exact figure, such as a foreign invoice or a tuition bill, choose OUR. Under SHA or BEN, the recipient will come up short and you may need to send a top-up payment to close the gap.

Extra Requirements on Larger Transfers

Banks collect more information as the amount grows. For any international transfer of $3,000 or more, the FinCEN “Travel Rule” requires your bank to record and forward your name, address, and account number with the payment message and to retain those records for five years.4Financial Crimes Enforcement Network. Funds Travel Regulations – Questions and Answers This happens automatically, but it is why banks ask for so much identifying information even on modest wires.

For transfers of $10,000 or more, expect additional questions. Federal law requires financial institutions to file a Currency Transaction Report for cash transactions exceeding that threshold.5CFTC. Currency Transaction Reporting – Anti-Money Laundering Even on non-cash wires at that size, banks routinely ask for the source of funds, the reason for the transfer, and sometimes an invoice or contract to back it up. Have those ready.

Verify the Recipient Before You Send

Wire fraud is the reason to slow down at exactly the moment you feel rushed. The FBI reported over $55 billion in exposed losses from business email compromise between 2013 and 2023.6FBI Internet Crime Complaint Center. Business Email Compromise – The $55 Billion Scam The typical scheme uses a hacked or spoofed email to send fraudulent bank details for what looks like a legitimate wire request. Criminals often sit inside an email account for weeks studying templates before striking.

The signs are consistent: unexpected changes to payment instructions, urgent last-minute requests, slight misspellings in domain names, and pressure to skip verification steps. The single most effective countermeasure is out-of-band verification. Before you send, call the recipient using a phone number you already had on file, not one supplied in the email carrying the wiring instructions. For high-value or non-routine transfers, some banks also offer a callback service in which a designated official must provide a passcode before funds release. The extra minutes are worth it.

Submitting the Transfer

With the fields complete, you submit online or at a branch. Online submissions end with a summary screen showing every field. Read it as if you were proofreading someone else’s work. Most banks trigger a multi-factor authentication step at this point, such as a code sent to your phone. In person, you will show government-issued identification so the bank can verify your identity under anti-money-laundering rules.

Clicking confirm or signing the paper form is a binding commitment: you are authorizing the bank to debit your account and send the funds. The bank will provide a receipt with the transaction reference number from Field 20, the amount, and the date. Keep it. It is your proof that the bank accepted and initiated the instructions.

The 30-Minute Cancellation Window

If you catch a mistake after confirming, act immediately. Under federal rules, you can cancel a remittance transfer for a full refund, including all fees and taxes, if you contact your bank within 30 minutes of authorizing payment.7Consumer Financial Protection Bureau. Comment for 1005.34 – Procedures for Cancellation and Refund of Remittance Transfers The right applies regardless of the bank’s normal business hours, and the bank must be able to process the request as long as it can identify the specific transfer.

After that window closes, retrieval gets much harder. Your bank can send a recall request to the receiving bank, but it operates on a best-efforts basis; if the funds have already been credited, the receiving bank needs the recipient’s consent to return them. Recalls can take two weeks or longer and both banks may charge fees. There is no guarantee of success. That is why the review screen matters.

Mistakes That Get Transfers Rejected

Most SWIFT problems trace back to data entry, and each fix costs money. Amendment or investigation fees typically run $25 to $75 when a bank has to intervene manually.

A few specific traps catch senders repeatedly:

  • The beneficiary name in Field 59 does not match the account holder’s name at the receiving bank exactly. Nicknames, abbreviations, and missing initials can all trigger a compliance hold.
  • The destination country uses IBANs and you supplied only a local account number. The transfer will almost certainly bounce.
  • Field 70 is left blank or filled with a vague description in a country that requires a specific purpose-of-payment code. The receiving bank rejects it.
  • The currency code does not match what the recipient’s account can accept.
  • Sanctions screening flags the recipient’s name, country, or bank. Every bank in the chain screens against lists maintained by the Office of Foreign Assets Control and equivalent bodies abroad. A match can freeze or block the transfer regardless of how carefully you filled out the form.8FFIEC. BSA/AML Manual – Office of Foreign Assets Control

Before you confirm, run one last pass over the summary. Check the beneficiary name character by character against a document from the recipient. Confirm the IBAN or account number the same way. Verify the BIC. Make sure the currency and amount are what you intended and the charge code (OUR, SHA, or BEN) matches what you agreed to pay. The few minutes this takes are cheaper than any of the fixes.