SWIFT message guide

MT103 fields explained

A practical guide to the main fields in a SWIFT MT103 customer credit transfer, what each field represents and what an operations user should check.

Published 5 September 2026 ยท 8 minute read

What an MT103 represents

An MT103 is used to communicate a single customer credit transfer. The message combines network headers with a text block containing numbered fields. Those fields identify the payment, settlement amount, ordering party, beneficiary, routing institutions, remittance details and charge arrangement.

Common MT103 fields

FieldTypical purposeOperational check
:20:Sender's transaction referenceUse it to trace the instruction and prevent duplicate handling.
:23B:Bank operation codeConfirm that the operation type matches the expected credit transfer.
:32A:Value date, ISO currency code and amountRead the six-digit date, three-letter currency and decimal amount together.
:50A/F/K:Ordering customer in one of several permitted formatsReview the account, name and address or identifier supplied.
:52A/D:Ordering institution when different from the senderCheck whether another institution originated the instruction.
:53a:Sender's correspondentReview the reimbursement or correspondent route.
:54a:Receiver's correspondentConfirm the receiver-side correspondent when present.
:56a:Intermediary institutionIdentify a bank between the sender and account-with institution.
:57a:Account with institutionConfirm the beneficiary's servicing institution.
:59a:Beneficiary customerCheck the beneficiary account or identifier and name.
:70:Remittance informationMatch invoice numbers, purpose or other payment references.
:71A:Details of chargesReview whether charges are borne by the sender, beneficiary or shared.

Reading field 32A

Field 32A combines three values without labels. In :32A:260902USD25000,00, 260902 is the value date in YYMMDD format, USD is the currency and 25000,00 is the amount using a comma as the decimal separator.

Party-field options matter

A letter appended to a field number changes its format. For example, option A generally emphasizes an identifier such as a BIC, while options F or K can carry party details in different structured or line-based forms. Do not assume that every MT103 will use exactly fields 50K, 57A and 59.

Headers and text block

The basic header begins with block 1, while block 2 carries application-header information and can reveal the message type and receiver. The numbered payment fields usually appear inside block 4. A viewer should preserve the raw message because header interpretation and field options may be important during an investigation.

Use this as an operational introduction. Exact network validation rules, permitted options and usage requirements depend on the applicable SWIFT documentation and market practice.

Check the :32A: value in your own MT103

Field :32A: combines the six-digit value date, three-letter currency and comma-decimal amount. If a message is being rejected or is difficult to read, open the MT103 format checker, use the safe example or paste an authorized complete FIN message, and inspect any relevant warnings.

Fastest way to inspect a message

Paste a redacted message into the free MT103 viewer. FinMessage identifies common fields, presents a readable payment summary and lets you export the result to Excel.