Format of files
Format of files to be uploaded by the member giving client & quantity details of early pay-in of securities
The file should be in CSV format.
Naming convention:
<XXXXX>_CLNTEPI_YYYYMMDD.Ynn
where,
XXXXX - Is the member code
YYYYMMDD - Date in YYYYMMDD format
Y - The file indicator (T in this case for upload)
nn - The batch number of file to be uploaded.
Control Record
| FIELD NAME | LENGTH | MANDATORY / OPTIONAL | DESCRIPTION |
|---|---|---|---|
| Record Type | Char (2) | Mandatory | Value is 10 |
| File Type | Char(4) | Mandatory | Value = CLEP |
| Member Type | Char (1) | Mandatory | Member Type |
| Member Code | Char (5) | Mandatory | Member code for which file generated/received |
| Batch Date | Char (8) | Mandatory | Format : DDMMYYYY should be same as that in the file name. |
| Batch No. | Number (2) | Mandatory | The batch number of the file sent |
| Number Records | Number (7) | Mandatory | Total number of records in the file |
Detail Record:
| FIELD NAME | LENGTH | MANDATORY / OPTIONAL | DESCRIPTION |
|---|---|---|---|
| Record Type | Char (2) | Mandatory | Value is 20 |
| Symbol | Char(10) | Mandatory | |
| Series | Char (2) | Mandatory | |
| Client Code | Char (20) | Mandatory | |
| Settlement Type | Char (1) | Mandatory | |
| Settlement No. | Number (7) | Mandatory | |
| Early Payin Quantity | Numeric | Mandatory |
Return files:
In case the file uploaded by the member gets rejected, then the file extension 'Tnn' will get replaced with 'Rnn' and the return file will be downloaded to the members in CEP directory. The control record in the file will have R appended.
The naming convention for return files will be: <XXXXX>_CLNTEPI_YYYYMMDD.Rnn
In case the file is accepted (success) then the file extension 'Tnn' will get replaced with 'Snn' and the return file will be downloaded to the members in CEP directory. The return file with extension 'Snn' will have S appended for successful records and R appended for rejected records.
The naming convention for return files will be: <XXXXX>_CLNTEPI_YYYYMMDD.Snn
Note:
- Member should mention the total quantity for the clients to whom EPI needs to be allocated. If member wants to change the EPI once allocated to a client, the same needs to be provided in the next file with the revised quantity and the old quantity will get updated with the revised quantity. If member wants to remove the EPI benefit given earlier to a client, a record needs to be sent in the subsequent file with the revised quantity as zero. Where the quantity is specified for a client as zero the client will become eligible for random allocation.
- Wherever allocation is specified by the member for a client -security-settlement type- settlement number, EPI will be specifically allocated to that client irrespective whether the client has any outstanding sell position or not and such clients shall not be considered for random allocation. Even if the client is allocated excess EPI, the xcess will not be considered in the pool for random allocation.
- Where the member has to provide EPI for his proprietary position, he has to specify client code as his member code, and in case he wants to specify EPI for OTR Un-allocation and non-contraction he has to specify the client code as PRO_Memcode.
- At the end of the day EPI allocation will be done on the same lines as intra day i.e. first specific and then random.
- Specific client level EPI should be given only for all open settlements
- Members are requested to verify the benefit received in the EPI report downloaded.
- The latest file uploaded by the member shall be considered as final.
Format of files to be uploaded by the members/custodians giving allocation details of early pay-in of funds.
The file shall be in CSV format.
Naming convention:
CLNTEPF_N_XXXXXXX_YYYYMMDD.Ynn
where,
N - Settlement type (Should be N for normal segment and W for trade for trade segment)
XXXXXXX - Settlement number (e.g "2010001")
YYYYMMDD - Date in YYYYMMDD format
Y - The file indicator (T in this case for upload)
nn - The batch number of file to be uploaded.
Control Record
| Field Name | Length | Mandatory / Optional | Description |
|---|---|---|---|
| Record Type | Char (2) | Mandatory | Value = 01 |
| File Type | Char(7) | Mandatory | Value = CLNTEPF |
| Member Code | Char (5) | Mandatory | Member code for which file generated/received |
| Batch Date | Char (8) | Mandatory | Format : YYYYMMDD Should be same as that in the file name. |
| Batch Number | Numeric (2) | Mandatory | The batch number of the file sent. |
| Settlement Type | Char (1) | Mandatory | Settlement type for which EPI is made. Should be N for normal segment and W for trade for trade segment |
| Settlement No. | Char(7) | Mandatory | Settlement number (e.g “2010001”) |
| Number of Records | Number (7) | Mandatory | Total number of records in the file |
| Total value of EPI | Number (15,2) | Mandatory | Total amount of early pay-in across all clients |
Detail Record
| Field Name | Length | Mandatory / Optional | Description |
|---|---|---|---|
| Record Type | Char (2) | Mandatory | Value = 20 |
| Client Code | Char(12) | Mandatory | |
| Amount of funds early pay-in (in Rs.) | Number (15,2) | Mandatory | |
| Symbol | CHAR(10) | Optional | |
| Series | CHAR(2) | Optional (Series is Mandatory where Symbol is specified) |
Return files:
In case the file uploaded by the member gets rejected, then the file extension 'Tnn' will get replaced with 'Rnn' and the return file will be available under menu 'Funds EPI -File upload- Files failed in processing' in 'Collateral Interface for Members (CIM).The control record in the file will have R appended.
The naming convention for return files will be:
<XXXXX> _CLNTEPF_N_XXXXXXXX_YYYYMMDD.Rnn
In case the file is accepted (success) then the file extension 'Tnn' will get replaced with 'Snn' and the return file will be available under menu 'Funds EPI -File upload –Files successfully processed' in 'Collateral Interface for Members (CIM).
The return file with extension 'Snn' will have S appended for successful records and R appended for rejected records.
The naming convention for return files will be:
<XXXXX> _CLNTEPF_ N_XXXXXXXX_YYYYMMDD.Snn
Note:
- File upload facility and the screen based allocation is a request for allocation only and a separate Funds EPI request has to be put for Bank confirmation for availing margin benefit If member wants to change the EPI once allocated to a client a screen based modify request can be given or a revised file may be uploaded. If member wants to remove the EPI benefit given earlier to a client, a record needs to be sent in the subsequent file with the revised amount as zero or the record can be deleted through the screen.
- Where the member has to provide EPI for his proprietary position, he has to specify client code as his member code.
- Specific client level EPI should be given only for all open settlements
- Members are requested to verify the successful uploading of the file from the return file.
Format of files to be uploaded by the clearing member giving client wise details
The file shall be in CSV format.
Naming convention: CMPYYYYMMDD.Tnn
where: is the current date
and 'nn' is the batch number of the file
The files are required to be uploaded in the following path on the CIM -Home Page> Cross Margin> File upload
Control Record
| SR. NO. | FIELD NAME | LENGTH | DESCRIPTION |
|---|---|---|---|
| 1 | Record Type | Char (2) | Value is 10 |
| 2 | File Type | Char(3) | Value = CMP |
| 3 | Member Code | Char (5) | Primary Member code of the clearing member |
| 4 | Batch Date | Char (8) | Format : YYYYMMDD Should be same as that in the file name |
| 5 | Number Records | Numeric (7) | Total number of records in the file |
Detail Record
| SR. NO. | FIELD NAME | LENGTH | DESCRIPTION |
|---|---|---|---|
| 1 | Record Type | Char (2) | Value : 10 for proprietary code 20 for retail client code 30 for Custodial Participant code |
| 2 | Code | Char(12) | Value : For proprietary code it shall be PRO_TMCODE For retail client code it shall be client code allotted to the client and used during order execution For Custodial Participant code it shall be 12 digit alphanumeric code allotted by NSE Clearing for such custodial participant |
Return files:
The files uploaded by the member are processed and return files downloaded in CIM. Members can check the return files at Home Page> Cross Margin> File download
In case the file uploaded by the member gets rejected, then the file extension 'Tnn' will get replaced with 'Rnn'
The naming convention for return files will be:
<XXXXX>_CMPYYYYMMDD.Rnn
Where XXXXX shall be the Primary member code
<YYYYMMDD> is the trade date
and 'nn' is the batch number of the file.
In case the file is accepted (success) then the file extension 'Tnn' will get replaced with 'Snn' and the return file will be downloaded to the members on CIM. The return file with extension 'Snn' will have S appended for successful records and F appended for rejected records.
The naming convention for return files will be: <XXXXX>_CMPYYYYMMDD.Snn
Where XXXXX shall be the Primary member code
<YYYYMMDD> is the trade date
and 'nn' is the batch number of the file
Members are required to take note of following whilst uploading the client codes eligible for cross margining-
- Members shall upload all eligible client codes in a single file only.
- If any modification or deletion is required in the file then the member will upload new file with all records.
The latest file uploaded by the member shall be considered as final
File format
Control Record
| Field Name | Length | Mandatory / Optional | Description |
|---|---|---|---|
| Record Type | Number (2) | Mandatory | Value is 10 |
| Applicable Month | Char(3) | Mandatory | Applicable month - MON |
| Applicable Year | Char (4) | Mandatory | Applicable Year - YYYY |
| Total records | Numeric (6) | Mandatory | Total number of detail records |
Detail Record
| Field Name | Length | Mandatory / Optional | Description |
|---|---|---|---|
| Record Type | Number (2) | Mandatory | Value is 20 |
| Sec Symbol | Char(10) | Mandatory | Symbol of the security |
| Sec Series | Char(2) | Mandatory | Series of the security |
| ISIN | Char(12) | Mandatory | ISIN of the security |
| Security Category | Char (1) | Mandatory | Security Category applicable on that security in the following month |
| Security Impact Cost | Number (5,2) | Mandatory | Security Impact Cost |
Updated on: 07/01/2023
