SWIFT MT103 Field 57A — Account With Institution

Last reviewed: · Curated by Ohmyfin Organisation editorial.

Field 57A is the Account With Institution — the beneficiary's bank. A correct BIC in this field is one of the most important factors in on-time payment delivery. Look up any BIC free →

Payment Tracker

LIVE

Paste your UETR — we query the SWIFT GPI network in real time.

36-character UUID from your MT103 field 121 or pacs.008 <UETR> tag. Where to find it →

Receive your tracking result instantly after search
If not found, we’ll monitor for 7 days and alert you
No account needed — one-click unsubscribe
2
Trusted by 2M+ users monthly  ·  No account or card required
Encrypted | SWIFT Network Coverage | Real-time GPI
SWIFT MT103 message diagram showing fields 20, 32A, 50K, 59, 70 and 121 (UETR)
How an MT103 maps to the UETR (field 121), sender reference (field 20), value-date/currency/amount (field 32A) and beneficiary details. Source: SWIFT MT103 specification.

Details

Format: BIC (8 or 11 characters), optionally preceded by a party identifier (the account at the beneficiary bank, if it needs to be specified at the institutional level). Variants 57B (clearing code and address), 57C (account number at the receiver), and 57D (free-format name and address) also exist. Field 57A (BIC) is the preferred variant in all modern MT103 implementations because it unambiguously identifies the beneficiary's bank and enables straight-through processing at every preceding correspondent without any manual routing decisions.

Field 57 is the "Account With Institution" — the bank that holds the beneficiary's account and will perform the final credit. This is distinct from field 59 (Beneficiary Customer), which follows immediately and identifies the specific account holder at that bank. The relationship is: field 57 tells the SWIFT network "deliver to this bank", and field 59 tells that bank "credit this specific account." Together, fields 57 and 59 define the complete end-point of the payment.

Getting field 57A wrong is one of the most common causes of payment failure. Common errors: (1) Providing a head-office BIC (e.g. 8 characters) when the branch-specific BIC (11 characters) is required — most major banks accept both forms, but some route payments differently by branch code; (2) Providing the wrong BIC altogether — the payment is delivered to an unintended bank; (3) Providing an 8-character BIC when a payment is intended for a SEPA beneficiary bank that uses different routing at the branch level. Always verify the BIC at /swift-codes before sending.

For SEPA payments (intra-EEA credit transfers), the BIC in field 57A can in theory be derived from the IBAN in field 59, and SEPA rules allow field 57A to be omitted on certain SEPA Credit Transfer schemes. However, for non-SEPA SWIFT payments, field 57A must always be present — correspondent banks cannot route the payment without knowing the beneficiary bank's BIC. Omitting field 57A on a non-SEPA SWIFT payment will cause misrouting or manual intervention at an intermediary.

In ISO 20022 pacs.008, the beneficiary bank is represented by the CdtrAgt (Creditor Agent) element, which contains a FinInstnId (Financial Institution Identification) with BICFI (BIC), optionally a ClrSysMmbId (clearing system member ID, e.g. ABA routing number or Sort Code), Nm (name), and PstlAdr (postal address). The richer pacs.008 structure allows the creditor agent to be identified by multiple methods simultaneously — BIC plus ABA routing number, for example — giving more routing options than the single-value MT103 field 57.

Quick facts

SWIFT field specification
Example value:57A:BENEBNK4XXX
Valid characters / formatBIC
Required on MT103Mandatory
Required on MT202Mandatory
Required on pacs.008Mandatory
NotesAccount-with institution (beneficiary bank).

Key facts

Frequently asked questions

What if field 57A contains the wrong BIC?

The payment may be delivered to an unintended bank (if the BIC is valid but wrong) or rejected mid-chain (if the BIC is invalid or unreachable). Either outcome requires a return or recall process that can take 1–10 business days. Always verify the BIC at /swift-codes or directly with the beneficiary before sending.

Is an 8-character BIC the same as an 11-character BIC?

The 8-character BIC identifies the bank's primary/head office. An 11-character BIC includes a 3-character branch suffix (e.g. "XXX" = head office, or a specific branch code). For SWIFT routing purposes, 8-character and 11-character BICs for the same primary office are equivalent — you can safely append XXX to an 8-character BIC to get the 11-character form.

How do I find the correct BIC for a bank?

Search Ohmyfin's free BIC directory at /swift-codes. You can search by bank name, city, or country. The directory covers over 8,000 active registered BICs. Alternatively, ask the beneficiary to check their bank's official website under "international payments" or "SWIFT/BIC code." Banks are required to disclose their BIC for international payment purposes.

Why does field 57 not include the beneficiary's account number?

Field 57 identifies the institution (the bank). The account number within that institution is in field 59 (Beneficiary Customer). The two-field design reflects the routing logic: field 57 routes the SWIFT message to the right bank, and field 59 routes the credit to the right account within that bank.

What is the difference between field 56A and field 57A?

Field 56A (Intermediary Institution) is an intermediate correspondent bank in the chain — it receives the payment and forwards it to the next bank. Field 57A (Account With Institution) is the final destination bank where the beneficiary holds their account. Payments may or may not have a field 56A, but will almost always have a field 57A.

Get 100 free credits — track unlimited SWIFT payments

No card needed. Free for ordinary users — completely free for individuals — no daily limit, no card required. Track any international wire across 11,000+ banks.

Track a payment now — completely free Or try the tracker now →
ExploreSWIFT trackerUETR trackerCurrency exchange ratesUSD → EUR rateGBP → USD rateEUR → GBP rateUSD → JPY rateWestern Union MTCN trackerMoneyGram reference trackerRia PIN trackerRemitly trackerXoom / PayPal trackerWorldRemit trackerWise trackerRevolut trackerOFX trackerZelle trackerVenmo trackerCash App trackerPayoneer trackerSkrill trackerNeteller trackerInstarem trackerTRN trackerDraft & validate hubMT ↔ MX translatorMX → MT translator@ohmyfin/swift-draft (npm)MT103 drafterMT202 drafterMT202COV drafterMT199 drafterpacs.008 drafterpacs.009 drafterpacs.002 draftercamt.053 draftercamt.054 drafterMT103 trackerWire-transfer trackerSWIFT GPI trackerBIC lookupIBAN explainedUETR explainedTRN explainedBIC explainedMT103 guideMT202 guidepacs.008 guideField 20Field 32AField 50KField 121 (UETR)Track USDTrack EURTrack GBPTrack CNYTrack INRSWIFT vs SEPASWIFT vs ACHSWIFT vs WiseUETR vs TRNBIC vs IBANMT103 vs pacs.008How long: UKHow long: USHow long: IndiaHow long: EurozoneStatus: ACSPStatus: ACCCStatus: RJCTStatus: PDNGSWIFT GPISWIFTNetOhmyfin AI AssistantSWIFT status todayBank trackersTrack HSBCTrack ChaseTrack BarclaysTrack NatWestTrack WiseTrack RevolutAsk: How to track SWIFTAsk: UETR not foundAsk: Stuck 2 weeksAsk: Get UETR from bankAsk: Is Ohmyfin freeAlliance AccessAlliance GatewaySWIFT GoKYC RegistryAbout swift.comSWIFT productsCurrency guidesPayment comparisonsPayment speedStatus codesSWIFT field referencePayments glossarySWIFT message typesSWIFT/BIC directoryCorrespondent banksKnowledge centerReject codesAC01 rejectAC04 rejectBE01 rejectCH09 rejectRR04 rejectHelp & troubleshootingPayment not receivedFind UETR on MT103Cancel SWIFT paymentFake MT103 warningMajor banksJPMorgan Chase BICHSBC BICDeutsche Bank BICCiti BICBNY Mellon BICCountry corridorsSend US → IndiaSend US → MexicoSend US → PhilippinesSend UK → IndiaSend UK → PakistanSend UAE → IndiaSend UAE → PhilippinesSend Saudi → IndiaSend Canada → IndiaSend Australia → IndiaMT message referenceMT202COVMT199MT940MT942MT900MT910MT195MT103 STPBanks by countryBanks in USBanks in UKBanks in GermanyBanks in IndiaBanks in ChinaBanks in UAEBanks in Saudi ArabiaBanks in SingaporeBanks in Hong KongBanks in JapanBanks in BrazilUse casesFreelancer paid abroadPay overseas supplierE-commerce payoutsTuition paymentReal estate abroadFamily remittanceScam alertsFake MT103 fraudMoney-transfer providersTrack WiseTrack RevolutTrack Western UnionTrack MoneyGramTrack RemitlyTrack RiaTrack XoomTrack WorldRemitTrack PayoneerTrack PayPalTrack OFXTrack SkrillTrack SendwaveTrack InstaremTrack TransferGoTrack Stripe payoutTrack AirwallexTrack HSBC Global MoneyTrack Monzo / Revolut / N26Wise vs RevolutWise vs PayPalWise vs Western UnionWise vs bank wireWestern Union vs MoneyGramRemitly vs Western UnionSend money to IndiaSend money to PhilippinesSend money to MexicoSend money to NigeriaSend money to PakistanSend money to UKAdvance-fee fraudBEC / CEO fraudPig butchering scamRomance scam wire