SDD CIRT KSEI Version v3.0.1 XCSD English
CIRT
System Design Document
Version 3.0.1 Last updated on 26/01/2018 Indonesian Central Securities Depository Information System Development Division
TABLE OF CONTENTS
TABLE OF CONTENTS ..................................................................................................................................... 2
1. FOREWORDS ......................................................................................................................................... 7
1.1 Background and Objective ............................................................................................................ 7
1.2 Scope ............................................................................................................................................. 7
2. SYSTEM OVERVIEW ............................................................................................................................... 8
3. SYSTEM ARCHITECTURE ........................................................................................................................ 8
3.1 Application Architecture ............................................................................................................... 8
3.2 Application Component ................................................................................................................ 9
3.2.1 Outgoing ................................................................................................................................ 9
3.2.2 Incoming ................................................................................................................................ 9
3.3 Socket Programming Concept ..................................................................................................... 10
3.4 Network Topology ....................................................................................................................... 11
3.5 Cross Functional Flowchart ......................................................................................................... 12
3.5.1 Outgoing Flow ..................................................................................................................... 12
3.5.2 Incoming Flow ..................................................................................................................... 13
3.6 Sequence Diagram ...................................................................................................................... 14
3.6.1 Message Sending Process (except Reconciliation) ............................................................. 14
3.6.2 Reconciliation Message Sending Process............................................................................ 15
4. MESSAGE FORMAT.............................................................................................................................. 16
4.1 Outgoing Message Format .......................................................................................................... 16
4.1.1 Over The Counter (OTC) ..................................................................................................... 16
4.1.1.1 Message Data .................................................................................................................. 16
4.1.1.2 Message Definition ......................................................................................................... 16
4.1.2 Bond Over The Counter ...................................................................................................... 17
4.1.2.1 Message Data .................................................................................................................. 17
4.1.2.2 Message Definition ......................................................................................................... 18
4.1.3 Prematch OTC ..................................................................................................................... 19
4.1.3.1 Message Data .................................................................................................................. 19
4.1.3.2 Message Definition ......................................................................................................... 19
4.1.4 Prematch Bond Over The Counter ...................................................................................... 20
4.1.4.1 Message Data .................................................................................................................. 20
4.1.4.2 Message Definition ......................................................................................................... 21
4.1.5 Approval of Prematching Instruction .................................................................................. 22
4.1.5.1 Message Data .................................................................................................................. 22
4.1.5.2 Message Definition ......................................................................................................... 22
4.1.6 Securities Transfer .............................................................................................................. 22
4.1.6.1 Message Data .................................................................................................................. 23
4.1.6.2 Message Definition ......................................................................................................... 23
4.1.7 Book Transfer ...................................................................................................................... 23
4.1.7.1 Message Data .................................................................................................................. 23
4.1.7.2 Message Definition ......................................................................................................... 24
4.1.8 Wire Transfer ...................................................................................................................... 24
4.1.8.1 Message Data .................................................................................................................. 24
4.1.8.2 Message Definition ......................................................................................................... 24
4.1.9 Request for Reconsile ......................................................................................................... 25
4.1.9.1 Message Data .................................................................................................................. 25
4.1.9.2 Message Definition ......................................................................................................... 25
4.1.10 Message ID Not Exist ........................................................................................................... 25
4.1.10.1 Message Data .............................................................................................................. 25
4.1.10.2 Message Definition ..................................................................................................... 26
4.1.11 Cancel Instruction ............................................................................................................... 26
4.1.11.1 Message Data .............................................................................................................. 26
4.1.11.2 Message Definition ..................................................................................................... 26
4.1.12 Voluntary Corporate Action (VCA) ...................................................................................... 26
4.1.12.1 Message Data .............................................................................................................. 26
4.1.12.2 Message Definition ..................................................................................................... 27
4.1.13 Collateral Deposit (COLDS) .................................................................................................. 27
4.1.13.1 Message Data .............................................................................................................. 27
4.1.13.2 Message Definition ..................................................................................................... 28
4.1.14 Lendable Deposit (LENDS) ................................................................................................... 28
4.1.14.1 Message Data .............................................................................................................. 28
4.1.14.2 Message Definition ..................................................................................................... 29
4.1.15 Investor Static Data Creation .............................................................................................. 29
4.1.15.1 Message Data .............................................................................................................. 29
4.1.15.1.1 Message Data For Individual Creation .................................................................... 29
4.1.15.1.2 Message Data For Institutional Creation ................................................................ 31
4.1.15.2 Message Definition ..................................................................................................... 33
4.1.15.2.1 Message Definition For Individual Creation ........................................................... 33
4.1.15.2.2 Message Definition For Institutional Creation ........................................................ 38
4.2 Incoming Message Format .......................................................................................................... 48
4.2.1 Account ............................................................................................................................... 48
4.2.1.1 Message Data .................................................................................................................. 48
4.2.1.2 Message Definition ......................................................................................................... 48
4.2.2 Balance ................................................................................................................................ 49
4.2.2.1 Message Data .................................................................................................................. 49
4.2.2.2 Message Definition ......................................................................................................... 49
4.2.3 Corporate Action ................................................................................................................. 49
4.2.3.1 Message Data .................................................................................................................. 49
4.2.3.2 Message Definition ......................................................................................................... 50
4.2.4 Corporate Action Entitlement ............................................................................................. 52
4.2.4.1 Message Data .................................................................................................................. 52
4.2.4.2 Message Definition ......................................................................................................... 52
4.2.5 Currency .............................................................................................................................. 53
4.2.5.1 Message Data .................................................................................................................. 53
4.2.5.2 Message Definition ......................................................................................................... 53
4.2.6 Instruction ........................................................................................................................... 53
4.2.6.1 Message Data .................................................................................................................. 53
4.2.6.2 Message Definition ......................................................................................................... 54
4.2.7 Interest Payment ................................................................................................................. 55
4.2.7.1 Message Data .................................................................................................................. 55
4.2.7.2 Message Definition ......................................................................................................... 55
4.2.8 Member .............................................................................................................................. 56
4.2.13.2 Message Definition ..................................................................................................... 62
4.2.18.1 Message Data .............................................................................................................. 67
4.2.18 Investor Account Statement ............................................................................................... 66
4.2.17.2 Message Definition ..................................................................................................... 66
4.2.17.1 Message Data .............................................................................................................. 66
4.2.17 Message ID for Reconsile .................................................................................................... 66
4.2.16.1 Message Data .............................................................................................................. 65
4.2.16 Acknowledgement .............................................................................................................. 65
4.2.15.2 Message Definition ..................................................................................................... 65
4.2.15.1 Message Data .............................................................................................................. 64
4.2.15 Tech Instruction .................................................................................................................. 64
4.2.14.2 Message Definition ..................................................................................................... 64
4.2.14.1 Message Data .............................................................................................................. 64
4.2.14 Securities Price .................................................................................................................... 63
4.2.13.1 Message Data .............................................................................................................. 61
4.2.8.1 Message Data .................................................................................................................. 56
4.2.13 Securities ............................................................................................................................. 61
4.2.12.2 Message Definition ..................................................................................................... 61
4.2.12.1 Message Data .............................................................................................................. 61
4.2.12 System Date ........................................................................................................................ 61
4.2.11.2 Message Definition ..................................................................................................... 61
4.2.11.1 Message Data .............................................................................................................. 60
4.2.11 Prematch ............................................................................................................................. 60
4.2.10.2 Message Definition ..................................................................................................... 60
4.2.10.1 Message Data .............................................................................................................. 59
4.2.10 Position Movement ............................................................................................................. 59
4.2.9.2 Message Definition ......................................................................................................... 58
4.2.9.1 Message Data .................................................................................................................. 57
4.2.9 OTC Bonds ........................................................................................................................... 57
4.2.8.2 Message Definition ......................................................................................................... 57
4.2.18.2 Message Definition ..................................................................................................... 67
4.2.19 Static Data Investor Instruction .......................................................................................... 68
4.2.19.1 Message Data .............................................................................................................. 68
4.2.19.1.1 Message Data For Individual Creation .................................................................... 68
4.2.19.1.2 Message Data For Institutional Creation ................................................................ 70
4.2.19.2 Message Definition ..................................................................................................... 72
4.2.19.2.1 Message Definition For Individual Creation ........................................................... 72
4.2.19.2.2 Message Definition For Institutional Creation ........................................................ 74
4.2.20 Transaction Type List (ISO Code) ........................................................................................ 78
5. Changes in Specification ..................................................................................................................... 80
1. FOREWORDS
1.1 Background and Objective
Currently, t he clients’ use of C-BEST system for securities transactions delivery are increasing in numbers, resulting in the increase of transactions volume through C-BEST system. In that regard, participants now require an information technology system which may provide an efficient interface mechanism from the participants
’ internal system to C-BEST. This CIRT System Design document act as references to participants, in developing the CIRT system to efficiently facilitate the transaction delivery from participants’ internal system to C-BEST, and vice versa.
Implementation of this system is expected to provide an added value, such as the elimination of dual-entry and minimizing human-error which resulted from dual-entry. The outgoing transactions entered through participants
’ internal system will be forwarded by the CIRT to C-BEST. In reverse, the C- BEST incoming transactions that goes through the CIRT system will be forwarded to the participant s’ internal system by C-BEST Interface for further processing. Before being processed, both outgoing and incoming transactions will be validated and managed, based on prevailing regulations and predefined parameters.
1.2 Scope
The scope of this document is to explain the CIRT system design to be developed by vendors and respective participants. The CIRT development of participant s’ internal system for data exchange, is handed to each respective participant (may be managed through vendors or internal developer).
2. SYSTEM OVERVIEW
CIRT is a system which connects C-BEST with the participants’s internal system for message instruction delivery from the participants’s internal system to CIRT, and vice versa. The message structure being delivered and received by CIRT system, is in acordance with the standard format determined on the document.
There are 2 (two) types of transactions on the C-BEST Interface system, namely : 1. Outgoing Transaction, an instruction message delivered from participants’s internal system to CIRT system.
2. Incoming Transaction, an instruction message delivered from the CIRT system to participants’s internal system.
The connection between CIRT system and internal system may be seen on the picture below: The CIRT system at KSEI will communicate with the participants’s internal system, using the TCP/IP protocol on leased line network. The incoming transaction from the internal system will be forwarded to CIRT. In reverse, the outgoing transaction from CIRT system will be forwarded to the internal system.
3. SYSTEM ARCHITECTURE
3.1 Application Architecture
The above diagram illustrates the entire application architecture on C-BEST server and Back-office server. The C-BEST server will be connected with the internal system at the Back-office. Communication between CIRT and the Internal System uses a socket connection.
3.2 Application Component
3.2.1 Outgoing
3.2.2 Incoming
The definitions of related components on the above pictures, are as follows : Business Component, which is a layer for methods related to the business process of the system. Data Access Component, which is a layer related to the access process to the database, such as insert, update and delete record. Socket, which is the endpoint of a two-way communications between two running programs on the network. A socket is inserted through a port, so that the TCP layer could identify the application suitable for the delivered data. The message delivery between CIRT and the Internal System uses the socket programming mechanism. As an indicator to differentiate different messages in a single delivery time, each message should be ended with a suffix fixed length (4 bytes). The format of data delivered through a socket is as illustrated below:
Fixed size Message Suffix Message Suffix Variable size
Suffix in hexadecimal format is : {FF, FE, FD, FC} The message structure can be viewed at the message format section. Suffix is a byte array delivered after the instruction message was sent. The format of suffix delivered should follow the above format.
3.3 Socket Programming Concept
Socket is the endpoint of two-way communication between two running applications in the network. A
socket is inserted through a port so that the TCP layer could identify which application suits the
delivered data. At the time when an application communicates, the application would first create a new socket before being given a reference number to be used as a socket reference. If there is a system which uses the socket reference number, a communication network between computers will be established with an equal quality to local data transfers.
The communication using socket between the CIRT application with the Internal System, is illustrated as follows: To communicate with Internal System application, CIRT application must recognize the Internal
System’s IP number and the destination port number, which shows the running service. In this case, the incoming and outgoing messages process uses the same pathway. The port for Internal System and CIRT will be set according to the needs, in the form of parameterize.
3.4 Network Topology
The back-office server will communicate with the available CIRT appplication in KSEI, through Leased Channel, Microwave, ISDN, Dial up Modem or Fiber Optic.
3.5 Cross Functional Flowchart
3.5.1 Outgoing Flow
3.5.2 Incoming Flow
CIRT sends messages to Back Office asynchronously, then Back Office needs to check the
uniqueIdentifier field and the lastUpdateTimestamp field. uniqueIdentifier field is an unique ID for each
instruction which sent from C-BEST while lastUpdateTimestamp field shows the instruction’s modification time. lastUpdateTimestamp field could determine the order of messages sent from C-BEST to Back Office through CIRT. If Back Office receives a new message which its lastUpdateTimestamp value is older than the latest processed, then the new message shouldn’t trigger the Back Office’s system to replace the existing instruction’s status.
For example: Back office receives a message with uniqueIdentifier ‘ABCD’ which has
lastUpdateTimestamp value
‘20140102101000000’ and its status is ‘Ready for Positioning’. A moment later, Back Office receives a new message with uniqueIdentifier ‘ABCD’ which has lastUpdateTimestamp value ‘2014102100900000’ and its status is ‘Validated’. Based on our knowledge above, the latest message should not be processed and not change the instruction’s status. Instruction with
uniqueIdentifier ‘ABCD’ will retain its status, that is ‘Ready for Positioning’.
3.6 Sequence Diagram
3.6.1 Message Sending Process (except Reconciliation)
3.6.2 Reconciliation Message Sending Process
4. MESSAGE FORMAT
4.1 Outgoing Message Format
4.1.1 Over The Counter (OTC) This Message is sent by CIRT for OTC instruction upload.
4.1.1.1 Message Data
<Message name="OTC" type="OutgoingMessage"> <Record name="data">
<Field name="externalReference">TESTING_001</Field> <Field name="instructionType">DVP</Field> <Field name="participantCode">9X000</Field> <Field name="participantAccount">9X000000400154</Field> <Field name="participantAccountCash">9X000000400154</Field> <Field name="counterpartCode">LG001</Field> <Field name="securityCodeType">LOCAL</Field> <Field name="securityCode">TLKM</Field> <Field name="numberOfSecurities">1000.25</Field> <Field name="tradeDate">20170228</Field> <Field name="currencyCode">IDR</Field> <Field name="settlementAmount">10000000</Field> <Field name="settlementDate">20170228</Field> <Field name="description">TESTING_001 Description</Field> <Field name="purpose">EXCHG</Field> <Field name="tradingReference"></Field> <Field name="settlementReason"></Field>
</Record> </Message>
4.1.1.2 Message Definition
Message name="OTC"
Field Name Status Data Type Length Description
externalReference M Character
35 External Reference Data instructionType M Character
10 DVP, RVP, DFOP, RFOP participantCode M Character
5 Participant’s Member Code participantAccount M Character
14 Participant’s Account Code participantAccountCash C Character
14 Participant’s Account Cash Mandatory for USD/SGD instructions counterpartCode M Character
5 Counterpart’s Member Code securityCodeType M Character
10 LOCAL, ISIN or ISO securityCode M Character
20 Security Code numberOfSecurities O Numeric
32.4 Amount of Securities tradeDate M Character 8 yyyyMMdd. Past Date currencyCode M Character
3 Currency Code in ISO Format settlementAmount M Numeric
32.4 Amount of Cash settlementDate M Character 8 yyyyMMdd description O Character 240 Free Description purpose C Character
8 EXCHG or NONEXCHG.
Mandatory for FOP tradingReference C Character
16 Mandatory for EXCHG settlementReason C Character
4 Mandatory for NONEXCHG
Description: M = Mandatory O = Optional C = Conditional
4.1.2 Bond Over The Counter This Message is sent by CIRT for OTC Bond instruction upload.
4.1.2.1 Message Data
<Message name="OTCBond" type="OutgoingMessage"> <Record name="data">
<Field name="externalReference">20170228_9X000_001</Field> <Field name="instructionType">DVPBOND</Field> <Field name="participantCode">9X000</Field> <Field name="participantAccount">9X000000100161</Field> <Field name="participantAccountCash">9X000000100161</Field> <Field name="counterpartCode">UOBB1</Field> <Field name="counterpartType">INTERNAL</Field> <Field name="taxSubmittedbyKSEI">N</Field> <Field name="securityCodeType">LOCAL</Field> <Field name="securityCode">FR0015</Field> <Field name="currencyCode">IDR</Field> <Field name="maturityDate">20110215</Field> <Field name="tradeDate">20070913</Field> <Field name="settlementDate">20070913</Field> <Field name="faceValue">1000000</Field> <Field name="price">98</Field> <Field name="yield">2</Field> <Field name="interestRate">13.4</Field> <Field name="accruedDays">31</Field> <Field name="accruedInterest">11288</Field> <Field name="miscAmount"></Field> <Field name="capitalGainTax">100000</Field> <Field name="accruedInterestTax">1000.25</Field>
<Field name="netProceeds">890288.75</Field> <Field name="description">TEST UPLOAD</Field> <Field name="ctpReference">HYUB_101222_OTB01</Field> <Field name="purpose">EXCHG</Field> <Field name="tradingReference">AB002160214-9999</Field> <Field name="settlementReason"></Field>
</Record> </Message>
4.1.2.2 Message Definition
Field Name Status Data Type Length Description
32.4 Face Value price M Numeric
8 EXCHG or NONEXCHG.
20 CTP Reference purpose C Character
32.4 Net Proceeds ctpReference M Character
32.4 Accrued Interest Tax netProceeds O Numeric
32.4 Capital Gain Tax accruedInterestTax O Numeric
32.4 Miscellanious Amount capitalGainTax M Numeric
32.4 Accrued Interest miscAmount O Numeric
10 Accrued Days accruedInterest M Numeric
8.3 Interest Rate accruedDays M Numeric
32.5 Yield interestRate M Numeric
11.5 Price yield M Numeric
3 Currency Code in ISO Format maturityDate M Character 8 yyyyMMdd tradeDate M Character 8 yyyyMMdd settlementDate M Character 8 yyyyMMdd faceValue M Numeric
externalReference M Character
Message name="OTCBond"
10 LOCAL, ISO or ISIN securityCode M Character
1 Y = Yes, N = No securityCodeType M Character
40 INTERNAL or EXTERNAL taxSubmittedbyKSEI M Character
5 Counterpart’s Member Code counterpartType M Character
Mandatory for VPBOND counterpartCode M Character
14 Participant’s Cash Account Code.
14 Participant’s Account Code participantAccountCash C Character
5 Participant’s Member Code participantAccount M Character
10 DVPBOND, RVPBOND, DFOPBOND, RFOPBOND participantCode M Character
35 External Reference Data instructionType M Character
20 Security Code currencyCode M Character
Mandatory For FOP tradingReference C Character 100 Mandatory if field purpose is EXCHG settlementReason C Character 100 Mandatory if field purpose is NONEXCHG
Description: M = Mandatory O = Optional C = Conditional
4.1.3 Prematch OTC This Message is sent by CIRT for OTC prematch instruction upload.
4.1.3.1 Message Data
<Message name="PrematchOTC" type="OutgoingMessage"> <Record name="data">
<Field name="externalReference">YPS-UP-DVP-01A</Field> <Field name="instructionType">DVP</Field> <Field name="participantCode">9X000</Field> <Field name="participantAccount">9X000000100161</Field> <Field name="participantAccountCash"></Field> <Field name="counterpartCode">LG001</Field> <Field name="securityCodeType">LOCAL</Field> <Field name="securityCode">TLKM</Field> <Field name="numberOfSecurities">1000</Field> <Field name="tradeDate">20170215</Field> <Field name="currencyCode">IDR</Field> <Field name="settlementAmount">1250000</Field> <Field name="settlementDate">20170215</Field> <Field name="description"></Field> <Field name="purpose">EXCHG</Field> <Field name="tradingReference">AB002160214-9999</Field> <Field name="settlementReason"></Field>
</Record> </Message>
4.1.3.2 Message Definition
Message name="PrematchOTC"
Field Name Status Data Type Length Description
externalReference M Character
35 External Reference Data instructionType M Character
10 DVP, RVP, DFOP, RFOP participantCode M Character
5 Participant’s Member Code participantAccount M Character
14 Participant’s Account Code participantAccount C Character
14 Participant’s Account
Code. Mandatory for USD and SGD counterpartCode M Character
5 Counterpart’s Member Code securityCodeType M Character
10 LOCAL, ISO or ISIN securityCode M Character
20 Security Code numberOfSecurities O Numeric
32.4 Amount of Securities tradeDate M Character
8 YYYYMMDD currencyCode M Character
3 IDR, USD, and Other Countries’ Currency Code settlementAmount M Numeric
32.4 Amount of Securities settlementDate M Character
8 YYYYMMDD description C Character 240 Mandatory if SettlementReason is OTHR purpose C Character
8 Mandatory for FOP (EXCHG or NONEXCHG) tradingReference C Character
16 Mandatory if purpose is EXCHG settlementReason C Character 100 Mandatory if purpose is NONEXCHG
Description: M = Mandatory O = Optional C = Conditional
4.1.4 Prematch Bond Over The Counter This Message is sent by CIRT for OTC Bond instruction upload.
4.1.4.1 Message Data
<Message name="PrematchOTCBond"type="OutgoingMessage"> <Record name="data">
<Field name="externalReference">YPS_UP_DVPB_01B</Field> <Field name="instructionType">DVPBOND</Field> <Field name="participantCode">9X000</Field> <Field name="participantAccount">9X000000100161</Field> <Field name="participantAccountCash">9X000000100161</Field> <Field name="counterpartCode">LG001</Field> <Field name="counterpartType">INTERNAL</Field> <Field name="securityCodeType">LOCAL</Field> <Field name="securityCode">FR0050</Field> <Field name="currencyCode">IDR</Field> <Field name="maturityDate">20201015</Field> <Field name="tradeDate">20170220</Field> <Field name="settlementDate">20170220</Field> <Field name="faceValue">1000000</Field> <Field name="price">101</Field>
<Field name="interestRate">10</Field> <Field name="accruedDays">25</Field> <Field name="accruedInterest">33333</Field> <Field name="accruedInterestTax">1500</Field> <Field name="miscAmount">10000</Field> <Field name="netProceeds">1036833</Field> <Field name="taxSubmittedbyKSEI">Y</Field> <Field name="capitalGainTax">15000</Field> <Field name="description"></Field> <Field name="yield">5</Field> <Field name="ctpReference">HYUB_101222_OTB01</Field> <Field name="purpose">EXCHG</Field> <Field name="tradingReference">AB002160214-9999</Field>
<Field name="settlementReason"></Field> </Record>
</Message>
4.1.4.2 Message Definition
Field Name Status Data Type Length Description
8 YYYYMMDD tradeDate M Character
32.4 Miscellanious Amount
32.4 Accrued Interest Tax miscAmount O Numeric
32.4 Accrued Interest accruedInterestTax M Numeric
10 Accrued Days accruedInterest M Numeric
20.1 Interest Rate accruedDays M Numeric
11.5 Price interestRate M Numeric
32.4 Face Value price M Numeric
8 YYYYMMDD faceValue M Numeric
8 YYYYMMDD settlementDate M Character
3 IDR, USD, and Other Countri es’ Currency Code maturityDate M Character
externalReference M Character
20 Data Security Code currencyCode M Character
Message name="PrematchOTCBond"
10 INTERNAL or EXTERNAL securityCodeType M Character
5 Participant’s Account Code counterpartType M Character
14 Participant’s Member Code counterpartCode M Character
14 Participant’s Account Code participantAccountCash C Character
5 Participant’s Member Code participantAccount M Character
10 DVPBOND, RVPBOND, DFOPBOND, RFOPBOND participantCode M Character
35 External Reference Data instructionType M Character
10 LOCAL or ISO securityCode M Character netProceeds M Numeric
32.4 Net Proceeds taxSubmittedbyKSEI M Character
4.1.5 Approval of Prematching Instruction This Message is sent by CIRT for prematch approval instruction upload.
4.1.5.2 Message Definition
O = Optional
1 A = Approve; R= Reject Description: M = Mandatory
35 External Reference Data approveOrReject M Character
35 External Reference Data uniqueIdentifier M Character
externalReference M Character
Field Name Status Data Type Length Description
Message name="PrematchApproval"
</Record> </Message>
5 Tax Submitted by KSEI capitalGainTax M Numeric
<Field name="externalReference">YPS-UP-DFOP-01</Field> <Fieldname="uniqueIdentifier"> YPS-UP-DFOP-01</Field> <Field name="approveOrReject">A</Field>
<Message name="PrematchApproval" type="OutgoingMessage"> <Record name="data">
4.1.5.1 Message Data
Description: M = Mandatory O = Optional C = Conditional
8 Mandatory for FOP EXCHG or NONEXCHG tradingReference C Character 100 Mandatory if field purpose is EXCHG settlementReason C Character 100 Mandatory if field purpose is NONEXCHG
20 CTP Reference purpose C Character
32.5 Yield ctpReference M Character
32.4 Capital GainTax description C Character 240 Mandatory if settlementReason is OTHR yield M Numeric
4.1.6 Securities Transfer This Message is sent by CIRT for securities transfer instruction upload.
4.1.6.1 Message Data
<Message name="SecuritiesTransfer" type="OutgoingMessage"> <Record name="data">
<Field name="externalReference">TESTING_SECTRS</Field> <Field name="participantCode">9X000</Field> <Field name="sourceAccount">9X000000000131</Field> <Field name="targetAccount">9X000000100161</Field> <Field name="securityCodeType">LOCAL</Field> <Field name="securityCode">ASII</Field> <Field name="numberOfSecurities">1500.2</Field> <Field name="settlementDate">20080228</Field> <Field name="description">TESTING_SECTRS_DESC</Field>
</Record> </Message>
4.1.6.2 Message Definition
Message name="SecuritiesTransfer"
Field Name Status Data Type Length Description
externalReference M Character
35 External Reference Data participantCode M Character
5 Participan t’s Member Code sourceAccount M Character
14 Source Account Code targetAccount M Character
14 Target Account Code securityCodeType M Character
10 LOCAL, ISO or ISIN securityCode M Character
20 Security Code numberOfSecurities O Numeric
32.4 Amount of Securities settlementDate M Character 8 yyyyMMdd description O Character 240 Free Description
Description: M = Mandatory O = Optional
4.1.7 Book Transfer This Message is sent by CIRT for book transfer instruction upload.
4.1.7.1 Message Data
<Message name="BookTransfer" type="OutgoingMessage"> <Record name="data">
<Field name="externalReference">TESTING_BTS</Field> <Field name="instructionType">BTS</Field> <Field name="participantCode">9X000</Field> <Field name="participantAccount">9X000000000131</Field> <Field name="counterpartAccount">9X000000100161</Field> <Field name="valueDate">20170228</Field> <Field name="currencyCode">IDR</Field> <Field name="cashAmount">10000.15</Field>