MT103 Straight-Through Processing (STP): Field Validation & Format Specifications

The MT103 Single Customer Credit Transfer is governed by SWIFT User Handbook standards and structured across five standard FIN message blocks: Block 1 (Basic Header containing application ID and logical terminal address), Block 2 (Application Header with input/output direction, message priority, and delivery monitoring), Block 3 (User Header containing Service Identifier 103 and Tag 121 UETR), Block 4 (Text Block containing mandatory and optional transaction fields), and Block 5 (Trailers containing Message Authentication Code and Checksums). Adherence to MT103 STP syntax guarantees uninterrupted processing across correspondent banking gateways.

STP compliance mandates strict validation on all Block 4 fields. Field 23B (Bank Operation Code) must specify standard codes such as 'CRED' (Credit Transfer) or 'SPAY' (SWIFT Pay). Field 33B (Instructed Amount) and Field 36 (Exchange Rate) must align with currency precision standards. Field 71A (Details of Charges) dictates cost allocation: 'OUR' (all charges borne by ordering customer), 'BEN' (all charges borne by beneficiary), or 'SHA' (charges shared between parties). Beneficiary account numbers in Field 59 must follow validated IBAN or standardized national account formats to avoid correspondent investigation fees.

Before an MT103 message is dispatched onto the SWIFT network, the sending node must verify bilateral Relationship Management Application (RMA) authorization with the receiver's BIC. Cloud Global Server embeds pre-flight RMA validation, real-time sanctions list matching against OFAC/UN/EU watchlists, and automated sub-millisecond BIC verification to maximize straight-through execution rates and eliminate wire hold delays.