Citi Mini Series and Reference Guide Part 1

ISO 20022: Citi Mini Series & Reference Guide  | 2 1 | Treasury and Trade Solutions XML Elements How is an MT Structure Different From an MX Structure? XML Elements An XML instance or document contains data in elements and nested elements (elements which contain other elements) corresponding to the hierarchy imposed by the XML schema. Naming conventions An XML element is named according to the following rules: • Can contain letters, numbers, and other characters, but must not start with a number or punctuation mark • Must not start with XML, xml, or Xml • Must not contain any spaces MX naming conventions There are some generic naming rules that apply to most items in the database: • The names of all items in the database use the upper CamelCase convention, as follows: • Each word starts with a capital letter • There are no white spaces between words • A name may be made up of multiple words, each consisting of alphanumeric characters • Words use British English vocabulary • All names must start with an alphabetic character • All characters that follow the first characters must be letters or numbers Example of a Street Name element: <StrtNm>OxfordStreet</StrtNm> MX message element multiplicity (occurrences) An MX message element specifies its cardinality (number of elements in a set) using minimum (min) and maximum (max) to describe the occurrences. Interbank Settlement Amount Interbank Settlement Date Required element Optional element Unlimited element occurrences Credit Transfer Transaction Information Min Max 1 1 0 1 0 Element Multiplicity MT ISO 20022 (MX) (1: F01OELBATWWAXXX09750000073 (2: I103ABNANL2AXXXU3003) (3: (113:URGT)(108:1NTLPMTS)) (4: (CrLf) :20:494932/DEV (CrLf) :32A:0307031EUR19658, 47 (CrLf) :33B:EUR1958, 47 (CrLf) :50K: Franz Holzappfel GMBH (CrLf) Vienna (CrLf) :59:H.F. JANSSEN (CrLf) AMSTERDAM (CrLf) :70:/INV 19042 910412 (CrLf) :71A: SHA (CrLf) -) (5: (CHK: 123456789AVC)) What’s Different? • MX message structure is dynamic, allowing for an enhanced data model with dedicated, structured elements for specific information • MX messages are significantly longer than MT messages, capturing a much larger amount of data • MX messages have element hierarchy with nested elements for logical grouping of data Basic header block Application header block User header block Text block Trailer block SWIFTNet Headers Envelope — container for the business message The business message comprises the application header and “business” document The “business” document contains the MX message instance (or ISO 20022 message instance) ISO 20022 Business Application Header ISO 20022 Message Business Message Application Header Request Payload Request Header Request Exchange Request Document MX Message Instance Crypto <AppHdr> … </AppHdr> <Document> … </Document> Source: SWIFT. For more information, visit myStandards. Source: SWIFT. For more information, visit myStandards. “ISO 20022 provides rich, structured data with a consistent business directory across domestic and cross- border payments. It will significantly improve compliance, speed of processing and efficiency, while improving the quality of service to clients.” – Saqib Sheikh, SWIFT Global Head of the ISO 20022 Program