GiftNiftyFutures 28-Nov-2024
23,531.50 9.00 (0.04%)

19-Nov-2024 20:21

27-Nov-2024 | 84.4600

19-Nov-2024 17:00

Lac Crs 427.49 | Tn $ 5.06

19-Nov-2024

Login to

You will be redirected to
another link to complete the login

Feedback
Login to Mutual Fund, NCFM

Electronic Reporting


CP code modification

Members are required to enter a custodial participant code (CP code) at the time of order entry in the NEAT system. The CP code can either be INST or a valid CP code. On any particular trading day, members can modify the CP code at the order level during market hours and post market hours up to 4.15 p.m. This can be done through the NSE Clearing Clearing Management System (NCMS) by uploading a CP code modification file as per the prescribed format or through the NCMS screen itself. In case of file upload, the return file is generated in the members’ NCMS local database and it contains the success or reject status of the records along with the rejection code.

OTR allocation

Members may execute institutional orders with a single custodial participant (CP) code i.e. INST and assign the respective custodial participant codes subsequent to execution. For all such orders executed on a given T day, members can generate Obligation Transfer Request (OTR) files in NCMS. Members are required to give a break-up of obligations by different institutional clients along with the contract note number latest by 9.30 a.m. on the next working day by uploading the OTR file in the specified format in NCMS. The return file is generated in the member’s NCMS local database and it contains the success or reject status of the records along with the rejection code

If a member fails to furnish the break up of the obligations by different clients, such unallocated obligations will be reverted to the member. Allocation to CP codes shall not be allowed thereafter and exposures and margins will be applicable with immediate effect.

Members can also nullify the previous allocation and make fresh allocations before the cut off time. This modification cannot be done if the custodian has already confirmed the same. The CP codes allowable in this category are all institutional codes (i.e. pertaining to FIIs, DFIs, Insurance companies, Banks, Mutual Funds and Pension Funds under PFRDA).

Members can view the custodian confirmation status of OTR records through NCMS

Rejection Confirmation file

This file in the specified format, is downloaded to the members at 8.15 a.m. on the day following the T day. It gives information about orders and OTR allocations rejected or unconfirmed by custodians. Members can modify CP codes latest by 9.30 a.m. on that day provided the same have not been confirmed by the custodian. Here members can only make modifications from one CP code to another.

Client code modifications

Trading Members are required to enter the Client Code at the time of order entry in the NEAT system. Trading Members, who desire to modify the client codes subsequently, shall be provided with a facility to modify client codes at order level (not at trade level) on the trade date, during market hours and post market hours upto 4.15 p.m. However, proprietary trades are not allowed to be modified to client trades and vice-versa. Trading Members are allowed to modify the Client Codes in respect of client orders only on the trade date. Such modifications of a client code will be at the order level, hence all trades in respect of that order shall be modified with the client code provided against the order. Client code modification can be done through the NSE Clearing Clearing Management System (NCMS) by uploading a client code modification file as per the prescribed format or through the NCMS screen itself. In case of file upload, the return file is generated in the members’ NCMS local database and it contains the success or reject status of the records along with the rejection code.

Download NSE Clearing Clearing Management System files (zip)

Download CP code modification (.pdf)

Download NCMS Rejection codes (.pdf)

Download OTR Allocation (.pdf)

Download Client code modification (.pdf)

Updated on: 03/01/2023