Type of Report |
STR |
Description of Report |
SUSPICIOUS TRANSACTION REPORT |
Reporting Entity |
INTERMEDIARY |
Version |
1.0 |
MARCH 2006
Contents
2. Financial Intelligence Unit – India
3. Prevention of Money Laundering Act, 2002
4. Suspicious Transaction Report
11. Steps in preparation of Data files
12. Steps in validation of Data files
13. General Notes for all Data files
14. Data Structure of Control File (SINCTL.txt)
15. Data Structure of Branch Data File (SINBRC.txt)
16. Data Structure of Account Data File (SINACC.txt)
17. Data Structure of Transaction Data File (SINTRN.txt)
18. Data Structure of Individual Data File (SININP.txt)
19. Data Structure of Legal Person/Entity Data File (SINLPE.txt)
Appendix
Suspicious Transaction Report for an intermediary
Annexure A- Individual Detail Sheet for an intermediary
Annexure B- Legal Person/ Entity Detail Sheet for an intermediary
The Prevention of Money Laundering Act, 2002 (PMLA 2002) forms the core of the legal framework put in place by India to combat money laundering. PMLA 2002 and the Rules notified thereunder came into force with effect from July 1, 2005. Director, FIU-IND and Director (Enforcement) have been conferred with exclusive and concurrent powers under relevant Sections of the Act to implement the provisions of the Act.
The PMLA 2002 and Rules notified thereunder impose an obligation on banking companies, financial institutions and intermediaries to verify identity of clients, maintain records and furnish information to FIU-IND.
The Government of India set up Financial Intelligence Unit – India (FIU-IND) on 18th November 2004 as an independent body to report directly to the Economic Intelligence Council (EIC) headed by the Finance Minister.
FIU-IND has been established as the central national agency responsible for receiving, processing, analyzing and disseminating information relating to suspect financial transactions. FIU-IND is also responsible for coordinating and strengthening efforts of national and international intelligence and enforcement agencies in pursuing the global efforts against money laundering and related crimes. The address of Financial Intelligence Unit – India (FIU-IND) is:
Director, FIU-IND
Financial Intelligence Unit-India
6th Floor, Hotel Samrat
Chanakyapuri, New Delhi -110021
India
Website: www.fiuindia.gov.in
Section 12 of the Prevention of Money Laundering Act, 2002 lays down following obligations on intermediaries.
“12. (1) Every banking company, financial institution and intermediary shall-
(a) maintain a record of all transactions, the nature and value of which may be prescribed, whether such transactions comprise of a single transaction or a series of transactions integrally connected to each other, and where such series of transactions take place within a month;
(b) furnish information of transactions referred to in clause (a) to the Director within such time as may be prescribed;
(c) verify and maintain the records of the identity of all its clients, in such a manner as may be prescribed.
Provided that where the principal officer of a banking company or financial institution or intermediary, as the case may has reason to believe that a single transaction or series of transactions integrally connected to each other have been valued below the prescribed limit so as to defeat the provisions of this section, such officer shall furnish information in respect of such transactions to the Director within the prescribed time.
(2) The records referred to in sub-section (1) shall be maintained for a period of ten years from the date of cessation of the transactions between the clients and the banking company or financial institution or intermediary, as the case may be.”
The Prevention of Money laundering Act, 2002 and the Rules notified thereunder require every intermediary to furnish details of suspicious transactions whether or not made in cash. Suspicious transaction means a transaction whether or not made in cash which, to a person acting in good faith –
(a) gives rise to a reasonable ground of suspicion that it may involve the proceeds of crime; or
(b) appears to be made in circumstances of unusual or unjustified complexity; or
(c) appears to have no economic rationale or bonafide purpose.
Broad categories of reason for suspicion and examples of suspicious transactions for an intermediary are indicated as under:
Identity of Client
- False identification documents
- Identification documents which could not be verified within reasonable time
- Non-face to face client
- Doubt over the real beneficiary of the account
- Accounts opened with names very close to other established business entities
Suspicious Background
- Suspicious background or links with known criminals
Multiple Accounts
- Large number of accounts having a common account holder, introducer or authorized signatory with no rationale
- Unexplained transfers between multiple accounts with no rationale
Activity in Accounts
- Unusual activity compared to past transactions
- Use of different accounts by client alternatively
- Sudden activity in dormant accounts
- Activity inconsistent with what would be expected from declared business
- Account used for circular trading
Nature of Transactions
- Unusual or unjustified complexity
- No economic rationale or bonafide purpose
- Source of funds are doubtful
- Appears to be case of insider trading
- Investment proceeds transferred to a third party
- Transactions reflect likely market manipulations
- Suspicious off market transactions
Value of Transactions
- Value just under the reporting threshold amount in an apparent attempt to avoid reporting
- Large sums being transferred from overseas for making payments
- Inconsistent with the clients apparent financial standing
- Inconsistency in the payment pattern by client
- Block deal which is not at market price or prices appear to be artificially inflated/deflated
Rule 8 of Notification No. 9/2005 dated 1-7-2005 require the Principal Officer of an intermediary to furnish the information of the suspicious transactions to Director, FIU-IND within 7 working days of establishment of suspicion at the level of Principal Officer.
Intermediary includes following persons registered under section 12 of the Securities and Exchange Board of India (SEBI) Act, 1992.
(i) Stock brokers
(ii) Sub-brokers
(iii) Share transfer agents
(iv) Bankers to an issue
(v) Trustees to trust deed
(vi) Registrars to issue
(vii) Merchant bankers
(viii) Underwriters
(ix) Portfolio Managers
(x) Depositories and Participants
(xi) Custodian of securities
(xii) Foreign institutional investors
(xiii) Credit rating agencies
(xiv) Venture capital funds
(xv) Collective investment schemes including mutual funds
Suspicious Transaction Reports can be filed either in manual or electronic format. However, a reporting agency must submit all reports to FIU-IND in electronic format if it has the technical capability to do so. The required technical capability is defined as follows:
i) A personal computer with 32 MB memory RAM, 800 x 600 VGA video display, Windows® 98/Me/NT/2000; and
ii) An Internet connection.
Suspicious Transaction Report in manual format has to be filed in following forms:
Description of Form |
Information |
Suspicious Transaction Report for an intermediary |
Details of suspicious transactions |
Annexure A- Individual Detail Sheet for an intermediary |
Identification details of individual |
Annexure B- Legal Person/ Entity Detail Sheet for an intermediary |
Identification details of legal person /entity |
Annexure C- Account Detail Sheet for an intermediary |
Details of account and transactions |
The above forms are given in the Appendix.
FIU-IND is in the process of developing technological infrastructure to enable submission of electronic return over a secure gateway. In the interim the intermediaries exercising the electronic option should submit the following to Director, FIU-IND:
i) One CD containing six data files in prescribed data structure. A label mentioning name of the intermediary, SEBI registration number of intermediary, type of report (STR), date of sending report should be affixed on each CD for the purpose of identification.
ii) Each CD should be accompanied by Suspicious Transaction Report for an intermediary (same form should be used for both manual as well as electronic format) in physical form duly signed by the principal officer. This summary should match with the data in Control File (SINCTL.txt). There is no need to submit other annexures in the physical form.
Important:
i) In case the size of data files exceeds the capacity of one CD, the data files should be compressed by using Winzip 8.1 or ZipItFast 3.0 (or higher version) compression utility only to ensure quick and smooth acceptance of the file.
ii) The CD should be virus free.
In case of electronic filing, the STR data for the intermediary should have following six data files:
S No. |
Filename |
Description |
1 |
SINCTL.txt |
Control File |
2 |
SINBRC.txt |
Branch Data File |
3 |
SINACC.txt |
Account Data File |
4 |
SINTRN.txt |
Transaction Data File |
5 |
SININP.txt |
Individual Data File |
6 |
SINLPE.txt |
Legal Person/Entity Data File |
i) The records containing details of suspicious transactions to be reported are extracted in Transaction Data File (SINTRN.txt).
ii) The records containing details of accounts containing the suspicious transactions are extracted in Accounts Data File (SINACC.txt).
iii) If the account is for Individuals, the records containing details of Individuals who are account holders are extracted in Individual Data File (SININP.txt). The Relation Flag should be set to “A”.
iv) If the account is for a Legal Person /Entity, the records containing details of Legal Persons /Entities who are account holders are extracted in Legal Persons /Entities Data File (SINLPE.txt). The Relation Flag should be set to “A”.
iii) If the account is for a Legal Person /Entity, the records containing details of Directors/ Partner/ Members etc. of Legal Persons /Entities are appended to Individual Data File (SININP.txt). The Relation Flag should be set to “C”.
v) The records containing details of authorised signatories if not an account holder are appended to Individual Data File (SININP.txt) or Legal Persons /Entities Data File (SINLPE.txt) as the case may be. The Relation Flag should be set to “B”.
vi) The records containing details of account introducers are appended to Individual Data File (SININP.txt) or Legal Persons /Entities Data File (SINLPE.txt) as the case may be. The Relation Flag should be set to “D”.
vii) The records containing details of account guarantors are appended to Individual Data File (SININP.txt) or Legal Persons /Entities Data File (SINLPE.txt) as the case may be. The Relation Flag should be set to “E”.
viii) The records containing details of branches/ franchisees etc. which have reported suspicious transactions are extracted in Branch Data File (SINBRC.txt).
ix) The report level details and summary of other five tables is entered in Control file. (SINCTL.txt)
i) There should be six data files with appropriate naming convention.
ii) The data files should be as per specified data structure and business rules.
iii) None of the mandatory fields should be left blank.
iv) Date of report should be same in all data files.
v) The summary figures in control file should match with the totals in other data files.
vi) The primary key integrity should be validated as under:
a. [Branch Reference Number] should be unique in Branch Data File (SINBRC.txt)
b. [Branch Reference Number + Account Number] should be unique in Account Data File (SINACC.txt)
vii) The foreign key integrity should be validated as under:
a. All values of [Branch Reference Number] in Account Data File (SINACC.txt) should have a matching [Branch Reference Number] value in Branch Data File (SINBRC.txt)
b. All values of [Branch Reference Number + Account Number] in Transaction Data File (SINTRN.txt) should have matching [Branch Reference Number + Account Number] value in Account Data File (SINACC.txt)
c. All values of [Branch Reference Number + Account Number] in Individual Data File (SININP.txt) should have matching [Branch Reference Number + Account Number] value in Account Data File (SINACC.txt)
d. All values of [Branch Reference Number + Account Number] in Legal Person / Entity Data File (SINLPE.txt) should have matching [Branch Reference Number + Account Number] value in Account Data File (SINACC.txt)
viii) The data sufficiency should be validated as under:
a. All values of [Branch Reference Number + Account Number] in Account Data File (SINACC.txt) should have at least one matching [Branch Reference Number + Account Number] value in Transaction Data File (SINTRN.txt).
b. All values of [Branch Reference Number + Account Number] in Account Data File (SINACC.txt) should have at least one matching [Branch Reference Number + Account Number] value in Individual Data File (SININP.txt). (As account for legal person/entity would have individuals as authorised signatories).
c. All values of [Branch Reference Number + Account Number] in Account Data File (SINACC.txt) with Type of Account Holder = “B” (Legal Person/Entity) should have at least one matching [Branch Reference Number + Account Number] value in Legal Person / Entity Data File (SINLPE.txt).
i) All Data Files should be generated in ASCII Format with ".txt" as filename extension.
ii) Each Record (including last record) must start on new line and must end with a newline character. Hex Values: "0D" & "0A".
iii) All CHAR fields must be left justified.
iv) If CHAR field has no data or less data with respect to defined length, then the entire field (in case of no data) or the remaining field (in case of less data) has to be filled with right justified blank characters (Spaces).
v) All NUM fields must be right justified.
vi) If NUM field has no data or less data with respect to defined length, then the entire field (in case of no data) or the remaining field (in case of less data) has to be filled with left justified zeroes.
vii) If DATE field has no data then the entire field has to be filled with blank characters (Spaces).
viii) Fields with an asterisk (*) have to be compulsorily filled up. Fields that have hash (#) have to be compulsorily filled up in case they are applicable to the transaction being reported.
ix) For fields that do not have an asterisk (*) or hash (#), reasonable efforts have to be made to get the information. Enter “N/A” to indicate that the field is not applicable. Do not substitute any other abbreviations or special characters (e.g., “x”, “-” or “*”).
|
Field |
Type |
Size |
From |
To |
Remarks |
Report Name* |
CHAR |
3 |
1 |
3 |
Value should be “SIN” signifying STR for intermediaries |
|
2 |
Serial Number of Report* |
NUM |
8 |
4 |
11 |
Indicates the running sequence number of STR for the reporting agency starting from 00000001 |
3 |
Record Type* |
CHAR |
3 |
12 |
14 |
Value should be “CTL” signifying Control file |
4 |
Date of Report |
DATE |
8 |
15 |
22 |
Date of sending report in DDMMYYYY Format |
5 |
Complete name of intermediary * |
CHAR |
80 |
23 |
102 |
Field + filler spaces = 80 |
6 |
Category of intermediary * |
CHAR |
1 |
103 |
103 |
"A"- Stock brokers "B"- Sub-brokers "C"- Share transfer agents "D"- Bankers to an issue "E"- Trustees to trust deed "F"- Registrars to issue "G"- Merchant bankers "H"- Underwriters "I"- Portfolio Managers "J"- Investment advisers "K"- Depositories "L"- Depository participants "M"- Custodian of securities "N"- Foreign institutional investors "O"- Credit rating agencies "P"- Venture capital funds "Q"- Collective investment schemes "R"- Mutual funds “Z”- Others |
7 |
SEBI registration number * |
CHAR |
12 |
104 |
115 |
SEBI registration number of intermediary |
8 |
Unique ID issued by FIU* |
CHAR |
10 |
116 |
125 |
Use XXXXXXXXXX till the ID is communicated |
9 |
Principal Officer’s Name* |
CHAR |
80 |
126 |
205 |
Field + filler spaces = 80 |
10 |
Principal Officer’s Designation* |
CHAR |
80 |
206 |
285 |
Field + filler spaces = 80 |
11 |
Principal Officer’s Address1* |
CHAR |
45 |
286 |
330 |
No., Building Field + filler spaces = 45
|
12 |
Principal Officer’s Address2 |
CHAR |
45 |
331 |
375 |
Street/Road Field + filler spaces = 45 |
13 |
Principal Officer’s Address3 |
CHAR |
45 |
376 |
420 |
Locality Field + filler spaces = 45 |
14 |
Principal Officer’s Address4 |
CHAR |
45 |
421 |
465 |
City/Town, District Field + filler spaces = 45
|
15 |
Principal Officer’s Address5 |
CHAR |
45 |
466 |
510 |
State, Country Field + filler spaces = 45 |
16 |
Principal Officer’s Pin code* |
NUM |
6 |
511 |
516 |
Pin code without “-” or space |
17 |
Principal Officer’s Telephone |
CHAR |
30 |
517 |
546 |
Telephone in format STD Code-Telephone number |
18 |
Principal Officer’s FAX |
CHAR |
30 |
547 |
576 |
Fax number in format STD Code-Telephone number |
19 |
Principal Officer’s E-mail |
CHAR |
50 |
577 |
626 |
E-mail address |
20 |
Report Type* |
CHAR |
1 |
627 |
627 |
“N”- New Report “R”- Replacement to earlier submitted report |
21 |
Reason for Replacement* |
CHAR |
1 |
628 |
628 |
“A” – Acknowledgement of Original Report had many warnings or error messages. “B” – Operational error, data omitted in Original Report. “C” – Operational error, wrong data submitted in Original Report. “N”- Not Applicable as this is a new report “Z”- Other Reason |
22 |
Serial Number of Original Report * |
NUM |
8 |
629 |
636 |
Serial Number of the Original Report which is being replaced. Mention 00000000 if Report Type is “N” |
23 |
Operational Mode* |
CHAR |
1 |
637 |
637 |
“P”- Actual/ Production mode “T”- Test / Trial mode |
24 |
Data Structure Version* |
CHAR |
1 |
638 |
638 |
Value should be 1 to indicate Version 1.0 |
25 |
Number of accounts linked to suspicious transactions* |
NUM |
8 |
639 |
646 |
Count of total number of records in SINACC.txt |
26 |
Number of Transactions* |
NUM |
8 |
647 |
654 |
Count of total number of records in SINTRN.txt |
27 |
Number of Individual Persons* |
NUM |
8 |
655 |
662 |
Count of total number of records in SININP.txt |
28 |
Number of Legal Person/ entities* |
NUM |
8 |
663 |
670 |
Count of total number of records in SINLPE.txt |
29 |
Suspicion due to Identity of Client* |
CHAR |
1 |
671 |
671 |
Mention “Y” or “N” |
30 |
Suspicion due to Suspicious background* |
CHAR |
1 |
672 |
672 |
Mention “Y” or “N” |
31 |
Suspicion due to Multiple Accounts* |
CHAR |
1 |
673 |
673 |
Mention “Y” or “N” |
32 |
Suspicion due to Activity in Accounts* |
CHAR |
1 |
674 |
674 |
Mention “Y” or “N” |
33 |
Suspicion due to Nature of Transactions* |
CHAR |
1 |
675 |
675 |
Mention “Y” or “N” |
34 |
Suspicion due to Value of Transactions* |
CHAR |
1 |
676 |
676 |
Mention “Y” or “N” |
35 |
Grounds of Suspicion* |
CHAR |
4000 |
677 |
4676 |
Write summary of suspicion and sequence of events |
36 |
Details of other investigations |
CHAR |
4000 |
4677 |
8676 |
Write details about agency, contact person and contact details |
37 |
Acknowledgement Number |
NUM |
10 |
8677 |
8686 |
For internal use of FIU-IND. Use value 0000000000 |
38 |
Date of Acknowledgement |
DATE |
8 |
8687 |
8694 |
For internal use of FIU-IND. Use value “XXXXXXXX” |
|
Field |
Type |
Size |
From |
To |
Remarks |
1 |
Record Type* |
CHAR |
3 |
1 |
3 |
Value should be “BRC” signifying Branch Data file |
2 |
Date of Report |
DATE |
8 |
4 |
11 |
Date of sending report in DDMMYYYY Format. This date should be same as in control file |
3 |
Line Number* |
NUM |
6 |
12 |
17 |
Running Sequence Number for each line in the file starting from 000001. This Number will be used during validation checks. |
4 |
Name of Branch/Franchisee* |
CHAR |
80 |
18 |
97 |
Field + filler spaces = 80 |
5 |
Branch Reference Number* |
CHAR |
20 |
98 |
117 |
[SEBI registration number +unique code for branch/franchisee]. Use only SEBI registration number if there are no branches/franchisees. Unique code for branch/franchisee can be DP Id (for depository), Broker code (for stock exchange), sub broker code (for broker) |
6 |
Unique OD issued by FIU* |
CHAR |
10 |
118 |
127 |
Use XXXXXXXXXX till the ID is communicated |
7 |
Branch Address1* |
CHAR |
45 |
128 |
172 |
No., Building Field + filler spaces = 45
|
8 |
Branch Address2* |
CHAR |
45 |
173 |
217 |
Street/Road Field + filler spaces = 45 |
9 |
Branch Address3 |
CHAR |
45 |
218 |
262 |
Locality Field + filler spaces = 45 |
10 |
Branch Address4 |
CHAR |
45 |
263 |
307 |
City/Town, District Field + filler spaces = 45 |
11 |
Branch Address5 |
CHAR |
45 |
308 |
352 |
State, Country Field + filler spaces = 45 |
12 |
Branch Pin code* |
NUM |
6 |
353 |
358 |
Pin code without “-” or space |
13 |
Branch Telephone |
CHAR |
30 |
359 |
388 |
Telephone number in format STD Code-Telephone number |
14 |
Branch Fax |
CHAR |
30 |
389 |
418 |
Fax number in format STD Code-Telephone number |
15 |
Branch E-mail |
CHAR |
50 |
419 |
468 |
E-mail address |
|
Field |
Type |
Size |
From |
To |
Remarks |
1 |
Record Type* |
CHAR |
3 |
1 |
3 |
Value should be “RAC” signifying Reported Account file |
2 |
Date of Report |
DATE |
8 |
4 |
11 |
Date of sending report in DDMMYYYY Format. This date should be same as in control file |
3 |
Line Number* |
NUM |
6 |
12 |
17 |
Running Sequence Number for each line in the file starting from 000001. This Number will be used during validation checks. |
4 |
Branch Reference Number* |
CHAR |
20 |
18 |
37 |
Refer Branch Data File |
5 |
Account Number* |
CHAR |
20 |
38 |
57 |
Number to uniquely identify the account. It can be Client code (share broker), Demat account number (depository) or share application number (registrar to the issue) etc. |
6 |
Name of first/sole account holder |
CHAR |
80 |
58 |
137 |
Field + filler spaces = 80
|
7 |
Type of Account* |
CHAR |
1 |
138 |
138 |
“A”- Trading Account “B”- Demat Account “C”- Account with Portfolio Manager “Z”- Other |
8 |
Type of Account Holder* |
CHAR |
1 |
139 |
139 |
“A”- Individual “B”-Legal Person /Entity excluding “C” and “D” “C”- Central/ State Government “D”- Central/ State Government owned undertaking “Z”- Other |
9 |
Date of Account opening* |
DATE |
8 |
140 |
147 |
Date in DDMMYYYY Format |
10 |
Risk Category |
CHAR |
1 |
148 |
148 |
Risk Category as per the Internal Risk Assessment System of the intermediary “A”- Low Risk “B”- Medium Risk “C”- High Risk |
11 |
Cumulative Credit Turnover* |
NUM |
20 |
149 |
168 |
Sum of all credits in the Account (trading account etc.) from 1st April of the financial year till the last day of the month of reporting. If report is being furnished for Jan 2006 then transactions from 1st April 2005 to 31st Jan 2006 have to be aggregated. The amount should be rounded off to nearest rupee without decimal. |
12 |
Cumulative Debit Turnover* |
NUM |
20 |
169 |
188 |
Sum of all debits in the Account (trading account etc.) from 1st April of the financial year till the last day of the month of reporting. The amount should be rounded off to nearest rupee without decimal. |
|
Field |
Type |
Size |
From |
To |
Remarks |
1 |
Record Type* |
CHAR |
3 |
1 |
3 |
Value should be “TRN” signifying Transaction data file |
2 |
Line Number* |
NUM |
6 |
4 |
9 |
Running Sequence Number for each line in the file starting from 000001. This Number will be used during validation checks. |
3 |
Branch Reference Number* |
CHAR |
20 |
10 |
29 |
Refer Branch Data File |
4 |
Account Number* |
CHAR |
20 |
30 |
49 |
Account number (trading/demat etc.). Refer Account Data file |
5 |
Transaction ID |
CHAR |
20 |
50 |
69 |
Unique ID to identify transaction (if available) |
6 |
Date of Transaction* |
DATE |
8 |
70 |
77 |
Date in DDMMYYYY Format |
7 |
Mode of Transaction* |
CHAR |
1 |
78 |
78 |
“A”- Cheque “B”- Transfer within Branch “C”- Cash “D”-Demand Draft “E”- Electronic Fund Transfer “F”-Travelers Cheque “G”- Share Trading “H”-Share Delivery “I”-Mutual Fund application “Z”- Others |
8 |
Debit/Credit* |
CHAR |
1 |
79 |
79 |
“D” – Debit “C”– Credit |
9 |
Security identifier |
CHAR |
12 |
80 |
91 |
Unique code for security (ISIN etc.) |
10 |
Number of security |
NUM |
14 |
92 |
105 |
Number of security involved in transaction |
11 |
Amount* |
NUM |
20 |
106 |
125 |
The amount should be rounded off to nearest rupee without decimal. If this amount was not in Indian Rupees, it should be converted into Indian rupees. |
12 |
Currency of Transaction* |
CHAR |
3 |
126 |
128 |
“INR” for Indian Rupees, Mention Currency code as per SWIFT Code |
13 |
Disposition of Funds |
CHAR |
1 |
129 |
129 |
Reserved for later use. Use Value “X” |
14 |
Remarks |
CHAR |
10 |
130 |
139 |
Mention any other information related to the transaction. |
|
Field |
Type |
Size |
From |
To |
Remarks |
Record Type* |
CHAR |
3 |
1 |
3 |
Value should be “INP” signifying Individual data file |
|
2 |
Date of Report |
DATE |
8 |
4 |
11 |
Date of sending report in DDMMYYYY Format. This date should be same as in control file |
3 |
Line Number* |
NUM |
6 |
12 |
17 |
Running Sequence Number for each line in the file starting from 000001. This Number will be used during validation checks. |
4 |
Branch Reference Number* |
CHAR |
20 |
18 |
37 |
Refer Branch Data File |
5 |
Account Number* |
CHAR |
20 |
38 |
57 |
Account number (trading/demat etc.). Refer Account Data file |
6 |
Relation Flag* |
CHAR |
1 |
58 |
58 |
“A”- Account Holder “B”- Authorised Signatory “C”- Director/ Partner/Member etc. of a Legal Person /Entity “D”- Introducer “E”- Guarantor “Z” - Other |
7 |
Full name of Individual* |
CHAR |
80 |
59 |
138 |
Full Name Field + filler spaces = 80 |
8 |
Client Code/Number |
CHAR |
10 |
139 |
148 |
Client Code/Number if it has been allotted by the intermediary |
9 |
Name of Father/Spouse |
CHAR |
80 |
149 |
228 |
Full Name of Father/Spouse Field + filler spaces = 80 |
10 |
Occupation |
CHAR |
50 |
229 |
278 |
Where Applicable |
11 |
Date of Birth |
DATE |
8 |
279 |
286 |
In DDMMYYYY format |
12 |
Sex |
CHAR |
1 |
287 |
287 |
“M”- Male “F”- Female |
13 |
Nationality |
CHAR |
2 |
288 |
289 |
Country code as per SWIFT |
14 |
Type of Identification |
CHAR |
1 |
290 |
290 |
“A” –Passport “B”- Election ID Card “C”- PAN Card “D”- ID Card “E”- Driving License “F”- Account Introducer “Z” - Other |
15 |
Identification Number |
CHAR |
10 |
291 |
300 |
Number mentioned in the identification document |
16 |
Issuing Authority |
CHAR |
20 |
301 |
320 |
Authority which had issued the identification document |
17 |
Place of Issue |
CHAR |
20 |
321 |
340 |
Place where document was issued |
18 |
PAN |
CHAR |
10 |
341 |
350 |
Ten Digit PAN used by Income Tax Department |
19 |
Communication Address 1* |
CHAR |
45 |
351 |
395 |
Field + filler spaces = 45 |
20 |
Communication Address 2 |
CHAR |
45 |
396 |
440 |
Field + filler spaces = 45 |
21 |
Communication Address 3 |
CHAR |
45 |
441 |
485 |
Field + filler spaces = 45 |
22 |
Communication Address 4 |
CHAR |
45 |
486 |
530 |
Field + filler spaces = 45 |
23 |
Communication Address 5 |
CHAR |
45 |
531 |
575 |
Field + filler spaces = 45 |
24 |
Communication Address Pin code* |
NUM |
6 |
576 |
581 |
Pin code without “-” or space |
25 |
Contact Telephone |
CHAR |
30 |
582 |
611 |
Telephone number in format STD Code-Telephone number |
26 |
Contact Mobile number |
CHAR |
30 |
612 |
641 |
Mobile number |
27 |
Contact E-mail |
CHAR |
50 |
642 |
691 |
E-mail address |
28 |
Place of Work |
CHAR |
80 |
692 |
771 |
Name of Organisation/ employer |
29 |
Second Address 1 |
CHAR |
45 |
772 |
816 |
Permanent address / Place of work (if other than communication address) |
30 |
Second Address 2 |
CHAR |
45 |
817 |
861 |
Field + filler spaces = 45 |
31 |
Second Address 3 |
CHAR |
45 |
862 |
906 |
Field + filler spaces = 45 |
32 |
Second Address 4 |
CHAR |
45 |
907 |
951 |
Field + filler spaces = 45 |
33 |
Second Address 5 |
CHAR |
45 |
952 |
996 |
Field + filler spaces = 45 |
34 |
Second Address Pin code |
NUM |
6 |
997 |
1002 |
Pin code without “-” or space |
35 |
Second Telephone |
CHAR |
30 |
1003 |
1032 |
Telephone number in format STD Code-Telephone number |
|
Field |
Type |
Size |
From |
To |
Remarks |
1 |
Record Type* |
CHAR |
3 |
1 |
3 |
Value should be “LPE” signifying Legal Persons/ Entity data file |
2 |
Date of Report |
DATE |
8 |
4 |
11 |
Date of sending report in DDMMYYYY Format. This date should be same as in control file |
3 |
Line Number* |
NUM |
6 |
12 |
17 |
Running Sequence Number for each line in the file starting from 000001. This Number will be used during validation checks. |
4 |
Branch Reference Number* |
CHAR |
20 |
18 |
37 |
Refer Branch Data File |
5 |
Account Number* |
CHAR |
20 |
38 |
57 |
Account number (trading/demat etc.). Refer Account Data file |
6 |
Relation Flag* |
CHAR |
1 |
58 |
58 |
“A”- Account Holder “D”- Introducer “E”- Guarantor “Z”- Other |
7 |
Name of Legal Person /Entity* |
CHAR |
80 |
59 |
138 |
Full Name Field + filler spaces = 80 |
8 |
Client Code/Number |
CHAR |
10 |
139 |
148 |
Client Code/Number if it has been allotted by the intermediary |
9 |
Nature of Business |
CHAR |
50 |
149 |
198 |
Where Applicable |
10 |
Date of Incorporation |
DATE |
8 |
199 |
206 |
In DDMMYYYY format |
11 |
Type of Constitution* |
CHAR |
1 |
207 |
207 |
“A”- Sole Proprietorship “B”- Firm “C”- HUF “D”- Corporate “E”- Trust “F”- FI “G”- Mutual Fund “H”- Bank “I”- Society “J”- NBFC “K”- FII “L”- OCB “Z”- Other |
12 |
Registration Number |
CHAR |
20 |
208 |
227 |
Registration Number of mentioned in deed/document |
13 |
Registering authority |
CHAR |
20 |
228 |
247 |
Authority Registering deed/document |
14 |
Place of Registration |
CHAR |
20 |
248 |
267 |
Place where the document was registered |
15 |
PAN |
CHAR |
10 |
268 |
277 |
Ten Digit PAN used by Income Tax Department |
16 |
Communication Address 1* |
CHAR |
45 |
278 |
322 |
Field + filler spaces = 45 |
17 |
Communication Address 2 |
CHAR |
45 |
323 |
367 |
Field + filler spaces = 45 |
18 |
Communication Address 3 |
CHAR |
45 |
368 |
412 |
Field + filler spaces = 45 |
19 |
Communication Address 4 |
CHAR |
45 |
413 |
457 |
Field + filler spaces = 45 |
20 |
Communication Address 5 |
CHAR |
45 |
458 |
502 |
Field + filler spaces = 45 |
21 |
Communication Address Pin code* |
NUM |
6 |
503 |
508 |
Pin code without “-” or space |
22 |
Contact Telephone |
CHAR |
30 |
509 |
538 |
Telephone number in format STD Code-Telephone number |
23 |
Contact Fax |
CHAR |
30 |
539 |
568 |
Fax number in format STD Code-Telephone number |
24 |
Contact Email |
CHAR |
50 |
569 |
618 |
E-mail address |
25 |
Second Address 1 |
CHAR |
45 |
619 |
663 |
Registered address (if different from above). |
26 |
Second Address 2 |
CHAR |
45 |
664 |
708 |
Field + filler spaces = 45 |
27 |
Second Address 3 |
CHAR |
45 |
709 |
753 |
Field + filler spaces = 45 |
28 |
Second Address 4 |
CHAR |
45 |
754 |
798 |
Field + filler spaces = 45 |
29 |
Second Address 5 |
CHAR |
45 |
799 |
843 |
Field + filler spaces = 45 |
30 |
Second Address Pin code |
NUM |
6 |
844 |
849 |
Pin code without “-” or space |
31 |
Second Telephone |
CHAR |
30 |
850 |
879 |
Telephone number in format STD Code-Telephone number |
32 |
Second Fax |
CHAR |
30 |
880 |
909 |
Fax number in format STD Code-Telephone number |