A Basic MT103 Decrypted: Mandatory Fields Only

An MT103 is a single customer credit transfer instruction sent through SWIFT FIN. It tells the receiving bank to pay a named beneficiary a stated amount in a stated currency on a stated value date. The mandatory fields are field 20 for the transaction reference, field 23B for the bank operation code, field 32A for the value date, currency and amount, field 50a for the ordering customer, field 59a for the beneficiary customer, and field 71A for the details of charges. Every MT103 must carry these fields, and a message missing any one of them will be rejected by SWIFT validation before it reaches the receiver. Field 20 carries a unique reference that the sender creates, such as 103REF405775 or PAY20241105A, and it must be no more than 16 characters. Field 23B carries the bank operation code, and for a normal customer payment that code is CRED, which means a credit transfer. The receiver uses field 20 to match the payment to its own books, to answer customer queries, and to link the MT103 to later confirmations, statements and investigations. If two payments carry the same reference on the same day, operations teams cannot tell them apart, so uniqueness is a control, not a courtesy. Field 32A combines three facts in one line. The value date in YYMMDD format, the three letter ISO currency code, and the amount with a comma as the decimal separator. A value of 261105USD367574,90 means value on 5 November 2026, in United States dollars, for 367,574.90 dollars. The value date is the date on which the receiving bank must make the funds available to the beneficiary, subject to cut off times and local holidays. An incorrect value date can create interest claims, so senders check it against the currency calendar before release. Field 50a identifies the ordering customer, the person or company that asked for the payment, and field 59a identifies the beneficiary customer who must receive it. Field 50a can be 50A with a BIC, 50F with a party identifier, or 50K with a name and address, while field 59a is normally 59A or 59F with an account number. For example, a Paris exporter named Atelier Lumiere SARL might appear in field 50K with its Paris address, while the Madrid beneficiary appears in field 59A with account ES6300491800132710387658. Both fields are screened against sanctions lists. Field 71A states who bears the charges, using OUR, BEN or SHA. OUR means the ordering customer pays all charges, BEN means the beneficiary pays all charges, and SHA means the ordering customer and the beneficiary share the charges, with each bank deducting its own fee. In a direct relationship, these six mandatory fields are enough because the sender knows the receiver, holds a nostro account with it, and can debit that account directly. The receiver knows the beneficiary account, credits it, and the payment reaches the beneficiary without any other bank being involved. Worked example with real numbers: a basic MT103 for EUR 48,250 from a buyer in Munich to a supplier in Lyon carries only the mandatory fields: field 20 transaction reference, field 23B bank operation code, field 32A value date, currency and amount, field 50K ordering customer, field 59 beneficiary customer, and field 71A details of charges. The payment is credited in full, less the beneficiary bank charges under SHA, so the supplier receives EUR 48,250 less EUR 12, or EUR 48,238, and reconciles it by the reference in field 20. The difference between a basic MT103 and a REMIT is therefore the remittance data, not the payment, and the basic MT103 is the minimum that will move the money. Source: SWIFT MT103 format specifications. Failure and recovery: a basic MT103 fails when a mandatory field is missing, and the failure is immediate, because the receiving bank rejects it with a pacs.002 RJCT in the ISO 20022 world, or returns it in the legacy world, and the sender must correct the field and resend. A basic MT103 that is sent as REMIT, with remittance data that the receiving bank does not expect, may be processed as a standard MT103, and the remittance data may be ignored, so the supplier cannot reconcile, and the recovery is a separate advice. A sender who needs remittance data should use pacs.008, not REMIT, because pacs.008 carries structured remittance that cannot be ignored. For a business analyst, product owner or subject matter expert, the basic MT103 requirement must name the mandatory fields, state that REMIT is a legacy variant for remittance-heavy payments, and state that after 22 November 2025 new payments use pacs.008. The requirement must map each mandatory field to its pacs.008 equivalent, so the migration preserves the payment, and must state the validation that rejects a payment with a missing mandatory field before it is sent, because a payment rejected after sending costs a day, while a payment rejected before sending costs a minute. A mandatory field that is not validated is a payment that will fail in production.