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:

1. 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.




2. 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.




3. 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.




4. 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.




5. Specific client level EPI should be given only for all open settlements




6. 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.