07.18 Networking for Equities Transfer Agent Approve/Update Active Transactions ICM (NFT1 & NFT5) Function User s Guide

Transcription

1 CCF/CCF-II/MQ Series Transmission Guides Networking for Equities Transfer Agent Approve/Update Active Transactions ICM (NFT1 & NFT5) Function User s Guide The Depository Trust Company July 2003

2 ( DTC ). All rights reserved. This work is proprietary and is intended for the exclusive use of DTC s Participants and other users of DTC s services. No part of this work may be reproduced or distributed (including by transmission) in any form or by any means, or stored in any information storage and retrieval system, without DTC s prior written permission. All requests for additional copies of this work or inquiries about this work should be directed to DTC Participant Interface Planning, The Depository Trust Company, 55 Water Street, New York, NY 10041, USA NFT1/NFT5: FUNCTION USER'S GUIDE Page ii July 2003

3 Revision History Date By Version Description July, 2003 blue2man 1 Document created NFT1/NFT5: FUNCTION USER'S GUIDE Page iii July 2003

4 Table of Contents Section Page 1.0 Overview Availability of NFT1 and NFT The ICM Header Record The NFT1/NFT5 Detail Record Error Conditions Error Codes and Description Appendix NFT1/NFT5: FUNCTION USER'S GUIDE Page iv July 2003

5 1.0 Overview This document describes how transfer agents can use the ICM service to take upon their active NFE deposit transactions for dematerialization. This function is available over CCF, CCF-II and MQ Series. This is a combined User Guide for CCF, CCF-II, and MQ Series. It is recommended that agents familiarize themselves with the DTC document Interface Control Management CCF, CCF-II and MDH User's Guide for Transaction Input. This Interface Control Management (ICM) document describes new standards for transaction processing using DTC's automated systems, including specifics relating to operation, error processing and recovery for CCF, CCF-II and MDH transmissions. The NFT1/NFT5 function provides the transfer agents with a means to update, approve, fully reject, or partial approve/reject their active broker controlled or non-broker controlled NFE deposit transaction. An NFE Transaction is a group of records that identifies one NFE deposit. Each transaction will consist of the following: One transaction header record record type 01 One to fifty certificate records record type 88 One to ninety nine transfer agent comment record record type 89 One trailer record marking the end of that transaction - record type 99 NFE deposit transaction file processing: Transmitting an NFE deposit transaction to DTC. 1) Only NFE deposit transactions the have been modified should be returned to DTC. 2) All record types and all occurrences of record type 88 retrieved by DTF function NFTAFL must be returned to DTC. 3) One blank record type 89 will be retrieved by DTF function NFTAFL, but up to ninetynine completed comment records can be transmitted back to DTC. 4) All numeric fields must be right justified with leading zeros. 5) All alphanumeric fields must be left justified with trailing spaces. FILE LENGTH ICM HEADER = 26 BYTES NFT1/NFT5 USER DATA = 1290 BYTES TOTAL FILE LENGTH = 1316 BYTES NFT1/NFT5 USER'S GUIDE Page 1 July 2003

6 1.1 Availability of NFT1 and NFT5 Interface Function Name Available from: Available to: MQ Series NFT1 18:00 23:00 CCF NFT5 18:00 23:00 CCF-II NFT5 18:00 23: NFT1/NFT5 USER'S GUIDE Page 2 July 2003

7 1.2 The ICM Header Record The field layout of the 26-byte header is defined as: Position Length Format Field Name CCF Header Record Description 1 1 Character Feedback Indicator Leave blank on input. On output indicates whether any errors were encountered during processing. 2 1 Character Production/Test Indicator (Required) indicator of whether the transaction is to be processed in the Test or Production environment. P = Production T = Test 3 6 Character Record Type Value = NFTAFL Numeric Record Suffix Indicates the record # on single and multiple data records within a transaction. 2 Numeric Version Number 6 Numeric User Reference Number Used to indicate which version (for example, latest or previous format) the data is in: must be 01 (Optional) used by transmitting party to uniquely identify the transaction. 8 Character Addressee (Required) CCF Sign-on used to transmit this file NFT1/NFT5 USER'S GUIDE Page 3 July 2003

8 2.0 The NFT1/NFT5 Detail Record Position Length Format Field Name NFT1/NFT5 Transfer Agent Daily Active Customer Account Approve/Update Detail Record Description Networking for Equities Transfer Agent Daily Active Transaction Approve/Update Customer Account Record Layout Length CUSTOMER ACCOUNT HEADER RECORD Type 01 layout follows: 27 8 Numeric 9(8) Transfer Agent ID (Required)- Transfer Agent identification number Numeric NFE Transaction ID (Required) - DTC generated number that uniquely identifies NFE transaction at DTC. Format: YYJJJNNNNN (year, Julian date, a sequence number count) Numeric 55 2 Character Transaction 57 2 Numeric 9(2) TA Transaction ID (Required) - Transfer agent generated number that uniquely identifies NFE transactions at the Transfer Agent. Format: YYJJJNNNNN (year, Julian date, a sequence number count) Record Type Transaction Record Sequence Number 59 1 Character Transaction Action Type Code (Required) - Value: 01 Customer account information record (Required) - Value: 00 for 01 record type (Required) - Defines the action to be taken on the transaction: Values: N no actions on 01-record A approve NFE transaction (implies all certificates) R reject NFE transaction (implies all certificates) P partially approve/reject NFE transaction (each certificate record must have an A or R for Approve / Reject ) U update 01-record information (at least one of the 01- record s updateable fields must be changed). (See attached appendix) 60 8 Numeric Participant ID (Required) - Participant Identification number 9(8) 68 9 Character CUSIP (Required) - 9-character Security CUSIP number Character Participant Contact Name (Required) - Name of the person responsible for this transaction at the participant NFT1/NFT5 USER'S GUIDE Page 4 July 2003

9 Position Length Format Field Name NFT1/NFT5 Transfer Agent Daily Active Customer Account Approve/Update Detail Record Description Numeric Character Participant Contact Telephone Extension Participant Contact (Required) - Telephone number of the person responsible for Telephone Number this transaction at the participant. (Optional) - Telephone extension of the person responsible for the transaction at the participant Character User CUSIP (Optional) - Participant s security identification number Format: Position 1 through 2 = US Position 3 through 11 = SECURITY CUSIP NUMBER Position 12 = Numeric 9(11)V9(5) Transaction Quantity Character Account Control Code Character Investor Account ID Character Tax ID Update Indicator Numeric 9(9) Numeric 9(2) Investor Tax ID Certificate Count (Required) Transaction total share quantity (Required) Indicates the account is under the brokers control or the investors control. Value: B - Broker Control I Investor Control (Required) - Investor s account identifier at the participant. (Required) - Indicates whether TA updated Customer Tax ID. Value: Y update occurred (Required) Investors tax id (Required) - The number of certificates associated with the NFE transaction. Value: 1 to Character Transaction Status (Required) - Transaction status code on DTC database: Value: 05 - pending TA approval 06 approved by TA 07 partially approved by TA Character Media Type (Required) - Communication media type code Value: P PTS C CCF R created by special request Character SCL ID (Optional) - Shipment Control List identification number Character Entry Timestamp (Required) - Timestamp at the time the NFE Transaction was entered. Format: CCYY-MM-DD-HH.MM.SS.NNNNNN - format Character Restriction Indicator (Required) - Defines the certificates as free or restricted. Value: F free R restricted NFT1/NFT5 USER'S GUIDE Page 5 July 2003

10 Position Length Format Field Name NFT1/NFT5 Transfer Agent Daily Active Customer Account Approve/Update Detail Record Description Character Affiliate Update Indicator (Required) - Indicates whether TA updated Affiliate indicator. Value Y update occurred Character Affiliate Indicator (Optional) - Determines whether the customer has an affiliation with the issuer of the certificates. Value: Y - Affiliated N No affiliation Space - nothing entered Character Participant Comments Character Registration Update Indicator Character Certificate Registration Character TA Account Update Indicator Character TA Customer Account ID Character Reject Info Update Indicator Numeric 9(3) Reject Reason Code (Optional) Comments entered by the participant (Required) - Indicates whether TA updated Certificate Registration Text. Value: Y update occurred (Required) Certificate registration (Required) - Indicates whether TA Customer Account ID updated Value: Y update occurred N No update. (Optional) Customer account identifier at the transfer agent. Only required when certificate lock up information is entered. (Required) - Indicates whether TA provided rejected information for fully rejected or partial approved/rejected transactions. Value: Y TA provided reject info (Required only for rejected or partial approved/rejected transactions) Uniquely identifies the reason for fully rejected or partial rejected transactions. A reject reason code, reject reason text or both must be entered for fully rejected or partial rejected transactions. Value: '001' - Escheated '002' - Cert not on TA REC '003' Conditional stop '004' - Mixed deposit '005 - Quantity mismatch '006' No longer TA of REC '007' - Cert repl/cancelled 999 Free form text. Default: spaces NFT1/NFT5 USER'S GUIDE Page 6 July 2003

11 Position Length Format Field Name NFT1/NFT5 Transfer Agent Daily Active Customer Account Approve/Update Detail Record Description Character Free Form Reject Reason (Required only for rejected or partial approved/rejected transactions) Uniquely identifies the reason for fully rejected or partial rejected transactions. A reject reason code, reject reason text or both must be entered for fully rejected or partial rejected transactions Character TA Contact Name (Required for fully rejected or partial approve/rejected) Contact name at the transfer agent Numeric TA Contact Telephone Number (Required for fully rejected or partial approve/rejected) Contact telephone number at the transfer agent. Default: Zeros Character TA Contact Extension Number (Optional) Contact telephone number extension Character Filler RESERVED FOR DTC USE ONLY NFT1/NFT5 USER'S GUIDE Page 7 July 2003

12 Position Length Format Field Name NFT1/NFT5 Transfer Agent Daily Active Transaction Approve/Update Certificate Detail Record Description Networking for Equities Transfer Agent Daily Active Transaction Approve/Update Certificate Record Layout Length 1290 CERTIFICATE RECORD Type 88 layout follows: 27 8 Numeric 9(8) Numeric Numeric 55 2 Character Transfer Agent ID (Required) - Transfer Agent identification number. NFE Transaction ID (Required) - DTC generated number that uniquely identifies NFE transaction at DTC. Format: YYJJJNNNNN (year, Julian date, a sequence number count) TA Transaction ID (Required) - Transfer agent generated number that uniquely identifies NFE transaction at the Transfer Agent. Format: YYJJJNNNNN (year, Julian date, a sequence number count) Transaction Record Type (Required) 88 Certificate record 57 2 Numeric 9(2) Record Sequence Number (Required) - Certificate sequence number on NFE database Valid values are 01 to Character Action Type Code (Required) - Defines the action to be taken on the certificate: Value: N no action on certificate record A approve certificate R reject certificate U update certificate (at least one of the 88-record s updateable fields must be changed) Character Certificate ID Update Indicator 61 5 Character Certificate ID Prefix 66 7 Character Certificate ID Base 73 5 Character Certificate ID Suffix Numeric Certificate V9(5) Denomination 93 1 Character Certificate Issue Date Update Indicator (Required) - Indicates whether TA updated Certificate ID. Value: Y update occurred (Optional) Certificate Id prefix Value: Certificate Id prefix entered by the participant. (Required) Certificate Id base Value: Certificate base Id entered by the participant. Optional) Certificate Id suffix entered by the participant.. (Required)- Certificate denomination (Required) - Indicates whether TA updated certificate issue date. Value: Y update occurred NFT1/NFT5 USER'S GUIDE Page 8 July 2003

13 Position Length Format Field Name NFT1/NFT5 Transfer Agent Daily Active Transaction Approve/Update Certificate Detail Record Description 94 8 Numeric 9(8) Certificate Issue Date Character Certificate Acquisition Date Update Indicator Numeric 9(8) Certificate Acquisition Date Character Certificate Status Code Character Blanket Opinion Update Indicator (Required) Certificate Issue date Value: Valid business date. (Required) - Indicates whether TA updated certificate acquisition date. Value: Y update occurred (Optional) - Acquisition date by customer Value: Valid business date Default: Zeros.. (Required) - Defines the status of the certificate on NFE database: Value: - The same status as the whole transaction 2 Approved by TA 3 Rejected by TA 4 Deleted via STPU (Required) - Indicates whether TA updated blanket opinion indicator. Value: Y update occurred Character Blanket Indicator (Required) - Indicates whether opinion of counsel at TA is on file or not required Value: N - not required Y on file at TA Character Certificate Restriction Update Indicator Character Certificate Restriction Code # Character Certificate Restriction Code # Character Certificate Restriction Code #3 (Required) - Indicates whether TA updated certificate restrictions. Value: Y update occurred (Optional) - Restriction codes used by the Participant Valid values are: '144 ', 144A ', '144K ', '145 ', '701 ', 'AFFL ', 'REG S', 'RESG ', 'S-3 '.. (Optional) - Restriction codes used by the Participant Valid values are: '144 ', 144A ', '144K ', '145 ', '701 ', 'AFFL ', 'REG S', 'RESG ', 'S-3 '.. (Optional) - Restriction codes used by the Participant Valid values are: '144 ', 144A ', '144K ', '145 ', '701 ', 'AFFL ', 'REG S', 'RESG ', 'S-3 ' NFT1/NFT5 USER'S GUIDE Page 9 July 2003

14 Position Length Format Field Name NFT1/NFT5 Transfer Agent Daily Active Transaction Approve/Update Certificate Detail Record Description Character Certificate Free Form Restriction Character LOCKUP Information Update Indicator Character Book Lot Number # Character Lockup Date # Numeric V9(5) Lot Shares # Character Lift Date # Character Book Lot Number # Character Lockup Date # Numeric 9(10V9(5) Lot Shares # Character Lift Date # Character Book Lot Number #3 (Optional) - Free form certificate restriction text entered in addition to or instead of restriction codes.. (Required) - Indicates whether TA updated certificate LOCKUP information. Value: Y update occurred (Optional) - Book lot/receipt number within TA account only required when Lock-up information has been entered. Default: spaces. (Optional) Certificate lock-up date required when lock-up Value: valid future date (Optional) Locked up Lot share quantity required when lockup Default: Zero. (Optional) The date when the lock is lifted. Default: spaces (Optional) - Book lot/receipt number within TA account only required when Lock-up information has been entered. Default: spaces. (Optional) Certificate lock-up date required when lock-up Value: valid future date (Optional) Locked up Lot share quantity required when lockup Default: Zero. (Optional) - The date when the lock is lifted. Default: spaces (Optional) - Book lot/receipt number within TA account only required when Lock-up information has been entered. Default: spaces NFT1/NFT5 USER'S GUIDE Page 10 July 2003

15 Position Length Format Field Name NFT1/NFT5 Transfer Agent Daily Active Transaction Approve/Update Certificate Detail Record Description Character Lockup Date # Numeric V9(5) Lot Shares # Character Lift Date # Character Book Lot Number # Character Lockup Date # Numeric V9(5) Lot Shares # Character Lift Date # Character Book Lot Number # Character Lockup Date # Numeric V9(5) Lot Shares #5 (Optional) Certificate lock-up date required when lock-up Value: valid future date (Optional) Locked up Lot share quantity required when lockup Default: Zero. (Optional) - The date when the lock is lifted. Default: spaces (Optional) - Book lot/receipt number within TA account only required when Lock-up information has been entered. Default: spaces. (Optional) Certificate lock-up date required when lock-up Value: valid future date (Optional) Locked up Lot share quantity required when lockup Default: Zero. (Optional) - The date when the lock is lifted. Default: spaces (Optional) - Book lot/receipt number within TA account only required when Lock-up information has been entered. Default: spaces. (Optional) Certificate lock-up date required when lock-up Value: valid future date (Optional) Locked up Lot share quantity required when lockup Default: Zero Character Lift Date #5 (Optional) - The date when the lock is lifted. Default: spaces Character Filler RESERVED FOR DTC USE ONLY NFT1/NFT5 USER'S GUIDE Page 11 July 2003

16 Position Length Format Field Name NFT1/NFT5 Transfer Agent Daily Active Transaction Comment Detail Record Description Networking for Equities Transfer Agent Daily Active Transaction Approve/Update Comment Record Layout Length 1290 COMMENT RECORD Type 89 layout follows: 27 8 Numeric 9(8) Numeric Numeric 55 2 Character Transfer Agent ID NFE Transaction ID TA Transaction ID Transaction Record Type (Required) Transfer Agent identification number. (Required) DTC generated number that uniquely identifies NFE transaction at DTC. Format: YYJJJNNNNN (year, Julian date, a sequence number count) (Required) Transfer agent generated number that uniquely identifies NFE transaction at the Transfer Agent. Format: YYJJJNNNNN (year, Julian date, a sequence number count) (Required) - 89 TA message record 57 2 Numeric 9(2) Record Sequence number (Required) - TA message record occurrence Valid values from 01 to Character Action Type Code (Required) Defines the action to be taken on the message: Value: N no action U add new TA message Character TA Contact Name (Required for action code U ) Character TA Contact (Required for action code U ) Telephone Number 90 4 Character TA Contact (Optional) Extension Number Character TA Message Text (Required for action code U ) Character Filler RESERVED FOR DTC USE ONLY NFT1/NFT5 USER'S GUIDE Page 12 July 2003

17 Position Length Format Field Name NFT1/NFT5 Transfer Agent Daily Active Transaction Trailer Detail Record Description Networking for Equities Transfer Agent Daily Open Transaction Approve/Update Transaction Trailer Record Layout Length TRAILER Record Type 99 layout follows: 27 8 Numeric 9(8) Numeric Numeric 55 2 Character Transfer Agent ID (Required) - Transfer Agent identification number. NFE Transaction ID (Required) DTC generated number that uniquely identifies NFE transaction Format: YYJJJNNNNN (year, Julian date, a sequence number count) TA Transaction ID (Required) Transfer agent generated number that uniquely identifies NFE transaction at the Transfer Agent. Format: YYJJJNNNNN (year, Julian date, a sequence number count) Transaction Record Type (Required) 99 trailer record 57 2 Numeric 9(2) Record Sequence Number (Required) Value: 00 - Valid value for trailer record 59 1 Character Action Type Code (Required) N default for trailer record Character Filler RESERVED FOR DTC USE ONLY NFT1/NFT5 USER'S GUIDE Page 13 July 2003

18 3.0 Error Conditions 3.1 Error Codes and Description In the case of errors that occur during processing, the following occurs: CCF/CCF II Users receive their input record with 40 bytes of errors appended to the end of the record. MQ Series users receive a maximum of a 121 byte record consisting of: 50 byte ICM Ack Record 26 byte ICM Header Record 5 byte sequence number 8 byte error code with a maximum of 5 occurrence s (possible total of 40 bytes). The following table lists errors that can be received during the edit of an NFE Participant New Transaction record. This error list describes both the Field Identifier and the Error Code. These codes are defined in the DTF files: ICMFLD for Field Identifiers, ICMERR for Error Codes. Note: Refer to the Interface Control Management document for specifics relating to the way errors are returned to your system. Data Field in Error Error Description Field Code Message Code Function Type Function is not NFTAFL EAA7 9AAA Record Type Missing record type AAAB 9ADB Record Type Invalid record type AAAB 9AAA ICM-UPD-FUNC-NAME Function is not NFT1 or NFT5 JAAA 9AAL Transfer agent number Transfer agent number is invalid. CAA6 9AAA Transfer agent number Transfer agent is not numeric CAA6 9AAF Transfer agent number Transfer agent number in missing CAA6 9ABD Transfer agent number Invalid Transfer agent number CAA6 9AAI Record Type Missing record type AAAB 9ABD Record Type Record type is invalid AAAB 9AAA DTCC transaction id DTCC transaction id is not numeric GACO 9AAF Transfer agent transaction id TA transaction id is not numeric GACO 9AAF Transfer agent transaction id TA transaction id equals zero GACO 9ABD Record sequence number Not numeric GACB 9AAF Record sequence number Invalid record sequence number GACB 9AAA Cutoff time Past cutoff time JAAA 9AAL Cutoff time Cutoff Quiesce JAAA 9ABJ Master table Master table look up error JAAC 9AAM Info table Info table look up error JAAC 9AAA NFT1/NFT5 USER'S GUIDE Page 14 July 2003

19 4.0 Appendix Table of applicable values for field, TRANS-PROCESS-TYPE, for each different, RECORD-TYPE. N= NO ACTION A=APPROVE TRANSACTION OR CERTIFICATE U=UPDATE TRANSACTION/CERTIFICATE OR ENTER A MESSAGE R=REJECT TRANSACTION OR CERTIFICATE Record type 01 (customer account info) Record type 88 certificate Record type 89 TA Message Record type 99 Trailer N N, U N, U N A A N, U N R R N, U N P A, R N, U N U N, U N, U N NFT1/NFT5 USER'S GUIDE Page 15 July 2003