SWIFT MT103 Field 59 — Beneficiary Customer
Field 59 is the Beneficiary Customer — the final recipient of the payment. Mandatory on every MT103. Draft an MT103 with complete beneficiary data →
Details
Format: the account number on line 1 (preceded by a slash, e.g. /12345678 or /GB82WEST12345698765432 for an IBAN), then 1–4 lines of up to 35 characters each for the beneficiary name and address. Variant 59A uses a BIC instead of free-format details when the beneficiary is itself a financial institution. Variant 59F is the ISO 20022-aligned structured format — it uses tagged sub-fields (same 1/ name, 2/ address, 3/ country/town, 4–8/ identity tags as field 50F) for the beneficiary, enabling machine-readable compliance screening.
Field 59 is mandatory on every MT103 and is one of the most scrutinised fields in the payment chain. Every correspondent bank runs AML (anti-money-laundering) and sanctions screening on the beneficiary name and account in field 59. An incomplete or ambiguous beneficiary — for example, just a company abbreviation with no address — is a common cause of compliance holds. Best practice: include the full legal name (matching registration documents), a complete postal address, and the account number or IBAN on the first line.
For SEPA payments, the account number in field 59 should be the beneficiary's IBAN (International Bank Account Number) — SEPA scheme rules require an IBAN for all SEPA Credit Transfers. For non-SEPA payments, a local account number format is acceptable — ABA plus account for US payments, Sort Code plus account for UK payments, etc. When an IBAN is available (even outside SEPA), it is best practice to include it because IBANs self-validate via the MOD-97 check digit.
The 35-character-per-line limit in field 59 creates challenges for beneficiaries with long names or addresses. A corporate beneficiary with a long registered name may need to be abbreviated or split across multiple lines. Critical: the beneficiary name on line 2 of field 59 must be complete enough for the beneficiary bank to identify the account. The beneficiary bank cannot credit the account if the name in field 59 does not match its records — this is a key fraud-prevention check.
In ISO 20022 pacs.008, the beneficiary customer is represented by the Cdtr (Creditor) element with structured Nm (name), PstlAdr (postal address with separate sub-elements for each address component), Id (identifier — national ID, company registration, LEI), and CtryOfRes (country of residence). The richer pacs.008 structure eliminates the ambiguity inherent in 35-character free-format text and allows the beneficiary bank to automatically match the payment to the correct account with high confidence.
Quick facts
| Example value | :59:/87654321\nJANE ROE\n55 BEACH RD\nSYDNEY AU |
|---|---|
| Valid characters / format | Account + 4 free-text lines |
| Required on MT103 | Mandatory |
| Required on MT202 | Not used |
| Required on pacs.008 | Mandatory |
| Notes | Beneficiary. Mapped to <Cdtr> on pacs.008. |
Key facts
- Mandatory on every MT103 — always required
- /account (or /IBAN) on line 1, then name and address up to 4 × 35 chars
- SEPA requires an IBAN in field 59; non-SEPA accepts local account formats
- Full legal name + complete address required for clean compliance screening
- 59A for financial institution beneficiaries (BIC); 59F for ISO 20022 structured format
- pacs.008 equivalent: Cdtr element with structured Nm, PstlAdr, Id
Frequently asked questions
Does field 59 need an IBAN?
For SEPA payments (intra-EEA credit transfers), yes — an IBAN is required under SEPA scheme rules. For non-SEPA SWIFT payments, a local account number format is acceptable (e.g. ABA + account for US, Sort Code + account for UK). When an IBAN is available even outside SEPA, it is best practice to use it because it self-validates.
What happens if the beneficiary name in field 59 does not match the account?
The beneficiary bank will typically return the payment or place it on hold pending confirmation of the beneficiary's identity. Banks have strict policies about crediting accounts where the name in the SWIFT message differs from the account holder name in their records. Always ensure the name in field 59 exactly matches the account name at the beneficiary bank.
Can field 59 contain an individual's name?
Yes — individual beneficiaries use field 59 (standard or 59F). Line 1 is the account number, line 2 is the full name, and lines 3–4 are the address. Individuals in SEPA or other IBAN-using regions should have their IBAN on line 1. The FATF Travel Rule requires the full legal name and account number of the beneficiary to be present.
Is field 59F replacing field 59?
Like the 50F vs 50K transition for ordering customers, 59F (structured) is gradually replacing plain 59 (free-format) as the preferred format for ISO 20022 alignment. 59F uses tagged sub-fields that allow automated compliance screening without heuristic parsing. As part of the SWIFT CBPR+ migration, 59F is becoming the expected format for beneficiary data on cross-border SWIFT payments.
What should I do if the beneficiary's address is longer than 4 × 35 characters?
You must abbreviate or truncate to fit within the 4 × 35 character limit. Prioritise: account number on line 1, full legal name on line 2, street address on line 3, city and country on line 4. If the address still does not fit, use standard postal abbreviations. Critically, never omit the country — it is essential for compliance screening. Put the complete address in field 70 (remittance information) as supplementary context if it helps.
Related guides
Related — more from swift field reference and beyond
Get 100 free credits — track unlimited SWIFT payments
No card needed. Free for ordinary users — 10 free trackings per day per IP, no signup required. Track any international wire across 11,000+ banks.
Track a payment now — completely free Or try the tracker now →