CTM SETTLEMENT SERVICES REFERENCE: SWIFT MT541/543 AND CSV MAPPING

Transcription

1 CTM SETTLEMENT SERVICES REFERENCE: SWIFT MT541/543 AND CSV MAPPING MAY 03, 2018

2 Copyright 2018 The Depository Trust & Clearing Corporation ("DTCC"). All rights reserved. This work (including, without limitation, all text, images, logos, compilation and design) is proprietary and protected by copyright, and is for the exclusive use of users authorized by DTCC. If this work is received from DTCC in any electronic medium, authorized users of this work are granted a limited, non-exclusive, non-transferable, nonsublicensable and freely revocable license to make reproductions and transmissions necessary for downloading and storage of this work on the users' computers and to print one or more paper copies from the electronic version for their own use. Other than to this limited extent, no part of this work (including any paper copies thereof or print versions thereof) may be printed, copied, altered, modified, posted, reproduced, displayed, published, sold, licensed, used or distributed (including by transmission) in any form or by any means, or stored in any information storage and retrieval system, without DTCC's prior written permission. DTCC is the brand name under which certain affiliates of The Depository Trust & Clearing Corporation provide services in particular geographic areas. The Depository Trust & Clearing Corporation does not provide services to clients. Each of The Depository Trust & Clearing Corporation s affiliates is a legally separate and independent entity, and each is subject to the laws and regulations of the particular country in which it operates. Please see for more information on the legal structure of The Depository Trust & Clearing Corporation and its related entities. All product or service names are the property of their respective owners. Publication Date: May 03, 2018 Publication Code: CT741 Service: CTM Title: Settlement Services Reference: SWIFT MT541/543 and CSV Mapping

3 CONTENTS Contents 3 Preface 4 Audience 4 Changes in this Version of the Document 4 Related Documents and Training 4 Questions? 4 1. Creating Settlement Instructions and Notifications 5 Introduction 5 Overview 5 Enriching Settlement and Broker/Dealer Instructions 6 Enriching Instructions with ALERT 6 Executing Broker Enrichment Trade Component Fields 7 Instructing Party Enrichment TradeDetail Fields 8 When L1 Pairing Breaks Amend and Force-Match Effects on SSIs and BDIs 8 When Trades Settle in the Future Settlement Date Submission 8 Enriching Instructions Manually 8 Dual Enrichment Instruction 9 Dual Enrichment of TradeDetails ALERT Instructions 9 Dual Enrichment of TradeDetails Manual Instructions 10 Sourcing of Settlement Data 11 Error Handling SWIFT MT541/543 Message 12 Introduction 12 Overview 12 SWIFT MT541/543 Layout 12 Example of a SWIFT MT541/543 Message 28 Trade Blotter Example 29 Message Layout Example CSV File 33 Introduction 33 Overview 33 File Naming and Other Applicable Rules 33 SWIFT Fields, Codes, and Sample Values 35 Mapping SWIFT Fields with Multiple or Concatenated Values to CSV 35 Handling Fields with Multiple Values 35 Multiple Values and Serial Ordering 35 Concatenated Values 35 Narrative Value (settlement indicator processing narrative) 36 CSV File Layout 36 Example of a CSV File 46

4 PREFACE This document provides comprehensive information about how to use optional post-trade, pre-settlement services for CTM. Audience Read this manual if your business requirements include the following: Investment managers You are an investment manager and subscribe to any of the optional CTM settlement service offerings. You enrich settlement instructions automatically using ALERT or manually. Executing brokers You are an executing broker and subscribe to the optional ALERT Broker Dealer Instruction (BDI) enrichment or enrich your trades manually. Note DTCC offers settlement services only for the party that identifies as the InstructingParty on trade components, typically an investment manager. Since both parties to a trade supply extensive enrichment on allocations and contracts (also known as confirmations) this reference is for both trade sides. It also addresses workflows that involve non-dtcc counterparties. Changes in this Version of the Document This version of the document includes the following: SWIFT Message Layout Additional Notes in the following tags, qualifiers, and lines: o 95a BUYR SELL Line No 65 o 19a LOCO Line No 78 CSV Message Layout Local Broker s Commission Related Documents and Training For related documents and training in the DTCC Learning Center, go to Institutional Trade Processing CTM. Questions? The DTCC Client Center provides general assistance and technical help. Visit to: Enter a service request or check the status of an existing service request Search the knowledge base Obtain contact information Preface 4

5 1. CREATING SETTLEMENT INSTRUCTIONS AND NOTIFICATIONS Introduction This chapter describes how CTM uses TradeDetail messages to enrich settlement information and map the information to third party details. Overview The figure below shows an example of how CTM enriches settlement instructions and constructs third party details in the context of overall settlement services. The term third party details is used as a container for the following two specific uses, shown in Step 4: Settlement instructions, which custodians, subcustodians, and agents require to act upon allocations. Settlement notifications, which interested parties require for informational purposes. Figure 1.1 Enriching, Constructing, and Releasing Third Party Details Table 1.1 outlines each step in Figure 1.1 above. Table 1.1 Third Party Details Flow Description Step Stakeholder 1 Instructing Party and/or Executing Broker Action Description You submit TradeDetails (allocations or confirmations/contracts) and, optionally, TradeLevels (blocks). 2a ALERT ALERT CTM queries the ALERT database to enrich the SSIs on the instructing party s side and the BIA reference information on the executing broker s trade side. For more information about dual enrichment (also know as counterparty enrichment), see Dual Enrichment Instruction Creating Settlement Instructions and Notifications 5

6 Table 1.1 Third Party Details Flow Description (Continued) Step Stakeholder 2b Instructing Party and/or Executing Broker Action Description You or your counterparty manually enrich settlement instructions as follows: Instructing parties can enrich their TradeDetails. Executing brokers can enrich their TradeDetails and the corresponding TradeLevel. 3 CTM CTM constructs a third party detail based on the trade components. CTM formats and releases the third party detail using one or both of the following: MT541/543 over SWIFT Comma-separated value (CSV) file over Secure File Transfer Protocol (SFTP) You can query for the third party detail with an InfoRequest message. Supply SDET in the QueryType element to obtain settlement details in the InfoSettlementResponse. Work with your DTCC consultant to configure your message requirements, destination channels, and recipients. 4 CTM CTM releases the MT541/543 or CSV files, depending on the following: If FunctionOfTheMessage in the TradeDetail is NEWM or CANC, CTM releases a settlement instruction to a custodian. If FunctionOfTheMessage in the TradeDetail is COPY, CTM releases two settlement notifications to a fund administrator and value agent. When FunctionOfTheMessage in a TradeDetail is REPC and L1 pairing or L2 matching breaks, CTM removes any enrichment done for the trade up to that point. When the amended trade L1 pairs, CTM commences enrichment for ALERT subscribers. This manual addresses Steps 2a, 2b, and 3 shown in the shaded portion of Figure 1.1. Enriching Settlement and Broker/Dealer Instructions You and your counterparty can have ALERT automatically enrich your instructions or you can enrich them manually: ALERT enrichment For CTM clients who use ALERT: o o Executing brokers: CTM requires the ALERT BIA subscription and a minimal set of ALERT key look-up elements (also known as ALERT keys) in the submitted TradeDetail and optional TradeLevel elements. Investment managers: CTM requires the ALERT SSI subscription and a minimal set of ALERT keys in the submitted TradeDetail. Manual enrichment If you manually supply enrichment information on trade components, ensure that you provide the required elements described in Enriching Instructions Manually. The SettlementInstructionsSourceIndicator element value in the TradeDetail specifies how CTM either retrieves settlement instructions from ALERT or relies on your manually supplied values. If you subscribe to settlement services (including third party notification), CTM requires a value in the SettlementInstructionsSourceIndicator element. Enriching Instructions with ALERT In addition to other mandatory elements, DTCC specifically requires the XML message elements in the next three tables to automatically enrich trades from ALERT with the following: BDI Enrichment Executing broker s Broker Delivery Instructions (BDIs). SSI Enrichment Investment manager s Standing Settlement Instructions (SSIs). Note The XPaths in all of the tables in this manual provide XML element specificity. For example, AccountID occurs in the IPSettlement composite and the EBSettlement composite. IPSettlement/AccountID refers to AccountID in the IPSettlement composite just as EBSettlement/AccountID refers to AccountID in the EBSettlement composite. Creating Settlement Instructions and Notifications 6

7 Executing Broker Enrichment Trade Component Fields Executing brokers can use the TradeDetail and the TradeLevel to supply ALERT keys. CTM requires valid ALERT keys on at least one of the trade components. Table 1.2 outlines the elements in the TradeDetail that CTM requires for BDI enrichment on the executing broker s trade side. Table 1.2 ALERT Enrichment TradeDetail Fields for Executing Brokers TradeDetail XPath Description Example Meaning EBSettlement/AccountReference Executing broker s account reference identifier in ALERT Executing broker account for BIA enrichment EBSettlement/AccountID 1 The instructing party s account identifier in ALERT Institutional account for US equities that settle at the DTC PartySettlement/PartyIdentifier PartySettlement/Settlement InstructionsSourceIndicator Declares which trade side s ALERT keys are in the composite: instructing party (INST) or executing broker (EXEC). Directs DTCC to enrich settlement instruction elements with ALERT BDIs. EXEC ALRT Executing broker s ALERT keys ALERT enrichment PartySettlement/AlertCountryCode The country in the ALERT BDI. USA United States of America PartySettlement/AlertMethodType PartySettlement/AlertSecurityType PartySettlement/ AlertSettlementModelName 1 The manner in which a settlement takes place for a given security. It typically occurs in a national or international central securities depository. The type of security settling with the chosen ALERT method, such as an equity or corporate bond. The model name that you or your custodian give a BDI in ALERT. 1 AlertSettlementModelName is a mandatory element for the executing broker trade side only. DTC EQU INST-USEQU- DTC Depository Trust Company Equity Institutional account for US equities that settle at the DTC CTM also allows executing brokers to supply the ALERT look-up keys in the following table. Only executing brokers use the TLEBSettlement composite in the TradeLevel. Table 1.3 outlines the elements in the TradeLevel that DTCC requires for BDI enrichment on the executing broker s trade side. Table 1.3 ALERT Enrichment TradeLevel Fields for Executing Brokers TradeLevelXPath Description Example Meaning TLEBSettlement/PartyIdentifier element for executing brokers only. EXEC Executing broker s ALERT keys are used TLEBSettlement/Settlement InstructionsSourceIndicator Directs CTM to enrich instruction elements with ALERT BDIs. ALRT ALERT enrichment. TLEBSettlement/AlertCountryCode The country in the ALERT BDI. USA United States of America TLEBSettlement/AlertMethodType TLEBSettlement/AlertSecurityType The manner in which a settlement takes place for a given security. It typically occurs in a national or international central securities depository. The type of security settling with the chosen ALERT method, such as an equity or corporate bond. TLEBSettlement/AlertSettlement The model name that you give a BDI in ALERT. INST-USEQU- ModelName 1 DTC 1 AlertSettlementModelName is a mandatory element for the executing broker trade side only. DTC EQU Depository Trust Company Equity Institutional account for US equities that settle at the DTC The following rules apply when executing parties supply conflicting or missing information in the TradeDetail and TradeLevel ALERT elements outlined in the next two tables. Creating Settlement Instructions and Notifications 7

8 CTM evaluates the TradeDetail first. If there is missing or invalid information on the elements, CTM evaluates the TradeLevel for information. CTM evaluates the TradeLevel and uses the message for missing and invalid elements on the TradeDetail. If it discovers two values for the same element, CTM maps the value in the TradeDetail to the third party detail. Instructing Party Enrichment TradeDetail Fields To enrich SSIs from ALERT, instructing parties can only supply ALERT keys on a TradeDetail. The following table lists the ALERT keys in the TradeDetail. Table 1.4 outlines the elements in the TradeDetail that CTM requires for BDI enrichment on the executing broker s trade side. Table 1.4 ALERT Enrichment TradeDetail Fields for Instructing Parties TradeDetail XPath Description Example Meaning IPSettlement/AccountID The instructing party s account identifier in the ALERT SSI Institutional account for US equities that settle at the DTC PartySettlement/PartyIdentifier Declares which trade side s ALERT keys are in the composite. INST Instructing party s ALERT keys SettlementInstructions SourceIndicator Directs CTM to enrich settlement instruction elements with ALERT SSIs. ALRT ALERT enrichment AlertCountryCode The country in the ALERT BDI. USA United States of America AlertMethodType AlertSecurityType The manner in which a settlement takes place for a given security. It typically occurs in a national or international central securities depository. The type of security settling with the chosen ALERT method, such as an equity or corporate bond. DTC EQU Depository Trust Company Equity When L1 Pairing Breaks Amend and Force-Match Effects on SSIs and BDIs Whenever one of the following situations occurs, CTM requires SSI and BDI re enrichment for a trade: Amend Amending an L1 paired (paired) TradeLevel with a trade component using FunctionOfTheMessage=REPC breaks paired TradeLevels. When CTM pairs the amended TradeLevels again, CTM proceeds with SSI and BDI enrichment. Force Match CTM updates the value of the SettlementInstructionsSourceIndicator element to MANI, regardless of its value at pairing. PSET field value change If either party amends its value in the PSET element of a TradeDetail, then L1 pairing breaks and CTM requires SSI and BDI re enrichment. When Trades Settle in the Future Settlement Date Submission The CTM SettlementDate element maps to the Effective Settlement Date element in ALERT. For trades in both of the following categories, CTM requires that investment managers include the future effect date in the SettlementDate element in the TradeDetail: The settlement date is at least one day from today. The settlement date is no more than 400 days in the future. Enriching Instructions Manually Table 1.5 lists the required TradeDetail elements for manual settlement instruction enrichment. Leave all elements in the TradeDetail with the prefix Alert blank. Creating Settlement Instructions and Notifications 8

9 Table 1.5 Manual Enrichment Executing Brokers and Instructing Parties TradeDetail XPath Description Example Meaning SettlementInstructionsSource Indicator Directs CTM to enrich settlement instruction elements with manually supplied settlement instructions. MANI CTM requires the following instruction fields on the TradeDetail to construct a third party detail: ReceiverAgentBIC CustodianBIC SubAgentBIC SecurityAccount CTM reviews the TradeDetail elements in the order listed to map the value to the third party detail. For example, if there is not a value in ReceiverAgentBIC, CTM evaluates the CustodianBIC value, and so on. A fund account number at one of the following: Instructing party s global custodian or subcustodian Executing broker s account number at its clearing agent or clearing broker BANKUS33 Manual enrichment Settling custodian or bank BIC is BANKUS Fund account number is CashAccountNo IdentificationOfASecurity An account where cash settles at one of the following: Instructing party s global custodian, subcustodian, or local agent Executing broker s account number at its clearing agent or clearing broker Composite containing the following three elements: CountryCode NumberingAgencyCode SecurityCode DescriptionOfTheSecurity is an optional element Cash account number is US/01N GNMA 30YR US financial instrument as a 30- year Ginnie Mae bond with security code 01N Dual Enrichment Instruction Regardless of how you enrich your own trade components, CTM also provides the option to enrich your counterparty s settlement instructions on TradeDetails. Supplying counterparty settlement information is useful when your counterparty is not in the DTCC/CTM community. Enrichment of counterparty information is also known as dual instruction enrichment or counterparty SSI enrichment (even when enriching an executing broker s BDIs). CTM always uses the self supplied values on trade components before evaluating counterparty elements. For example, suppose you are an instructing party and on your TradeDetail you supply PartySettlement/AlertCountryCode=USA and your (executing broker) counterparty supplies PartySettlement/AlertCountryCode=JPY in its TradeDetail. CTM maps your USA value for the AlertCountryCode element. Note CTM allows dual enrichment on TradeDetails only and requires a subscription. Dual Enrichment of TradeDetails ALERT Instructions Table 1.6 lists the TradeDetail values you can supply to enrich your counterpartyʹs trade side. Table 1.6 Dual Enrichment of ALERT Fields XPath Element Description Executing brokers supply their instructing party s information in the following TradeDetail elements IPSettlement/AccountID Supply the instructing party s account identifier in the ALERT SSI for the submitted TradeDetail. Creating Settlement Instructions and Notifications 9

10 Table 1.6 Dual Enrichment of ALERT Fields (Continued) XPath Element PartySettlement/PartyIdentifier1 PartySettlement/Settlement InstructionsSourceIndicator PartySettlement/AlertCountryCode PartySettlement/AlertMethodType PartySettlement/AlertSecurityType Description Supply INST to indicate that you are submitting ALERT keys for the instructing party s trade side. CTM allows two instances of the PartySettlement composite, one for each trade party (INST and EXEC) to identify the trade side being enriched. Supply ALRT to direct CTM to automatically enrich the instructing party s trade side with its ALERT SSIs. Supply the instructing party s country in its ALERT SSI. Supply the instructing party manner in which a settlement takes place for a given security, such as a national central securities depository. Supply the instructing party s type of security settling with the chosen ALERT method, such as an equity or corporate bond. Instructing parties supply their executing broker s information in the following TradeDetail elements. EBSettlement/AccountReference EBSettlement/AccountID 2 PartySettlement/PartyIdentifier 1 PartySettlement/Settlement InstructionsSourceIndicator PartySettlement/AlertCountryCode PartySettlement/AlertMethodType PartySettlement/AlertSecurityType PartySettlement/Alert SettlementModelName Supply the executing broker s BIA in its ALERT BDI for the TradeDetail. Supply the same value as the instructing party s IPSettlement/AccountID element. Supply EXEC to indicate that you are submitting ALERT keys for the executing broker s trade side. CTM allows two instances of the PartySettlement composite, one for each trade party (INST and EXEC) to identify the trade side being enriched. Supply ALRT to direct CTM to automatically enrich the executing broker s trade side with its ALERT BDIs. Supply the executing broker s country in its ALERT BDIs. Supply the executing broker s manner in which a settlement takes place for a given security, such as a national central securities depository. Supply the executing broker s type of security settling with the chosen ALERT method, such as an equity or corporate bond. The model name that the executing broker maintains in its ALERT BDI. 1 Regardless of the value you supply in the SettlementInstructionsSourceIndicator, all remaining elements within the PartySettlement composite (down to the PlaceOfSafekeeping composite) pertain to the value in the PartyIdentifier element. 2 Even though the AccountID element is in the EBSettlement composite, CTM requires the investment manager s value to resolve the prior AccountReference value (if omitted). See Executing Broker Enrichment Trade Component Fields for more information about how CTM handles the executing broker s BIA look-up when one or both elements in the EBSettlement composite are missing. Dual Enrichment of TradeDetails Manual Instructions All of the elements in the SettlementInstructions composite pertain to manual enrichment. Table 1.7 shows the TradeDetail elements you can supply values in to manually enrich your counterparty s trade side. Table 1.7 Dual Enrichment of Manually-Supplied Fields XPath Element Description Executing brokers supply their instructing party s information in the following TradeDetail elements PartySettlement/PartyIdentifier PartySettlement/Settlement InstructionsSourceIndicator Supply INST to indicate that you are supplying instructions for the instructing party s trade side. Supply MANI to indicate that you are manually supplying instructions for the instructing party s trade side. Instructing parties supply their executing broker s information in the following TradeDetail elements. PartySettlement/PartyIdentifier PartySettlement/Settlement InstructionsSourceIndicator Supply EXEC to indicate that you are manually supplying instructions for the executing broker s trade side. Supply MANI to indicate that you are manually supplying instructions for the executing broker s trade side. Creating Settlement Instructions and Notifications 10

11 For dual enrichment, all of the remaining (non-alert) elements in the PartySettlement composite pertain to the party you supply in the PartyIdentifier element. Sourcing of Settlement Data CTM sources settlement data uniquely for each trade side. Regardless of trade side (instructing party or executing broker), CTM settlement information from the trade side s TradeDetails always overrides any TradeLevel values. Error Handling CTM generates synchronous and asynchronous error messages for any errors during settlement enrichment. Asynchronous errors during enrichment do not indicate a problem with the trade message, but with the settlement instructions. CTM applies a WARNING (WARN) asynchronous error. Creating Settlement Instructions and Notifications 11

12 2. SWIFT MT541/543 MESSAGE Introduction This chapter describes the SWIFT MT541/543 message layout and includes an example SWIFT MT541 message. Overview CTM maps and constructs a SWIFT MT541/543 message (SWIFT MT541/543 Layout) based on information supplied by both trade sides using the rules described in this chapter. The data included in the CSV file conforms to SWIFT formatting, data length, and optional/mandatory rules and specifications. SWIFT MT541/543 Layout The following table describes the contents of the MT541/543 column headers in the SWIFT MT541/543 Specification and the equivalent CSV File Specification: The shaded rows indicate MT541/543 sequences. The shaded rows with an arrow ( ) to indicate an MT541/543 subsequence. Table 2.1 SWIFT MT541/543 Specification Column Header Key Column Header SWIFT Tag /Qualifier & Line # SWIFT Field Name/ Format/Example Description The information in this column identifies the generic field label in a SWIFT message separated by a line return. SWIFT Tag The two-digit SWIFT tag followed by a letter marking the start of a field. The letter indicates the format option for the field. A lowercase letter typically indicates that CTM provides more than one SWIFT option. SWIFT options are described in the SWIFT Field Name /Format/Example column and the Source of Field Data column. Qualifier A four-letter SWIFT value that represents the information a field contains. For example, in Mandatory Subsequence E1 Settlement Parties: o o DEAG represents the delivery agent in the :95a::BUYR or SELL Party field. REAG represents the receiving agent in the :95a::BUYR or SELL Party field. Line No. Line No. maps to the SWIFT message line number in the SWIFT publication Category 5 Securities Markets For Standard MT November 2016 Message Reference Guide: Volume 2 (MT519-MT543). The information in this column contains the following on separate lines in the table cell: SWIFT Field Name SWIFT field name. Format The SWIFT format, separated by a slash (/). Also shown is subfield formatting, with optional subfields in brackets [ ]. The names of the subfields are in parentheses following the formatting specification. Example An example of the field tag, qualifier (when applicable), and an example value. For the HDR fields, the example also includes its exact location in the header line. SWIFT MT541/543 Message 12

13 Table 2.1 SWIFT MT541/543 Specification Column Header Key (continued) Column Header SWIFT Codes/M-O Description When applicable, the information in this column identifies all SWIFT code values CTM supports. SWIFT allows one code per field. Indicates that a field contains a dynamic value, such as a date, account identifier, party value, or other unique information in an instruction. Superscript (x) A superscript number such as 1 indicates that the corresponding table footnote contains an extensive list of supported code values. M/O Indicates whether SWIFT requires a value in the field derived from CTM: o o Mandatory While some composites are mandatory, elements within the composites can be optional, such as CountryCode within the IdentificationOfASecurity composite. DTCC maps the composite information to the Identification of the Financial Instrument in Sequence B Trade Details. Start () and End () blocks are mandatory. CTM supports optional sequences. Within optional sequences, there are mandatory fields, such as the Party (Account with Institution) field insubsequence E2 Cash Parties. Any missing or incorrectly formatted information in a mandatory SWIFT field results in settlement processing failure. For more information, see Error Handling on page 11 AG/ CTM Mapping Source/Note The information in this column indicates whether CTM derives data for the MT541/543 from one of the following two sources: AG Automatically generated from CTM during the trade cycle and settlement process. Examples are the CTMTradeDetailID and CTMTradeSideId values. TradeDetail element from one of the parties according to the rules, if any, described for the element. In some cases, for executing broker values, CTM derives information from the TradeLevel; however, all information pertains to the settling allocation. The information in this column indicates the following: Source The name of the element in the TradeDetail that CTM uses to derive or map data for the third party detail. If the element is not unique in the message, the XPath is included. For example, PartyValue is an element in the InstructingParty and ExecutingBroker composites. When used for mapping, the PartyValue XPath is: o o InstructingParty/PartyValue ExecutingBroker/PartyValue Note Notes include whether CTM maps the instructing party or executing broker value and other rules or validations CTM applies. The following table provides the SWIFT MT541/543 specification. It also contains only fields applicable to settlement according to SWIFT requirements. Table 2.2 SWIFT MT541/543 Specification SWIFT Tag/ Qualifier & Line # SWIFT Field Name/Format/Example SWIFT Codes/M-0 AG/ CTM Mapping Source/Note Basic Header Block (Block 1) HDR HDR Name: Block Identifier Format: String Example: 1 1{1:F01OMGOUS30AXXX } Name: Application Identifier Format: String Example: F 1{1:F01OMGOUS30AX XX } AG Value is always 1. AG Value is always F to indicate a Financial Application (FIN) message. SWIFT MT541/543 Message 13

14 Table 2.2 SWIFT MT541/543 Specification (continued) SWIFT Tag/ Qualifier & Line # SWIFT Field Name/Format/Example SWIFT Codes/M-0 AG/ CTM Mapping Source/Note HDR HDR HDR HDR Name: Service Identifier Format: String Example: 01 1{1:F01OMGOUS30AXXX } Name: LT (Logical Terminal) Identifier Format: String Example: OMGOUS30AXXX 1{1:F01OMGOUS30AX XX } Name: Session Number Format: 4!n Example: 0001{1:F01OMGOUS30AXX X } Name: Sequence Number Format: 6!n (String) Example: } 1{1:F01OMGOUS30AXX X } Application Header Block (Block 2) HDR HDR HDR Name: Block Identifier Format: String Example: 2 {2:I541BANKUS33N}{4: Name: Input/Output Identifier Format: String Example: I {2:I541BANKUS33N}{4: Name: Message Type Format: 3!n Example: 541 {2:I541BANKUS33N}{4: AG Value is always 01 to indicate a FIN user-to-user message service. AG Value is always the DTCC BIC and branch code. AG FIN session number. AG Input session sequence number. AG Value is always 2. AG Value is always I (Input) to SWIFT. Source: CTM maps the BuySellIndicator as follows: If the SWIFT represents a buy side and: o o BuySellIndicator=SELL, Message Type=543 BuySellIndicator=BUYI, Message Type=541 If the SWIFT message represents a sell side and: o o BuySellIndicator=SELL, Message Type=541 BuySellIndicator=BUYI, Message HDR HDR Name: Receiver s Address Format: 12x Example: BANKUS33 {2:I541BANKUS33N}{4: Name: Message Priority Format: 1x (String) Example: N} {2:I541BANKUS33N}{4: Source: CTM requires that you or your counterparty supply a value in at least one of the following TradeDetail elements: ReceiverAgentBIC CustodianBIC SubAgentBIC To determine the SWIFT message receiver s address, CTM maps the XML in the order listed. For example, if you supply a value in ReceiverAgentBIC, CTM maps that value. If there is no value in ReceiverAgentBIC, CTM maps the CustodianBIC value, and so on. AG Value is always N (Normal). SWIFT MT541/543 Message 14

15 Table 2.2 SWIFT MT541/543 Specification (continued) SWIFT Tag/ Qualifier & Line # SWIFT Field Name/Format/Example SWIFT Codes/M-0 AG/ CTM Mapping Source/Note Text Block (Block 4) HDR Name: Text Block Format: String Example: 4: {2:I541BANKUS33N}{4: Mandatory Sequence A General Information Line No SEME Line No. 2 Start of Block / Option R 16c Example: ::GENL Name: Sender s Reference Format: :4!c//16x (Qualifier) (Reference) Example: :20C::SEME// AG Value is always 4 for a FIN message. Mandatory AG or Source: Depending on the FunctionOfTheMessage: NEWM CTM generates the Sender s Reference CANC CTM maps the CTMTradeDetailID when the FunctionOfTheMessage in the TradeDetail is CANC (:23G:CANC). 23G Line No. 3 Name: Function of the Message Format: 4!c[/4!c] (Function) [Subfunction] Example: :23G:NEWM NEWM CANC COPY Mandatory Source: FunctionOfTheMessage NEWM Directs the custodian to process the settlement instruction. CANC Directs the custodian to cancel a previous settlement instruction. COPY Subfunction that serves as a settlement notification for interested parties. 98C PREP Line No. 4 99B TOSE Line No. 5 99B SETT Line No. 5 Name: Preparation Date/Time Format: :4!c//8!n6!n (Qualifier) (Date) (Time) Example: :98C::PREP// Name: Total of Linked Settlement Instructions Format: :4!c//3!n Example: :99B::TOSE//3 Name: Current Settlement Instruction Number Format: :4!c//3!n Example: :99B::SETT//2 Subsequence A1 Linkages See Sequence A Qualifier 23G Note: CTM maps this subsequence only when Function of the Message=CANC Line No. 6 20C PREV Line No. 9 Line No. 11 Line No. 6 Start of Block / Option R 16c Example: ::LINK Name: Previous Reference Format: :4!c//16x (Qualifier) (Reference) Example: :20C::PREV// End of Block / Option S 16c Example: ::LINK Start of Block / Option R 16c Example: ::LINK Mandatory AG AG AG AG or CTM generates as YYYYMMDDHHMMSS using the time zone set up by the instructing party. Source: PartySettlement Note: CTM only maps this element for omnibus block settlements with dependent allocations. Source: PartySettlement Note: CTM only maps this element if :99B::TOSE contains a value. The reference pair remains constant through any exception processing, such as a trade cancellation. CTMTradeDetailID SWIFT MT541/543 Message 15

16 Table 2.2 SWIFT MT541/543 Specification (continued) SWIFT Tag/ Qualifier & Line # SWIFT Field Name/Format/Example SWIFT Codes/M-0 AG/ CTM Mapping Source/Note 20C RELA Line No. 9 Name: Related Reference Format: :4!c//16x (Qualifier) (Reference) Example: :20C::RELA//8933 Mandatory Source: One or both of the following: References/ReferenceType References/ReferenceValue Note: CTM only maps the References composite for pooled locations that share a common reference such as block settlement trades. Line No. 11 End of Block / Option S 16c Example: ::LINK Line No. 6 Start of Block / Option R 16c Example: ::LINK 20C POOL Line No. 9 Name: Pool Related Reference Format: :4!c//16x (Qualifier) (Reference) Example: :20C::POOL//8931 Mandatory Source: One or both of the following: References/ReferenceType References/ReferenceValue Note: CTM only maps the References composite for pooled allocations that share a common reference such as block settlement trades. Line No. 11 End of Block / Option S 16c Example: ::LINK Line No. 12 End of Block / Option S 16c Example: ::GENL Mandatory Sequence B Trade Details Start of Block / Option R 16c Line No. 13 Example: ::TRADDET 94a CLEA Line No. 14 Name: Place of Clearing Format Option H: :4!c//4!a2!a2!c[3!c (Qualifier) (Identifier Code) Example Option H:94H::CLEA//OMGOUS33 Source: PlaceOfClearing Note: CTM maps the BIC, which represents the place of clearing for the allocation, such as a central counterparty. 94a TRAD Line No. 14 Name: Place of Trade Format Option B: :4!c/[8c]/4!c[/30x] (Qualifier) (Data Source Scheme) (Place Code) [Narrative] Example Option B: :94B::TRAD//EXCH/US EXCH OTCO VARI Source: One or both of the following: PlaceOfTrade/PlaceCode PlaceOfTrade/PlaceNarrative 98a SETT Line No. 15 Name: Settlement Date Format Option A: :4!c//8!n (Qualifier) (Date) Example Option A: :98A::SETT// Mandatory Source: SettlementDate 98a TRAD Line No. 15 Name: Trade Date Format Option A: :4!c//8!n (Qualifier) (Date) Example Option A: :98A::TRAD// Source: TradeDateTime Note: CTM only maps the date portion(yyyymmdd) of TradeDateTime. SWIFT MT541/543 Message 16

17 Table 2.2 SWIFT MT541/543 Specification (continued) SWIFT Tag/ Qualifier & Line # SWIFT Field Name/Format/Example SWIFT Codes/M-0 AG/ CTM Mapping Source/Note 90a DEAL Line No. 16 Name: Deal Price Format Option A: :4!c//4!c/15d (Qualifier) (Percentage Type Code) (Price) Example Option A: :90A::DEAL//PRCT/10 Format Option B: :4!c//4!c/3!a15d (Qualifier) (Amount Type Code) (Currency Code) (Price) Example Option B: :90B::DEAL//ACTU/ARS100 PRCT ACTU Source: SecurityType and one or both of the following: DealPrice/CurrencyCode DealPrice/Amount Note: CTM maps the options a follows: If CurrencyCode is blank, then CTM uses format Option A with PRCT (Percentage Type code). If CurrencyCode is not blank, then QuantityTypeCode=FAMT, and SecurityTypeGroup=DBT, CTM uses format A with PRCT (Percentage code). If CurrencyCode is not blank and SecurityTypeGroup=EQT, then CTM uses format Option B with ACTU (Actual Amount). 99A DAAC Line No. 17 Name: Number of Days Accrued Format: :4!c//[N]3!n (Qualifier) (Sign) (Number) Example: :99A::DAAC//9 Source: NumberOfDaysAccrued Note: CTM maps this element for fixed income (debt) instruments only. To map NumberOfDaysAccrued, CTM requires a positive value and does not include Sign. 35B Line No. 18 Name: Identification of the Financial Instrument Mandatory Source: A combination of the following elements in the IdentificationOfASecurity composite: Format: [ISIN1!e12!c] Identification of Security [4*35x] Description of Security Example: :35B:/US/01N GNMA 30YR CountryCode NumberingAgencyCode SecurityCode DescriptionOfTheSecurity Note: When ISIN is supplied in the TradeDetail, CTM includes a space between the ISIN and the SecurityCode. Subsequence B1 Financial Instrument Attributes Note: CTM only populates Subsequence B1 block if you supply a value in Current Factor field or Pool Number field and the PSET is not Germany. Line No. 19 Start of Block / Option R 16c Example: ::FIA 92A CUFC Line No. 25 Name: Rate (Current Factor) Format Option A: :4!c//[N]15d (Qualifier) (Sign) (Rate) Example Option A: :92A:://CUFC/14, Source: One or both of the following: CurrentFactor/Sign CurrentFactor/Amount 98A MATU Line No. 24 Name: Maturity Date Format: :4!c//8!n Example: :98A::MATU// Source: MaturityDate Note: CTM maps this element for fixed income (debt) instruments only. 92A INTR Line No. 25 Name: Coupon Rate Format: :4!c//[N]15d (Qualifier) (Sign) (Rate) Example: :92A::INTR//5,4 Source: CouponRate Note: CTM maps this element for fixed income (debt) instruments only. 92A MATR Line No. 25 Name: Yield to Maturity Rate Format: :4!c//[N]9d (Qualifier) (Rate) Example: :92A::YTMR//5,3 Source: Yield Type Note: CTM maps this element for fixed income (debt) instruments only when TradeLevelCommonValues/YieldType=MATR. 13a POOL Line No. 26 Name: Number Identification (Pool Number) Format Option B: :4!c/[8c]/30x (Qualifier) (Data Source Scheme) (Data Source Scheme) (Number) Example Option B: :13B::POOL//1256 Source: PoolNumber Note: CTM maps the issuer s identifier for a mortgage-backed security supplied on the TradeDetail. SWIFT MT541/543 Message 17

18 Table 2.2 SWIFT MT541/543 Specification (continued) SWIFT Tag/ Qualifier & Line # SWIFT Field Name/Format/Example SWIFT Codes/M-0 AG/ CTM Mapping Source/Note Line No. 32 End of Block / Option S 16c Example: ::FIA 22F TTCO Line No. 33 Name: Indicator Format: :4!c/[8c]/4!c (Qualifier) (Data Source Scheme) (Indicator) Example: :22F::TTCO//5,4 1 Source: TradeTransactionConditionIndicator Note: CTM repeats :22F:TTCO for each occurrence in the ISRTLCommonValues composite using a different indicator for each instance. 11A DENO Line No. 34 Name: Currency Format: :4!c//3!a (Qualifier) (Currency Code) Example: :11A::FXIS//USD FXIB FXIS Source: FXDealCurrencyCode Note: CTM maps this element to instruct the recipient of a settlement instruction to execute an FX deal. 25D MTCH Line No. 35 Name: Status Format: :4!c/[8c]/4!c (Qualifier) (Data Source Scheme) (Status Code) Example: :25DA::MTCH//MACH MACH AG Note: CTM does not map this element for block settlement trades where the following are true: BlockSettlementIndicator=Y SettlementTransactionConditionIndicator=BLCH 70E SPRO Line No. 36 Line No. 37 Name: Settlement Instruction Processing Narrative Format: :4!c//10*35x (Qualifier) (Narrative) Example: :70E::SPRO//Counterparty covers registration cost. End of Block / Option S 16c Example: :TRADDET Repetitive Mandatory Sequence C Financial Instrument/Account Line No B SETT Line No B SETT Line No a CASH Line No. 43 Start of Block / Option R 16c / ::FIAC Name: Quantity of Financial Instrument Format: :4!c//4!c/15d Examples: :36B::SETT//FAMT/123,50 :36B::SETT//UNIT/1000, Name: Quantity of Financial Instrument Format: :4!c//4!c/15d (Qualifier) (Quantity Type Code) (Quantity) Example: :36B::SETT//AMOR/2000 Name: Account (Cash Account) Format Option A: :4!c//35x (Qualifier) (Account Number) Example Option A: :97A::CASH// Format Option E: :4!c//34x (Qualifier) (International Bank Account Number) Example Option E: :97A::CASH//IBAN FAMT UNIT Mandatory AMOR Source: AdditionalText Note: CTM maps the element to supply additional information to an instruction. Source: QuantityAllocated Note: CTM maps the number of shares, units, face amount, or other indicator to describe the settling allocation. CTM allows up to two 36B::SETT field instances. If it maps two instances, CTM requires that one instance use the FAMT code and the other instance use the UNIT code. Source: CurrentFaceValue Note: For fixed income (debt) instruments, CTM maps, for example, the amount representing the current amortized face amount of a bond. Source: CashAccountNo Note: CTM maps the cash account number, including the option to use an International Bank Account Number (IBAN) for the settling allocation. SWIFT MT541/543 Message 18

19 Table 2.2 SWIFT MT541/543 Specification (continued) SWIFT Tag/ Qualifier & Line # SWIFT Field Name/Format/Example SWIFT Codes/M-0 AG/ CTM Mapping Source/Note 94a SAFE Line No. 44 Line No. 52 Name: Place (Place of Safekeeping) Format Option C: :4!c//2!a (Qualifier) (Country) Example Option C: :94C::SAFE//US Format Option F: :4!c//4!c/4!a2!a2c [3!c] (Qualifier) (Place) (BIC/BEI) Example Option F: :94F::SAFE//DTCC End of Block / Option S 16c / ::FIAC Repetitive Mandatory Sequence E Settlement Details Note: SWIFT requires at least one instance of Tag :22F in Sequence E. Line No F STCO Line No. 63 Start of Block / Option R 16c / ::SEET Name: Indicator (Settlement Transaction Condition) Format: :4!c/[8c]/4!c (Qualifier) (Data Source Scheme) (Indicator) Example: :22F::STCO/CLEN 2 Source: PlaceOfSafekeepingValue Source: One of the following TradeDetailData/SettlementTransactionConditionIndicator TradeLevelInformation/TradeTransactionConditionIndicator Note: CTM maps this element only when one of the following is true: TradeDetail contains a value in the SettlementTransactionConditionIndicator element. TradeDetail contains CLEN or DIRT in the TradeTransactionConditionIndicator. SWIFT tag :95C::PSET must use Option C if STCO SWIFT code is PHYS or CTM fails validation. 22F SETR Name: Indicator (Type of Settlement Transaction) 3 Source: TypeOfTransactionIndicator Note: CTM maps NETT for allocations that are eligible for netting. Line No. 63 Format: :4!c/[8c]/4!c (Qualifier) (Data Source Scheme) (Indicator) Example: :22F::SETR/TRAD 22F STAM Line No. 63 Name: Indicator (Stamp Duty) Format: :4!c/[8c]/4!c (Qualifier) (Data Source Scheme) (Indicator) Example: :22F::STAM/CRST/GBT3 4 Source: SettlementTransactionConditionIndicator Note: CTM maps REGT only once, using the first code in the TradeDetail. 22F RTGS Line No. 63 Name: Indicator (Securities Real-Time Gross Settlement) Format: :4!c/[8c]/4!c (Qualifier) (Data Source Scheme) (Indicator) Example: :22F::RTGS/NRTG NRTG YRTG Source: SettlementTransactionConditionIndicator Note: CTM maps RTGS only once, using the first code in the TradeDetail. 22F REGT Line No. 63 Name: Indicator (Registration) Format: :4!c/[8c]/4!c (Qualifier) (Data Source Scheme) (Indicator) Example: :22F::REGT/NREG NREG YREG Source: SettlementTransactionConditionIndicator Note: CTM maps REGT only once, using the first code in the TradeDetail. 22F BENE Line No. 63 Name: Indicator (Beneficial Ownership) Format: :4!c/[8c]/4!c (Qualifier) (Data Source Scheme) (Indicator) Example: :22F::BENE/NBEN NBEN YBEN Source: SettlementTransactionConditionIndicator Note: CTM maps BENE only once, using the first code in the TradeDetail. SWIFT MT541/543 Message 19

20 Table 2.2 SWIFT MT541/543 Specification (continued) SWIFT Tag/ Qualifier & Line # 22F CASY Line No F FXCX Line No F BLOC Line No F REST Line No F SETS Line No F NETT Line No F CCPT Line No F LEOG Line No F COLE Line No. 63 SWIFT Field Name/Format/Example Name: Indicator (Cash Settlement System) Format: :4!c/[8c]/4!c (Qualifier) (Data Source Scheme) (Indicator) Example: :22F::CASY/NETS Name: Indicator (Foreign Exchange Cancellation) Format: :4!c/[8c]/4!c (Qualifier) (Data Source Scheme) (Indicator) Example: :22F::FXCX/FXYE Name: Indicator (Foreign Exchange Cancellation) Format: :4!c/[8c]/4!c (Qualifier) (Data Source Scheme) (Indicator) Example: :22F::BLOC/BLCH Name: Indicator (Restrictions) Format: :4!c/[8c]/4!c (Qualifier) (Data Source Scheme) (Indicator) Example: :22F::REST/NRST Name: Indicator (Settlement System/Method) Format: :4!c/[8c]/4!c (Qualifier) (Data Source Scheme) (Indicator) Example: :22F::SETS/YSET Name: Indicator (Netting Eligibility) Format: :4!c/[8c]/4!c (Qualifier) (Data Source Scheme) (Indicator) Example: :22F::NETT/YNET Name: Indicator (Central Counter Party Eligibility) Format: :4!c/[8c]/4!c (Qualifier) (Data Source Scheme) (Indicator) Example: :22F::CCPT/YCCP Name: Indicator (Letter of Guarantee) Format: :4!c/[8c]/4!c (Qualifier) (DataSource Scheme) (Indicator) Example: :22F::LEOG/NLEG Name: Indicator (Collateral Pool) Format: :4!c/[8c]/4!c (Qualifier) (Data Source Scheme) (Indicator) Example: :22F::COLE/COLA SWIFT Codes/M-0 GROS NETS FXYE FXNO BLCH BLPA 144A NRST RSTR SETS YSET NNET YNET NCCP YCCP NLEG YLEG COLA COLN AG/ CTM Mapping Source/Note Repetitive Mandatory Subsequence E1 Settlement Parties Note: CTM requires PartyValue in the TradeDetail to format each party in Subsequence E1. Line No. 64 Start of Block / Option R 16c / ::SETPRTY Source: SettlementTransactionConditionIndicator Note: CTM maps CASY only once, using the first code in the TradeDetail. Source: SettlementTransactionConditionIndicator Note: CTM maps this element only if Function of the Message in Sequence A is CANC:23G::CANC. Source: SettlementTransactionConditionIndicator Note: CTM maps BLOC only once, using the first code in the TradeDetail. Source: SettlementTransactionConditionIndicator Note: CTM maps REST only once, using the first code in the TradeDetail. Source: SettlementTransactionConditionIndicator Note: CTM maps SETS only once, using the first code in the TradeDetail. Source: SettlementTransactionConditionIndicator Note: CTM maps NETT only once, using the first code in the TradeDetail. Source: SettlementTransactionConditionIndicator Note: CTM maps CCPT only once, using the first code in the TradeDetail. Source: SettlementTransactionConditionIndicator Note: CTM maps LEOG only once, using the first code in the TradeDetail. Source: SettlementTransactionConditionIndicator Note: CTM maps COLE only once, using the first code in the TradeDetail. SWIFT MT541/543 Message 20

21 Table 2.2 SWIFT MT541/543 Specification (continued) SWIFT Tag/ Qualifier & Line # SWIFT Field Name/Format/Example SWIFT Codes/M-0 AG/ CTM Mapping Source/Note 95a BUYR SELL Line No. 65 Name: Party Format Option P: :4!c//4!a2!a2!c[3!c] (Qualifier) (BIC/BEI) Example Option P: :95P::BUYR//ABCABCABXXX Format Option Q: :4!c//4*35x (Qualifier) (Name & Address) Example Option Q: :95Q::BUYR//ABC BuyerA,100 Buyer Lane, NY, NY Format Option R: :4!c/8c/34x (Qualifier) (Data Source Scheme) (Proprietary Code) Example Option R: :95R::BUYR/OMGUSXXYZ Format Option L: 4!c//18!c2!n (Qualifier)(Legal Entity Identifier) Mandatory HDR Source: One of the following, in order: 1. ExecutingBroker/SettlementInstructions/ InstitutionBIC 2. ExecutingBroker/PartyValue (CTM BIC value) 3. ExecutingBroker/OrgName Note: If PSET BIC is FRNYUS33XXX (US FED Wire) or DTCYUS33XXX (DTC) then: 1. ExecutingBroker/SettlementInstructions/INSTor BrokerID 2. ExecutingBroker/SettlementInstructions/ID3 3. As above, if neither is populated. CTM typically maps the information used in the following options: Option P If PartyValue is a valid BIC, CTM uses Option P. Option R CTM uses Option R with proprietary code, which is an internal identifier used by depositories. Option L- CTM uses Option L when LEI is provided in either: Example Option L: :95L::ALTE//ABCDEFGHIJKLMQR12 ISRExecutingBroker/PartySettlement/Settlement Instructions/LEI or ISRTradeLevel/TLEBSettlement/SettlementInstructions/LEI Note: If PSET BIC is IBRCESMMXXX 5 then: Check if one of the following in order: 1. ISRExecutingBroker/ID2 2. TLEBSettlement/ID2 field is populated with 11 characters (COD) or 9 characters (NIF) If yes, map to::95r::sell/ibrc/codornif or ::95R::BUYR/IBRC/CODorNIF Otherwise, use existing logic to identify the broker through the Institution Broker BIC. End of Block / Option S 16c / ::SETPRTY Line No. 70 Start of Block / Option R 16c / ::SETPRTY Line No a DECU RECU Line No. 65 Name: Party Format Option P: :4!c//4!a2!a2!c[3!c] (Qualifier) (BIC/BEI) Example Option P: :95P::DECU//ABCABCABCXX Format Option Q: :4!c//4*35x (Qualifier) (Name & Address) Example Option Q: :95Q::RECU//Custodian A,200Custodian Lane, NY, NY Source: One of the following: CustodianBIC CustodianName1 CustodianName2 Note: CTM maps the qualifier as follows: If MT541=DECU If MT543=RECU Option P If CustodianBIC is a valid BIC, CTM uses CustodianBIC SWIFT MT541/543 Message 21

22 Table 2.2 SWIFT MT541/543 Specification (continued) SWIFT Tag/ Qualifier & Line # SWIFT Field Name/Format/Example SWIFT Codes/M-0 AG/ CTM Mapping Source/Note 97a SAFE Line No. 66 Name: Safekeeping Account Format Option A: :4!c//35x (Qualifier) (Account Number) Example Option A: :97A::SAFE//12345 Source: SubAccountNo Note: CTM maps the SubAccountNo for the settling allocation as follows: Instructing Party If the InstructingParty is the buyer, CTM derives the SettlementInstructions/SubAccountNo where PartySettlement/ PartyIdentifier=INST. Executing Broker If the ExecutingBroker is the buyer, CTM derives the SettlementInstructions/SubAccountNo where PartySettlement/ PartyIdentifier=EXEC. End of Block / Option S 16c / ::SETPRTY Line No. 70 Start of Block / Option R 16c / ::SETPRTY Line No a DEAG REAG Line No. 65 Name: Party Format Option P: :4!c//4!a2!a2!c[3!c] (Qualifier) (BIC/BEI) Example Option P: :95P::DEAG//ABCABCABCXX Mandatory Source: One of the following: SubAgentBIC SubAgentName1 and SubAgentAddress1 SubAgentName2 and SubAgentAddress2 ID1 Format Option Q: :4!c//4*35x (Qualifier) (Name & Address) Example Option Q: :95Q::DEAG//Custodian A, 300 Subagent Lane, NY, NY Note: CTM maps the qualifier according to local market rules as follows: If MT541=DEAG If MT543=REAG CTM maps the options as follows: Format Option R: :4!c/8c/34x (Qualifier) (Data Source Scheme) (Proprietary Code) Example Option R: :95R::REAG//OMGUSAXXX Option P and Option Q CTM interprets a country code in the PSET element as a physical settlement and uses Option P or Q. CTM maps the SubAgentBIC to the BIC. Option Q CTM maps the following name/address pairs: SubAgentName1 and SubAgentAddress1 SubAgentName2 and SubAgentAddress2 Option R If the PSET value is FRNYUS33XXX or DTCYUS33XXX, CTM maps ID1. 97a SAFE Line No. 66 Name: Safekeeping Account Format: :4!C//35x (Qualifier) (Account Number) Example: :97A::SAFE//12345 Source: One or both of the following: ID1 ID2 Note: CTM maps the SubAccountNo account number for the settling allocation as follows: Instructing Party If the InstructingParty is the buyer, CTM derives the SettlementInstructions/SubAccountNo where PartySettlement/ PartyIdentifier=INST. Executing Broker If the ExecutingBroker is the buyer, CTM derives the SettlementInstructions/SubAccountNo where PartySettlement/ PartyIdentifier=EXEC. Line No. 70 Line No. 64 End of Block / Option S 16c / ::SETPRTY Start of Block / Option R 16c / ::SETPRTY SWIFT MT541/543 Message 22

23 Table 2.2 SWIFT MT541/543 Specification (continued) SWIFT Tag/ Qualifier & Line # SWIFT Field Name/Format/Example SWIFT Codes/M-0 AG/ CTM Mapping Source/Note 95a DEI1 REI1 Line No. 65 Name: Party Format Option P: :4!c//4!a2!a2!c[3!c] (Qualifier) (BIC/BEI) Example Option P: :95P::DEI1//ABCABCABCXX Format Option Q: :4!c//4*35x (Qualifier) (Name & Address) Example Option Q: :95Q::REI1//Custodian A, 400 Correspondent Lane, NY, NY Source: One of the following from the InstructingParty trade side: CorrespBIC CorrespName1 and CorrespName2 Note: Used by CTM only when the instructing party uses an intermediary and SettlementInstructions/Relationship=C (Correspondent) when the PartyIdentifier=INST. CTM maps the qualifier as follows: If MT541=DEI1 If MT543=REI1 Option P If the CorrespBIC is valid, CTM uses Option P. 97a SAFE Line No. 66 Name: Safekeeping Account Format: :4!c//35x (Qualifier) (Account Number) Example: :97A::SAFE//12345 Source: CorrespSecAccountNo Note: CTM maps the CorrespSec AccountNo account number for the settling allocation as follows: Instructing Party If the InstructingParty is the buyer, CTM derives the Settlement Instructions/ CorrespSecAccountNo where PartySettlement/PartyIdentifier=INST. Executing Broker If the ExecutingBroker is the buyer, CTM derives the Settlement Instructions/ CorrespSecAccountNo where PartySettlement/PartyIdentifier=EXEC. End of Block / Option S 16c / ::SETPRTY Line No. 70 Start of Block / Option R 16c / ::SETPRTY Line No a PSET Line No. 65 Name: Party Format Option C: :4!c//2!a (Qualifier) (Country Code) Example Option C: :95C::PSET//US Format Option P: :4!c//4!a2!a2!c[3!c] (Qualifier) (BIC/BEI) Example Option P: :95P::PSET//ABCABCABCXX Source: PSET from the instructing party trade side where the PartySettlement/ PartyIdentifier=INST. Note: CTM maps the options as follows: Option C If PSET length is two (2) characters, CTM uses Option C. CTM requires that the SWIFT tag :95C::PSET use Option C if :22F::STCO SWIFT code is PHYS. Option P If PSET length is 8 (eight) or 11 (eleven) characters (padded), CTM uses Option P. Line No. 70 End of Block / Option S 16c / ::SETPRTY Subsequence E2 Cash Parties Notes: CTM only maps Subsequence E2 if Relationship=C (Custodian) in the TradeDetail and if the executing broker supplies a value in :95P/95Q:ACCW. Line No. 71 Start of Block / Option R 16c / ::CSHPRTY SWIFT MT541/543 Message 23

24 Table 2.2 SWIFT MT541/543 Specification (continued) SWIFT Tag/ Qualifier & Line # SWIFT Field Name/Format/Example SWIFT Codes/M-0 AG/ CTM Mapping Source/Note 95a ACCW Line No a CASH Line No. 73 Line No. 75 Name: Party (Account with Institution) Format Option P: :4!c//4!a2!a2!c[3!c] (Qualifier) (BIC/BEI) Example Option P: :95P::ACCW//ABCABCABCXX Format Option Q: :4!c//4*35x (Qualifier) (Name & Address) Example Option Q: :95Q::ACCW//Custodian A, Two Bank Lane, NY, NY Name: Cash Account Format Option A: :4!c//35x (Qualifier) (Account Number) Example Option A: :97A::CASH// Format Option E: :4!c//34x (Qualifier) (International Bank Account Number) Example Option E: :97A::CASH//IBAN Mandatory End of Block / Option S 16c / ::CSHPRTY Repetitive Mandatory Subsequence E3 Amounts Line No A ACRU Line No. 78 Line No. 81 Line No A CHAR Line No. 78 Line No. 81 Line No A COUN Line No. 78 Line No. 81 Start of Block / Option R 16c / ::AMT Name: Accrued Interest Amount Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::ACRU//KRW5000, End of Block / Option S 16c / ::AMT Start of Block / Option R 16c / ::AMT Name: Charges or Fees Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::CHAR//CAD40000, End of Block / Option S 16c / ::AMT Start of Block / Option R 16c / ::AMT Name: Country, National, Federal Tax Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::CHAR//GBR100, End of Block / Option S 16c / ::AMT Source: One of the following from the executing broker trade side where the PartySettlement/PartyIdentifier=EXEC: CorrespBIC CorrespName1 CorrespName2 Note: CTM maps the options as follows: Option C If CorrespBIC is valid and present, CTM uses Option P. Option Q If CorrespBIC is invalid or present, CTM uses Option P. Source: CorrespCashAccountNo from the executing broker trade side where the PartySettlement/PartyIdentifier=EXEC. Note: Used by CTM only when Relationship=C (Correspondent). CTM maps the cash account number, including the option to use an International Bank Account Number (IBAN), for the settling allocation. Source: AccruedInterestAmount/Sign, AccruedInterestAmount/CurrencyCode, AccruedInterestAmount/Amount Source: ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount Note: CTM maps only if ChargeTaxType= CHAR. Source: ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount Note: CTM maps only if ChargeTaxType=COUN. SWIFT MT541/543 Message 24

25 Table 2.2 SWIFT MT541/543 Specification (continued) SWIFT Tag/ Qualifier & Line # Line No A DEAL Line No. 78 Line No. 81 Line No A EXEC Line No. 78 Line No. 81 Line No A LADT Line No. 78 Line No. 81 Line No A LEVY Line No. 78 Line No. 81 Line No A LOCL Line No. 78 Line No. 81 Line No. 76 SWIFT Field Name/Format/Example Start of Block / Option R 16c / ::AMT Name: Trade Amount Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::DEAL//SEK100, End of Block / Option S 16c / ::AMT Start of Block / Option R 16c / ::AMT Name: Charges/Fees (Executing Broker) Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::EXEC//GBR10, End of Block / Option S 16c / ::AMT Start of Block / Option R 16c / ::AMT Name: Local Tax (country specific 1) Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::LADT//EUR4, End of Block / Option S 16c / ::AMT Start of Block / Option R 16c / ::AMT Name: Payment Levy Tax Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::LEVY//BRL153, End of Block / Option S 16c / ::AMT Start of Block / Option R 16c / ::AMT Name: Local Tax Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::LOCL//CNY15, End of Block / Option S 16c / ::AMT Start of Block / Option R 16c / ::AMT SWIFT Codes/M-0 Mandatory AG/ CTM Mapping Source/Note Source: TradeAmount/Sign, TradeAmount/CurrencyCode, TradeAmount/Amount Source: Commission/Sign, Commission/CurrencyCode, Commission/Amount Note: CTM maps only if ChargeTaxType=EXEC. Source: ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount Note: CTM maps only if ChargeTaxType= LADT. Source: ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount Note: CTM maps only if ChargeTaxType= LEVY. Source: ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount Note: CTM maps sum of the following ChargeTaxType elements: LOCL, LIDT, LOTE, and LYDT. Crested is non-existent. SWIFT MT541/543 Message 25

26 Table 2.2 SWIFT MT541/543 Specification (continued) SWIFT Tag/ Qualifier & Line # SWIFT Field Name/Format/Example SWIFT Codes/M-0 AG/ CTM Mapping Source/Note 19A LOCO Line No. 78 Name: Local Broker s Commission Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::LOCO//DKK15, Source: Commission/Sign, Commission/CurrencyCode, Commission/Amount Notes: CTM maps only if ChargeTaxType=LOCO. If a RSCH Commission Type is one of the broker commission codes on the CTM MAGR trade, it is mapped to 19A::LOCO//. This mapping remains in place until the weekend of November 17, 2018, which is when SWIFT begins support of the new 19A::RSCH qualifier. After that date, if RSCH is provided by the broker on a MAGR trade, it maps to :19A::RSCH//. End of Block / Option S 16c / ::AMT Line No. 81 Start of Block / Option R 16c / ::AMT Line No A OTHR Line No. 78 Name: Other Amount Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::OTHR//SEK15. Source: ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount Note: CTM maps only if ChargeTaxType=OTHR. End of Block / Option S 16c / ::AMT Line No. 81 Start of Block / Option R 16c / ::AMT Line No A OTHR Line No. 78 Name: Regulatory Amount Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::REGF//BRL15, Source: ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount Note: CTM maps only if ChargeTaxType=REGF. End of Block / Option S 16c / ::AMT Line No. 81 Start of Block / Option R 16c / ::AMT Line No A SETT Line No. 78 Name: Settlement Amount Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::SETT//GBR15, Mandatory Source: One of the following composites, in order: SettlementAmount/Sign, SettlementAmount/CurrencyCode, SettlementAmount/Amount, NetCashAmount/Sign, NetCashAmount/ CurrencyCode, NetCashAmount/Amount Note: If SettlementAmount exists in the TradeDetail, CTM maps it; otherwise, CTM maps NetCashAmount. End of Block / Option S 16c / ::AMT Line No. 81 Start of Block / Option R 16c / ::AMT Line No A SHIP Line No. 78 Name: Shipping Amount Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::SHIP//CNY15, Source: ChargeAmount/Sign, ChargeAmountCurrencyCode, ChargeAmount/Amount Note: ChargeTaxType must equal SHIP. End of Block / Option S 16c / ::AMT Line No. 81 SWIFT MT541/543 Message 26

27 Table 2.2 SWIFT MT541/543 Specification (continued) SWIFT Tag/ Qualifier & Line # Line No A SPCN Line No. 78 Line No. 81 Line No A STAM Line No. 78 Line No. 81 Line No A STEX Line No. 78 Line No. 81 Line No A TRAN Line No. 78 Line No. 81 Line No A STEX Line No. 78 Line No. 81 Line No A TRAN Line No. 78 SWIFT Field Name/Format/Example Start of Block / Option R 16c / ::AMT Name: Special Concessions Amount Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::SPCN//HKD15, End of Block / Option S 16c / ::AMT Start of Block / Option R 16c / ::AMT Name: Stamp Duty Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::STAM//GBR15, End of Block / Option S 16c / ::AMT Start of Block / Option R 16c / ::AMT Name: Stock Exchange Tax Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::STEX//JPY15, End of Block / Option S 16c / ::AMT Start of Block / Option R 16c / ::AMT Name: Transfer Tax Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::TRAN//USD15, End of Block / Option S 16c / ::AMT Start of Block / Option R 16c / ::AMT Name: Stock Exchange Tax Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::STEX//JPY15, End of Block / Option S 16c / ::AMT Start of Block / Option R 16c / ::AMT Name: Transfer Tax Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::TRAN//USD15, SWIFT Codes/M-0 4 AG/ CTM Mapping Source/Note Source: ChargeAmount/Sign, ChargeAmountCurrencyCode, ChargeAmount/Amount Note: ChargeTaxType must equal SPCN. Source: ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount Note: ChargeTaxType must equal STAM. Source: ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount Note: ChargeTaxType must equal STEX. Source: ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount Note: ChargeTaxType must equal TRAN. Source: ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount Note: ChargeTaxType must equal STEX. Source: ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount Note: ChargeTaxType must equal TRAN. SWIFT MT541/543 Message 27

28 Table 2.2 SWIFT MT541/543 Specification (continued) SWIFT Tag/ Qualifier & Line # Line No. 81 Line No A TRAX Line No. 78 Line No. 81 Line No A VATA Line No. 78 Line No. 81 Line No. 82 SWIFT Field Name/Format/Example End of Block / Option S 16c / ::AMT Start of Block / Option R 16c / ::AMT Name: Transaction Tax Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::TRAX//ARS15, End of Block / Option S 16c / ::AMT Start of Block / Option R 16c / ::AMT Name: Value-Added Tax Format: :4!c//[N]3!a15d (Qualifier) (Sign) (Currency Code) (Amount) Example: :19A::VATA//BRL15, End of Block / Option S 16c / ::AMT SWIFT Codes/M-0 End of Block / Option S 16c / ::SEET Mandatory Sequence F Other Parties Note: This sequence is optional for SWIFT, but mandatory for CTM. Line No a MEOR Line No. 84 Line No. 88 -} Start of Block / Option R 16c / ::OTHRPRTY Name: Originator of Message Format Option P: :4!c//4!a2!a2!c[3!c] (Qualifier) (BIC/BEI) Example Option P: :95P::MEOR//THANUS31XXX Mandatory End of Block / Option S 16c / ::OTHRPRTY AG/ CTM Mapping Source/Note Source: ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount Note: ChargeTaxType must equal TRAX. If the place of settlement is Australia, ChargeTaxType of TRAX is mapped to 19A::VATA. Source: ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount Note: ChargeTaxType must equal VATA. If the place of settlement is Australia, ChargeTaxType of TRAX is mapped to 19A::VATA. Source: One of the following composites: ExecutingBroker/PartyValue InstructingParty/PartyValue 1 CTM supports the following SWIFT codes: BCFD, BCPD, CBNS, CCPN, CDIV, CRTS, GL, SPCU, SPEX, XBNS, XCPN, XDIV, and XRTS. 2 CTM supports the following SWIFT codes: BUTC, CLEN, DIRT, EXER, FRCL, NOMC, NPAR, PART, PHYS, RPTO, SHOR, SPDL, SPST, UNEX, and TRIP. 3 CTM supports the following SWIFT codes: CONV, ETFT, ISSU, NETT, OAUX, OTCS, OWNI, PLAC, and TRAD 4 CTM supports the following SWIFT codes: GBAX, GBBX, GBCX, GBDX, GBEX, GBFX, GBGX, GBHX, GBIX, GBLX, GBMX, GBNX, GBOX, GBPX, GBRX, GBSX, GBTX, GBUX, GBVX, GBWX, GBXX, GB2X, GB3X, GB4X, GB5X, GB6X, GB7X, IEJX, IEQX, IEYX, IE1X, IE8X, and USTN. 5 The following PSET BICS merged into a single BIC, IBRCESMMXXX: IBRCESMM, IBRCESMMSCL, IBRCESMMCDE, IBRCESMMMVL, and IBRCESMMXXX. Example of a SWIFT MT541/543 Message CTM requires that investment managers open the trade blotter to view an MT541/543 message. SWIFT MT541/543 Message 28

29 Trade Blotter Example Before you attempt viewing an MT541/543, ensure that you have the required subscriptions, roles, and so on. To view a SWIFT MT541/543 in the trade blotter: 1. Open the trade blotter and navigate to the Settlement Notification Summary view (Figure 2.1). Figure 2.1 Settlement Notification Summary view Depending on your set-up, adjust the date range of the notifications shown in the next figure. 2. Right-click the SWIFT Settlement Notification you want to view. The View Notification appears, an example of which is shown below. SWIFT MT541/543 Message 29

30 Figure 2.2 View Notification The View Notification shows how the SWIFT fields and values in Figure 2.1 on the previous page correspond to a TradeDetail. Message Layout Example The shaded rows in the Table 2.3 indicate Start and End block fields and the column headers represent the following: Inbound to CTM TradeDetail XPath Elements: The XPaths in the column assume the TradeDetailBody composite as the root element. Each path is subsequent to one indent level. For example, the first XPath in the following table, InstructingParty/PartyValue, represents: SWIFT MT541/543 Message 30

31 o o InstructingParty at indent level 2, which is also a composite. PartyValue at indent level 3, which is an element in the InstructingParty composite. Outbound to Receiver SWIFT MT541 Field-Value Pairs: The column lists SWIFT tag, qualifier, option (where appropriate), and corresponding value. Meaning: Describes the value for the MT541 field. Table 2.3 SWIFT MT541 Message Example Inbound to CTM TradeDetail XPath Element Outbound to Receiver SWIFT MT541 Field-Value Pairs ::GENL Meaning Start of block containing general information. CTMTradeDetailID :20C::SEME// CTM generates the value when FunctionOfTheMessage is NEWM. Sender s reference identifier is FunctionOfTheMessage :23G:NEWM Settlement instruction is new (NEWM). ::GENL ::TRADDET End of block. Start of block containing allocation details. SettlementDate :98A::SETT// Settlement date is April 21, TradeDateTime :98A::TRAD// Trade date is April 18, DealPrice/CurrencyCode, DealPrice/Amount SecurityTypeGroup IdentificationOfASecurity :90B::DEAL//ACTU/GBR27 :35B:/ISIN/DE AACHESTRASSENBAHN Deal price for the single allocation is GBR sterling. Identifies a security using an ISIN as the NumberingAgencyCode, with a security code of DE , described as AACHEN STRASSENBAHN. CTM generates the value. :25d::MTCH//MACH MatchStatus on the trade is MATCHED. ::TRADDET ::FIAC End of block containing trade details. Start of block containing financial information and account details. QuantityAllocated :36B::SETT//UNIT/2500, Quantity of the financial instrument allocation is 2500 units. SecurityAccount :97A::SAFE// Allocation settles in a fund with security account number ::FIAC ::SEET End of block containing financial information and account details. Start of block containing settlement details. TypeOfTransactionIndicator :22F::SETR//TRAD The instruction relates to the settlement of a trade. BuySellIndicator, InstructingParty/PartyValue ::SETPRTY :95P::SELL//OMGOUS33XXX ::SETPRTY ::SETPRTY Start of block containing settling parties. Instructing party is the seller and its BIC is OMGOUS33XXX. End of block containing settling parties. Start of block containing settling parties. SubAgentName1 :95R::DEAG/PARBDEFFXXX Delivery agent BIC IS PARBDEFFXXX. SecurityAccount :97A::SAFE// Allocation settles in a fund with security account number ::SETPRTY ::SETPRTY End of block containing settling parties. Start of block containing settling parties. PSET :95P::PSET//DAKVDEFFXXX The PSET BIC for the instructing party is DAKVDEFFXXX. TradeAmount/CurrencyCode, TradeAmount/Amount ::SETPRTY ::AMT :19A::DEAL//CAD81000, ::AMT ::AMT End of block containing amounts. Start of block containing amounts. Gross consideration for the 1,000 bond units, which represent the entire allocation, is $81, Canadian dollars. End of block containing amounts. Start of block containing amounts. SWIFT MT541/543 Message 31

32 Table 2.3 SWIFT MT541 Message Example (continued) Inbound to CTM TradeDetail XPath Element NetCashAmount/CurrencyCode, NetCashAmount/Amount CommissionReasonCode, Commission/CurrencyCode, Commission/Amount InstructingParty/PartyValue Outbound to Receiver SWIFT MT541 Field-Value Pairs :19A::SETT//CAD81400, ::AMT ::AMT :19A::EXEC//CAD400, -} ::AMT ::SEET ::OTHRPRTY Meaning The settlement price of the 1,000 bond units is $81, Canadian dollars due to the executing broker s commission of $ Canadian dollars in the subsequent commission field. Note: The SettlementAmount composite in the TradeDetail was empty, so CTM derived the values from the NetCashAmount composite. End of block containing amounts. Start of block containing amounts. The executing broker s commission for the allocation is $ Canadian dollars. End of block containing amounts. End of block containing settlement details. Start of block containing instructing party identifier. :95P::MEOR//ZYOTUS30ESN Instructing party s BIC, ZYOTUS30ESN. ::OTHRPRTY -} End of MT541. End of block containing instructing party identifier. SWIFT MT541/543 Message 32

33 3. CSV FILE Introduction This chapter describes the CSV file layout and includes an example CSV file. Overview CTM provides the option of constructing a CSV file containing settlement instructions for release to custodians and interested parties. CTM releases the CSV third party details using secure File Transfer Protocol (SFTP) as the delivery method. With a CSV file, CTM: Constructs and releases settlement instructions and notifications to custodians and interested parties. Provides multiple parties that do not have SWIFT connectivity with relevant trade data in CSV format. The data included in the CSV file conforms to SWIFT formatting, data length, and optional/mandatory rules and specifications. The CSV file contains MT541/543 message fields and several administrative fields. The CSV file represents MT541/543 fields using the X character set. The administrative fields in the CSV file display all the special characters that are used for corresponding fields in CTM. For example, CTM represents the MasterReference administrative field with a value of ABCabc%#123 in an MT541/543 as ABCabc%#123 in a CSV file. Note For more information about CTM format notation and the X character set, refer to the XML Message Specification corresponding to your asset class. File Naming and Other Applicable Rules The CTM file naming convention is: <NEWM/CANC><underscore><Notification Id><underscore><Notification Order><underscore><Timestamp> Example: NEWM_ _01_ _ CSV File 33

34 When creating CSV files, CTM applies the following rules: The CSV file contains all mandatory MT541/543 SWIFT fields and required administrative fields. CTM uses the same validation rules processing as SWIFT. Fields you submit must be constructed and ordered in accordance with those rules. Fields in the CSV file structure use the same formatting rules and fulfill the same mandatory/optional requirements as the SWIFT fields. For example, if Settlement Date is formatted as in an MT541/543, CTM formats it the same way in the CSV file. Correct SWIFT format is Incorrect CSV format is 03-Dec-16 The CSV file contains two rows. o o The first row contains column identifiers separated by commas. The second row contains corresponding values to those in the first row separated by commas. In both the rows, CTM does not include space(s) between a field value and the preceding or following comma, unless the space(s) is part of the field value. Correct Message Type, Receiver s Address, Buy Sell Indicator Incorrect Message Type, Receiver's Address, Buy Sell Indicator The file fields follow the X character set. CTM replaces characters that are not in the X character set (invalid for SWIFT) with a <space>, in accordance with MT541/543 message rules. The administrative fields follow the Z character set and do not map to SWIFT. Those field values are mapped directly from source fields and conform to the Z character set. CTM escapes fields containing a comma by embedding the field inside double quotes. Correct Incorrect data1, data2a,data2b,data3 CTM escapes fields containing a sub-string enclosed in double quotes as follows: o o Embeds the sub-string enclosed in double quotes inside an additional set of double quotes. Embeds the whole field inside a set of double quotes. Correct Incorrect data1, data 2 A,data3 CTM escapes end of line characters in a field by embedding the field inside a set of double quotes. CTM does not escape fields containing slashes (/) or any other special characters. CTM populates optional fields in the CSV file only when they are present in the MT541/543 message. If an optional field value is not present, the column header is created for the field but CTM inserts only the comma. CSV File 34

35 SWIFT Fields, Codes, and Sample Values CTM always populates the CSV file fields in the following table with the corresponding SWIFT codes. Table 3.1 SWIFT fields, codes, and sample values SWIFT Field Name SWIFT Code(s) Example Value Currency FXIB, FXIS FXIS/USD Deal Price PRCT, ACTU ACTU/USD19493 Place of Trade EXCH, OTCO OTCO/US Quantity of Financial Instrument FAMT, UNIT FAMT/19493 Buyer/Seller BUY, SELL SELL/BICXXXXX Deliverer's/Receiver's Agent DEAG, REAG DEAG/SUBAGENT1/SUBAGENT2/SUBAGENT ADDRESS1/SUBAGENT ADDRESS2 Deliverer's/Receiver's Custodians Deliverer's/Receiver's Intermediary DECU, RECU DECU/CUST 1/CUST 2 DEI, REI DEI1/BICXXXXX Place of Settlement PSET PSET/HK Mapping SWIFT Fields with Multiple or Concatenated Values to CSV This section describes MT541/543 message and corresponding CSV file fields containing multiple concatenated values. Handling Fields with Multiple Values Some fields in the CSV file can contain multiple values. All possible values for the fields are specified in the SWIFT Code column in the CSV File Layout on page 36. If any of the fields has multiple values, CTM populates the values in the same CSV file field, separated by slashes (/). CTM does not populate the qualifier, but does populate the Data Source Scheme (DSS) for Trade Transaction Condition Indicator. Slashes separate SWIFT code from each value. For example, TradeTransactionConditionIndicator maps to XCPN/XRTS/XDIV. Note For fields that contain a DSS, the CTM always separate the DSS by a slash. Refer to for more information about the DSS in SWIFT messaging. Multiple Values and Serial Ordering The following fields can also contain multiple values and follow SWIFT rules. Multiple values are ordered by the Account with Institution and Cash Account CSV fields in the same serial order that they appear on the SWIFT message. Concatenated Values The CSV file value for the Place of Safekeeping composite is a concatenation of the Place of Safekeeping Type and Place of Safekeeping Value elements separated by slashes. The following rules apply: For Option F: Place of Safekeeping Type=BIC (for example, BIC/INSTXX34) For Option C: Place of Safekeeping Type=COUN (for example, COUN/AG) CSV File 35

36 Narrative Value (settlement indicator processing narrative) Due to its potential length, CTM maps the Settlement Indicator Processing Narrative field as follows: Leaves no space between slashes for empty and omitted lines. For example, if Line 2 is not present: "Line1//Line3...Line 10" If a file specifies an exact number of lines, then CTM omits all references after the last line. For example, if Line 4 onward is not present: "Line1/Line2/Line3" CTM maps all other SWIFT tags and qualifiers sourced from CTM trade data to CSV fields with source trade data only. CSV files do not include SWIFT tags and slashes. CSV File Layout CTM provides the option of constructing a CSV file containing settlement instructions for release to custodians and interested parties. CTM releases the CSV third party details using secure File Transfer Protocol (SFTP) as the delivery method. With a CSV file, CTM: Constructs and releases settlement instructions and notifications to custodians and interested parties. Provides multiple parties that do not have SWIFT connectivity with relevant trade data in CSV format. Table 3.2 describes the contents of the MT541/543 column headers in the CSV File Specification: The shaded rows indicate corresponding sequences in the MT541/543. The shaded rows with an arrow ( ) indicate corresponding subsequences in the MT541/543. Table 3.2 SWIFT MT541/543 Specification Column Header Key Column Header CSV Field Name SWIFT Tag/Qualifier/Field Name/Codes CSV Example Description The information in this column provides the CSV field name in the Header row of a CSV file. The information in this column contains the following, when corresponding SWIFT elements exist: SWIFT Tag/Qualifier If applicable, the field corresponds to the same tag and qualifier in a SWIFT MT541/543. SWIFT Field Name If applicable, the field corresponds to the same field name in a SWIFT MT541/543. SWIFT Codes If applicable, identifies all static SWIFT code values CTM supports: o o Commas separate the codes and SWIFT allows one code per field A superscript number such as 1 indicates that the corresponding table footnote contains an extensive list of supported code values. CSV Example An example field value as it appears in the message row of a CSV file. CSV File 36

37 Table 3.2 SWIFT MT541/543 Specification Column Header Key (continued) Column Header AG / CTM Mapping Source / Note Description The information in this column indicates the source that CTM uses to derive data for the CSV file: AG Automatically generated from CTM during the trade cycle and settlement process. Examples are the CTMTradeDetailID and CTMTradeSideId values. TradeDetail that you or your counterparty submit according to the rules described for the field in SWIFT MT541/543 Layout. TradeDetail that you or your counterparty submit according to the rules described for the field in SWIFT MT541/543 Layout. The information in this column indicates the following: Source The name of the element in the TradeDetail that CTM uses to derive or map data for the third party detail. If the element is not unique in the message, the XPath is included. For example, PartyValue is an element in the InstructingParty and ExecutingBroker composites. When used for mapping, the PartyValue XPath is: o o InstructingParty/PartyValue ExecutingBroker/PartyValue Mandatory and optional elements within composites conform to SWIFT mandatory and optional fields. For example, the Currency composite contains the optional Sign element and the mandatory CurrencyCode and Amount elements. Note Notes include whether CTM maps the instructing party or executing broker value and other rules or validations CTM applies. The following table provides the CSV file specification. It only contains fields applicable to settlement according to CSV requirements. Table 3.3 CSV File Specification CSV Field Name SWIFT Tag/Qualifier/Field Name/Codes/CSV Example AG/ /TL CTM Mapping Source/Note Header Information (Block 1 and Block 2) Message Type Receiver s Address Buy Sell Indicator SWIFT Tag/Qualifier: HDR Field Name: Message Type CSV Example: 541 SWIFT Tag/Qualifier: HDR Field Name: Receiver s Address CSV Example: XXX SWIFT Tag/Qualifier: HDR Field Name: Receiver s Address CSV Example: BUYI AG BuySellIndicator Trade Side ID CSV Example: CTMTradeSideId Concatenation of Domain Name, Port Number, and Destination Directory in the eligible Destination Profile. BuySellIndicator Administrative field TradeDetail ID CSV Example: CTMTradeDetailID Master Reference CSV Example: MasterReference Client Allocation Reference CSV Example: ClientAllocationReference Version Number CSV Example: 2 Administrative field Notification ID CSV Example: AG Administrative field Notification Order CSV Example: 1 AG Administrative field General Information (Mandatory Sequence A) CSV File 37

38 Table 3.3 CSV File Specification (continued) CSV Field Name SWIFT Tag/Qualifier/Field Name/Codes/CSV Example AG/ /TL CTM Mapping Source/Note Sender s Reference SWIFT Tag/Qualifier: :20C::SEME Field Name: Sender s Reference AG or CTMTradeDetailID or identifier supplied by CTM. CSV Example: Function of the Message SWIFT Tag/Qualifier: :23G: Field Name: Function of the Message SWIFT Codes: NEWM, CANC, COPY AG Source: FunctionOfTheMessage Note: CTM release the CSV file to recipients in the following order, as they occur in the TradeDetail: CSV Example: NEWM NEWM and CANC ReceiverAgentBIC, CustodianBIC, or SubAgentBIC. COPY Interested party or parties. Preparation Date/Time SWIFT Tag/Qualifier: :98C::PREP Field Name: Preparation Date/Time CSV Example: Linkages ( Subsequence A Qualifier 23G) Note: CTM map the optional Linkages subsequence only when Function of the Message=CANC Previous Reference SWIFT Tag/Qualifier: :20C::PREV Field Name: Previous Reference SWIFT Codes: NEWM, CANC CSV Example: AG CTM generates as YYYYMMDDHHMMSS using the time zone setup with the instructing party. Administrative field. Depending on the FunctionOfTheMessage, CTM only maps the CTMTradeDetailID for multiple linked allocations when the FunctionOfTheMessage=CANC. NEWM CTM generates the Sender s Reference. CANC CTM maps the CTMTradeDetailID when the FunctionOfTheMessage in the TradeDetail is CANC (:23G:CANC). Related Reference SWIFT Tag/Qualifier: :20C::RELA Field Name: Related Reference CSV Example: 1 Pool Related Reference SWIFT Tag/Qualifier: :20C::POOL Field Name: Pool Related Reference CSV Example: 1 Trade Details (Mandatory Sequence B) Source: One or both of the following: References/ReferenceType References/ReferenceValue Note: CTM only maps thereferences composite when you share a common reference for grouped or pooled allocations. Source: One or both of the following: References/ReferenceType References/ReferenceValue Note: CTM only maps thereferences composite when you share a common reference for grouped or pooled allocations. Place of Trade SWIFT Tag/Qualifier: :94B::TRAD One or both of the following: Field Name: Place of Trade PlaceOfTrade/PlaceCode SWIFT Codes: EXCH, OTCO, VARI PlaceOfTrade/PlaceNarrative CSV Example: EXCH/XNYS Settlement Date SWIFT Tag/Qualifier: :98A::SETT SettlementDate Field Name: Settlement Date CSV Example: Trade Date SWIFT Tag/Qualifier: :98A::TRAD Source: TradeDateTime Field Name: Trade Date CSV Example: Note: CTM only maps the date portion (YYYYMMDD) of TradeDateTime. CSV File 38

39 Table 3.3 CSV File Specification (continued) CSV Field Name SWIFT Tag/Qualifier/Field Name/Codes/CSV Example AG/ /TL CTM Mapping Source/Note Deal Price Number of Days Accrued SWIFT Tag/Qualifier: :90a::DEAL Field Name: Deal Price CSV Example: JPY3925 SWIFT Tag/Qualifier: :99A::DAAC Field Name: Number of Days Accrued CSV Example: 3 Country Code SWIFT Tag/Qualifier: :35B Numbering Agency Code Field Name: Identification of the Financial Instrument CSV Example: ARS SWIFT Tag/Qualifier: :35B Field Name: Identification of the Financial Instrument CSV Example: ISIN Security Code SWIFT Tag/Qualifier: :35B Description Of The Security 1 Description Of The Security 2 Description Of The Security 3 Description Of The Security 4 Field Name: Identification of the Financial Instrument CSV Example: JP SWIFT Tag/Qualifier: :35B Field Name: Identification of the Financial Instrument CSV Example: AEON YUSHU SWIFT Tag/Qualifier: :35B Field Name: Identification of the Financial Instrument CSV Example: IDFI2 SWIFT Tag/Qualifier: :35B Field Name: Identification of the Financial Instrument CSV Example: IDFI3 SWIFT Tag/Qualifier: :35B Field Name: Identification of the Financial Instrument CSV Example: IDFI4 Financial Instrument/Account ( Subsequence B1) Source: SecurityType and one or both of the following: DealPrice/CurrencyCode DealPrice/Amount Note: For mapping options, see SWIFT tag 90a DEAL Line No. 16. Source: NumberOfDaysAccrued Note: To map NumberOfDaysAccrued, CTM requires a positive value that does not include Sign. CountryCode NumberingAgencyCode SecurityCode DescriptionOfTheSecurity DescriptionOfTheSecurity DescriptionOfTheSecurity DescriptionOfTheSecurity Note: Only populated when PSET is Germany and you supply Current Factor or Pool Number fields values. Current Factor Pool Number Maturity Date Coupon Rate SWIFT Tag/Qualifier: :92A::CUFC Field Name: Current Factor CSV Example: 1,559 SWIFT Tag/Qualifier: :13B::POOL Field Name: Pool Number CSV Example: 4 SWIFT Tag/Qualifier: :98a::MATU Field Name: Maturity Date CSV Example: SWIFT Tag/Qualifier: :92A::INTR Field Name: Coupon Rate CSV Example: 5,4 Source: One or both of the following: CurrentFactor/Sign CurrentFactor/Amount Source: PoolNumber Note: CTM maps the issuer s identifier for a mortgagebacked security supplied on the TradeDetail. Source: MaturityDate Note: CTM maps the MaturityDate for fixed income (debt) instruments only. Source: CouponRate Note: CTM maps the CouponRate for fixed income (debt) instruments only. CSV File 39

40 Table 3.3 CSV File Specification (continued) CSV Field Name SWIFT Tag/Qualifier/Field Name/Codes/CSV Example AG/ /TL CTM Mapping Source/Note Yield to Maturity Rate Trade Transaction Condition Indicator Currency Match Status Settlement Instruction Processing Narrative SWIFT Tag/Qualifier: :92A::YTMR Field Name: Yield to Maturity Rate CSV Example: 5,3 SWIFT Tag/Qualifier: :22F::TTCO Field Name: Indicator SWIFT Codes: 1 CSV Example: 5,8 SWIFT Tag/Qualifier: :11A::DENO Field Name: Currency SWIFT Codes: FXIB or FXIS CSV Example: FXIS/CNY SWIFT Tag/Qualifier: :25D::MTCH Field Name: Match Status SWIFT Codes: MACH or NMAT CSV Example: MACH SWIFT Tag/Qualifier: :70E::SPRO Field Name: Settlement Instruction Processing Narrative CSV Example: Counterparty covers registration cost. Financial Instrument/Account (Mandatory Sequence C) Source: YieldType Note: CTM maps the YieldToMaturityRate for fixed income (debt) instruments only when TradeLevelCommonValues/YieldType=MATR. Source: TradeTransactionConditionIndicator Note: CTM repeats :22F:TTCO for each occurrence in the ISRTLCommonValues composite using a different indicator for each instance. Source: AdditionalText or FXDealCurrencyCode Note: CTM maps the element to instruct the recipient of a settlement instruction to execute an FX deal. CTM maps as follows: If MatchStatus=MACH, CTM supplies MACH. If MatchStatus=NMAT or MISM, CTM supplies NMAT. AdditionalText line, including a valid FX value. If the PSET value in is in the India market, CTM formats AdditionalText (lines 7-10) in Tag 70E Narrative on the MT541/543. For example, :70E::SPRO//BSE/CH/5). Note: CTM only populates Subsequence B1 block only if CurrentFactor or PoolNumber are in the TradeDetail. The PSET cannot be not Germany. Quantity of Financial Instrument SWIFT Tag/Qualifier: :36B::SETT Field Name: Quantity of Financial Instrument SWIFT Codes: FAMT or UNIT CSV Example: UNIT/200 CTM maps as follows: If :36B::SETT//FAMT, CTM maps QuantityAllocated, QuantityTypeCode, QuantityAllocated, and Amount. If :36B::SETT//UNIT/, CTM maps QuantityOfTheBlockTrade. Current Face Value SWIFT Tag/Qualifier: :36B::SETT Field Name: Quantity of Financial Instrument SWIFT Code: AMOR CSV Example: AMOR/3344, Cash Account SWIFT Tag/Qualifier: :97A::CASH Field Name: Account (Cash Account) CSV Example: Place of Safekeeping SWIFT Tag/Qualifier: :94a::SAFE Field Name: Place (Place of Safekeeping) CSV Example: DTCC Repetitive Settlement Details (Mandatory Sequence E) Source: CurrentFaceValue Note: For fixed income (debt) instruments, CTM maps the amount representing, for example, the current amortized face amount of a bond. Source: CashAccountNo Note: CTM maps the cash account number, including the option to use an International Bank Account Number (IBAN), for the settling allocation. For mapping options, see SWIFT tag 97a CASH Line No. 43. Source: Both of the following: PlaceOfSafekeeping/Value PlaceOfSafekeeping/Place Note: For mapping options, see SWIFT tag 94a SAFE Line No. 44. CSV File 40

41 Table 3.3 CSV File Specification (continued) CSV Field Name SWIFT Tag/Qualifier/Field Name/Codes/CSV Example AG/ /TL CTM Mapping Source/Note Settlement Transaction Condition Indicator SWIFT Tag/Qualifier: :22F::STCO Field Name: Indicator (Settlement Transaction Condition) SWIFT Codes: 2 CSV Example: CLEN Source: One of the following TradeDetailData/ SettlementTransactionConditionIndicator TradeLevelInformation/ TradeTransactionConditionIndicator Note: CTM maps the element only when one of the following is true: TradeDetail contains a value in the SettlementTransactionConditionIndicator element. TradeDetail contains a value in the TradeTransactionConditionIndicator that is CLEN or DIRT. SWIFT tag :95C::PSET, must use Option C if STCO SWIFT code is PHYS or CTM fails validation. Type of Settlement Transaction Indicator SWIFT Tag/Qualifier: :22F::SETR Field Name: Indicator (Type of Settlement Transaction) SWIFT Codes: 3 Source: TypeOfTransactionIndicator Note: CTM maps NETT for allocations that are eligible for netting. CSV Example: TRAD Stamp Duty Indicator SWIFT Tag/Qualifier: :22F::STAM Source: SettlementTransactionConditionIndicator Field Name: Indicator (Stamp Duty Indicator) SWIFT Codes: 4 CSV Example: CRST/GBT Registration Override Indicator SWIFT Tag/Qualifier: :22F::REGT Field Name: Indicator (Registration Override Indicator) SWIFT Codes: NREG or YREG Source: SettlementTransactionConditionIndicator Note: CTM maps REGT only once, using the first code in the TradeDetail. CSV Example: NREG Beneficial Ownership Override Indicator SWIFT Tag/Qualifier: :22F::BENE Field Name: Indicator (Beneficial Ownership Override Indicator) Source: SettlementTransactionConditionIndicator Note: CTM maps BENE only once, using the first code in the TradeDetail. SWIFT Codes: NBEN or YBEN CSV Example: NBEN Cash Settlement System Override Indicator SWIFT Tag/Qualifier: :22F::CASY Field Name: Indicator (Cash Settlement System Override Indicator) Source: SettlementTransactionConditionIndicator Note: CTM maps CASY only once, using the first code in the TradeDetail. SWIFT Codes: GROS or NETS CSV Example: NETS Forex Order Cancellation Indicator SWIFT Tag/Qualifier: :22F::FXCX Field Name: Indicator (Forex Order Cancellation Indicator) SWIFT Codes: FXYE or FXNO Source: SettlementTransactionConditionIndicator Note: CTM maps the element only if Function of the Message in Sequence A is CANC. CSV Example: FXNO Netting Eligibility Indicator SWIFT Tag/Qualifier: :22F::NETT Field Name: Indicator (Netting Eligibility Indicator) SWIFT Codes: NNET or YNET Source: SettlementTransactionConditionIndicator Note: CTM maps NETT only once, using the first code in the TradeDetail. CSV Example: YNET CSV File 41

42 Table 3.3 CSV File Specification (continued) CSV Field Name SWIFT Tag/Qualifier/Field Name/Codes/CSV Example AG/ /TL CTM Mapping Source/Note Central Counter Party Eligibility Indicator Letter of Guarantee Indicator Settlement System Method Indicator Real-Time Gross Settlement System Indicator Restrictions Indicator Block Trade Indicator SWIFT Tag/Qualifier: :22F::CCPT Field Name: Indicator (Central Counterparty Eligibility Indicator) SWIFT Codes: NCCP or YCCP CSV Example: NCCP SWIFT Tag/Qualifier: :22F::LEOG Field Name: Indicator (Letter of Guarantee Indicator) SWIFT Codes: NLEG or YLEG CSV Example: NLEG SWIFT Tag/Qualifier: :22F::SETS Field Name: Indicator (Settlement System/Method Indicator SWIFT Codes: NSET or YSET CSV Example: YSET SWIFT Tag/Qualifier: :22F::RTGS Field Name: Indicator (Real-Time Gross Settlement System Indicator) SWIFT Codes: NRTG or YRTG CSV Example: NRTG SWIFT Tag/Qualifier: :22F::REST Field Name: Indicator (Restrictions) SWIFT Codes: NRST, RSTR, or 144A CSV Example: NRST SWIFT Tag/Qualifier: :22F::BLOC Field Name: Indicator (Block Trade Indicator) SWIFT Codes: BLCH or BLPA CSV Example: BLPA Settlement Parties (Mandatory Subsequence E1) Source: SettlementTransactionConditionIndicator Note: CTM maps CCPT only once, using the first code in the TradeDetail. Source: SettlementTransactionConditionIndicator Note: CTM maps LEOG only once, using the first code in the TradeDetail. Source: SettlementTransactionConditionIndicator Note: CTM maps SETS only once, using the first code in the TradeDetail. Source: SettlementTransactionConditionIndicator Note: CTM maps RTGS only once, using the first code in the TradeDetail. Source: SettlementTransactionConditionIndicator Note: CTM maps REST only once, using the first code in the TradeDetail. Source: SettlementTransactionConditionIndicator Note: CTM maps BLOC only once, using the first code in the TradeDetail. Note: CTM only maps the parties in the TradeDetail. For example, if there is not a SubAgent for the trade, CTM omits the Delivering/Receiving Agent and corresponding Safekeeping Account fields. Buyer/Seller SWIFT Tag/Qualifier: :95a::BUYR or SELL Field Name: Party CSV Example: BUYI/ABCJPYABXXX HDR Source: One of the following: ExecutingBroker/PartyValue or ExecutingBroker/ OrgName InstructingParty/PartyValue or InstructingParty/ OrgName Note: For CSV mapping, CTM uses the codes BUYI and SELL. For mapping options and other information, see SWIFT tag 95a BUYR or SELL Line No. 65. Deliverer s/ Receiver s Custodian SWIFT Tag/Qualifier: :95a::DECU or RECU Field Name: Party Source: CustodianBIC, CustodianName1, or CustodianName2 CSV Example: DECU/HIJABCABCXX Note: For mapping options, see SWIFT tag 95a DECU or RECU Line No. 65. Deliverer s/ Receiver s Custodian's Safekeeping Account SWIFT Tag/Qualifier: :97A::SAFE Field Name: Safekeeping Account CSV Example: Source: SubAccountNo Note: For mapping options, see SWIFT tag 97a SAFE Line No. 66. CSV File 42

43 Table 3.3 CSV File Specification (continued) CSV Field Name SWIFT Tag/Qualifier/Field Name/Codes/CSV Example AG/ /TL CTM Mapping Source/Note Delivering/ Receiving Agent SWIFT Tag/Qualifier: :95a::DEAG or REAG Field Name: Party Source: SubAgentBIC, ID1, or one or more of the following: CSV Example: DEAG/ABCABCABCXX SubAgentName1 and SubAgentAddress1 SubAgentName2 and SubAgentAddress2 Note: For mapping rules, see SWIFT tag 95a DEAG or REAG Line No. 65. Delivering/ Receiving Agent s Safekeeping Account SWIFT Tag/Qualifier: :97A::SAFE Field Name: Safekeeping Account CSV Example: Repetitive Cash Parties ( Subsequence E2) Source: ID1, ID2 Note: For mapping rules, see SWIFT tag 97a SAFE Line No. 66. Note: CTM only maps Subsequence E2 if Relationship=C (Correspondent) in the TradeDetail and if 95P/95Q:ACCW is populated. Account with Institution Cash Account SWIFT Tag/Qualifier: :95a::ACCW Field Name: Party (Account with Institution) CSV Example: ABCABCABCXX SWIFT Tag/Qualifier: :97a::CASH Field Name: Cash Account CSV Example: Repetitive Amounts (Mandatory Subsequence E3) Source: Relationship or CorrespBIC Source: CorrespCashAccountNo from the executing broker trade side where the SettlementInstructions composite for the SettlementInstructions/PartyIdentifier is the executing broker. Note: Used by CTM only when Relationship=C (Correspondent). CTM maps the cash account number, including the optional International Bank Account Number (IBAN). Accrued Interest Amount SWIFT Tag/Qualifier: :19A::ACRU Field Name: Accrued Interest Amount AccruedInterestAmount/Sign, AccruedInterestAmount/ CurrencyCode, AccruedInterestAmount/Amount CSV Example: USD500, Charges or Fees SWIFT Tag/Qualifier: :19A::CHAR Field Name: Charges or Fees Source: ChargeAmount/Sign, ChargeAmount/ CurrencyCode, ChargeAmount Amount CSV Example: GBR40000, Note: CTM maps only if ChargeTaxType= CHAR. Country National Federal Tax SWIFT Tag/Qualifier: :19A::COUN Field Name: Country, National Federal Tax Source: ChargeAmount/Sign, ChargeAmount/ CurrencyCode, ChargeAmount Amount CSV Example: JPY100, Note: CTM maps only if ChargeTaxType=COUN. Trade Amount SWIFT Tag/Qualifier: :19A::DEAL Field Name: Trade Amount TradeAmount/Sign, TradeAmount/CurrencyCode, TradeAmount/Amount CSV Example: EUR100, Executing Broker s Amount SWIFT Tag/Qualifier: :19A::EXEC Field Name: Executing s Broker Amount Source: Commission/Sign, Commission/CurrencyCode, Commission/Amount CSV Note: CTM maps only if ChargeTaxType=EXEC. Example: USD1007, Payment Levy Tax SWIFT Tag/Qualifier: :19A::LEVY Field Name: Payment Levy Tax Source: ChargeAmount/Sign, ChargeAmount/ CurrencyCode, ChargeAmount Amount CSV Example: USD41, Note: CTM maps only if ChargeTaxType= LEVY. CSV File 43

44 Table 3.3 CSV File Specification (continued) CSV Field Name SWIFT Tag/Qualifier/Field Name/Codes/CSV Example AG/ /TL CTM Mapping Source/Note Local Tax SWIFT Tag/Qualifier: :19A::LOCL Field Name: Local Tax Source: ChargeAmount/Sign, ChargeAmount/ CurrencyCode, ChargeAmount Amount CSV Example: ARS23, Note: CTM maps sum of the following ChargeTaxType elements: LOCL, LIDT, LOTE, and LYDT. Crested is nonexistent. Local Broker s Commission SWIFT Tag/Qualifier: :19A::LOCO Field Name: Local Broker s Commission Source: Commission/Sign, Commission/CurrencyCode, Commission/Amount CSV Example: USD15, Note: CTM maps only if ChargeTaxType=LOCO. If a RSCH Commission Type is one of the broker commission codes on the CTM MAGR trade, it is mapped to Local Broker s Commission. This mapping remains in place until the weekend of November 17, 2018, which is when SWIFT begins support of the new Research Commission. After that date, if RSCH is provided by the broker on a MAGR trade, it maps to Research Commissions in CSV position 92. Other Amount SWIFT Tag/Qualifier: :19A::OTHR Field Name: Other Amount Source: ChargeAmount/Sign, ChargeAmount/ CurrencyCode, ChargeAmount Amount CSV Example: DKK10, Note: CTM maps only if ChargeTaxType=OTHR. Regulatory Amount SWIFT Tag/Qualifier: :19A::REGF Field Name: Regulatory Amount Source: ChargeAmount/Sign, ChargeAmount/ CurrencyCode, ChargeAmount Amount CSV Example: GBR12, Note: CTM maps only if ChargeTaxType=REGF. Settlement Amount SWIFT Tag/Qualifier: :19A::SETT Source: One of the following: Field Name: Settlement Amount CSV Example: JPY15, NetCashAmount/Sign, NetCashAmount, CurrencyCode, NetCashAmount/Amount SettlementAmount/Sign, SettlementAmount, CurrencyCode, SettlementAmount/Amount Note: If SettlementAmount exists, CTM maps it; otherwise, CTM maps NetCashAmount. Shipping Amount SWIFT Tag/Qualifier: :19A::SHIP Field Name: Shipping Amount Source: ChargeAmount/Sign, ChargeAmount/ CurrencyCode, ChargeAmount Amount CSV Example: 67, Note: CTM maps only if ChargeTaxType=SHIP. Special Concessions Amount SWIFT Tag/Qualifier: :19A::SPCN Field Name: Special Concessions Amount Source: ChargeAmount/Sign, ChargeAmount/ CurrencyCode, ChargeAmount Amount CSV Example: 6, Note: CTM maps only if ChargeTaxType=SPCN. Stamp Duty SWIFT Tag/Qualifier: :19A::STAM Field Name: Stamp Duty Source: ChargeAmount/Sign, ChargeAmount/ CurrencyCode, ChargeAmount Amount CSV Example: 9, Note: CTM maps only if ChargeTaxType=STAM. Stock Exchange Tax SWIFT Tag/Qualifier: :19A::STEX Field Name: Stock Exchange Tax Source: ChargeAmount/Sign, ChargeAmount/ CurrencyCode, ChargeAmount Amount CSV Example: 30, Note: CTM maps only if ChargeTaxType=STEX. Transfer Tax SWIFT Tag/Qualifier: :19A::TRAN Field Name: Transfer Tax Source: ChargeAmount/Sign, ChargeAmount/ CurrencyCode, ChargeAmount Amount CSV Example: 34, Note: CTM maps only if ChargeTaxType=TRAN. CSV File 44

45 Table 3.3 CSV File Specification (continued) CSV Field Name SWIFT Tag/Qualifier/Field Name/Codes/CSV Example AG/ /TL CTM Mapping Source/Note Transaction Tax Value Added Tax SWIFT Tag/Qualifier: :19A::TRAX Field Name: Transaction Tax CSV Example: 3, SWIFT Tag/Qualifier: :19A::VATA Field Name: Value Added Tax CSV Example: 23, Repetitive Amounts (Mandatory Subsequence E3) Originator of Message SWIFT Tag/Qualifier: :95P::MEOR Field Name: Party Originator of Message CSV Example: ZYOTUS30ESN HDR Source: ChargeAmount/Sign, ChargeAmount/ CurrencyCode, ChargeAmount Amount Note: If the SWIFT Qualifier is TRAX and the PSET is Australia, CTM substitutes VATA for TRAX. For all other markets, CTM enforces standard mapping. Source: ChargeAmount/Sign, ChargeAmount/ CurrencyCode, ChargeAmount/Amount Note: If the SWIFT Qualifier is TRAX and the PSET is Australia, CTM substitutes VATA for TRAX. For all other markets, CTM enforces standard mapping. One of the following: Additional Fields (See SWIFT Tag Location for the sequence or subsequence identifier of the fields.) Place of Clearing Collateral Pool Indicator Local Tax (country specific 1) Yield to Maturity Buyer/Seller LEI SWIFT Tag/Qualifier: :94H::CLEA SWIFT Tag Location: Sequence B Field Name: Place of Clearing CSV Example: TYKTUS30ESN SWIFT Tag/Qualifier: :22F::COLE SWIFT Tag Location: Sequence E Field Name: Indicator (Collateral Pool Indicator) SWIFT Codes: COLA or COLN CSV Example: COLA SWIFT Tag/Qualifier: :19A::LADT SWIFT Tag Location: Subsequence E3 Field Name: Local Tax (country specific 1) CSV Example: LADT/21, SWIFT Tag/Qualifier: :92A::YTMR Field Name: Yield to Maturity CSV Example: 2 SWIFT Tag/Qualifier: :95L/ALTE Field Name: Party CSV Example: ALTE/ RHC4YFEI25 TL/ ExecutingBroker/PartyValue or ExecutingBroker/ OrgName InstructingParty/PartyValue or InstructingParty/ OrgName Source: PlaceOfClearing Note: CTM maps the BIC, which represents the place of clearing for the allocation, such as a central counterparty. Source: SettlementTransactionConditionIndicator Source: ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount Amount Source: Yield Type Note: CTM maps this element for fixed income (debt) instruments only when TradeLevelCommonValues/ YieldType=MATR. Source: ISRExecutingBroker/PartySettlement/Settlement Instructions/LEI or ISRTradeLevel/TLEBSettlement/Settlement Instructions/LEI 1 CTM supports the following SWIFT codes: BCFD, BCPD, CBNS, CCPN, CDIV, CRTS, GL, SPCU, SPEX, XBNS, XCPN, XDIV, and XRTS. 2 CTM supports the following SWIFT codes: BUTC, CLEN, DIRT, EXER, FRCL, NOMC, NPAR, PART, PHYS, RPTO, SHOR, SPDL, SPST, UNEX, and TRIP. 3 CTM supports the following SWIFT codes: CONV, ETFT, ISSU, NETT, OAUX, OTCS, OWNI, PLAC, and TRAD 4 CTM supports the following SWIFT codes: GBAX, GBBX, GBCX, GBDX, GBEX, GBFX, GBGX, GBHX, GBIX, GBLX, GBMX, GBNX, GBOX, GBPX, GBRX, GBSX, GBTX, GBUX, GBVX, GBWX, GBXX, GB2X, GB3X, GB4X, GB5X, GB6X, GB7X, IEJX, IEQX, IEYX, IE1X, IE8X, and USTN. CSV File 45

46 Example of a CSV File CTM requires that investment managers open the trade blotter to view an MT541/543 message. Before you attempt viewing an MT541/543, ensure that you have the required subscriptions, roles, Java software, and so on. To view a SWIFT MT541/543: 1. Open the trade blotter and navigate to the Settlement Notification Summary view shown below. Depending on your set-up, adjust the date range of the notifications shown in the next figure. 2. Right-click the SWIFT Settlement Notification you want to view. The View Notification appears, an example of which is shown below. CSV File 46

47 The following table shows how the CSV file header and data rows in the preceding figure correspond to a TradeDetail. The shaded rows in the following table correlate to SWIFT sequences. The column headers represent the following: Inbound to CTM TradeDetail XPath: The XPaths in the column assume the TradeDetailBody composite as the root element. Each path is subsequent to one indent level. For example, the first XPath InstructingParty/PartyValue represents: o o InstructingParty at indent level 2, which is also a composite. PartyValue at indent level 3, which is an element in the InstructingParty composite. Outbound to Receiver CSV File Header-Data Rows: The column lists the header row field and corresponding data row value or values, depending on the information in the TradeDetail. Meaning: Describes the value for the CSV file field. Table 3.4 SWIFT MT541 Message Example Inbound to CTM TradeDetail XPath Header Information BuySellIndicator and InstructingParty/ PartyValue CustodianBIC BuySellIndicator Outbound to Receiver CSV File Header-Data Rows Header: Message Type Data: 541 Header: Receiver s Address Data: /22/ Header: Buy Sell Indicato Data: BUYI Meaning The CSV file represents an instructing party where the BuySellIndicator=BUYI, which translates to an MT541. Concatenation of domain name, port number, and destination directory for the CustodianBIC is /22/. The instructing party is a buyer. CSV File 47

48 Table 3.4 SWIFT MT541 Message Example (continued) Inbound to CTM TradeDetail XPath CTMTradeSideId CTMTradeDetailID MasterReference ClientAllocationReference CTM generates the value. CTM generates the value. CTM generates the value. General Information CTM generates the value. FunctionOfTheMessage CTM generates the value. CTM generates the value. References/ReferenceType, References/ReferenceValue References/ReferenceType, References/ReferenceValue Mandatory Trade Details PlaceOfTrade/PlaceCode, PlaceOfTrade/ PlaceNarrative SettlementDate TradeDateTime DealPrice/CurrencyCode, DealPrice/ Amount SecurityTypeGroup Mandatory Identification of a Security NumberOfDaysAccrued CountryCode NumberingAgencyCode Outbound to Receiver CSV File Header-Data Rows Header: Trade Side ID Data: Header: TradeDetail ID Data: Header: Master Reference Data: Header: Client Allocation Reference Data: Alc-SNTF3Aeon Header: Version Number Data: 1.0 Header: Notification ID Data: Header: Notification Order Data: 1 Header: Sender s Reference Data: Header: Function of the Message Data: NEWM Header: Preparation Date/Time Data: Header: Pool Related Reference Header: Pool Related Reference Header: Pool Related Reference Header: Place of Trade Data: EXCH/XTFF Header: Settlement Date Data: Header: Trade Date Data: Header: Deal Price Data: "ACTU/JPY3925, Header: Number of Days Accrued Header: Country Code Header: Numbering Agency Code Data: ISIN Meaning CTM-supplied sender s reference identifier is CTM-supplied sender s reference identifier Client-supplied MasterReference is Client-supplied ClientAllocationReference is Alc-SNTF3Aeon. Administrative field. Administrative field. Administrative field. Sender s reference identifier is Settlement instruction is for a new trade. Preparation date and time of instruction is April 5, 2015 at 9:00 AM. Not supplied in the TradeDetail because it is not a block settlement trade. Not supplied in the TradeDetail because it is not a block settlement trade. Not supplied in the TradeDetail because it is not a block settlement trade. The market for the trade is the Tokyo International Financial Futures Exchange. Settlement date is March 31, Trade date is March 28, Deal price for the allocation and corresponding third party detail is 3925 Japanese yenmandatory Identification Not supplied in the TradeDetail. Not supplied in the TradeDetail. Numbering agency code identifier for the traded security is ISIN. CSV File 48

49 Table 3.4 SWIFT MT541 Message Example (continued) Inbound to CTM TradeDetail XPath SecurityCode DescriptionOfTheSecurity DescriptionOfTheSecurity DescriptionOfTheSecurity DescriptionOfTheSecurity Mandatory Financial Instrument/Account CurrentFactor/Sign, CurrentFactor/Amount PoolNumber MaturityDate CouponRate TradeTransactionConditionIndicator AdditionalText or FXDealCurrencyCode MatchStatus CTM generates the value. AdditionalText QuantityOfTheBlockTrade CurrentFaceValue SecurityAccount CashAccountNo PlaceOfSafekeeping/Value, PlaceOfSafekeeping/Place Outbound to Receiver CSV File Header-Data Rows Header: Security Code Data: JP Header: Description Of The Security 1 Data: AEON YUSHU Header: Description Of The Security 2 Header: Description Of The Security 3 Header: Description Of The Security 4 Header: Current Factor Header: Pool Number Header: Maturity Date Header: Coupon Rate Header: Trade Transaction Condition Indicator Header: Currency Header: Match Status Data: MACH Header: Settlement Instruction Processing Narrative Header: Quantity of Financial Instrument Data: UNIT/300000, Header: Current Face Value Header: Security Account Data: 3173 Header: Cash Account Header: Place Of SafeKeeping Meaning Security code for the traded security is 01N Not supplied in the TradeDetail. Not supplied in the TradeDetail. Not supplied in the TradeDetail. Not supplied in the TradeDetail. Not supplied in the TradeDetail allocation is not for a debt instrument. Not supplied in the TradeDetail allocation is not for a mortgage-backed security. Not supplied in the TradeDetail allocation is not for a debt instrument. Not supplied in the TradeDetail allocation is not for a debt instrument. Not supplied on the TradeDetail. Not supplied on the TradeDetail allocation does not require foreign exchange. All L1 elements pair and L2 elements for the trade components match. The trade is MATCHED. Not supplied on the TradeDetail. The allocation is for units of the traded security. Not supplied in the TradeDetail not a debt instrument. Instructing party requires deposit of the bond units in security account Not supplied in the TradeDetail because instructing party uses a security account. Not supplied in the TradeDetail. CSV File 49

50 Table 3.4 SWIFT MT541 Message Example (continued) Inbound to CTM TradeDetail XPath TradeDetailData/ SettlementTransactionConditionIndicator TypeOfTransactionIndicator SettlementTransactionConditionIndicator SettlementTransactionConditionIndicator SettlementTransactionConditionIndicator SettlementTransactionConditionIndicator Mandatory Settlement Details Outbound to Receiver CSV File Header-Data Rows Header: Settlement Transaction Condition Indicator Header: Type of Settlement Transaction Indicator Data: TRAD Header: Stamp Duty Indicator Header: Registration Override Indicator Header: Beneficial Ownership Override Indicator Header: Cash Settlement System Override Indicator Header: Forex Order Cancellation Indicator Header: Netting Eligibility Indicator Header: Central Counter Party Eligibility Indicator Header: Letter of Guarantee Indicator Header: Settlement System Method Indicator Header: Real-Time Gross Settlement System Indicator Header: Restrictions Indicator Header: Block Trade Indicator Meaning Not supplied in the TradeDetail. Settlement transaction relates to the settlement of a trade. Not supplied in the TradeDetail. Not supplied in the TradeDetail. Not supplied in the TradeDetail. Not supplied in the TradeDetail. BuySellIndicator and InstructingParty/PartyValue SecurityAccount Header: Buyer/Seller Data: BUY1/SCAMCAT1XXX Header: Buyer/Seller Safekeeping Account Data: Instructing party is the buyer and its BIC is SCAMCAT1XXX. Not supplied in the TradeDetail. CSV File 50

51 Table 3.4 SWIFT MT541 Message Example (continued) Inbound to CTM TradeDetail XPath CustodianBIC, CustodianName1, CustodianName2 SubAccountNo SubAgentBIC, ID1, or one or more of the following: SubAgentName1 and SubAgentName2 SubAgentAddress1 and SubAgentAddress2 Outbound to Receiver CSV File Header-Data Rows Header: Deliverer s/receiver s Custodian Header: Deliverer s/receiver s Custodian's Safekeeping custodian for the specified trade type Account Header: Delivering/Receiving Agent Data: DEAG/OMGOUS30XXX Meaning Not supplied in the TradeDetail instructing party does not use a global custodian for the specified trade type. Settlement occurs at Subagent BIC (DEAG) OMGOUS30XXX. Instructing party safekeeping account number is ID1, ID2 Relationship and CorrespBIC, CorrespName1, CorrespName2 Relationship, CorrespSecAccountNo PSET Cash Parties Relationship, CorrespBIC Relationship, CorrespCashAccountNo Mandatory Amounts AccruedInterestAmount/Sign, AccruedInterestAmount/CurrencyCode, AccruedInterestAmount/Amount Header: Delivering/Receiving Agent s Safekeeping Account Data: 1234 Header: Deliverer s/receiver s Intermediary Header: Deliverer s/receiver s Intermediary s Safekeeping Account Header: Place of Settlement Data: PSET/JP Header: Account with Institution Header: Cash Account Header: Accrued Interest Amount Instructing party safekeeping account number is Not supplied in the TradeDetail instructing party does not use an intermediary or correspondent for the trade type. Place of settlement is Japan. Not supplied in the TradeDetail. Not supplied in the TradeDetail. ChargeAmount/Sign, ChargeAmount/ CurrencyCode, ChargeAmount/Amount ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount TradeAmount/Sign,TradeAmount/CurrencyCode, TradeAmount/Amount Header: Charges or Fees Header: County National Federal Tax Header: Trade Amount Data: JPY , The cost of the allocation is CSV File 51

52 Table 3.4 SWIFT MT541 Message Example (continued) Inbound to CTM TradeDetail XPath CommissionReasonCode, Commission/CurrencyCode, Commission/Amount ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount CommissionReasonCode, Commission/CurrencyCode, Commission/Amount ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmoun/Amount SettlementAmount/Sign, SettlementAmount/CurrencyCode, SettlementAmount/Amount ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount ChargeAmount/Sign, ChargeAmount/CurrencyCode, ChargeAmount/Amount InstructingParty/PartyValue Place of Clearing Collateral Pool Indicator Local Tax (country specific 1) Outbound to Receiver CSV File Header-Data Rows Header: Executing Broker s Amount Header: Payment Levy Tax Header: Local Tax Header: Local Broker's Commission Data: 10000, Header: Other Amount Header: Regulatory Amount Header: Settlement Amount Data: JPY , Header: Shipping Amount Header: Special Concessions Amount Data: JPY1000, Header: Stamp Duty Header: Stock Exchange Tax Header: Transfer Tax Header: Transaction Tax Header: Value Added Tax Header: Originator of Message Data: ZYOTUS30ESN Header: Header: Header: Meaning Not supplied in the TradeDetail. Local broker commission for the allocation is Not supplied in the TradeDetail. Settlement amount, after addition of broker commission and special concession amount, is Note: The SettlementAmount composite was populated, so CTM derived the value. If the SettlementAmount had been left blank, CTM would have derived the NetCashAmount composite. Not supplied in the TradeDetail. Special concessions for the allocation total Not supplied in the TradeDetail. Not supplied in the TradeDetail. Not supplied in the TradeDetail. Originator of message is the instructing party BIC ZYOTUS30ESN. Not supplied in the TradeDetail. CSV File 52

53 FOR MORE INFORMATION DTCC Learning at: or visit us on the web at: