| |
- Each row of the file MG 13 ('Client Margin
File for Trading Members' provided to TMs) provides the details of margins for a
specific constituent, as per the client code entered by the Trading members at
the time of order entry.
- Members are required to add a field (field 8) at the end of each row (for
each constituent) in the file MG 13 representing the actual initial margin
amount collected from that constituent.
- The file should be uploaded in the Collateral Interface for Members (CIM) or
the Extranet Server with the file name F_MRG_TM_<DDMMYYYY>.nn.CSV.
Where :
<DDMMYYYY> is the trade date
and 'nn' is the batch number of the file.
Members are required to provide batch number in every file they upload starting
with 01. Thereafter subsequent files are required to have incremental batch
numbers viz 02, 03 etc up to maximum of 99. This enables members to send
multiple files for the same trade date with incremental batch numbers. Multiple
files can be sent by the members till 5 working days after the trade date. Where
multiple files are uploaded by members for a client for a trade day, the
information of client margin collected as provided in the file with latest batch
number for the trade day is considered as final by the Clearing Corporation.
For eg. For the file to be uploaded by trading member 09999 for the trade date, the filename should be F_MRG_TM_ddmmyyyy_01.CSV
If the trading member has a client code 101 with margin reported as Rs.10000
in the file with batch number 01 and Rs 5000 in the file with batch number 02
then Rs.5000 reported in the latest file batch number 02 is considered by the
Clearing Corporation.
- The TM is required to append the initial margin amount collected from each
constituent against the relevant record for the constituent in MG 13 file. This
figure should not be negative.
- The file format is comma delimited.
- The file should be placed in the CIM or Extranet Server on or before the end
of the T+5 day.
- Members are required to ensure that no other record in the file is modified
other than as detailed above. Any modification of a record results in such
record being rejected by NSCCL.
- Margins are required to be reported by TMs only for client positions.
- Any variation in the file naming convention as specified above results in
the file not being picked by the Clearing Corporation and this is treated as non
reporting of client margin.
- Members are required to ensure that the size of the file transferred to the
CIM or extranet server is not “0” bytes. If the file size is “0” bytes, it is
not picked up for processing and hence this will be treated as non reporting of
client margin.
- Each row of the file MG 12 (Detail Margin
File of Clearing Members) provides the details of margins for a specific Trading
member/ Constituent of the CM.
- Members are required to add a field (field 7) at the end of each row (for
each Trading member/ constituent) in the file MG 12 representing the actual
initial margin amount collected from that Trading Member/ constituent.
- The file should be uploaded in the CIM or the Extranet Server with the file
name F_MRG_CM_<DDMMYYYY>_nn.CSV
Where :
<DDMMYYYY> is the trade date
and 'nn' is the batch number of the file.
Members are required to provide batch number in every file they upload starting
with 01. Thereafter subsequent files are required to have incremental batch
numbers viz 02, 03 etc up to maximum of 99. This enables members to send
multiple files for the same trade date with incremental batch numbers. Multiple
files can be sent by the members till 5 working days after the trade date. Where
multiple files are uploaded by members for a client for a trade day, the
information of client margin collected as provided in the file with latest batch
number for the trade day is considered as final by the Clearing Corporation.
For eg. For the file to be uploaded by clearing member having primary (trading)
member code as 09999 for the trade date, the filename should be
F_MRG_CM_ddmmyyyy_01.CSV
If the clearing member has a trading member 00001 with margin reported as Rs
10000 in the file with batch number 01 and Rs 5000 in the file with batch number
02, then Rs 5000 reported in the file batch number 02 is considered correct by
the Clearing Corporation.
- CMs are required to append the initial margin amount collected from each
trading member/ constituent against the relevant record for the trading member/
constituent in MG 12 file.
- The file is comma delimited.
- The file should be placed in the CIM or Extranet server on or before the end
of the T+5 day.
- CMs are required to ensure that no other record in the file is modified
other than as detailed above. Any modification of the record results in such
record being rejected by the NSCCL
- Any variation in the file naming convention as specified above results in
the file not being picked by the Clearing Corporation and this is treated as non
reporting of client margin.
- Members are required to ensure that the size of the file transferred to the
CIM or extranet server is not “0” bytes. If the file size is “0” bytes, it is
not picked up for processing and hence this will be treated as non reporting of
client margin
A return file is generated for all client margin reporting files uploaded by
members. No return files are generated for the following files:
i) File with wrong naming convention: If the member has provided a file with
naming convention different from that specified above, such files are not picked
up by Clearing Corporation. This is treated as non reporting of client margin.
ii) File with “0” bytes : If a file size is “0” bytes, it is not picked up for
processing. This is treated as non- reporting of client margin.
In the CIM the return file can be viewed in Client margin Reporting>File
download. The return file for Clearing members/ Trading members is placed in the
directory FAOFTP/F<CODE>/COLAT/DNLD. The file naming convention and structure
are detailed below:
In case of files uploaded through the CIM as well as the extranet, the return
file is provided on the same day within an hour of file upload. In case of any
errors in the file, the member can correct the same and upload on the CIM or the
extranet server with incremental batch number anytime prior to Trade Date+5
days.
Two types of return files are generated for the members
1. Rejected Files - where the whole file has been rejected
2. Processed File Records - some or all records in the file have been rejected
1. Rejected Files
File Naming convention for trading members
: F_MRG_TMF_TMCODE_<DDMMYYYY>_nn.CSV
File Naming convention for clearing members
: F_MRG_CMF_CMCODE_<DDMMYYYY>_nn.CSV.
- File loaded after the sign off date - Members are allowed to load the
margin reporting file up to T+5 days. Accordingly, if a member does not upload
the margin reporting file till the T+5 date, the same is treated as non
reporting of client margin and such files are
rejected with the reason “File is not being processed as file upload date is
greater than sign off date”.
- File loaded for future date - If the member uploads the file for a
future date, then the return file indicates the rejection reason
as ‘File is not being processed as file date is greater than system current
date’. This is treated as non reporting of client margin
- Member uploads file for an invalid day - If a member is not required
to report the client margin file for a day (say Saturday, Sunday, holiday etc.)
and he still uploads the same, then the return file is rejected with the message
‘File is not being processed as the member code is invalid for the file date’.
This is treated as non reporting of client margin
- Member uses non-serial batch number in file name - If the batch
number provided by the member for a trade date is not in sequence, for example
if the member has uploaded two files for the trade date with file
names F_MRG_TM_ddmmyyyy_01.CSV and F_MRG_TM_ddmmyyyy_03.CSV, the second file
will be rejected with error message ‘File is not being processed as file batch
number is not proper. Last successful batch no for the day was 01’. This is
treated as non reporting of client margin
- File in wrong format - If the member has provided a file which cannot
be read by the system for example. a non csv file, then return file is rejected
with the message ‘File is not being processed as the file is not in format’.
This is treated as non reporting of client margin
2. Processed File Records
File Naming Convention for trading members:
F_MRG_TMR_TMCODE_<DDMMYYYY>_nn.CSV
File Naming Convention for clearing members:
F_MRG_CMR_CMCODE_<DDMMYYYY>_nn.CSV.
After processing of client margin file, each record has a reason code indicating
acceptance/ rejection, as the case may be. The details of reason codes are as
follows:
| Code | Message description |
|---|
| 01 | Record size does not match for e.g.
extra comma in the record |
| 02 | Date in record does not match with
file date |
| 03 | Record is altered i.e. matching
record does not exist in MG-13 file. Possible error in date/ client code/
margin amount. |
| 04 | Record pertains to proprietary
position for trading member. |
| 05 | Record pertains to proprietary
position for clearing member. |
| 06 | Margin amount collected is negative
or non numeric. |
| 07 | Insufficient Margin |
| 08 | Sufficient Margin |
- For reason codes 1 to 6, the difference amount, represented by the
difference between the margin reported and the initial margin payable, is not
indicated in the return file. However for reason codes 7 and 8, the difference
amount is indicated.
- If the record contains multiple errors for e.g. reason code 1 as well as 6,
the reason code which is the lowest in number appears against the record i.e.
reason code 1.
- If the member uploads the file in a different naming convention than as
specified above, the file is not picked up by the Clearing Corporation and is
treated as non-reporting of margin by the member and accordingly it invites
suitable action as specified from time to time.
Penalty reports for Trading Members
- Detail penalty for short/ non-reporting by trading members
Naming convention:
F_PNL01_<MEMBER CODE>_DDMMYYYY.CSV
Location: FAOFTP/F<MEMBER CODE>/ REPORTS/DNLD/PNL01
File details and format:
Trade Date
Client Code
Shortfall Amount
Penalty Amount
Penalty reports for Clearing Members
- Detail penalty for short/non reporting by clearing member
Naming convention:
F_PNL02_<MEMBER CODE>_DDMMYYYY.CSV
Location: FAOFTP/F<MEMBER CODE>/REPORTS/DNLD/PNL02
File details and format:
Trade Date
TM Code/CP Code
Shortfall Amount
Penalty Amount
- Penalty for short/ non-reporting by trading members affiliated to clearing member
Naming convention:
F_PNL03_<MEMBER CODE>_DDMMYYYY.CSV
Location: FAOFTP/F<MEMBER CODE>/REPORTS/DNLD/PNL03
File details and format:
Trade Date
TM Code
Penalty Amount
Liquid Assets |
Margins |
NSCCL SPAN |
PC SPAN
Payment of margins |
Position Limits | Violations
|
FII / MF position limits
Client Margin Reporting |
Data and reports download |
Formats for collaterals
Other formats |
Cross Margin Top
|
|