SWIFT Formatting Guidelines - ubs.com
AbSWIFT Formatting Guidelines MT103+ and MT210For marketing purposesQualified Formatting Guidelines for SWIFT MT103+ and MT210 messages are currency-independent and hence have been provided to you below as part of the UBS basic Guidelines for Customer Transfer MT103+The code STP must be indicated in the header of the SWIFT message in the validation flag field NameMeeting UBS STP/Qualified StandardsM20Transaction reference Number16XO13cTime Indication/ 8c / 4!n1!x4!nM23BBank Operation CodeCREDO23EInstruction CodeAccepted code words: SDVA, INTC or CORT11O26TTransaction Type CodeNot to be usedM32AValue Date, Currency Code, Amount6!n3!a15dO33BCurrency/Instructed Amount3!a15dO36ExchangeRate 12dM50aOrdering CustomerOption A with BEI2 Option KO51ASending InstitutionNot to be usedO52AOrdering InstitutionOption A with BIC codeO53aSender s CorrespondentOption A with BIC codeOption B with your UBS account number in a 21-digit format in the account number : If an account number is then the 21-digit format of this account is separators must be used.
O 26T Transaction Type Code Not to be used M 32A Value Date, Currency Code, Amount 6!n3!a15d ... header of the message (block 3) is mandatory and must contain the code STP in the validation flag field 119. ... Melbourne. You send UBS in Zurich a SWIFT MT210, using reference 318393.
Download SWIFT Formatting Guidelines - ubs.com
Information
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document:
Related search queries
MT 103 - ClearingLine Format Specifications MT 103, Swift, Reference, Message, FORMAT FIELD23 Field 23B: Bank Operation, 103+ Single Customer Credit Transfer, Message type, Customer Statement Message, S.W.I.F.T, SWIFTStandards - Category n - Common Group, SWIFTStandards Category n Common Group, SWIFT message, Swift User Guide, Bank Code Definitions for Requesting Wires, Message Reference Guide, UBPHPHMMXXX PHSBPHMMXXX PHILIPPINE, Xact via SWIFT, SWIFT message type, Type