Document User Manual – FINGate 2.

0
Module Reports
Version 1.1
Year 2022

Restricted Page |1
 User Manual - FINGate 2.0 - Reports Version 1.1

Version Control Chart

Version Date Remarks

1.0 8-May-2022 Initial Version
Updated for:
CTR for FI/NBFC/Others
CCR – Banks,
1.1 18-July-2022 CBWTR – Banks, Casinos
STR – Banks, Brokerage firms, Card Service Operators,
Depositories, Exchange Houses, MTSS, FI/NBFC/Others,
Payment Aggregators

Financial Intelligence Unit – India (FIU-IND) Page |2

 User Manual - FINGate 2.0 - Reports Version 1.1

Table of Contents

1 Introduction ......................................................................................................................................... 5
1.1 Purpose ........................................................................................................................................ 5
1.2 Scope ............................................................................................................................................ 5
2 Report Preparation and Submission ..................................................................................................... 6
2.1 Overview of ‘Report dashboard navigation and actions’ .............................................................. 6
2.2 Batch and Report creation through Bulk Upload process ............................................................ 8
2.2.1 Bulk Data Upload ...................................................................................................................8
2.2.1.1 Fresh data ......................................................................................................................... 9
2.2.1.2 Incremental data ............................................................................................................ 10
2.2.2 Rectification of errors during bulk upload .......................................................................... 11
2.2.2.1 Error rectification directly through portal ...................................................................... 11
2.2.2.2 Error rectification in bulk file .......................................................................................... 13
2.2.3 Batch Creation from bulk uploaded source data ................................................................ 13
2.3 Batch and Report creation through Manual process.................................................................. 14
2.3.1 Report Preparation ............................................................................................................. 15
2.3.1.1 Cash transaction Report Type (CTR) for Banks ............................................................... 15
2.3.1.2 Counterfeit Currency Report (CCR) for Banks ................................................................ 17
2.3.1.3 Non-Profit Organisation Transaction Report (NTR) for Banks ........................................ 18
2.3.1.4 Cross Border Wire Transfer Reports (CBWTR) for Banks ................................................ 20
2.3.1.5 Suspicious Transaction Reports (STR) for Banks ............................................................. 21
2.3.1.6 Cash transaction Report Type (CTR) for Casino .............................................................. 24
2.3.1.7 Cross Border Wire Transfer Report (CBWTR) for Casino ................................................ 25
2.3.1.8 Suspicious Transaction Report (STR) for Casino ............................................................. 26
2.3.1.9 Cash Transaction Report Type (CTR) for FI/NBFC/Others ............................................... 26
2.3.1.10 Suspicious Transaction Report Type (STR) for FI/NBFC/Others .................................. 28
2.3.1.11 Suspicious Transaction Report Type (STR) for Payment Aggregators ......................... 30
2.3.1.12 Suspicious Transaction Report Type (STR) for Brokerage Firms ................................. 32
2.3.1.13 Suspicious Transaction Report Type (STR) for Exchange Houses................................ 33
2.3.1.14 Suspicious Transaction Report Type (STR) for Depositories ....................................... 35
2.3.1.15 Suspicious Transaction Report Type (STR) for MTSS .................................................. 37
2.3.1.16 Suspicious Transaction Report Type (STR) for Card System Operators ...................... 38
2.3.1.17 Property Transaction Report (PTR) ............................................................................. 39
2.3.2 Report creation .................................................................................................................. 40
2.4 Batch Submission Process .......................................................................................................... 42

Financial Intelligence Unit – India (FIU-IND) Page |3

 User Manual - FINGate 2.0 - Reports Version 1.1

2.5 Report modification through manual process ............................................................................ 43

2.6 Adding more reports to an existing batch .................................................................................. 45
2.7 Batch Recall and Resubmission Process ..................................................................................... 46
3 Annexures .......................................................................................................................................... 48
3.1 Bulk Templates ........................................................................................................................... 48
3.1.1 KC1 - KYC Individuals - Bulk Template ................................................................................ 48
3.1.2 KC2 - KYC Non-Individuals - Bulk Template......................................................................... 54
3.1.3 KCS1 - Simplified KYC Individuals - Bulk Template .............................................................. 58
3.1.4 KCS2 - Simplified KYC Non-Individuals - Bulk Template ...................................................... 62
3.1.5 Account_Detail - Account Details - Bulk Template ............................................................. 64
3.1.6 Account_Person_Relation - Account to Person Relationship - Bulk Template ................... 65
3.1.7 TC1 - Transaction - Cash at ATM - Bulk Template............................................................... 65
3.1.8 TC2-Transaction-Cash at Branch-Bulk Template ................................................................ 67
3.1.9 TC3 -Transaction- Casino cash transaction -Bulk Template ................................................ 68
3.1.10 TS1 - NPO NEFT/RTGS Transaction. - Bulk Template .......................................................... 70
3.1.11 TS2 - NPO IMPS transaction. - Bulk Template..................................................................... 71
3.1.12 TS3 - NPO UPI Transaction - Bulk Template ........................................................................ 73
3.1.13 GT1 - General transaction format- Bulk Template.............................................................. 75
3.1.14 CB1 - Cross-border wire transfer- Bulk Template ............................................................... 78
3.1.15 CC1 - Counterfeit currency transaction. - Bulk Template ................................................... 82
3.1.16 Counterfeit_Detail - Bulk Template .................................................................................... 83
3.1.17 CB2- Cross Border Wire Transaction for Casino - Bulk Template ....................................... 84
3.1.18 TS6 – Wallet STR Format - Bulk Template .......................................................................... 86
3.1.19 TS7 – Brokerage Firms STR Format - Bulk Template ........................................................... 87
3.1.20 TS8 – Exchange House STR Format - Bulk Template........................................................... 88
3.1.21 TS9 – Depositories STR Format - Bulk Template................................................................. 89
3.1.22 TS10 – NBFC STR Format - Bulk Template .......................................................................... 90
3.1.23 TS11 – Card System Operators STR Format - Bulk Template .............................................. 92
3.1.24 TS12 – Casino STR Format - Bulk Template ........................................................................ 94
3.1.25 MT1 – MTSS Transaction Reporting Format -Bulk Template .............................................. 95
3.1.26 PTR -Property Transaction -Bulk Template ....................................................................... 100
3.2 Acronyms and Abbreviations .................................................................................................... 103

Financial Intelligence Unit – India (FIU-IND) Page |4

 User Manual - FINGate 2.0 - Reports Version 1.1

1 Introduction

1.1 Purpose

Project FINnet 2.0 envisions to streamline and redefine the process of collection, processing, and
dissemination of data for the purpose of effectively generating meaningful intelligence to curb
money laundering activities and enforce the provision of PMLA in India. This is a project of national
importance and aims to strengthen the financial security architecture of India. The mission
statement of FINnet 2.0 states – To provide quality financial intelligence for safeguarding the
financial system from the abuses of money laundering, terrorism financing, and other economic
offenses.

FINnet 2.0 is implemented as a set of three (3) systems to ensure that the data ingested and
processed by the three is isolated and immune to security threats as much as possible and all data
is secure. The systems are listed below –

1. FINGate – Collection and pre-processing system

2. FINCore – Processing and analysis system

3. FINex – Dissemination system

The proposed FINGate system shall consist of multiple reporting mechanisms to ensure compliance
and facilitate quick and easy reporting.

This document is the user manual for FINGate Portal – Reports module of the FINnet 2.0 System. To
access the FINGate portal, navigate to https://fingate.gov.in.

1.2 Scope

The scope of this document is to provide guidance on using the FINGate module and act as a user
manual. The functionalities covered in this user manual are submission of:

1. Cash Transaction Report (CTR)

2. Property Transaction Report (PTR)
3. Cross Border Wire Transfer Report (CBWTR)
4. Counterfeit Currency Report (CCR)
5. Non-Profit Organisation Transaction Report (NTR)
6. Suspicious Transaction Report (STR)

The target audience for this user manual is:

1. Principal Officers of RE
2. Designated Directors of RE
3. Non Principal Officer users of RE

The following functionalities are excluded in this version of the user manual and will be included
in subsequent versions of the user manual.

1. Actions post report submission for all reports

2. Desktop app for report submission

Financial Intelligence Unit – India (FIU-IND) Page |5

 User Manual - FINGate 2.0 - Reports Version 1.1

2 Report Preparation and Submission

This sub-module deals with report preparation and submission by REs using FINGate 2.0 portal.
Reports can be prepared either by the principal officer or non-principal officer user. Only the principal
officer can submit the batches which consist of one or more reports. Users can create the reports in
bulk or individually.

All the reports submitted will have the following report sections:

a) KYC profile
i. The KYC section of the report is compulsory for all reports where the RE is filing a
report on its customers or non-customers.
ii. The KYC and Transaction formats have been combined for certain RE types including
MTSS, Card System Operators and all Property transactions.
iii. Along with a common KYC profile, there would also be account profile that would
capture details of different accounts held by the customer. This account profile would
differ based on the RE type. As an example, a banking account profile would be
different from an insurance policy account.
iv. The relationships between KYC / Simplified KYC with the accounts must be specified in
the Account Person Relation section
b) Transaction profile

i. The Transaction section of the report covers details of every transaction that the RE is
including as part of the concerned report.
ii. For each type of format, the RE has the flexibility to report one or many transactions.
iii. For each type of transaction, the format will be standardised. Such a format may differ
across RE types but will be the same within a RE type.

2.1 Overview of ‘Report dashboard navigation and actions’

The user will access the reports module by clicking on ‘My Reports’ link on the left panel.

The user will view major tabs for report preparation and submission. This section will give an
overview to navigate through the ‘My Reports’ module of FINGate 2.0 system.

Financial Intelligence Unit – India (FIU-IND) Page |6

 User Manual - FINGate 2.0 - Reports Version 1.1

1. Bulk Data Upload: The user will be able to upload data to create bulk submission. Source data
for multiple reports and report types can be uploaded at once which can also be modified from
the below screen. Furthermore, the user can also upload the incremental data to the previously
uploaded data.

2. Batch Creation: The user will be able to create batch from the uploaded data. The user can view the
list of all the batches created till date irrespective of the batch status and can also filter the reports
by the respective batch ‘Status’.

Reports: The user will be able to view all the created reports. The user can do the modification to
an existing report and can also add more reports to an existing batch. The user will also be able to
filter the reports by their respective ‘Batch Number’, ‘Report Type’ and ‘Status’. Furthermore, the
user can delete the reports in the draft status.

Financial Intelligence Unit – India (FIU-IND) Page |7

 User Manual - FINGate 2.0 - Reports Version 1.1

3. Create New Report: In this tab, the user will input certain reference fields to initiate batch
creation for the following report types:
• Reports to be submitted periodically
1. Cash Transaction Report (CTR)
2. Cross Border Wire Transfer Report (CBWTR)
3. Property Transaction Report (PTR)
4. Non-Profit Organization Transaction Report (NTR)
5. Counterfeit Currency Transaction Report (CCR)

• Alert Based Reports

1. Suspicious Transaction Report (STR)

2.2 Batch and Report creation through Bulk Upload process

A batch is referred to as a group of reports submitted by a RE PO. A batch can only contain one
type of report. For instance, a batch can only have one or more CTRs or STRs, but a batch cannot
contain both a CTR and STR. Each record within a batch will be referred to as a report, which will
be a combination of the KYC section, transaction(s), and GoS (in case of STR only).

2.2.1 Bulk Data Upload

1. The user will navigate to ‘Bulk Data Upload’ tab as shown in the below screenshot.

Financial Intelligence Unit – India (FIU-IND) Page |8

 User Manual - FINGate 2.0 - Reports Version 1.1

2. The user will click on ‘Add’.

3. The user will be directed to the ‘Bulk Data Upload’ page from where the option to browse and
select the applicable .zip file for bulk upload can be accessed.

4. Allowed file format is CSV. The files are to be uploaded as a .zip file.
5. The zip file should not have any sub folders, the upload will fail in this case.
6. The different report types will have applicable sample .zip files. The .zip file will contain all the
report type specific relevant KYC, transaction and GOS format files.
Please refer to Annexure (Section 3.1) to view the template of the .csv file.
7. The user can update only the applicable format files and can choose to remove the irrelevant
format files from the .zip folder to be uploaded.
8. Please note that the names of the csv files should not be changed.
9. The user can load data as fresh or incremental data. The details are listed below.

2.2.1.1 Fresh data

The user can choose to upload fresh data. This will ensure that all previously loaded files are overwritten,
and data in the current file will be considered for creation of batches and reports.

Financial Intelligence Unit – India (FIU-IND) Page |9

 User Manual - FINGate 2.0 - Reports Version 1.1

2.2.1.2 Incremental data

The user can upload incremental data. Using this option, the user will be able to incrementally add more
data to the previously uploaded data. If the user has distributed all the report data into multiple zip files,
then the first zip file should be uploaded with option as ‘Fresh data’ and subsequent files should be
uploaded with option as ‘Incremental Data’. After all the files have been uploaded, errors corrected,
batches created and submitted the cycle for the current period is completed.

In the next cycle or for additional reports to be created, the process mentioned above must be repeated.

Financial Intelligence Unit – India (FIU-IND) P a g e | 10

 User Manual - FINGate 2.0 - Reports Version 1.1

2.2.2 Rectification of errors during bulk upload

After uploading source data, the user will be able to view all the errors in the uploaded file.

2.2.2.1 Error rectification directly through portal

1. The user can also modify the errors directly though the portal.
2. The user can click on the error count to see the error details in the respective record.
3. The user can hover over ‘error’ to know the error details and then click the ‘edit’ icon to modify the
record.

Financial Intelligence Unit – India (FIU-IND) P a g e | 11

 User Manual - FINGate 2.0 - Reports Version 1.1

Financial Intelligence Unit – India (FIU-IND) P a g e | 12

 User Manual - FINGate 2.0 - Reports Version 1.1

2.2.2.2 Error rectification in bulk file

1. The user can download the error file.

2. The user can make the changes in the source file and upload again as fresh data.

2.2.3 Batch Creation from bulk uploaded source data

1. After uploading bulk source data and correcting all the identified errors, the user can proceed with
batch creation.
2. Users should take care to correct all errors before batch creation, else the system will ignore records
with errors for the batch creation and proceed with the rest of the records.
3. It should be noted that FIU will conduct advanced data validations after batch submission. RE should
not assume that the errors detected in the portal are the complete list of data validations. It is possible
that reports may get rejected subsequently by FIU after report submission.
4. The user shall click on the ‘Batch creation’ tab.

Financial Intelligence Unit – India (FIU-IND) P a g e | 13

 User Manual - FINGate 2.0 - Reports Version 1.1

5. The user will be navigated to the ‘New batch’ screen where the user can select the report type as the
uploaded data.
6. The user is required to select the relevant reporting month. In the case of PTR, user should select the
reporting quarter. In the case of STR, user should select the reporting date.
7. The user shall also mention the Batch reference number which can be of ‘alphanumeric’ type. This
number is an internal reference number of the RE and FIU will not do any validations on this number.

2.3 Batch and Report creation through Manual process

1. The user can create reports manually by using web form in the portal.
2. The user shall navigate to the ‘Create new report’ tab. The user will be directed to ‘New report’
screen.
3. The user can choose from six report types that are listed below. Please note that only the report
types applicable for the RE type will be listed.
a) Cash Transaction Report (CTR)
b) Property Transaction Report (PTR)
c) Counterfeit Currency Transaction Report (CCR)
d) Non-Profit Organisation Transaction Report (NTR)
e) Cross Border Wire Transfer Report (CBWTR)
f) Suspicious Transaction Report (STR)
4. The user shall mention report reference number, batch reference number as well as reporting
period is to be selected from the drop down. The report reference and batch reference number
are alphanumeric and are internal reference numbers of RE. FIU will not perform any validations
on this.

Financial Intelligence Unit – India (FIU-IND) P a g e | 14

 User Manual - FINGate 2.0 - Reports Version 1.1

5. The user shall click on ‘Save & Next’ to proceed.

2.3.1 Report Preparation

1. The user will land on the below page on selecting the report type.
2. The user can see previously entered details such as reporting period, batch, and report reference
number.
3. This information will be common for every report type.
4. The detailed process of report creation for every report type is explained in the next sections.

2.3.1.1 Cash transaction Report Type (CTR) for Banks

1. The user will see the following tabs for Cash transaction Report type:
a) Customer
i. Individual KYC – to be filled for Individual persons
ii. Non-Individual KYC – to be filled for non-individuals or legal entities
iii. Account Details – to be filled with account details. If the transactions pertain to a customer,
please ensure that the account details are entered and saved before entering the
transaction details.
iv. Account Person Relation – the KYC details for individual / non-individual for customers
and simplified KYC for non-customers need to be linked to the account.
b) Non-Customer
i. Simplified KYC Individual - to be filled for Individual persons

Financial Intelligence Unit – India (FIU-IND) P a g e | 15

 User Manual - FINGate 2.0 - Reports Version 1.1

ii. Simplified KYC Non-Individual - to be filled for non-individuals

c) Transaction detail
i. Cash at ATM
ii. Cash at Branch
2. User can fill multiple KYC details in one CTR, minimum one KYC is mandatory. After filling the details,
click on ‘Save’. Mandatory fields need to be filled to save the records.
3. Account detail is mandatory in case of customer.
4. There can be multiple transactions in one CTR. After filling the details, click on ‘Save’. Mandatory
fields need to be filled to save the records.
5. The user can select and fill relevant KYC (for customer and non-customer) and transaction from the
list view as shown below.

Financial Intelligence Unit – India (FIU-IND) P a g e | 16

 User Manual - FINGate 2.0 - Reports Version 1.1

2.3.1.2 Counterfeit Currency Report (CCR) for Banks

1. The user will see the following tabs for Counterfeit currency Report type:
a) Customer
i. Individual KYC – to be filled for Individual persons
ii. Non-Individual KYC – to be filled for non-individuals
iii. Account Details – to be filled with account details
iv. Account Person Relation– the KYC details for individual / non-individual for customers and
simplified KYC for non-customers need to be linked to the account.
b) Non-Customer
i. Simplified KYC Individual - to be filled for Individual persons
ii. Simplified KYC Non-Individual - to be filled for non-individuals
c) Transaction detail
i. Counterfeit currency deposited
2. User can fill multiple KYC details in one CCR, KYC is not mandatory. However, if KYC is available, then
the RE must provide it. After filling the details, click on ‘Save’. Mandatory fields need to be filled to save
the records.
3. Account detail is mandatory in case of customer.
4. There can be multiple transactions in one CCR. After filling the details, click on ‘Save’. Mandatory fields
need to be filled to save the records.
5. The user can select and fill relevant KYC (for customer and non-customer) and transaction from the list
view as shown below.

Financial Intelligence Unit – India (FIU-IND) P a g e | 17

 User Manual - FINGate 2.0 - Reports Version 1.1

2.3.1.3 Non-Profit Organisation Transaction Report (NTR) for Banks

1. The user will see the following tabs for NTR Report type:
a) Customer
i. Individual KYC – to be filled for Individual persons
ii. Non-Individual KYC – to be filled for non-individuals
iii. Account Details – to be filled with account details
iv. Account Person Relation – the KYC details for individual / non-individual for customers
and simplified KYC for non-customers need to be linked to the account.
b) Non-Customer
i. Simplified KYC Individual - to be filled for Individual persons
ii. Simplified KYC Non-Individual - to be filled for non-individuals

Financial Intelligence Unit – India (FIU-IND) P a g e | 18

 User Manual - FINGate 2.0 - Reports Version 1.1

c) Transaction detail
i. NEFT/RTGS Transaction
ii. IMPS transaction
iii. UPI Transaction
iv. Cash transaction at ATM
v. Cash transaction at branch
vi. General transaction format
2. User can fill multiple KYC details in one NTR, minimum one KYC is mandatory. After filling the details,
click on ‘Save’. Mandatory fields need to be filled to save the records.
3. Account detail is mandatory in case of customer.
4. There can be multiple transactions in one NTR. After filling the details, click on ‘Save’. Mandatory
fields need to be filled to save the records.
5. The user can select and fill relevant KYC (for customer and non-customer) and transaction from the
list view as shown below.

Financial Intelligence Unit – India (FIU-IND) P a g e | 19

 User Manual - FINGate 2.0 - Reports Version 1.1

2.3.1.4 Cross Border Wire Transfer Reports (CBWTR) for Banks

1. The user will see the following tabs for Cross Border Wire Transfer Report:
a) Customer
i. Individual KYC – to be filled for Individual persons
ii. Non-Individual KYC – to be filled for non-individuals
iii. Account Details – to be filled with account details
iv. Account Person Relation– the KYC details for individual / non-individual for customers
and simplified KYC for non-customers need to be linked to the account.
b) Non-Customer
i. Simplified KYC Individual - to be filled for Individual persons
ii. Simplified KYC Non-Individual - to be filled for non-individuals
c) Transaction detail
i. Cross border wire transfer beyond specified threshold
2. User can fill multiple KYC details in one CBWTR, minimum one KYC is mandatory. After filling the
details, click on ‘Save’. Mandatory fields need to be filled to save the records.
3. Account detail is mandatory in case of customer.
4. There can be multiple transactions in one CBWTR. After filling the details, click on ‘Save’. Mandatory
fields need to be filled to save the records.
5. The user can select and fill relevant KYC (for customer and non-customer) and transaction from the
view as shown below.

Financial Intelligence Unit – India (FIU-IND) P a g e | 20

 User Manual - FINGate 2.0 - Reports Version 1.1

2.3.1.5 Suspicious Transaction Reports (STR) for Banks

1. The user will see the following tabs for Suspicious Transaction Report:
a. Customer
i. Individual KYC – to be filled for Individual persons
ii. Non-Individual KYC – to be filled for non-individuals
iii. Account Details – to be filled with account details
iv. Account Person Relation– the KYC details for individual / non-individual for
customers and simplified KYC for non-customers need to be linked to the
account.
b. Non-Customer
i. Simplified KYC Individual - to be filled for Individual persons
ii. Simplified KYC Non-Individual - to be filled for non-individuals
c. Transaction detail
i. Cash ATM – for cash transactions conducted at an ATM/CDM
ii. Cash Branch – for cash transactions conducted at a branch
iii. NEFT – for transactions conducted via NEFT/RTGS
iv. IMPS – for transactions conducted via IMPS
v. Bank UPI – for transactions conducted via UPI
vi. General Reporting – for general reporting of transactions.
d. Ground of Suspicion
2. User can fill multiple KYC details in one STR, minimum one KYC is mandatory. After filling the
details, click on ‘Save’. Mandatory fields need to be filled to save the records.
3. Account detail is mandatory in case of customer.

Financial Intelligence Unit – India (FIU-IND) P a g e | 21

 User Manual - FINGate 2.0 - Reports Version 1.1

4. There can be multiple transactions in one STR. After filling the details, click on ‘Save’. Mandatory
fields need to be filled to save the records.
5. The user can select and fill relevant KYC (for customer and non-customer) and transaction details.
6. The following sections, as described below, constitute the GOS profile –
a. First part shows the KYC summary. These details will be auto populated from the KYC /
simplified KYC details entered and is non-editable. User should select at least one record
as ‘Primary Entity’.
b. Second part shows the transaction summary. These details will be auto populated and
non-editable
c. Third part shows the account summary of all reported accounts. Transaction summaries
for 12 months preceding the first reported transaction need to be entered by the RE user
for each account.
d. User must enter the details of Fund Flow – Source and Destination of Funds in the next
section
e. User will be required to add tags to the report depending on suspicions, in the next section
f. In the following section, user will then have to respond to queries that would be system
generated based on the tags selected above.
g. User may add attachments as shown below. Maximum size of each attachment is 5MB.
Multiple attachments can be uploaded up to 5 attachments. Allowed file types are pdf,
doc, docx, jpg, png, xls, xlsx and zip.

Financial Intelligence Unit – India (FIU-IND) P a g e | 22

 User Manual - FINGate 2.0 - Reports Version 1.1

Financial Intelligence Unit – India (FIU-IND) P a g e | 23

 User Manual - FINGate 2.0 - Reports Version 1.1

2.3.1.6 Cash transaction Report Type (CTR) for Casino

1. The user will see the following tabs for Cash transaction Report type:
a) Non-Customer

i. Simplified KYC Individual - to be filled for Individual persons

ii. Simplified KYC Non-Individual - to be filled for non-individuals

b) Transaction detail

i. Casino cash transaction format

2. User can fill multiple KYC details in one CTR, minimum one KYC is mandatory. After filling the details,
click on ‘Save’. Mandatory fields need to be filled to save the records.
3. There can be multiple transactions in one CTR. After filling the details, click on ‘Save’. Mandatory
fields need to be filled to save the records.
4. The user can select and fill relevant non-customer KYC and transaction from the list view as shown
below.

Financial Intelligence Unit – India (FIU-IND) P a g e | 24

 User Manual - FINGate 2.0 - Reports Version 1.1

2.3.1.7 Cross Border Wire Transfer Report (CBWTR) for Casino

1. The user will see the following tabs for Cross Border Wire Transfer Report:
a) Non-Customer
i. Simplified KYC Individual - to be filled for Individual persons
ii. Simplified KYC Non-Individual - to be filled for non-individuals
b) Transaction detail
i. Casino CBWTR Format
2. User can fill multiple KYC details in one CBWTR, minimum one KYC is mandatory. After filling the
details, click on ‘Save’. Mandatory fields need to be filled to save the records.
3. There can be multiple transactions in one CBWTR. After filling the details, click on ‘Save’. Mandatory
fields need to be filled to save the records.
4. The user can select and fill relevant KYC (for customer and non-customer) and transaction from the
list view as shown below.

Financial Intelligence Unit – India (FIU-IND) P a g e | 25

 User Manual - FINGate 2.0 - Reports Version 1.1

2.3.1.8 Suspicious Transaction Report (STR) for Casino

1. The user will see the following tabs for Suspicious Transaction Report:
a. Non-Customer
i. Simplified KYC Individual - to be filled for Individual persons
ii. Simplified KYC Non-Individual - to be filled for non-individuals or legal entities
b. Transaction detail
i. Casino STR format
c. Ground of Suspicion
2. User can fill multiple KYC details in one STR, minimum one KYC is mandatory. After filling the
details, click on ‘Save’. Mandatory fields need to be filled to save the records.
3. There can be multiple transactions in one STR. After filling the details, click on ‘Save’. Mandatory
fields need to be filled to save the records.
4. The user can select and fill relevant KYC (for customer and non-customer) and transaction from
the list view as shown below.
5. GOS profile must be entered as detailed in section 2.3.1.5, point 6 of this document.

2.3.1.9 Cash Transaction Report Type (CTR) for FI/NBFC/Others

1. The user will see the following tabs for Cash Transaction Report type:
a) Customer
i. Individual KYC – to be filled for Individual persons
ii. Non-Individual KYC – to be filled for non-individuals
iii. Account Details – to be filled with account details

Financial Intelligence Unit – India (FIU-IND) P a g e | 26

 User Manual - FINGate 2.0 - Reports Version 1.1

iv. Account Person Relation – the KYC details for individual / non-individual for customers and
simplified KYC details for non-customers need to be linked to the account.
b) Non-Customer
i. Simplified KYC Individual - to be filled for Individual persons
ii. Simplified KYC Non-Individual - to be filled for non-individuals
c) Transaction detail
i. Cash at Branch
2. User can fill multiple KYC details in one CTR, minimum one KYC is mandatory. After filling the details,
click on ‘Save’. Mandatory fields need to be filled to save the records.
3. Account detail is mandatory in case of customer.
4. There can be multiple transactions in one CTR. After filling the details, click on ‘Save’. Mandatory
fields need to be filled to save the records.
5. The user can select and fill relevant KYC (for customer and non-customer) and transaction from the
list view as shown below.

Financial Intelligence Unit – India (FIU-IND) P a g e | 27

 User Manual - FINGate 2.0 - Reports Version 1.1

2.3.1.10 Suspicious Transaction Report Type (STR) for FI/NBFC/Others

1. The user will see the following tabs for Suspicious Transaction Report:
a. Customer
i. Individual KYC – to be filled for Individual persons
ii. Non-Individual KYC – to be filled for non-individuals
iii. Account Details – to be filled with account details
iv. Account Person Relation – the KYC details for individual / non-individual for
customers and simplified KYC details for non-customers need to be linked to the
account.
b. Non-Customer
i. Simplified KYC Individual - to be filled for Individual persons
ii. Simplified KYC Non-Individual - to be filled for non-individuals
c. Transaction detail
i. NBFC STR Format
d. Ground of Suspicion
2. User can fill multiple KYC details in one STR, minimum one KYC is mandatory. After filling the
details, click on ‘Save’. Mandatory fields need to be filled to save the records. Every STR must have
one GOS record
3. Account detail is mandatory in case of customer.
4. There can be multiple transactions in one STR. After filling the details, click on ‘Save’. Mandatory
fields need to be filled to save the records.
5. The user can select and fill relevant KYC (for customer and non-customer) and transaction details.
6. GOS profile must be entered as detailed in section 2.3.1.5, point 6 of this document.

Financial Intelligence Unit – India (FIU-IND) P a g e | 28

 User Manual - FINGate 2.0 - Reports Version 1.1

Financial Intelligence Unit – India (FIU-IND) P a g e | 29

 User Manual - FINGate 2.0 - Reports Version 1.1

2.3.1.11 Suspicious Transaction Report Type (STR) for Payment Aggregators

1. The user will see the following tabs for Suspicious Transaction Report:
a. Customer
i. Individual KYC – to be filled for Individual persons
ii. Non-Individual KYC – to be filled for non-individuals
iii. Account Details – to be filled with account details
iv. Account Person Relation – the KYC details for individual / non-individual for
customers and simplified KYC details for non-customers need to be linked to the
account.
b. Non-Customer
i. Simplified KYC Individual - to be filled for Individual persons
ii. Simplified KYC Non-Individual - to be filled for non-individuals
c. Transaction detail
i. Bank UPI – for reporting UPI payments
ii. Wallet – for reporting wallet payments
iii. General Reporting – for general transaction reporting
d. Ground of Suspicion
2. User can fill multiple KYC details in one STR, minimum one KYC is mandatory. After filling the
details, click on ‘Save’. Mandatory fields need to be filled to save the records. Every STR must
have one GOS record
3. Account detail is mandatory in case of customer.
4. There can be multiple transactions in one STR. After filling the details, click on ‘Save’. Mandatory
fields need to be filled to save the records.
5. The user can select and fill relevant KYC (for customer and non-customer) and transaction
details.
6. GOS profile must be entered as detailed in section 2.3.1.5, point 6 of this document.

Financial Intelligence Unit – India (FIU-IND) P a g e | 30

 User Manual - FINGate 2.0 - Reports Version 1.1

Financial Intelligence Unit – India (FIU-IND) P a g e | 31

 User Manual - FINGate 2.0 - Reports Version 1.1

2.3.1.12 Suspicious Transaction Report Type (STR) for Brokerage Firms

1. The user will see the following tabs for Suspicious Transaction Report:
a. Customer
i. Individual KYC – to be filled for Individual persons
ii. Non-Individual KYC – to be filled for non-individuals
iii. Account Details – to be filled with account details
iv. Account Person Relation – the KYC details for individual / non-individual for
customers and simplified KYC details for non-customers need to be linked to the
account.
b. Non-Customer
i. Simplified KYC Individual - to be filled for Individual persons
ii. Simplified KYC Non-Individual - to be filled for non-individuals
c. Transaction detail
i. Brokerage STR Format
d. Ground of Suspicion
2. User can fill multiple KYC details in one STR, minimum one KYC is mandatory. After filling the
details, click on ‘Save’. Mandatory fields need to be filled to save the records. Every STR must have
one GOS record.
3. Account detail is mandatory in case of customer.
4. There can be multiple transactions in one STR. After filling the details, click on ‘Save’. Mandatory
fields need to be filled to save the records.
5. The user can select and fill relevant KYC (for customer and non-customer) and transaction details.
6. GOS profile must be entered as detailed in section 2.3.1.5, point 6 of this document.

Financial Intelligence Unit – India (FIU-IND) P a g e | 32

 User Manual - FINGate 2.0 - Reports Version 1.1

2.3.1.13 Suspicious Transaction Report Type (STR) for Exchange Houses

1. The user will see the following tabs for Suspicious Transaction Report:
a. Customer
i. Individual KYC – to be filled for Individual persons
ii. Non-Individual KYC – to be filled for non-individuals
iii. Account Details – to be filled with account details
iv. Account Person Relation – the KYC details for individual / non-individual for
customers and simplified KYC details for non-customers need to be linked to the
account.
b. Non-Customer
i. Simplified KYC Individual - to be filled for Individual persons
ii. Simplified KYC Non-Individual - to be filled for non-individuals
c. Transaction detail
i. Exchange Houses STR Format
d. Ground of Suspicion
2. User can fill multiple KYC details in one STR, minimum one KYC is mandatory. After filling the
details, click on ‘Save’. Mandatory fields need to be filled to save the records. Every STR must
have one GOS record
3. Account detail is mandatory in case of customer.
4. There can be multiple transactions in one STR. After filling the details, click on ‘Save’. Mandatory
fields need to be filled to save the records.

Financial Intelligence Unit – India (FIU-IND) P a g e | 33

 User Manual - FINGate 2.0 - Reports Version 1.1

5. The user can select and fill relevant KYC (for customer and non-customer) and transaction
details.
6. GOS profile must be entered as detailed in section 2.3.1.5, point 6 of this document.

Financial Intelligence Unit – India (FIU-IND) P a g e | 34

 User Manual - FINGate 2.0 - Reports Version 1.1

2.3.1.14 Suspicious Transaction Report Type (STR) for Depositories

1. The user will see the following tabs for Suspicious Transaction Report:
a. Customer
i. Individual KYC – to be filled for Individual persons
ii. Non-Individual KYC – to be filled for non-individuals
iii. Account Details – to be filled with account details
iv. Account Person Relation – the KYC details for individual / non-individual for
customers and simplified KYC details for non-customers need to be linked to the
account.
b. Non-Customer
i. Simplified KYC Individual - to be filled for Individual persons
ii. Simplified KYC Non-Individual - to be filled for non-individuals
c. Transaction detail
i. Depositories STR Format
d. Ground of Suspicion
2. User can fill multiple KYC details in one STR, minimum one KYC is mandatory. After filling the
details, click on ‘Save’. Mandatory fields need to be filled to save the records. Every STR must
have one GOS record
3. Account detail is mandatory in case of customer.
4. There can be multiple transactions in one STR. After filling the details, click on ‘Save’. Mandatory
fields need to be filled to save the records.
5. The user can select and fill relevant KYC (for customer and non-customer) and transaction
details.
6. GOS profile must be entered as detailed in section 2.3.1.5, point 6 of this document.

Financial Intelligence Unit – India (FIU-IND) P a g e | 35

 User Manual - FINGate 2.0 - Reports Version 1.1

Financial Intelligence Unit – India (FIU-IND) P a g e | 36

 User Manual - FINGate 2.0 - Reports Version 1.1

2.3.1.15 Suspicious Transaction Report Type (STR) for MTSS

1. The user will see the following tabs for Suspicious Transaction Report:
a. Transaction detail
i. Combined KYC and Transaction Profile
b. Ground of Suspicion
2. User can fill multiple Transaction details in one STR, minimum one Transaction is mandatory.
After filling the details, click on ‘Save’. Mandatory fields need to be filled to save the records.
Every STR must have one GOS record
3. GOS profile must be entered as detailed in section 2.3.1.5, point 6 of this document.

Financial Intelligence Unit – India (FIU-IND) P a g e | 37

 User Manual - FINGate 2.0 - Reports Version 1.1

2.3.1.16 Suspicious Transaction Report Type (STR) for Card System Operators

1. The user will see the following tabs for Suspicious Transaction Report:
a. Transaction detail
i. Card System Operators STR Format
b. Ground of Suspicion
2. There can be multiple transactions in one STR. After filling the details, click on ‘Save’. Mandatory
fields need to be filled to save the records. Every STR must have one GOS record.
3. GOS profile must be entered as detailed in section 2.3.1.5, point 6 of this document.

Financial Intelligence Unit – India (FIU-IND) P a g e | 38

 User Manual - FINGate 2.0 - Reports Version 1.1

2.3.1.17 Property Transaction Report (PTR)

1. The user will see the following tabs for Property transaction Report type:
a) Combined KYC and Transaction detail
2. User can fill multiple transactions in one PTR. After filling the details, click on ‘Save’. Mandatory fields
need to be filled to save the records.
3. The user can select and fill relevant transactions from the view as shown below.

Financial Intelligence Unit – India (FIU-IND) P a g e | 39

 User Manual - FINGate 2.0 - Reports Version 1.1

2.3.2 Report creation

1. Once the user fills all the relevant details in the form, the user can click on save.
2. The user will be able to preview the filled details.
3. The user can click on ‘Back to list’ to view the summary.
4. The user can add more KYC/transaction type.
5. The user can finally navigate to the ‘reports’ tab to view the created report.

Financial Intelligence Unit – India (FIU-IND) P a g e | 40

 User Manual - FINGate 2.0 - Reports Version 1.1

Financial Intelligence Unit – India (FIU-IND) P a g e | 41

 User Manual - FINGate 2.0 - Reports Version 1.1

2.4 Batch Submission Process

1. For submitting any draft batch, the user can click on the view icon.
2. The user will be able to view all the reports inside the batch.
3. The user can click on the ‘Submit’ button.
4. The user will be required to upload DSC.
5. Post successful upload of DSC the user can view the status of the batch as submitted.
6. Unique Batch ID and unique Report ID shall be generated by the system for each batch and each
report being submitted.

Financial Intelligence Unit – India (FIU-IND) P a g e | 42

 User Manual - FINGate 2.0 - Reports Version 1.1

2.5 Report modification through manual process

1. The user can modify the reports in ‘draft’ status.

2. The user can either navigate to any report through batch or the user can directly select any
report and edit/modify it.
3. The user shall go to the ‘Batch creation’ tab and then click on view icon.
4. The user will be able to view all the reports inside the batch.
5. On clicking the view button adjacent to any report, the user will be navigated to the ‘reports’
dashboard.
6. The user can click on the view button again to go inside the report and then the user can select
the already filled KYC/transaction format from the dropdown to edit the record.
7. The user will see edit icon adjacent to every KYC/transaction line item.eg. If the user initially filled
individual KYC form, then for updating that form the user shall select ‘individual KYC’ from the
customer tab.
8. Post editing the required field, the user can click on ‘update’.

Financial Intelligence Unit – India (FIU-IND) P a g e | 43

 User Manual - FINGate 2.0 - Reports Version 1.1

Financial Intelligence Unit – India (FIU-IND) P a g e | 44

 User Manual - FINGate 2.0 - Reports Version 1.1

2.6 Adding more reports to an existing batch

1. The user can add more reports to an existing batch by navigating to the ‘Reports’ tab and clicking
on ‘New Report’.
2. In the next page, select the report type, enter the RE report reference number, same RE batch
reference number in which new reports is to be added, reporting period and click on ‘Save & Next’.
3. The KYC and transaction details can be entered and saved. The new report will get added to the
existing batch.

Financial Intelligence Unit – India (FIU-IND) P a g e | 45

 User Manual - FINGate 2.0 - Reports Version 1.1

2.7 Batch Recall and Resubmission Process

1. Batches with submitted status can be recalled.

2. The user can click on the view button.
3. The user will be able to view all the reports inside the batch.
4. The user can click on the ‘Recall’ button and enter the reason of recall.
5. The user will get confirmation message as well as success message pop-up.
6. The user will be able to see the batch status as ‘recalled’

Financial Intelligence Unit – India (FIU-IND) P a g e | 46

 User Manual - FINGate 2.0 - Reports Version 1.1

7. The user can view the batch again in the list view, the status of the batch now will be “recalled”.
8. Batches with “recalled” status will only be in Read only mode.

Financial Intelligence Unit – India (FIU-IND) P a g e | 47

 User Manual - FINGate 2.0 - Reports Version 1.1

3 Annexures

3.1 Bulk Templates

3.1.1 KC1 - KYC Individuals - Bulk Template

The name of the file is KC1 and should not be changed. This file is used to capture data of Customer KYC
for Individuals.

Column Description Mandatory Validation Rules

Report Report Reference All KYC and transactions to be grouped under one
Reference Number maintained Yes report should have the same report reference
Number by RE number.
Unique customer ID
UCIC provided to the Yes
customer
Customer ID
Customer ID provided to the Yes
customer
PAN Number of the entity
Format: 10 Digit. (AAAAA)(NNNN)(A).
A = Alphabet and N = Number

PAN PAN of the individual No 4th Alphabet (AAAAA) will be "P" for individuals

FIU will accept reports without PAN up to a

threshold. If this threshold is exceeded, then
subsequent reports will get rejected.
Declaration (If If the PAN is not If the PAN is not
PAN is not available, this available, enter NA.
available) becomes mandatory Else leave it blank.
Format: 14 Digit Number
1. No Special Characters are allowed.
2. No Spaces are allowed.
CKYC number of the
CKYC Number No
individual
FIU will accept reports without CKYC up to a
threshold. If this threshold is exceeded, then
subsequent reports will get rejected.
Declaration (If If the CKYC Number If the CKYC Number is
CKYC is not is not available, this not available, enter
available) becomes mandatory NA. Else leave it blank.
Mandatory to give one
of five - Passport,
NREGA card, Voter ID,
If nationality is Indian then Passport number of
Driver’s License or
the individual should be in format ANNNNNNN
NPR number if PAN &
Format : 8 Alphanumeric
Passport Passport number of CKYC not available.
A = Upper case Alphabet, N = Number
Number the individual
If Nationality is not 'Indian' field length to be set
In case related
as 3 to 30
account been
NRE/NRO then
Passport number will
be mandatory
Voter ID of the Mandatory to give one 10 digit Alphanumeric (AAANNNNNNN)
Voter ID
individual of five - Passport, A = Alphabet

Financial Intelligence Unit – India (FIU-IND) P a g e | 48

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

NREGA card, Voter ID, N= Number
Driver’s License or
NPR number if PAN &
CKYC not available.
Mandatory to give one
of five - Passport,
Driver’s License
Driver’s License NREGA card, Voter ID, In case nationality is not 'Indian' field length for
Number of the
Number Driver’s License or driver's license should be 3 to 30
Individual
NPR number if PAN &
CKYC not available.
Mandatory to give one
of five - Passport, NREGA CARD
NREGA Card number NREGA card, Voter ID, Format: 16 Digit Alphanumeric
NREGA Card
of the individual Driver’s License or (AANNNNNNNNNNNNNN)
NPR number if PAN & A = Alphabet, N= Number
CKYC not available.
Unique ID of all the DIN format: 8 - digit numeric.
DIN / DPIN directors of the No DPIN format: 8 - digit numeric.
entity Mandatory if customer is a director.
1. Special Characters are not allowed.
First name of the
First Name Yes 2. Spaces are not allowed.
individual
3. Numbers are not allowed.
1. Special Characters are not allowed.
Middle Name of the
Middle Name No 2. Spaces are not allowed.
individual
3. Numbers are not allowed.
No, with declaration 1. Special Characters are not allowed.
Last name of the
Last Name that Last Name does 2. Spaces are not allowed.
individual
not exist 3. Numbers are not allowed.
If the last name of
Declaration (If If the last name is not
the individual is not
Last name is not available, enter NA.
available, this
available) Else leave it blank.
becomes mandatory
Name of the 1. Special Characters are not allowed.
Name of Father No
individual's father 2. Numbers are not allowed.
Name of the 1. Special Characters are not allowed.
Name of Mother No
individual's mother 2. Numbers are not allowed.
Name of the
Spouse/Partner 1. Special Characters are not allowed.
individual's Spouse No
Name 2. Numbers are not allowed.
or Partner
Gender of the
Gender Yes Acceptable values: Male, Female, Others
individual
Acceptable format DD/MM/YYYY
1. Date of birth cannot be less than 01-01-1900.
2. Date of birth cannot be greater than Current
Date.
3. Date of birth cannot be greater than date of
Date of Birth of the
Date of Birth Yes customer onboarding.
individual
4. Date of birth cannot be greater than date of
reported transaction.

Note: While using Excel to edit csv, please ensure

that the date format is saved as DD/MM/YYYY

Financial Intelligence Unit – India (FIU-IND) P a g e | 49

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Use the Country ID downloaded from the
Nationality of the
Nationality Yes metadata for country from ‘Learning and
individual
Resources’
It should be entered as AAA-NNNNNNNNNN
Where AAA represents country code without +
sign and NNNNNNNNNN represents the 10 Digit
Numeric (If country = India) and Free length,
Numeric (If country!= India)

Sample: 91-9562013300
Mobile number of 10 Digit Numeric (If country = India)
Mobile Number No
the individual

1. All 10 digits cannot be the same

2. "1234567890" not allowed

FIU will accept reports without mobile number

up to a threshold. If this threshold is exceeded,
then subsequent reports will get rejected.
It should be entered as AAA-NNNNNNNNNN
Where AAA represents country code without +
sign and NNNNNNNNNN represents the 10 Digit
Numeric (If country = India) and Free length,
Numeric (If country!= India)
Alternate Mobile
Alternate Mobile
number of the No
Number Sample: 91-9562013300
individual
10 Digit Numeric (If country = India)

1. All 10 digits cannot be the same

2. "1234567890" not allowed
It should be entered as AAA-BBBB-
NNNNNNNNNN
Where AAA represents country code without +
sign, BBBB represents STD code and
NNNNNNNNNN represents the 10 Digit Numeric
(If country = India) and Free length, Numeric (If
Telephone Telephone number country!= India)
No
Number of the individual
Sample: 91-469-9562013300
10 Digit Numeric (If country = India)

1. All 10 digits cannot be the same

2. "1234567890" not allowed
(Alphanumeric)@(Alphanuimeric).(Text)

1. Uppercase (A-Z) and lowercase (a-z) English

letters.
Email ID of the
Email ID No 2. Allowed Digits (0-9).
individual
3. Characters ! # $ % & ' * + - / = ? ^ _ ` { | } ~
4. Character . ( Period, dot or full stop) if it is not
the first or last character and it will not come one
after the other.

Financial Intelligence Unit – India (FIU-IND) P a g e | 50

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Primary Address Primary Address of
Yes Free text with length 5 -255
1 the individual
Use the Country ID downloaded from the
Primary Address Country as part of
Yes metadata for country from ‘Learning and
Country primary address
Resources’
PIN code (Metadata is applicable if Country =
Primary Address Pin code as part of India)
Yes
Pin Code primary address If the country is not India, leave this field as
blank.
Primary Address Locality as part of
Yes Free Text with Length 5 -255
Locality primary address
Use the State ID downloaded from the metadata
Primary Address State as part of for state from ‘Learning and Resources’
Yes
State primary address If the country is not India, leave this field as
blank.
Use the District ID downloaded from the
metadata for district from ‘Learning and
Resources’
Primary Address District as part of
Yes Note – The district id in combination with the
District primary address
state id will be unique
If the country is not India, leave this field as
blank.
Use the City ID downloaded from the metadata
Primary Address City as part of for city from ‘Learning and Resources’
Yes
City primary address If the country is not India, leave this field as
blank.
Secondary Primary Address of
No Free text with length 5 -255
Address 1 the individual
Use the Country ID downloaded from the
Secondary Country as part of
No metadata for country from ‘Learning and
Address Country secondary address
Resources’
PIN code (Metadata is applicable if Country =
Secondary
Pin code as part of India)
Address Pin No
secondary address If the country is not India, leave this field as
Code
blank.
Secondary Locality as part of
No Free Text with Length 5 -255
Address Locality secondary address
Use the State ID downloaded from the metadata
Secondary State as part of for state from ‘Learning and Resources’
No
Address State secondary address If the country is not India, leave this field as
blank.
Use the District ID downloaded from the
metadata for district from ‘Learning and
Resources’
Secondary District as part of
No Note – The district id in combination with the
Address District secondary address
state id will be unique
If the country is not India, leave this field as
blank.
Use the City ID downloaded from the metadata
Secondary City as part of for city from ‘Learning and Resources’
No
Address City secondary address If the country is not India, leave this field as
blank.

Financial Intelligence Unit – India (FIU-IND) P a g e | 51

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Use the Customer Type ID downloaded from the
Customer Type of the
Customer Type Yes metadata for Customer Type from ‘Learning and
Individual
Resources’
Annual Income Annual Income of the
No
(INR) individual
Business or Use the Occupation ID downloaded from the
Occupation Occupation of the No metadata for Occupation from ‘Learning and
individual Resources’
Name of the
Employer Name employer of the No Mandatory if profession is salaried.
Individual
Address of the
Employer Mandatory if
employer of the Free text with length 5 -255
Address 1 profession is salaried
individual
Address of the Use the Country ID downloaded from the
Employer Mandatory if
employer of the metadata for country from ‘Learning and
Address Country profession is salaried
individual Resources’
PIN code (Metadata is applicable if Country =
Employer Address of the
Mandatory if India)
Address Pin employer of the
profession is salaried If the country is not India, leave this field as
Code individual
blank.
Address of the
Employer Mandatory if
employer of the Free Text with Length 5 -255
Address Locality profession is salaried
individual
Use the State ID downloaded from the metadata
Address of the
Employer Mandatory if for state from ‘Learning and Resources’
employer of the
Address State profession is salaried If the country is not India, leave this field as
individual
blank.
Use the District ID downloaded from the
metadata for district from ‘Learning and
Address of the Resources’
Employer Mandatory if
employer of the Note – The district id in combination with the
Address District profession is salaried
individual state id will be unique
If the country is not India, leave this field as
blank.
Use the City ID downloaded from the metadata
Address of the
Employer Mandatory if for city from ‘Learning and Resources’
employer of the
Address City profession is salaried If the country is not India, leave this field as
individual
blank.
Acceptable date format DD/MM/YYYY
1. Customer On- boarding date cannot be later
than Current date.
Date on which the 2. Customer On-Boarding date cannot be earlier
Date of
individual was on- than Customer Date of Birth
Customer On- Yes
boarded as a 3. Customer On-Boarding date cannot be later
boarding
customer than date of Reported Transaction

Note: While using Excel to edit csv, please ensure

that the date format is saved as DD/MM/YYYY
Acceptable date format DD/MM/YYYY
Most recent date on
1. This date cannot be less than Date of
Date of Last KYC which the KYC or re-
Yes Customer On-boarding
/ re-KYC KYC of the customer
2. This date cannot be less than Customer Date
was conducted.
of Birth

Financial Intelligence Unit – India (FIU-IND) P a g e | 52

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Note: While using Excel to edit csv, please ensure

that the date format is saved as DD/MM/YYYY
Risk level assigned to
Customer Risk
the customer as per Yes Acceptable values are Low, Medium, High.
Level
last risk assessment
Mandatory to give one
of five - Passport,
National Population Format: 16 digits (NNNNNNNNNNNNNNNN)
NREGA card, Voter ID,
NPR Register Number of N= Number
Driver’s License or
the individual N = Cannot be zero
NPR number if PAN &
CKYC not available.
PAN Exemption Format: 10 Digit. (AAAAAAAAAA)
PEKRN No
Number A = Numeric
Free text.
Name of State as
If the country is not India, use this field for
part of primary Yes
Primary State Primary Address. If the country of the address is
address
Name India, leave this as blank.
Free text.
Name of District as
If the country is not India, use this field for
part of primary Yes
Primary District Primary Address. If the country of the address is
address
Name India, leave this as blank.
Free text.
Name of City as part If the country is not India, use this field for
Yes
Primary City of primary address Primary Address. If the country of the address is
Name India, leave this as blank.
Free text.
Name of State as
If the country is not India, use this field for
part of Secondary No
Secondary State Secondary Address. If the country of the address
address
Name is India, leave this as blank.
Free text.
Name of District as
If the country is not India, use this field for
part of Secondary No
Secondary Secondary Address. If the country of the address
address
District Name is India, leave this as blank.
Free text.
Name of City as part If the country is not India, use this field for
No
Secondary City of Secondary address Secondary Address. If the country of the address
Name is India, leave this as blank.
Free text.
Name of State as
If the country is not India, use this field for
part of Employee No
Employee State Employer Address. If the country of the address
address
Name is India, leave this as blank.
Free text.
Name of District as
If the country is not India, use this field for
part of Employee No
Employee Employer Address. If the country of the address
address
District Name is India, leave this as blank.
Free text.
Name of City as part If the country is not India, use this field for
No
Employee City of Employee address Employer Address. If the country of the address
Name is India, leave this as blank.
Free text.
Other Customer Other Customer Type No If the customer type is selected as ‘Others’ use
Type this field.

Financial Intelligence Unit – India (FIU-IND) P a g e | 53

 User Manual - FINGate 2.0 - Reports Version 1.1

3.1.2 KC2 - KYC Non-Individuals - Bulk Template

The name of the file is KC2 and should not be changed. This file is used to capture data of Customer KYC
for Non-Individuals or entities.

Column Description Mandatory Validation Rules

Report All KYC and transactions to be grouped under
Report Reference
Reference Yes one report should have the same report
Number
Number reference number.
Unique customer ID
UCIC provided to the Yes
customer
Name of the Account
Entity Name Yes
holding entity
Unique value of
company
incorporated as per
One out of the 4
MCA
identifiers (Unique
Unique
Company ID, GSTIN,
Company ID One out of the 4
PAN, TAN) is
identifiers (Unique
mandatory
Company ID, GSTIN,
PAN, TAN) is
mandatory
PAN Number of the entity
Format : 10 Digit. (AAAAA)(NNNN)(A) .
A = Alphabet and N = Number
(NNNN) - Cannot be 0000

Fourth letter will have specific values for

different types of entities

One out of the 4 "C" stands for Company

identifiers (Unique "H" stands for Hindu Undivided Family (HUF)
PAN of the account
PAN Number Company ID, GSTIN, "A" stands for Association of Persons (AOP)
holder
PAN, TAN) is "B" stands for Body of Individuals (BOI)
mandatory "G" stands for Government Agency
"J" stands for Artificial Juridical Person
"L" stands for Local Authority
"F" stands for Firm/ Limited Liability Partnership
"T" stands for Trust

FIU will accept reports without PAN up to a

threshold. If this threshold is exceeded, then
subsequent reports will get rejected.
Declaration (If
To be provided if Yes, if PAN is not If PAN is not available, enter NA, else leave it
PAN is not
PAN is not available available. blank.
available)
One out of the 4
TAN of the account identifiers (Unique Format: 10 Digit. (AAAA)(NNNNN)(A)
TAN holder Company ID, GSTIN, A = alphabets.
PAN, TAN) is N = numbers.
mandatory
GST ID number of the One out of the 4 Format: 15 Digit. (NNAAAAANNNNANZL)
GSTIN
entity identifiers (Unique A = alphabets.

Financial Intelligence Unit – India (FIU-IND) P a g e | 54

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Company ID, GSTIN, N = numbers.
PAN, TAN) is L = Alphabet/Number
mandatory 14th alphabet will always be Z by default
Mandatory only for
IEC Import Export code CBWT Trade Format: 10 Digit. Alphanumeric
transactions
Declaration (If
To be provided if IEC Yes, if IEC is not If IEC is not available, enter NA, else leave it
IEC is not
is not available available. blank.
available)
It should be entered as AAAA-BBBB-
NNNNNNNNNN
Where AAA represents country code without +
sign, BBBB represents STD code and
NNNNNNNNNN represents the 10 Digit Numeric
Contact number (If country = India) and Free length, Numeric (If
Telephone (landline) of the country!= India)
No
Number account holding
entity Sample: 91-469-9562013300
10 Digit Numeric (If country = India)

1. All 10 digits cannot be the same

2. "1234567890" not allowed
It should be entered as AAAA-NNNNNNNNNN
Where AAA represents country code without +
sign and NNNNNNNNNN represents the 10 Digit
Numeric (If country = India) and Free length,
Numeric (If country!= India)

Contact number Sample: 91-9562013300

(mobile) of the 10 Digit Numeric (If country = India)
Mobile Number No
account holding
entity
1. All 10 digits cannot be the same
2. "1234567890" not allowed

FIU will accept reports without mobile number

up to a threshold. If this threshold is exceeded,
then subsequent reports will get rejected
(Alphanumeric)@(Alphanuimeric).(Text)

1. Uppercase (A-Z) and lowercase (a-z) English

E-mail ID of the letters.
Email ID account holding No 2. Acceptable Digits (0-9).
entity 3. Characters ! # $ % & ' * + - / = ? ^ _ ` { | } ~
4. Character . ( Period, dot or full stop) if it is not
the first or last character and it will not come one
after the other.
Company Official website of
No
Website the entity
Use the Country ID downloaded from the
Country as part of
Country Yes metadata for country from ‘Learning and
the address
Resources’

Financial Intelligence Unit – India (FIU-IND) P a g e | 55

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Trading Address of
Address Line 1 the account holding Yes Free text with length 5 -255
entity
PIN code (Metadata is applicable if Country =
Trading Address of
India)
PIN Code the account holding Yes
If the country is not India, leave this field as
entity
blank.
Trading Address of
Locality the account holding Yes Free Text with Length 5 -255
entity
Use the State ID downloaded from the metadata
Trading Address of
for state from ‘Learning and Resources’
State the account holding Yes
If the country is not India, leave this field as
entity
blank.
Use the District ID downloaded from the
metadata for district from ‘Learning and
Trading Address of Resources’
District the account holding Yes Note – The district id in combination with the
entity state id will be unique
If the country is not India, leave this field as
blank.
Use the City ID downloaded from the metadata
Trading Address of
City / Village / for city from ‘Learning and Resources’
the account holding Yes
Town If the country is not India, leave this field as
entity
blank.
FIU will accept reports without line of business
Line of business of
Line of Business No up to a threshold. If this threshold is exceeded,
the entity
then subsequent reports will get rejected
Acceptable Values are Yes/No
Whether the account In case the FCRA Registration number is not
FCRA Status held is registered Yes applicable, then the RE would need to attach the
with FCRA letter of prior permission as received from the
concerned NPO
FCRA State in which the Mandatory if FCRA status is Yes
Registration entity registered for No Use the State ID downloaded from the metadata
State FCRA for state from ‘Learning and Resources’
FCRA
Registration Number
Registration No Mandatory if FCRA status is Yes
provided by FCRA
Number
ID of the Customer
Customer ID No
provided by RE
Use the Country ID downloaded from the
Registered
Registered Country No metadata for country from ‘Learning and
Country
Resources’
Registered
Registered Address No Free text with length 5 -255
Address
PIN code (Metadata is applicable if Country =
Registered PIN PIN Code as part of India)
No
Code registered address If the country is not India, leave this field as
blank.
Registered Locality as part of
No Free Text with Length 5 -255
Locality registered address
State as part of Use the State ID downloaded from the metadata
Registered State No
registered address for state from ‘Learning and Resources’

Financial Intelligence Unit – India (FIU-IND) P a g e | 56

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

If the country is not India, leave this field as
blank.
Use the District ID downloaded from the
metadata for district from ‘Learning and
Resources’
Registered District as part of
No Note – The district id in combination with the
District registered address
state id will be unique
If the country is not India, leave this field as
blank.
Use the City ID downloaded from the metadata
City / Village / Town
Registered City / for city from ‘Learning and Resources’
as part of registered No
Village / Town If the country is not India, leave this field as
address
blank.
Acceptable format DD/MM/YYYY
Date of incorporation
Date Of
of the account No
Incorporation Note: While using Excel to edit csv, please ensure
holding entity
that the date format is saved as DD/MM/YYYY
Use the Customer Type ID downloaded from the
What type of entity is
Customer Type Yes metadata for Customer Type from ‘Learning and
the account holder
Resources’
Acceptable date format DD/MM/YYYY
1. This date cannot be earlier than Date of
Most recent date on Customer On-boarding
which the KYC of the 2. This date cannot be earlier than Customer
Last KYC Date Yes
customer was Date of Incorporation
conducted
Note: While using Excel to edit csv, please ensure
that the date format is saved as DD/MM/YYYY
Acceptable date format DD/MM/YYYY
1. Customer On- boarding date cannot be later
than Current date.
Date on which the 2. Customer On-Boarding date cannot be earlier
customer first than Customer Date of Incorporation.
Onboarding Date Yes
opened an account 3. Customer On-Boarding date cannot be later
with the RE than date of Reported Transaction.

Note: While using Excel to edit csv, please ensure

that the date format is saved as DD/MM/YYYY
Risk level assigned to
Customer Risk
the customer as per Yes Acceptable values are Low, Medium, High.
Level
last risk assessment

FIU will accept reports without UBO up to a

UBO (Ultimate
UBO No threshold. If this threshold is exceeded, then
Beneficiary owners)
subsequent reports will get rejected

Declaration (If If the UBO is not

If the Ultimate beneficiary owner of the entity is
UBO is not UBO Not Available available, enter NA.
not available, this checkbox needs to be used
available) Else leave it blank.
PEKRN will be mandatory if “not available” flag is
selected for PAN
PAN Exempt Investor
PEKRN No
Category PEKRN
Format : 10 Digit. (AAAAAAAAAA)
A = Numeric

Financial Intelligence Unit – India (FIU-IND) P a g e | 57

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

If the country is not India, use this field for
State Name State Name of No Trading Address. If the country of the address is
Trading Address India, leave this as blank.
If the country is not India, use this field for
District Name District Name of No Trading Address. If the country of the address is
Trading Address India, leave this as blank.
City / Village / If the country is not India, use this field for
City Name of Trading
Town Name No Trading Address. If the country of the address is
Address
India, leave this as blank.
Registered State If the country is not India, use this field for
Registered State
Name No Registered Address. If the country of the address
Name
is India, leave this as blank.
If the country is not India, use this field for
Registered Registered District
No Registered Address. If the country of the address
District Name Name
is India, leave this as blank.
Registered City / If the country is not India, use this field for
City / Village / Town
Village / Town No Registered Address. If the country of the address
Name
Name is India, leave this as blank.
Name of the Director
Min length: 3
Director Name of the company, if No
Max length: 100
applicable
Free text.
Other Customer Other Customer Type No If the customer type is selected as ‘Others’ use
Type this field.

3.1.3 KCS1 - Simplified KYC Individuals - Bulk Template

The name of the file is KCS1 and should not be changed. This file is used to capture data of simplified KYC
for individuals who are not customers of the RE.

Column Description Mandatory Validation Rules

Report Report Reference All KYC and transactions to be grouped under
Reference Number maintained Yes one report should have the same report
Number by RE reference number.
1. Special Characters are not allowed.
First name of the
First Name Yes 2. Spaces are not allowed.
account holder
3. Numbers are not allowed.
1. Special Characters are not allowed.
Middle Name of the
Middle Name No 2. Spaces are not allowed.
individuals
3. Numbers are not allowed.
No, with declaration 1. Special Characters are not allowed.
Last name of the
Last Name that Last Name does 2. Spaces are not allowed.
account holder
not exist 3. Numbers are not allowed.
If the last name of
Declaration (If If the last name is not
the individual is not
Last name is not available, enter NA.
available, this
available) Else leave it blank.
becomes mandatory
PAN Number of the entity
PAN of the account Format: 10 Digit. (AAAAA)(NNNN)(A).
PAN No A = Alphabet and N = Number
holder

(NNNN) - Cannot be 0000

Financial Intelligence Unit – India (FIU-IND) P a g e | 58

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

4th Alphabet (AAAAA) will be "P" for individuals

Option to declare Not Available

If the PAN of the
Declaration (If If the PAN is not
individual is not
PAN is not available, enter NA.
available, this
available) Else leave it blank.
becomes mandatory
PAN Exempt Investor PEKRN
PEKRN No
Category Format : 10 Digit. (NNNNNNNNNN)
Format : 14 Digit Number
1. CKYC will be mandatory (with threshold) if
CKYC number of the PAN and PEKRN is not available.
CKYC number No
individual 2. No Special Characters are allowed.
3. No Spaces are allowed.
4. 'Not Available' flag to be added
If the CKYC number
Declaration (If If the CKYC number is
of the individual is
CKYC is not not available, enter
not available, this
available) NA. Else leave it blank.
becomes mandatory
Identification No
documents in case
Passport Number
PAN and CKYC
If nationality is Indian then Passport number of
Passport number are both
the individual should be in format ANNNNNNN
Number unavailable
(Passport/ NREGA
A = Upper case Alphabet, N = Number
card/ Voter ID/
Driver’s License)
Identification No
documents in case
PAN and CKYC Voter ID
number are both 10 digit Alphanumeric (AAANNNNNNN)
Voter ID
unavailable A = Alphabet
(Passport/ NREGA N= Number
card/ Voter ID/
Driver’s License)
Identification No
documents in case
PAN and CKYC
Driver’s License number are both
Min length 0, Max length 15
Number unavailable
(Passport/ NREGA
card/ Voter ID/
Driver’s License)
Identification No
documents in case
PAN and CKYC NREGA CARD
number are both Format: 16 Digit Alphanumeric
NREGA Card
unavailable (AANNNNNNNNNNNNNN)
(Passport/ NREGA A = Alphabet, N= Number
card/ Voter ID/
Driver’s License)
National Population No Format : 16 digits (NNNNNNNNNNNNNNNN)
NPR
Register N= Number

Financial Intelligence Unit – India (FIU-IND) P a g e | 59

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

N = Cannot be zero
It should be entered as AAA-NNNNNNNNNN
Where AAA represents country code without +
sign and NNNNNNNNNN represents the 10 Digit
Numeric (If country = India) and Free length,
Numeric (If country!= India)
Contact number
Mobile Number No
(mobile) of the entity Sample: 91-9562013300
10 Digit Numeric (If country = India)

1. All 10 digits cannot be the same

2. "1234567890" not allowed
Address of the
Address Line 1 No Free text with length 5 -255
individual
Use the Country ID downloaded from the
Country as part of
Country No metadata for country from ‘Learning and
the address
Resources’
PIN code (Metadata is applicable if Country =
Pin code as part of India)
PIN Code No
the address If the country is not India, leave this field as
blank.
Locality of the
Locality No Free Text with Length 5 -255
address
Use the State ID downloaded from the metadata
State as part of the for state from ‘Learning and Resources’
State No
address If the country is not India, leave this field as
blank.
Use the District ID downloaded from the
metadata for district from ‘Learning and
Resources’
District as part of the
District No Note – The district id in combination with the
address
state id will be unique
If the country is not India, leave this field as
blank.
Use the City ID downloaded from the metadata
Address of the
City / Village / for city from ‘Learning and Resources’
account holding No
Town If the country is not India, leave this field as
entity
blank.
Free text.
If the country is not India, use this field for
State Name State Name No
Address. If the country of the address is India,
leave this as blank.
Free text.
If the country is not India, use this field for
District Name District Name No
Address. If the country of the address is India,
leave this as blank.
Free text.
City / Village / City / Village / Town If the country is not India, use this field for
No
Town Name Name Address. If the country of the address is India,
leave this as blank.
City Name City Name No Free text.

Financial Intelligence Unit – India (FIU-IND) P a g e | 60

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

If the country is not India, use this field for
Address. If the country of the address is India,
leave this as blank.
Second Address Second Address Line
No Free text with length 5 -255
Line 1 1
Use the Country ID downloaded from the
Second Address Second Address
No metadata for country from ‘Learning and
Country Country
Resources’
PIN code (Metadata is applicable if Country =
Second Address Second Address PIN India)
No
PIN Code Code If the country is not India, leave this field as
blank.
Second Address Second Address
No Free Text with Length 5 -255
Locality Locality
Use the State ID downloaded from the metadata
Second Address for state from ‘Learning and Resources’
Second Address State No
State If the country is not India, leave this field as
blank.
Free text.
Second Address Second Address State If the country is not India, use this field for
No
State Name Name Second Address. If the country of the address is
India, leave this as blank.
Use the District ID downloaded from the
metadata for district from ‘Learning and
Resources’
Second Address Second Address
No Note – The district id in combination with the
District District
state id will be unique
If the country is not India, leave this field as
blank.
Free text.
Second Address Second Address If the country is not India, use this field for
No
District Name District Name Second Address. If the country of the address is
India, leave this as blank.
Use the City ID downloaded from the metadata
Second Address
Second Address City for city from ‘Learning and Resources’
City / Village / No
/ Village / Town If the country is not India, leave this field as
Town
blank.
Free text.
Second Address Second Address City If the country is not India, use this field for
No
City Name Name Second Address. If the country of the address is
India, leave this as blank.
Free text.
Non-Indian PIN If the country is not India, use this field for
Non-Indian PIN Code No
Code Address. If the country of the address is India,
leave this as blank.
Free text.
Second Address
Send Address Non- If the country is not India, use this field for
Non-Indian PIN No
Indian PIN Code Second Address. If the country of the address is
Code
India, leave this as blank.

Financial Intelligence Unit – India (FIU-IND) P a g e | 61

 User Manual - FINGate 2.0 - Reports Version 1.1

3.1.4 KCS2 - Simplified KYC Non-Individuals - Bulk Template

The name of the file is KCS2 and should not be changed. This file is used to capture data of simplified KYC
for non-individuals who are not customers of the RE.

Column Description Mandatory Validation Rules

Report Report Reference All KYC and transactions to be grouped under
Reference Number maintained Yes one report should have the same report
Number by RE reference number.
Full legal name of the
Full Name Yes NA
Entity
Unique Company
CIN/ FCRN/
Identification No
LLPIN/ FLLPIN
number of the entity
PAN Number of the entity
Format : 10 Digit. (AAAAA)(NNNN)(A) .
A = Alphabet and N = Number
(NNNN) - Cannot be 0000

Fourth letter will have specific values for

different types of entities

PAN PAN of the Entity No "C" stands for Company

"H" stands for Hindu Undivided Family (HUF)
"A" stands for Association of Persons (AOP)
"B" stands for Body of Individuals (BOI)
"G" stands for Government Agency
"J" stands for Artificial Juridical Person
"L" stands for Local Authority
"F" stands for Firm/ Limited Liability Partnership
"T" stands for Trust
Declaration (If Declaration to be If the PAN is not
If the PAN is not available, enter NA. Else leave it
PAN is not provided if PAN is available, this
blank.
available) not available becomes mandatory
Format: 15 Digit. (NNAAAAANNNNANZL)
A = alphabets.
GSTIN GSTIN of the entity No N = numbers.
L = Alphabet/Number
14th alphabet will always be Z by default
It should be entered as AAA-NNNNNNNNNN
Where AAA represents country code without +
sign and NNNNNNNNNN represents the 10 Digit
Numeric (If country = India) and Free length,
Numeric (If country!= India)
Mobile Number of
Mobile Number No
the entity Sample: 91-9562013300
10 Digit Numeric (If country = India)

1. All 10 digits cannot be the same

2. "1234567890" not allowed
Registered Registered Address
No Free text with length 5 -255
Address Line 1

Financial Intelligence Unit – India (FIU-IND) P a g e | 62

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Use the Country ID downloaded from the
Country as part of
Country No metadata for country from ‘Learning and
registered address
Resources’
PIN code (Metadata is applicable if Country =
Pin code as part of India)
PIN Code No
registered address If the country is not India, leave this field as
blank.
Locality of the
Locality No Free Text with Length 5 -255
address
Use the State ID downloaded from the metadata
State as part of for state from ‘Learning and Resources’
State No
registered address If the country is not India, leave this field as
blank.
Use the District ID downloaded from the
metadata for district from ‘Learning and
Resources’
District as part of
District No Note – The district id in combination with the
registered address
state id will be unique
If the country is not India, leave this field as
blank.
City / Village / City as part of Use the City ID downloaded from the metadata
No
Town registered address for city from ‘Learning and Resources’
PAN Exempt Investor
PEKRN No
Category
Free text.
If the country is not India, use this field for
State Name State Name No
Address. If the country of the address is India,
leave this as blank.
Free text.
If the country is not India, use this field for
District Name District Name No
Address. If the country of the address is India,
leave this as blank.
Free text.
City / Village / City / Village / Town If the country is not India, use this field for
No
Town Name Name Address. If the country of the address is India,
leave this as blank.
Free text.
If the country is not India, use this field for
City Name City Name No
Address. If the country of the address is India,
leave this as blank.
Second Address Second Address Line
No Free text with length 5 -255
Line 1 1
Use the Country ID downloaded from the
Second Address Second Address
No metadata for country from ‘Learning and
Country Country
Resources’
PIN code (Metadata is applicable if Country =
Second Address Second Address PIN India)
No
PIN Code Code If the country is not India, leave this field as
blank.
Second Address Second Address
No Free Text with Length 5 -255
Locality Locality
Second Address Use the State ID downloaded from the metadata
Second Address State No
State for state from ‘Learning and Resources’

Financial Intelligence Unit – India (FIU-IND) P a g e | 63

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

If the country is not India, leave this field as
blank.
No Free text.
Second Address Second Address State If the country is not India, use this field for
State Name Name Second Address. If the country of the address is
India, leave this as blank.
No Use the District ID downloaded from the
metadata for district from ‘Learning and
Resources’
Second Address Second Address
Note – The district id in combination with the
District District
state id will be unique
If the country is not India, leave this field as
blank.
No Free text.
Second Address Second Address If the country is not India, use this field for
District Name District Name Second Address. If the country of the address is
India, leave this as blank.
Second Address No
Second Address City Use the City ID downloaded from the metadata
City / Village /
/ Village / Town for city from ‘Learning and Resources’
Town
No Free text.
Second Address Second Address City If the country is not India, use this field for
City Name Name Second Address. If the country of the address is
India, leave this as blank.
No Free text.
Non-Indian PIN If the country is not India, use this field for First
Non-Indian PIN Code
Code Address. If the country of the address is India,
leave this as blank.
No Free text.
Second Address
Second Address Non- If the country is not India, use this field for
Non-Indian PIN
Indian PIN Code Second Address. If the country of the address is
Code
India, leave this as blank.

3.1.5 Account_Detail - Account Details - Bulk Template

The name of the file is Account_Detail and should not be changed. This file is used to capture data of
account.

Column Description Mandatory Validation Rules

Use the Account Type ID downloaded from the
Account Type Type of the account Yes metadata for account type from ‘Learning and
Resources’
Account Number Account number Yes Alphanumeric
Branch Code of Branch Code of This will be validated against the data uploaded
Yes
Account Account by RE in RE Profile details.
Acceptable format DD/MM/YYYY
Date of Account Opening cannot be later than
Date of Account Date of the opening Date of Account Closing.
Yes
Opening of the account
Note: While using Excel to edit csv, please ensure
that the date format is saved as DD/MM/YYYY

Financial Intelligence Unit – India (FIU-IND) P a g e | 64

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Acceptable format DD/MM/YYYY
Required if account is closed.
Date of Account Closing cannot be less than Date
Date of Account Date of closing of the
Yes of Account Opening
Closing account
Note: While using Excel to edit csv, please ensure
that the date format is saved as DD/MM/YYYY
Acceptable values are Active, Dormant, Closed,
Account Status Status of the account Yes
Blocked

3.1.6 Account_Person_Relation - Account to Person Relationship - Bulk Template

The name of the file is Account_Person_Relation and should not be changed. This file is used to capture
the relations between the accounts and persons in the report.

Column Description Mandatory Validation Rules

Account Number Account Number Yes
Acceptable Values Account Holder, Authorised
Signatory, Proprietor / Director / Partner /
Relation of the
Relationship Member of legal entity, Introducer, Guarantor,
persons to accounts Yes
Type Guardian, Nominee, Beneficial owner, Proposer,
in the report
Assignee, Life Assured, Beneficiary, Power of
Attorney, Others, Ultimate Beneficiary Owner
Either this field or
Unique The UCIC of the customer entered in KC1 and
Reference number of Name of Non-
Reference KC2 should be entered here in case the person to
the customer customer is
Number linked to the account is a customer.
mandatory
Indicate if the
Acceptable values are:
Individual / Non- related person is
Yes Individual
individual individual or non-
Non-individual
individual
The name or reference number of the non-
Name or Reference Either this field of
Name of Non- customer entered in KCS1 and KCS2 should be
number of the non- Unique Reference
customer entered here in case the person to linked to the
customer Number is mandatory
account is a non-customer.

3.1.7 TC1 - Transaction - Cash at ATM - Bulk Template

The name of the file is TC1 and should not be changed. This file is used to capture the details of cash
transactions conducted through ATM.

Column Description Mandatory Validation Rules

Indicates whether
the transaction is
Acceptable values are Customer or Non-
Relationship Flag conducted by a Yes
Customer.
customer of the RE
or a non-customer
Whether the
Transaction
transaction was Yes Acceptable values are Success or Fail.
Status
successful

Financial Intelligence Unit – India (FIU-IND) P a g e | 65

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Unique Transaction
Transaction ID Yes
Record Number
Acceptable format DD/MM/YYYY
Date of the
Transaction Date Yes
transaction Note: While using Excel to edit csv, please ensure
that the date format is saved as DD/MM/YYYY
Acceptable format HH:MM:SS
Time of the
Transaction Time No
transaction Note: While using Excel to edit csv, please ensure
that the time format is saved as HH:MM:SS
Whether the
Deposit/Withdra reported transaction
Yes Acceptable values are Deposit or Withdrawal
wal was a deposit or a
withdrawal
Amount
Transaction
Withdrawn/Deposite Yes
Amount
d
Account Number on
which the reported
Account Number Yes
transaction(s) took
place
Use the Account Type ID downloaded from the
The type of the Mandatory only for
Account Type metadata for account type from ‘Learning and
account customer
Resources’
Use the Card Type ID downloaded from the
Type of card used to Mandatory only for
Card Type metadata for card type from ‘Learning and
conduct transaction customer
Resources’
Card number of the
Mandatory only for
Card Number card used to conduct Mandatory only for customer
customer
transaction
Use the Country ID downloaded from the
metadata for country from ‘Learning and
Resources’
Card Issuing Country in which the
No FIU will accept reports without Card Issuing
Country card was issued
Country up to a threshold. If this threshold is
exceeded, then subsequent reports will get
rejected
Issuing Bank of the FIU will accept reports without Card Issuing Bank
Card Issuing
card used to conduct No up to a threshold. If this threshold is exceeded,
Bank
transaction then subsequent reports will get rejected
Report All KYC and transactions to be grouped under
Report Reference
Reference Yes one report should have the same report
Number
Number reference number.
Switch Provider Unique Transaction
Transaction ID (If ID provided by No
applicable) Switch Provider
ID of the ATM from If card issuing bank =
ATM ID/ CAM ID which cash was RE then ATM ID/ CAM
withdrawn ID will be mandatory.
Branch Code of Branch Code of Mandatory only for This will be validated against the data uploaded
Account Account customer by RE in RE Profile details.
Report Type Report Type Yes CTR for Cash Transaction Report

Financial Intelligence Unit – India (FIU-IND) P a g e | 66

 User Manual - FINGate 2.0 - Reports Version 1.1

3.1.8 TC2-Transaction-Cash at Branch-Bulk Template

The name of the file is TC2 and should not be changed. This file is used to capture the details of cash
transactions conducted through branch.

Column Description Mandatory Validation Rules

Acceptable values are
CTR
Report Type Enter the report type Yes
NTR
STR
Report All KYC and transactions to be grouped under
Report Reference
Reference Yes one report should have the same report
Number
Number reference number.
Branch Code of Branch Code of Mandatory only for This will be validated against the data uploaded
Account Account customer by RE in RE Profile details.
Account Number Account Number Yes
ID of the branch
Transaction where the
Yes
Branch Code transaction was
conducted
Whether the
Deposit/Withdra reported transaction
Yes Acceptable values are Deposit or Withdrawal
wal was a deposit or a
withdrawal
Unique Transaction
Transaction ID No
Record Number
Acceptable format DD/MM/YYYY
Date of the
Transaction Date Yes
transaction Note: While using Excel to edit csv, please ensure
that the date format is saved as DD/MM/YYYY
Acceptable format HH:MM:SS
Time of the
Transaction Time No
transaction Note: While using Excel to edit csv, please ensure
that the time format is saved as HH:MM:SS
Amount
Transaction
Withdrawn/Deposite Yes
Amount
d
What instrument was
Instrument Type used to conduct the Yes Acceptable Values are Cash/ Cheque/ DD/ Card
transaction
Instrument ID
ID of the instrument Yes, if instrument type
(Card Number/
used to conduct the is Card Number/
Cash/ Cheque/
transaction Cheque/ DD
DD)
Non-Customer Reference number of
Reference the person, if not a No
Number customer
Flag Indicating the
relationship the
Relationship Flag entity in the report Yes Acceptable values are Customer/Non-Customer.
maintains with the
RE
Third Party PAN PAN number of the PAN Number of the entity
No
(Non-Customer) entity conducting the Format : 10 Digit. (AAAAA)(NNNN)(A) .

Financial Intelligence Unit – India (FIU-IND) P a g e | 67

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

transaction in the A = Alphabet and N = Number
case where the entity
is not a customer of (NNNN) - Cannot be 0000
the RE

3.1.9 TC3 -Transaction- Casino cash transaction -Bulk Template

The name of the file is TC3 and should not be changed. This file is used to capture the details of cash
transactions conducted through casinos.

Column Description Mandatory Validation Rules

All KYC and transactions to be grouped
Report Reference
Report Reference Number Yes under one report should have the same
Number
report reference number.
Unique Transaction
Transaction ID Yes
Record Number
Whether transaction
Transaction Type was a pay-in or a pay- Yes Acceptable Values are Pay-in/Pay-out
out transaction
Acceptable format DD/MM/YYYY

Transaction Date Date of the transaction Yes Note: While using Excel to edit csv,
please ensure that the date format is
saved as DD/MM/YYYY
Acceptable format HH:MM:SS

Transaction Time Time of the transaction No Note: While using Excel to edit csv,
please ensure that the time format is
saved as HH:MM:SS
Amount of the
Amount Yes
transaction
If Entity Type = Individual
Name of the reported
Name Yes 1. Special Characters are not allowed.
entity
2. Numbers are not allowed.
Acceptable format DD/MM/YYYY
1. Date of birth cannot be less than 01-
01-1900.
2. Date of birth cannot be greater than
Current Date.
DoB of the reported
Date of Birth Yes 3. Date of birth cannot be greater than
entity
date of reported transaction.

Note: While using Excel to edit csv,

please ensure that the date format is
saved as DD/MM/YYYY
(Alphanumeric)@(Alphanuimeric).(Text)

1. Uppercase (A-Z) and lowercase (a-z)

EMAIL of the reported
Email No English letters.
entity
2. Acceptable Digits (0-9).
3. Characters ! # $ % & ' * + - / = ? ^ _ ` {
|}~

Financial Intelligence Unit – India (FIU-IND) P a g e | 68

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

4. Character . ( Period, dot or full stop)
if it is not the first or last character and
it will not come one after the other.

It should be entered as AAA-

NNNNNNNNNN
Where AAA represents country code
without + sign and NNNNNNNNNN
represents the 10 Digit Numeric (If
country = India) and Free length,
Mobile number of the Numeric (If country!= India)
Mobile No Yes
reported entity
Sample: 91-9562013300
10 Digit Numeric (If country = India)

1. All 10 digits cannot be the same

2. "1234567890" not allowed
Address Line 1 Address No Free text with length 5 -255
Use the Country ID downloaded from
Country as part of the
Country No the metadata for country from
address
‘Learning and Resources’
PIN code (Metadata is applicable if
Pin code as part of the Country = India)
PIN Code No
address If the country is not India, leave this
field as blank.
Use the State ID downloaded from the
metadata for state from ‘Learning and
State as part of the
State No Resources’
address
If the country is not India, leave this
field as blank.
Use the District ID downloaded from
the metadata for district from ‘Learning
and Resources’
District as part of the
District No Note – The district id in combination
address
with the state id will be unique
If the country is not India, leave this
field as blank.
Use the City ID downloaded from the
metadata for city from ‘Learning and
Address of the account
City / Village / Town No Resources’
holding entity
If the country is not India, leave this
field as blank.
Report Type Report Type Yes CTR for Cash Transaction Report
Free text.
State name for non- If the country is not India, use this field
State Name No
Indian address for Address. If the country is India,
leave this field as blank.
District name for non-
District Name No Free text.
Indian address

Financial Intelligence Unit – India (FIU-IND) P a g e | 69

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

If the country is not India, use this field
for Address. If the country is India,
leave this field as blank.
Free text.
City name for non- If the country is not India, use this field
City / Village / Town Name No
Indian address for Address. If the country is India,
leave this field as blank.

3.1.10 TS1 - NPO NEFT/RTGS Transaction. - Bulk Template

The name of the file is TS1 and should not be changed. This transaction profile will be filled in the
scenario the RE wishes to report a NEFT/RTGS payment

Column Description Mandatory Validation Rules

All KYC and transactions to be
Report Reference Report Reference Number grouped under one report
Yes
Number maintained by RE should have the same report
reference number.
Flag Indicating the position of Valid values are:
Relationship Flag the customer in the reported Yes Sender
transaction (Sender/Receiver) Receiver
Transaction ID Unique Transaction ID Yes
Whether transaction was an Valid values are:
Transaction Type incoming or an outgoing Yes Debit
transaction Credit
Transaction Amount Amount of the transaction Yes
Acceptable format
DD/MM/YYYY

Transaction Date Date of the transaction Yes Note: While using Excel to edit
csv, please ensure that the date
format is saved as
DD/MM/YYYY
Acceptable format HH:MM:SS

Note: While using Excel to edit

Transaction Time Time of the transaction No
csv, please ensure that the
time format is saved as
HH:MM:SS
Name of the entity sending the
reported funds. Non mandatory Yes, for
Sender Name Min length 3, Max length 100
in case the transaction type is outgoing
incoming.
IFSC Code of the sender of the
reported funds. Non mandatory Yes, for
Sender IFSC
in case the transaction type is outgoing
incoming.
Account number of the entity
sending the reported funds. Yes, for
Sender Account Number Min length 5, Max length 20
Non mandatory in case the outgoing
transaction type is incoming.

Financial Intelligence Unit – India (FIU-IND) P a g e | 70

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Name of the entity receiving the
Beneficiary Name Yes Min length 3, Max length 100
reported funds
IFSC code of the receiver of the
reported funds Non mandatory
Beneficiary IFSC Yes
in case the transaction type is
incoming.
Beneficiary Account Account number of the entity
Yes Min length 5, Max length 20
Number receiving the reported funds
Narration Purpose of the transaction No Min length 0, Max length 100
Report Type This should be NTR Yes

3.1.11 TS2 - NPO IMPS transaction. - Bulk Template

The name of the file is TS2 and should not be changed. This transaction profile will be filled in the
scenario the RE wishes to report an IMPS payment.

Column Description Mandatory Validation Rules

Flag Indicating the
position of the customer Valid values are:
Relationship Flag in the reported Yes Sender
transaction Receiver
(Sender/Receiver)
All KYC and transactions to be
Report Reference Report Reference grouped under one report should
Yes
Number Number have the same report reference
number.
Whether transaction was
Valid values are:
an incoming (Credit) or
Transaction Type Yes Debit
an outgoing (Debit)
Credit
transaction
Transaction ID Unique Transaction ID Yes
Transaction Amount of the
Yes
Amount transaction
Acceptable format DD/MM/YYYY

Transaction Date Date of the transaction Yes Note: While using Excel to edit csv,
please ensure that the date format
is saved as DD/MM/YYYY
Acceptable format HH:MM:SS

Transaction Time Time of the transaction No Note: While using Excel to edit csv,
please ensure that the time format
is saved as HH:MM:SS
Name of the entity
Sender Name sending the reported No Min length 3, Max length 100
funds

Financial Intelligence Unit – India (FIU-IND) P a g e | 71

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

OUTGOING – Either
Sender MMID or
Sender account
Account number of the number is mandatory
Sender Account
sender of the reported Min length 5, Max length 20
number
funds INCOMING – Neither
MMID nor Account
number are
mandatory
OUTGOING – Either
Sender MMID or
Sender account
Unique MMID of the number is mandatory
Sender MMID sender of the reported Min length 7, Max length 7
funds INCOMING – Neither
MMID nor Account
number are
mandatory

Account IFSC Code of the

Sender IFSC sender of the reported No
funds

It should be entered as AAA-

NNNNNNNNNN
Where AAA represents country
code without + sign and
NNNNNNNNNN represents the 10
Digit Numeric (If country = India)
and Free length, Numeric (If
country!= India)

Mobile number of the Sample: 91-9562013300

Sender Mobile
sender of the reported No 10 Digit Numeric (If country = India)
Number
funds

1. All 10 digits cannot be the same

2. "1234567890" not allowed

FIU will accept reports without

mobile number up to a threshold. If
this threshold is exceeded, then
subsequent reports will get
rejected.
Name of the entity
Beneficiary Name receiving the reported No Min length 3, Max length 100
funds
One of the two,
Unique MMID of the
Beneficiary MMID or
Beneficiary MMID beneficiary of the
Beneficiary Account
reported funds
number is mandatory

Financial Intelligence Unit – India (FIU-IND) P a g e | 72

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

One of the two,
Account Number of the
Beneficiary Account Beneficiary MMID or
receiver of the reported
number Beneficiary Account
funds
number is mandatory
It should be entered as AAA-
NNNNNNNNNN
Where AAA represents country
code without + sign and
NNNNNNNNNN represents the 10
Digit Numeric (If country = India)
Mobile number of the and Free length, Numeric (If
Beneficiary Mobile
beneficiary of the No country!= India)
Number
reported funds
Sample: 91-9562013300
10 Digit Numeric (If country = India)

1. All 10 digits cannot be the same

2. "1234567890" not allowed
Account IFSC code of the
Beneficiary IFSC receiver of the reported No
funds
Purpose of the
Narration No Min length 7, Max length 7
transaction
Report Type This should be NTR Yes

3.1.12 TS3 - NPO UPI Transaction - Bulk Template

The name of the file is TS and should not be changed. This transaction profile will be filled in the scenario
the RE wishes to report an UPI payment.

Column Description Mandatory Validation Rules

All KYC and transactions to be
Report
grouped under one report should
Reference Report Reference Number Yes
have the same report reference
Number
number.
Flag Indicating the position
Valid values are:
Relationship of the customer in the
Sender
Flag reported transaction
Receiver
(Sender/Receiver)
Transaction ID Unique Transaction ID Yes
Whether transaction was
Valid values are:
Transaction an incoming (Credit) or an
Yes Debit
Type outgoing (Debit)
Credit
transaction
Acceptable format DD/MM/YYYY
Transaction
Amount of the transaction Yes Note: While using Excel to edit csv,
Date
please ensure that the date format is
saved as DD/MM/YYYY
Transaction Acceptable format HH:MM:SS
Date of the transaction Yes
Time

Financial Intelligence Unit – India (FIU-IND) P a g e | 73

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Note: While using Excel to edit csv,
please ensure that the time format is
saved as HH:MM:SS
Transaction
Time of the transaction No
Amount
Name of the entity sending
Sender Name No Min length 3, Max length 100
the reported funds
Unique VPA of the sender
Non-mandatory in
of the reported funds. Non-
Sender VPA case of incoming Min length 3, Max length 30
mandatory in case of
transactions
incoming transactions
Mandatory in case
Declaration (If RE needs to provide a
Sender VPA is not Valid value is NA, if this field is not
Sender VPA is Declaration (If Sender VPA
available for required, leave it blank.
not available) is not available)
incoming transaction
It should be entered as AAA-
NNNNNNNNNN
Where AAA represents country code
without + sign and NNNNNNNNNN
represents the 10 Digit Numeric (If
country = India) and Free length,
Mobile number of the
Sender Mobile Numeric (If country!= India)
sender of the reported No
Number
funds
Sample: 91-9562013300
10 Digit Numeric (If country = India)

1. All 10 digits cannot be the same

2. "1234567890" not allowed
Unique MMID of the
Sender MMID sender of the reported No
funds
Account IFSC Code of the
Sender IFSC sender of the reported No
funds
Account Number of the
Sender Account
sender of the reported No Min length 5, Max length 20
Number
funds
Name of the entity
Beneficiary
receiving the reported No Min length 3, Max length 100
Name
funds
Unique VPA of the
Beneficiary VPA beneficiary of the reported Yes Min length 3, Max length 30
funds
It should be entered as AAAA-
NNNNNNNNNN
Where AAAA represents country
code without + sign and
Mobile number of the
Beneficiary NNNNNNNNNN represents the 10
beneficiary of the reported No
Mobile Number Digit Numeric (If country = India) and
funds
Free length, Numeric (If country!=
India)

Sample: 91-9562013300

Financial Intelligence Unit – India (FIU-IND) P a g e | 74

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

10 Digit Numeric (If country = India)

1. All 10 digits cannot be the same

2. "1234567890" not allowed
Beneficiary Account Number of the
Account receiver of the reported No Min length 5, Max length 20
Number funds
Unique MMID of the
Beneficiary
beneficiary of the reported No
MMID
funds
Account IFSC code of the
Beneficiary IFSC receiver of the reported No
funds
Beneficiary
This will be validated against the data
Account Branch No
uploaded by RE in RE Profile details.
Code
Narration Purpose of the transaction No Min length 0, Max length 100
Report Type This should be NTR Yes

3.1.13 GT1 - General transaction format- Bulk Template

This format will be used in scenarios where the above-mentioned reporting formats do not apply.

Column Description Mandatory Validation Rules

All KYC and transactions to be
Report
grouped under one report should
Reference Report Reference Number Yes
have the same report reference
Number
number.
Flag indicating the
relationship that the entity
in the report maintains Acceptable values are
Relationship Flag Yes
with the Customer/Non-Customer.
RE(Customer/Non-
Customer)
Valid values are:
Cash
What instrument/ channel
Cheque
Instrument Type was used to conduct the Yes
DD
transaction
POS
Card
Name of the Institute
Instrument which issued the
Issuer Institute Instrument used to Yes
Name conduct the reported
transaction
Min length:5, Max length:30
ID of the instrument used Mandatory in the case Payment
Instrument ID to conduct the reported Yes mode is Cash/DD
transaction Select Cash if mode as selected above
is Cash.
Acceptable format DD/MM/YYYY
Transaction Date Date of the transaction Yes

Financial Intelligence Unit – India (FIU-IND) P a g e | 75

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Note: While using Excel to edit csv,
please ensure that the date format is
saved as DD/MM/YYYY
Acceptable format HH:MM:SS

Transaction Time Time of the transaction No Note: While using Excel to edit csv,
please ensure that the time format is
saved as HH:MM:SS
Amount of the transaction
Amount INR Yes
in Indian Rupee
Amount of the transaction
Amount FC No Min length:1, Max length:20
in FC (if applicable)
Use the Currency ID downloaded
FC Code FC Code (if applicable) No from the metadata for country from
‘Learning and Resources’
FIU will accept reports without
Account number of the
account number up to a threshold. If
Account Number entity sending the No
this threshold is exceeded, then
reported funds
subsequent reports will get rejected
Branch Code of
Branch Code of Account No
Account
Purpose of
Purpose of Transaction No Min length:1, Max length:100
Transaction
Name of the entity sending Min length:3, Max length:100
the reported funds If Entity Type = Individual
Option to declare Not 1. Special Characters are not allowed.
Available 2. Numbers are not allowed.
Sender Name No
Either Sender Name or the FIU will accept reports without
declaration that it is not sender name up to a threshold. If this
available needs to be threshold is exceeded, then
provided. subsequent reports will get rejected
Either Sender Name or the
Declaration (If
declaration that it is not Yes, if Sender Name Valid values are NA. If this is not
Sender name is
available needs to be is not available required leave this field as blank.
not available)
provided.
10 Digit Numeric (If country = India)
Free length, Numeric (If country !=
India)
Mobile number of the
Sender Mobile 1. All 10 digits cannot be the same
sender of the reported No
Number 2. "1234567890" not allowed
funds
FIU will accept reports without
mobile number up to a threshold. If
this threshold is exceeded, then
subsequent reports will get rejected
IFSC Code/ branch ID of
Min length:3, Max length:30
the sender of the reported
Option to declare Not Available
Sender funds
FIU will accept reports without this
IFSC/Branch Either Sender IFSC/Branch No
field up to a threshold. If this
ID/MICR ID/MICR or the declaration
threshold is exceeded, then
that it is not available
subsequent reports will get rejected
needs to be provided.

Financial Intelligence Unit – India (FIU-IND) P a g e | 76

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Declaration (If
Either Sender IFSC/Branch
Sender Yes, if Sender
ID/MICR or the declaration Valid values are NA. If this is not
IFSC/Branch IFSC/Branch ID/MICR
that it is not available required leave this field as blank.
ID/MICR is not is not available
needs to be provided.
available)
Min length:5, Max length:20
Account number of the FIU will accept reports without this
Sender Account
entity sending the No field up to a threshold. If this
Number
reported funds threshold is exceeded, then
subsequent reports will get rejected
Declaration (If If Sender Account Number
Yes, if Sender
Sender Account is not available, Valid values are NA. If this is not
Account Number is
Number is not declaration needs to be if required leave this field as blank
not available
available) it is not available
Min length:3, Max length:30
Name of the entity
If Entity Type = Individual
receiving the reported
1. Special Characters are not allowed.
funds
2. Numbers are not allowed.
Beneficiary Either Beneficiary Name or
No
Name the declaration that
FIU will accept reports without this
Beneficiary Name is not
field up to a threshold. If this
available have to be
threshold is exceeded, then
provided.
subsequent reports will get rejected
Either Beneficiary Name or
Declaration (If
the declaration that
Beneficiary Yes, if Beneficiary Valid values are NA. If this is not
Beneficiary Name is not
Name is not Name is not available required leave this field as blank.
available have to be
available)
provided.
It should be entered as AAA-
NNNNNNNNNN
Where AAA represents country code
without + sign and NNNNNNNNNN
represents the 10 Digit Numeric (If
country = India) and Free length,
Numeric (If country!= India)

Mobile number of the Sample: 91-9562013300

Beneficiary
beneficiary of the reported No 10 Digit Numeric (If country = India)
Mobile Number
funds

1. All 10 digits cannot be the same

2. "1234567890" not allowed

FIU will accept reports without this

field up to a threshold. If this
threshold is exceeded, then
subsequent reports will get rejected
IFSC code/ Branch ID of
Min length:1, Max length:20
the receiver of the
Beneficiary reported funds
FIU will accept reports without this
IFSC/Branch Either Beneficiary No
field up to a threshold. If this
ID/MICR IFSC/Branch ID/MICR or
threshold is exceeded, then
the declaration that
subsequent reports will get rejected
Beneficiary IFSC/Branch

Financial Intelligence Unit – India (FIU-IND) P a g e | 77

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

ID/MICR is not available
have to be provided.
Either Beneficiary
Declaration (If
IFSC/Branch ID/MICR or
Beneficiary Yes, if Beneficiary
the declaration that Valid values are NA. If this is not
IFSC/Branch IFSC/Branch ID/MICR
Beneficiary IFSC/Branch required leave this field as blank.
ID/MICR is not is not available
ID/MICR is not available
available)
have to be provided.
Account number of the
entity receiving the Min length:5, Max length:20
reported funds
Beneficiary Either Beneficiary Account FIU will accept reports without this
No
Account Number Number or the declaration field up to a threshold. If this
that Beneficiary Account threshold is exceeded, then
Number is not available subsequent reports will get rejected
have to be provided.
Either Beneficiary Account
Declaration (If
Number or the declaration Yes, if Beneficiary
Beneficiary Valid values are NA. If this is not
that Beneficiary Account Account Number is
Account Number required leave this field as blank.
Number is not available not available
is not available)
have to be provided.
Acceptable values are
Report Type Enter the report type Yes NTR
STR

3.1.14 CB1 - Cross-border wire transfer- Bulk Template

The name of the file is CB1 and should not be changed. This transaction profile will be filled in the
scenario a bank wishes to report a cross-border wire transfer.

Column Description Mandatory Validation Rules

All KYC and transactions to be
Report Reference grouped under one report should
Report Reference Number Yes
Number have the same report reference
number.
Unique Transaction Record
Transaction ID Yes
Number
Transaction Date Date of the transaction Yes Acceptable format DD/MM/YYYY
Transaction Time Time of the transaction No Acceptable format HH:MM:SS
Use the Currency ID downloaded
Transaction
Foreign Currency Yes from the metadata for country
Currency
from ‘Learning and Resources’
Amount of the transaction in
Amount In INR Yes Min length 1, Max length 14
Indian Rupee
Amount In
Amount of the transaction in
Transaction Yes Min length 1, Max length 14
Foreign Currency
Currency
Use the Country ID downloaded
Transaction Origin Country of origin of the reported
Yes from the metadata for country
Country transaction
from ‘Learning and Resources’

Financial Intelligence Unit – India (FIU-IND) P a g e | 78

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Name of the Financial institution
Transaction
conducting the reported Yes Min length 5, Max length 20
Institution
transaction
Use the Country ID downloaded
Transaction Destination country of the
Yes from the metadata for country
Destination Country reported transaction
from ‘Learning and Resources’
Min length 1, Max length 50,
1. Special Characters are not
Name of the entity sending the
Sender Name Yes allowed.
reported funds
2. Spaces are not allowed.
3. Numbers are not allowed.
Sender Identifier Confirm the type of the identifier Valid values are PAN / Passport /
Yes
Type for the sender Account Number / Address
Mandatory if
the Sender
Sender Account Identifier
Account number of the sender Min length 1, Max length 50
Number Type is
‘Account
Number’
BIC to be provided mandatorily
Sender Bank BIC Yes Min length 5, Max length 100
for Sender and Beneficiary bank.
Mandatory if
the Sender
Sender Address Address of the entity sending the
Identifier Free text with length 5 -255
Line 1 reported funds
Type is
‘Address’
Mandatory if Use the Country ID downloaded
the Sender from the metadata for country
Address of the entity sending the
Sender Country Identifier from ‘Learning and Resources’
reported funds
Type is Country (Metadata. India will be
‘Address’ selected default)
PIN code if the country is India
Address of the entity sending the
Sender PIN Code No If the country is not India, leave
reported funds
this field as blank.
Address of the entity sending the
Sender Locality No Free text with length 5 -255
reported funds
Use the State ID downloaded from
the metadata for state from
‘Learning and Resources’
Address of the entity sending the
Sender State No State (Auto-populated using PIN
reported funds
code if country = India)
If the country is not India, leave
this field as blank.
Use the District ID downloaded
from the metadata for district
from ‘Learning and Resources’
Note – The district id in
Address of the entity sending the combination with the state id will
Sender District No
reported funds be unique
District (Auto-populated using PIN
code if country = India)
If the country is not India, leave
this field as blank.

Financial Intelligence Unit – India (FIU-IND) P a g e | 79

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Use the City ID downloaded from
the metadata for city from
Sender City / Village Address of the entity sending the
No ‘Learning and Resources’
/ Town reported funds
If the country is not India, leave
this field as blank.
Name of the entity receiving the
Beneficiary Name Yes Min length:1, Max length:50
reported funds
Beneficiary Bank BIC to be provided mandatorily
Yes Min length:1, Max length:50
BIC for Sender and Beneficiary bank.
Beneficiary Account Account number of the entity
No Min length:1, Max length:20
No receiving the reported funds
Beneficiary Address Mandatory if the Beneficiary
No Free text with length 5 -255
Line 1 Identifier Type is ‘Address’
Use the Country ID downloaded
Mandatory if the Beneficiary
Beneficiary Country No from the metadata for country
Identifier Type is ‘Address’
from ‘Learning and Resources’
PIN code (Metadata is applicable if
Beneficiary PIN Country = India)
Beneficiary PIN Code No
Code If the country is not India, leave
this field as blank.
Beneficiary Locality Beneficiary Locality No Free text with length 5 -255
Use the State ID downloaded from
the metadata for state from
Beneficiary State Beneficiary State No ‘Learning and Resources’
If the country is not India, leave
this field as blank.
Use the District ID downloaded
from the metadata for district
from ‘Learning and Resources’
Note – The district id in
Beneficiary District Beneficiary District No
combination with the state id will
be unique
If the country is not India, leave
this field as blank.
Use the City ID downloaded from
the metadata for city from
Beneficiary City /
Beneficiary City / Village / Town No ‘Learning and Resources’
Village / Town
If the country is not India, leave
this field as blank.
Name of any OBO persons (On
Name No Min length:5, Max length:50
behalf of)
ID of any OBO persons (On behalf
ID No Min length:5, Max length:50
of)
Address of any OBO persons (On
Address Line 1 No Free text with length 5 -255
behalf of)
Use the Country ID downloaded
Country of any OBO persons (On
Country No from the metadata for country
behalf of)
from ‘Learning and Resources’
PIN code (Metadata is applicable if
Pin code of any OBO persons (On Country = India)
PIN Code No
behalf of) If the country is not India, leave
this field as blank.
Locality of any OBO persons (On
Locality No Free text with length 5 -255
behalf of)

Financial Intelligence Unit – India (FIU-IND) P a g e | 80

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Use the State ID downloaded from
the metadata for state from
State of any OBO persons (On
State No ‘Learning and Resources’
behalf of)
If the country is not India, leave
this field as blank.
Use the District ID downloaded
from the metadata for district
from ‘Learning and Resources’
District any OBO persons (On Note – The district id in
District No
behalf of) combination with the state id will
be unique
If the country is not India, leave
this field as blank.
Use the City ID downloaded from
the metadata for city from
City of any OBO persons (On
City / Village / Town No ‘Learning and Resources’
behalf of)
If the country is not India, leave
this field as blank.
Use the RBI Purpose Code
Code depicting the purpose of downloaded from the metadata
Purpose Code Yes
the reported transaction for city from ‘Learning and
Resources’
Swift Message Text Text of the SWIFT message No Min length:5, Max length:200
Code of the SWIFT message
Swift Message Code Yes Min length:5, Max length:30
(MT103, MT202, MT202 COV)
Sender In case sender correspondent
Correspondent banks, is involved, BIC to be Yes Min length:5, Max length:100
Bank BIC provided for the same.
Beneficiary In case beneficiary correspondent
Correspondent banks, is involved, BIC to be Yes Min length:5, Max length:100
Bank BIC provided for the same.
Third In case Third Reimbursement
Reimbursement institute is involved, BIC to be Yes Min length:5, Max length:100
Institute Bank BIC provided for the same.
In case Intermediary institute is
Intermediary
involved, BIC to be provided for Yes Min length:5, Max length:100
Institute Bank BIC
the same.
Mandatory if
the Sender
Sender Identifier
Identifier number of the sender Identifier Min length 1, Max length 50
Number
Type is ‘PAN’
or ‘Passport’
Beneficiary Confirm the type of the identifier Valid values are PAN / Passport /
Yes
Identifier Type for the beneficiary Account Number / Address
Mandatory if
the
Beneficiary Identifier number of the Beneficiary
Min length 1, Max length 50
Identifier Number beneficiary Identifier
Type is ‘PAN’
or ‘Passport’
Free Text
Sender State Name as part of
Sender State Name No If the country is not India, use this
sender address.
field for Sender Address. If the

Financial Intelligence Unit – India (FIU-IND) P a g e | 81

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

country is India, leave this field as
blank.
Free Text
If the country is not India, use this
Sender District Sender District Name as part of
No field for Sender Address. If the
Name sender address.
country is India, leave this field as
blank.
Free Text
If the country is not India, use this
Sender City / Village Sender City / Village / Town
No field for Sender Address. If the
/ Town Name Name as part of sender address
country is India, leave this field as
blank.
Free Text
If the country is not India, use this
Beneficiary State Beneficiary State Name as part of
No field for Beneficiary Address. If the
Name beneficiary address
country is India, leave this field as
blank.
Free Text
If the country is not India, use this
Beneficiary District Beneficiary District Name as part
No field for Beneficiary Address. If the
Name of beneficiary address
country is India, leave this field as
blank.
Free Text
Beneficiary City / Beneficiary City / Village / Town If the country is not India, use this
Village / Town Name as part of beneficiary No field for Beneficiary Address. If the
Name address country is India, leave this field as
blank.
Free Text
If the country is not India, use this
State Name as part of OBO
State Name No field for OBO Address. If the
address
country is India, leave this field as
blank.
Free Text
If the country is not India, use this
District Name as part of OBO
District Name No field for OBO Address. If the
address
country is India, leave this field as
blank.
Free Text
If the country is not India, use this
City / Village / Town City / Village / Town Name as
No field for OBO Address. If the
Name part of OBO address
country is India, leave this field as
blank.

3.1.15 CC1 - Counterfeit currency transaction. - Bulk Template

The name of the file is CC1 and should not be changed. This file is used to capture the details of counterfeit
transaction.

Column Description Mandatory Validation Rules

Unique Transaction
Transaction ID No
Record Number

Financial Intelligence Unit – India (FIU-IND) P a g e | 82

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

All KYC and transactions to be
Report Reference Report Reference grouped under one report should
Yes
Number Number have the same report reference
number.

Date of Detection Date of the transaction Yes Acceptable format DD/MM/YYYY

Acceptable values are Cash
Location of detection of
Detected At Yes Counter/Branch/Currency Chest/RBI
counterfeit instrument
CVPS.
Acceptable values are
Report Type Enter the report type Yes
CCR
ID of the branch where
Branch or CAM ID the transaction was Yes
conducted

Total Amount of Total amount involved in

Yes Min length:5, Max length:100
Transaction the transaction

Name of the entity

Tendering Person Name depositing the No Min length:0, Max length:100
counterfeit instrument
PAN number of the
entity conducting the
Tendering Person PAN
transaction in the case No Min length:10, Max length:10
Number (Non-customer)
where the entity is not a
customer of the RE
If PAN is not available,
Declaration (If PAN is not Yes, PAN is not
declaration needs to be
available) available
filed
FICN / Fake Foreign
Yes Min length:1, Max length:20
Currency Face Value
Free text narration
Narration Yes Min length:3, Max length:100
summarising the report
Account Number(s) on
Account Number which the reported No Min length:10, Max length:50
transaction(s) took place
Name of the account
holder in whose account
Account Holder No Min length:3, Max length:30
the counterfeit funds
were being deposited
Whether the police were
informed of the
Police Informed detection of counterfeit Yes
Instrument (Yes/ No/
N.A.)
FIR Details Details of the FIR filed No Min length:0, Max length:100

3.1.16 Counterfeit_Detail - Bulk Template

The name of the file is Counterfeit_Detail and should not be changed. This file is used to capture the details
of counterfeit instruments involved in the transaction.

Financial Intelligence Unit – India (FIU-IND) P a g e | 83

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

All KYC and Transactions to be
Report Reference Report Reference grouped under one report should
Yes
Number Number have the same report reference
number.
Transaction ID is used to link CC1
Transaction ID Transaction ID Yes
and Counterfeit Details.
Instrument that was
Acceptable Values are Cash/
Instrument Type used to conduct the Yes
Cheque/ DD/ Card / Other
transaction
Instrument Serial Serial Number of the
No Free Text, Alphanumeric
Numbers Instrument
Denomination of the
Instrument Denomination No
counterfeit instrument
Count of the counterfeit
Instrument Count Yes Free Text, Alphanumeric
instrument
Use the Currency ID downloaded
Currency of the
Currency Code No from the metadata for country from
counterfeit instrument
‘Learning and Resources’
If Instrument Type is
Yes,
‘Other’, provide the
Other Instrument Type If Instrument
name of the instrument
Type = "Other"
Type
Amount Yes

3.1.17 CB2- Cross Border Wire Transaction for Casino - Bulk Template

This transaction format is to be used by casinos to report Cross Border transactions.

Column Description Mandatory Validation Rules

All KYC and transactions to be grouped
Report Reference
Report Reference Number Yes under one report should have the same
Number
report reference number.
Unique Transaction Record
Transaction ID No
Number
Whether transaction was a
Transaction Type pay-in or a pay-out Yes
transaction
Transaction Date Date of the transaction Yes Acceptable format DD/MM/YYYY
Transaction Time Time of the transaction No Acceptable format HH:MM:SS
Transaction Amount of the transaction
Yes Min length 1, Max length 14
Amount in Foreign Currency
What instrument/channel
Mode of Acceptable values are
was used to conduct the Yes
Transaction Cheque/DD/Card/Transfer
transaction
Min Length:5, Max Length:30
Instrument ID used to
Instrument ID Yes At least one required.
conduct the transaction
If field left Blank
IFSC Code of the transaction
IFSC Yes
branch
Min Length:3, Max Length:30
Name Name of the customer Yes If Entity Type = Individual
1. Special Characters are not allowed.

Financial Intelligence Unit – India (FIU-IND) P a g e | 84

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

2. Numbers are not allowed.
Min Length:10, Max Length:15
One out of PAN
‘PAN PAN Number of the entity
Number’ or Format : 10 Digit. (AAAAA)(NNNN)(A) .
‘Declaration A = Alphabet and N = Number
PAN Number PAN of the account holder
(If PAN is
not (NNNN) - Cannot be 0000
available)’ is
mandatory 4th Alphabet (AAAAA) will be "P" for
individuals.
One out of
‘PAN
Number’ or
Declaration (If
Provide a declaration if PAN ‘Declaration IF PAN is not available, enter NA. Else leave
PAN is not
is not available (If PAN is the field as blank
available)
not
available)’ is
mandatory
PAN Exempt Investor
PEKRN Category Number of the No
account holder
One of the 4
verification
NREGA Card/ One of the 4 verification
documents
Voter ID/Driving documents mandatory in Min Length:5, Max Length:30
mandatory
License/ NPR case PAN doesn’t exist
in case PAN
doesn’t exist
Passport
Passport Number of the If nationality is Indian, then Passport
Yes
Passport Number customer in case number of the individual should be in
(threshold)
PAN/PEKRN isn’t available format ANNNNNNN
A = Upper case Alphabet, N = Number
Acceptable format DD/MM/YYYY
1. Date of birth cannot be less than 01-01-
1900.
Date of Birth of the
Date Of Birth Yes 2. Date of birth cannot be greater than
customer
Current Date.
3. Date of birth cannot be greater than date
of reported transaction.
Min Length:10, Max Length:10
10 Digit Numeric (If country = India)
Mobile Number of the Free length, Numeric (If country != India)
Mobile Number Yes
Customer
1. All 10 digits cannot be the same
2. "1234567890" not allowed
Min Length:5, Max Length:30
(Alphanumeric)@(Alphanuimeric).(Text)

1. Uppercase (A-Z) and lowercase (a-z)

Email Email ID of the customer No
English letters.
2. Acceptable Digits (0-9).
3. Characters ! # $ % & ' * + - / = ? ^ _ ` { | }
~

Financial Intelligence Unit – India (FIU-IND) P a g e | 85

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

4. Character . ( Period, dot or full stop) if it
is not the first or last character and it will
not come one after the other.
Address Line 1 Address No Free text with length 5 -255
Use the Country ID downloaded from the
Country as part of the
Country No metadata for country from ‘Learning and
address
Resources’
Pin code as part of the PIN code (Metadata is applicable if Country
PIN Code No
address = India)
Locality State as part of the address No Free text with length 5 -255
Use the State ID downloaded from the
District as part of the
State No metadata for state from ‘Learning and
address
Resources’
Use the District ID downloaded from the
metadata for district from ‘Learning and
City / Village / Town as part
District No Resources’
of the address
Note – The district id in combination with
the state id will be unique
Use the City ID downloaded from the
City / Village /
Address No metadata for city from ‘Learning and
Town
Resources’
Secondary Address of the entity
No Free text with length 5 -255
Address Line 1 sending the reported funds
Use the Country ID downloaded from the
Secondary Address of the entity
No metadata for country from ‘Learning and
Country sending the reported funds
Resources’
Secondary PIN Address of the entity PIN code (Metadata is applicable if Country
No
Code sending the reported funds = India)
Secondary Address of the entity
No Free text with length 5 -255
Address Locality sending the reported funds
Use the State ID downloaded from the
Address of the entity
Secondary State No metadata for state from ‘Learning and
sending the reported funds
Resources’
Use the District ID downloaded from the
metadata for district from ‘Learning and
Address of the entity
Secondary District No Resources’
sending the reported funds
Note – The district id in combination with
the state id will be unique
Use the City ID downloaded from the
Secondary City / Address of the entity
No metadata for city from ‘Learning and
Village / Town sending the reported funds
Resources’

3.1.18 TS6 – Wallet STR Format - Bulk Template

This transaction format is to be used for reporting suspicious wallet transactions.

Column Description Mandatory Validation Rules

All KYC and transactions to be grouped
Report Reference
Report Reference Number Yes under one report should have the same
Number
report reference number.
Unique Transaction Record Must contain only numbers and/or
Transaction ID Yes
Number alphabets value

Financial Intelligence Unit – India (FIU-IND) P a g e | 86

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Transaction
Amount of the transaction Yes Must contain only number or decimal value
Amount
Transaction Date Date of the transaction No Acceptable format DD/MM/YYYY
Transaction Time Time of the transaction No Acceptable format HH:MM:SS
Special Characters are not allowed with
Name of the entity sending exception to below
Sender Name Yes
the reported funds - apostrophe '
Numbers are not allowed.
10 Digit Numeric (If country = India)
Mobile number of the Free length, Numeric (If country != India)
Sender Mobile
sender of the reported Yes
Number
funds 1. All 10 digits cannot be the same
2. "1234567890" not allowed
Special Characters are not allowed with
Name of the entity receiving exception to below
Beneficiary Name Yes
the reported funds a) apostrophe '
Numbers are not allowed.
10 Digit Numeric (If country = India)
Mobile number of the Free length, Numeric (If country != India)
Beneficiary
beneficiary of the reported Yes
Mobile Number
funds 1. All 10 digits cannot be the same
2. "1234567890" not allowed
Narration Purpose of the transaction Yes NA
Acceptable values are
Report Type Enter the report type Yes
STR

3.1.19 TS7 – Brokerage Firms STR Format - Bulk Template

This transaction format is to be used by brokerage firms to report suspicious transactions.

Column Description Mandatory Validation Rules

All KYC and transactions to be grouped
Report Reference
Report Reference Number Yes under one report should have the same
Number
report reference number.
Flag Indicating the
relationship the entity in Acceptable values are Customer/Non-
Relationship Flag Yes
the report maintains with Customer.
the RE
Unique Transaction Record Must contain only numbers and/or
Transaction ID Yes
Number alphabets value
Whether transaction was a
Transaction Type sale or a purchase Yes Acceptable Values are Buy/Sell
transaction
Whether the traded
Acceptable Values are Equity/ Futures/
Trade Type products were Equities, Yes
Options
Futures or Options
Trade Date Date of the transaction Yes Acceptable format DD/MM/YYYY
Trade Time Time of the transaction No Acceptable format HH:MM:SS
Must contain only number or decimal
Amount Amount of the transaction Yes
value

Financial Intelligence Unit – India (FIU-IND) P a g e | 87

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Unique ID of the Depository Alphanumeric
DP ID No
participant
Yes, If DP ID
Declaration (If DP
DP ID not available flag is not This is mandatory if DP ID is not available,
ID is not available)
available
Related Bank Account Number connected
No Alphanumeric
Account Number to the DP ID
Client ID/Customer Unique customer ID
No
ID/UCIC provided to the customer
The entered field will be validated from a
Account IFSC connected to
Related AC IFSC No list of IFSC Codes maintained as part of
the DP ID
Metadata.
ISIN/ Security International Securities
Code/ Product Identification
Yes Alphanumeric
Code/Commodity Number/Unique ID code of
Exchange Code the product
Rate at which the above
Must contain only number or decimal
Rate Per Unit / Lot mentioned units were Yes
value
sold/purchased
Number or Units/Lots Must contain only number or decimal
No Of Units / Lots Yes
which were sold/purchased value
Expiry Date Expiry Date of F&O No Mandatory in case of Futures and Options
Mandatory in case of Futures and Options
Whether F&O transaction is
Call / Put No
Call or Put
Acceptable values are Call/ Put
Must contain only number or decimal
Strike Price Strike Price of F&O No
value
Acceptable values are
Report Type Enter the report type Yes
STR

3.1.20 TS8 – Exchange House STR Format - Bulk Template

This transaction format is to be used by exchange houses to report suspicious transactions.

Column Description Mandatory Validation Rules

All KYC and transactions to be grouped
Report Reference
Report Reference Number Yes under one report should have the same
Number
report reference number.
Unique Transaction Record Must contain only numbers and/or
Transaction ID Yes
Number alphabets value
Unique ID of the
DP ID (Seller) Depository participant Yes Alphanumeric
(Seller)
Unique ID of the
DP ID (Buyer) Depository participant Yes Alphanumeric
(Buyer)
The entered field will be validated from a
Related Bank IFSC Account IFSC connected to
No list of IFSC Codes maintained as part of
(Seller) the DP ID
Metadata.
The entered field will be validated from a
Related Bank IFSC Account IFSC connected to
No list of IFSC Codes maintained as part of
(Buyer) the DP ID
Metadata.

Financial Intelligence Unit – India (FIU-IND) P a g e | 88

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Related Bank
Account Number
Account Number No Alphanumeric
connected to the DP ID
(Seller)
Related Bank
Account Number
Account Number No Alphanumeric
connected to the DP ID
(Buyer)
Client ID/UCIC
Client ID of the Seller No Alphanumeric
(Seller)
Client ID/UCIC
Client ID of the Buyer No Alphanumeric
(Buyer)
Trade Date Date of the transaction Yes Acceptable format DD/MM/YYYY
Trade Time Time of the transaction No Acceptable format HH:MM:SS
Whether the traded
Acceptable Values are Equity/ Futures/
Trade Type products were Equities, Yes
Options
Futures or Options
Must contain only number or decimal
Transaction Amount Amount of the transaction Yes
value
ISIN/ Security Code/ International Securities
Product Identification
Yes Alphanumeric
Code/Commodity Number/Unique ID code of
Exchange Code the product
Rate at which the above
Must contain only number or decimal
Rate Per Unit mentioned units were Yes
value
sold/purchased
Number or Units/Lots Must contain only number or decimal
Number of Units Yes
which were sold/purchased value
Must contain only number or decimal
Strike Price Strike Price of F&O No
value
Mandatory in case of Futures and Options
Whether F&O transaction
Call / Put No
is Call or Put
Acceptable values are Call/ Put
Acceptable format DD/MM/YYYY
Expiry Date Expiry Date of F&O No
Mandatory in case of Futures and Options
Report Type Enter the report type Yes Acceptable values are STR

3.1.21 TS9 – Depositories STR Format - Bulk Template

This transaction format is to be used by depositories to report suspicious transactions.

Column Description Mandatory Validation Rules

All KYC and transactions to be grouped
Report Reference
Report Reference Number Yes under one report should have the same
Number
report reference number.
Unique Transaction Record Must contain only numbers and/or
Transaction ID Yes
Number alphabets value
Flag Indicating the
relationship the entity in the
Acceptable values are Customer/Non-
Relationship Flag report maintains with the Yes
Customer.
RE(Customer/Non-
Customer)

Financial Intelligence Unit – India (FIU-IND) P a g e | 89

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Whether transaction was a
Transaction Type market or an off-market Yes Acceptable Values are Market/ Off Market
transaction
Transaction Date Date of the transaction Yes Acceptable format DD/MM/YYYY
Transaction Time Time of the transaction No Acceptable format HH:MM:SS
Sale / Purchase Must contain only number or decimal
Number of units/lots traded Yes
Quantity value
Sale / Purchase Must contain only number or decimal
Amount of the transaction Yes
Amount value
Alphanumeric
DP ID Unique ID of the Depository Yes
Total Value of the portfolio
BO ID Folio Must contain only number or decimal
of the depository Yes
Valuation value
participant
Whether the DP is a buyer
BO ID Flag Yes Acceptable Values are Buyer/Seller
or a seller
Only Numeric and/or alphabet values will
BO ID Unique ID of the Beneficiary Yes
be allowed.
International Securities
ISIN / Product Identification
Yes Alphanumeric
Code Number/Unique ID code of
the product
Rate at which the off-
Rate of Must contain only number or decimal
market transaction was No
Transaction value
conducted
Special Characters are not allowed with
exception to below
Seller Name Name of seller No
a) apostrophe '
Numbers are not allowed.
Special Characters are not allowed with
exception to below
Buyer Name Name of buyer No
a) apostrophe '
Numbers are not allowed.
Special Characters are not allowed with
exception to below
Customer Name Name of the customer Yes
a) apostrophe '
Numbers are not allowed.
International Securities
ISIN / Product Identification Must contain only number or decimal
Yes
Market Rate Number/Unique ID code of value
the product
Reason to Indicate the key
reason code for transaction
Reason Code Yes NA
value above permissible
limit for the transaction.
Acceptable values are
Report Type Enter the report type Yes
STR

3.1.22 TS10 – NBFC STR Format - Bulk Template

This transaction format is to be used by FI/NBFC/Others to report suspicious transactions.

Financial Intelligence Unit – India (FIU-IND) P a g e | 90

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

All KYC and transactions to be grouped
Report Reference
Report Reference Number Yes under one report should have the same
Number
report reference number.
Flag Indicating the position
of the customer in the
Relationship Flag Yes Acceptable values are Sender/Receiver
reported transaction
(Sender/Receiver)
Acceptable values are
Report Type Enter the report type Yes
STR
Unique Transaction Record Must contain only numbers and/or
Transaction ID Yes
Number alphabets value
Transaction Date Date of the transaction Yes Acceptable format DD/MM/YYYY
Transaction Time Time of the transaction No Acceptable format HH:MM:SS
Transaction Must contain only number or decimal
Amount of the transaction Yes
Amount value
What instrument/channel Acceptable Values are Cash/ Cheque/ DD/
Transaction Mode was used to conduct the Yes Card Payment/ PoS/ NEFT/ RTGS/ UPI/
transaction IMPS/ Wallet
Transaction
Branch ID No NA
Branch ID
Purpose of the transaction
Transaction
Yes NA
Purpose Free text (maximum 100
characters)
ID of the instrument used to If Cash is selected as instrument Type, this
conduct transaction in the will be non- mandatory and "CASH" can be
Instrument ID case where payment mode No entered as instrument ID,
is Cash/Cheque/DD/Card Else, "Only numbers and/or alphabets are
Number allowed."
Account Number(s) on
which the reported
Account Number transaction(s) took place in No Must be alphanumeric
case payment mode is
NEFT/RTGS
IFSC Number(s) on which
The entered field will be validated from a
the reported transaction(s)
IFSC No list of IFSC/Branch Codes maintained as
took place in case payment
part of Metadata
mode is NEFT/RTGS
Special Characters are not allowed with
exception to below
a) dot .
b) Ampersand &
Name of the wallet used for c) Braces ()
Wallet Name the transaction in case No d) Hyphen -
payment mode is Wallet e) apostrophe '
f) forward Slash /
g) Asterisk *
2. Spaces are allowed.
3. Numbers are allowed.
Unique VPA of the entity
Mandatory in the case Payment mode is
conducting the reported
VPA No UPI.
transaction in case payment
mode is UPI

Financial Intelligence Unit – India (FIU-IND) P a g e | 91

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Acceptable format (Text/Number)@(Text)
Example: Ram.kumar.1990@okaxis
Unique MMID of the entity Mandatory in the case Payment mode is
conducting the reported IMPS.
MMID No
transaction in case payment
mode is IMPS 7 Digit Numeric
Special Characters are not allowed with
Name of the entity sending exception to below
Customer Name No
the reported funds a) apostrophe '
2. Numbers are not allowed.
10 Digit Numeric (If country = India)
Mobile Number of the
Customer Mobile Free length, Numeric (If country != India)
entity conducting the Yes
Number 1. All 10 digits cannot be the same
reported transaction
2. "1234567890" not allowed
Account number of the
Customer Related
entity sending the reported No Must be alphanumeric
Account Number
funds
Customer Related IFSC Code/branch ID of the
IFSC/Branch sender of the reported No NA
ID/MICR funds

3.1.23 TS11 – Card System Operators STR Format - Bulk Template

This transaction format is to be used by card system operators to report suspicious transactions.

Column Description Mandatory Validation Rules

All KYC and transactions to be grouped
Report Reference
Report Reference Number Yes under one report should have the same
Number
report reference number.
Unique Transaction Record "Must contain only numbers and/or
Transaction ID Yes
Number alphabets value"
Whether the transaction
was a cash withdrawal, a Acceptable Values are Reversal/Charge /
Transaction Type Yes
card charge or a card ATM Cash withdrawal
reversal
Flag indicating whether card
Masked/Non-
number received is masked Yes Acceptable values are Masked/Non-Masked
Masked
or non-Masked
Card number of the card
Card Number Yes Only numeric values allowed
used to conduct transaction
Transaction Date Date of the transaction Yes Acceptable format DD/MM/YYYY
Transaction Time Time of the transaction No Acceptable format HH:MM:SS
Amount of the transaction Must contain only number or decimal
Amount In INR Yes
in Indian Rupee value
Currency Code of the FC in Use the Currency ID downloaded from the
Transaction
which transaction was Yes metadata for country from ‘Learning and
Currency Code
done. Resources’
Amount In Amount of the transaction Must contain only number or decimal
Yes
Foreign Currency in Foreign Currency value
Special Characters are not allowed with
Acquiring Bank Acquiring bank Yes exception to below
a) dot .

Financial Intelligence Unit – India (FIU-IND) P a g e | 92

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

b) Ampersand &
c) Braces ()
d) Hyphen -
e) apostrophe '
f) forward Slash /
g) Asterisk *
2. Spaces are allowed.
3. Numbers are allowed.
Special Characters are not allowed with
exception to below
a) dot .
b) Ampersand &
Bank that issued the card c) Braces ()
Issuing Bank used to conduct the No d) Hyphen -
reported transaction e) apostrophe '
f) forward Slash /
g) Asterisk *
2. Spaces are allowed.
3. Numbers are allowed.
Use the Country ID downloaded from the
Country in which the card
Issuing Country No metadata for country from ‘Learning and
was issued
Resources’
Special Characters are not allowed with
exception to below
a) dot .
b) Ampersand &
Name of the merchant c) Braces ()
Merchant Name through whom the reported Yes d) Hyphen -
transaction was conducted e) apostrophe '
f) forward Slash /
g) Asterisk *
2. Spaces are allowed.
3. Numbers are allowed.
ID of the merchant through
Merchant ID whom the reported Yes NA
transaction was conducted
Country of operation of the
Use the Country ID downloaded from the
merchant through whom
Merchant Country No metadata for country from ‘Learning and
the reported transaction
Resources’
was conducted
Category code of the
Merchant merchant through whom
No NA
Category Code the reported transaction
was conducted
PoS/ATM ID of the machine
Merchant POS /
at which the reported No NA
ATM ID
transaction was conducted
Address Line 1 Address No Free text with length 5 -255
Address of the entity
Locality No Free text with length 5 -255
Use the Country ID downloaded from the
Country as part of the
Country No metadata for country from ‘Learning and
address
Resources’

Financial Intelligence Unit – India (FIU-IND) P a g e | 93

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Pin code as part of the PIN code (Metadata is applicable if Country
PIN Code No
address = India)
Use the State ID downloaded from the
State State as part of the address No metadata for state from ‘Learning and
Resources’
Use the District ID downloaded from the
metadata for district from ‘Learning and
District as part of the
District No Resources’
address
Note – The district id in combination with
the state id will be unique
Use the City ID downloaded from the
City / Village /
Address of the entity No metadata for city from ‘Learning and
Town
Resources’
Narration Narration of the transaction No
Acceptable values are
Report Type Enter the report type Yes
STR

3.1.24 TS12 – Casino STR Format - Bulk Template

This transaction format is to be used by casinos to report suspicious transactions.

Column Description Mandatory Validation Rules

All KYC and transactions to be grouped
Report Reference
Report Reference Number Yes under one report should have the
Number
same report reference number.
Unique Transaction Must contain only numbers and/or
Transaction ID Yes
Record Number alphabets value
Whether transaction
Transaction Type was a pay-in or a pay- Yes Acceptable Values are Pay-in/Pay-out
out transaction
Transaction Date Date of the transaction Yes Acceptable format DD/MM/YYYY
Transaction Time Time of the transaction No Acceptable format HH:MM:SS
Amount of the Must contain only number or decimal
Transaction Amount Yes
transaction value
What
Acceptable values are(Cash/
instrument/channel was
Mode Of Transaction Yes Cheque/DD/Card/POS/ NEFT/ RTGS/
used to conduct the
UPI/ IMPS/ Wallet)
transaction
Acceptable format DD/MM/YYYY
1. Date of birth cannot be less than
01-01-1900.
Date of Birth of the Yes
Date of Birth 2. Date of birth cannot be greater
customer (Threshold)
than Current Date.
3. Date of birth cannot be greater
than date of reported transaction.
"Alphanumeric@(Alphanumeric).(Text
)
Allowed parameters in above
Email Email ID of the customer No alphanumeric portion:
1. Uppercase (A-Z) and lowercase (a-z)
English letters.
2. Acceptable Digits (0-9).

Financial Intelligence Unit – India (FIU-IND) P a g e | 94

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

3. Characters ! # $ % & ' * + - / = ? ^ _ `
{|}~
4. Character . ( Period, dot or full stop)
if it is not the first or last character and
it will not come one after the other.
5. Space not allowed in between any
character.
Acceptable values are
Report Type Enter the report type Yes
STR
Instrument ID/Account Instrument details used
No/Card to conduct the Yes
Number/VPA/MMID/Cash transaction
IFSC code if the
IFSC transaction is conducted No
through a Bank

3.1.25 MT1 – MTSS Transaction Reporting Format -Bulk Template

This transaction format is to be used by MTSS to report suspicious transactions.

Column Description Mandatory Validation Rules

All KYC and transactions to be grouped
Report Reference
Report Reference Number Yes under one report should have the same
Number
report reference number.
Money Transfer Must contain only numbers and/or
Unique Transaction ID Yes
Control No alphabets value
Unique Transaction Record Must contain only numbers and/or
Transaction ID Yes
Number alphabets value
Transaction Date Date of the transaction Yes Acceptable format DD/MM/YYYY
Transaction Time Time of the transaction No Acceptable format HH:MM:SS
Must contain only numeric or decimal
Amount in INR Amount of the transaction Yes
values
Transaction List of values will be fetched from Currency
Foreign Currency Code Yes
Currency Code Code Metadata
Amount in
Must contain only numeric or decimal
Transaction Amount of the transaction Yes
values
Currency
Transaction
Purpose of the transaction Yes NA
Purpose Code
Transaction
Description of the
Purpose Code Yes Free text with minimum characters of 3
transaction purpose code
Description
Special Characters are not allowed with
Name of the entity sending exception to below
Sender Name Yes
the reported funds a) apostrophe '
Numbers are not allowed.
10 Digit Numeric (If country = India)
Mobile number of the Free length, Numeric (If country != India)
Sender Mobile Yes
sender of the reported
Number (Threshold)
funds 1. All 10 digits cannot be the same
2. "1234567890" not allowed

Financial Intelligence Unit – India (FIU-IND) P a g e | 95

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Sender Address
Address of the sender No Free text with length 5 -255
Line 1
Use the Country ID downloaded from the
Sender Country Country of the sender No metadata for country from ‘Learning and
Resources’
PIN code (Metadata is applicable if Country
Sender PIN Code PIN Code of the sender No
= India)
Sender Locality Locality of the sender No Free text with length 5 -255
Use the State ID downloaded from the
Sender State State of the Sender No metadata for state from ‘Learning and
Resources’
Use the District ID downloaded from the
metadata for district from ‘Learning and
Sender District District of the Sender No Resources’
Note – The district id in combination with
the state id will be unique
Use the City ID downloaded from the
Sender City /
City of the sender No metadata for city from ‘Learning and
Village / Town
Resources’
Sender Agent ID Agent ID of the sender Yes NA
Sender Agent
Address of the sender agent No Free text with length 5 -255
Address Line 1
Use the Country ID downloaded from the
Sender Agent
Country of the sender Agent No metadata for country from ‘Learning and
Country
Resources’
Sender Agent PIN PIN Code of the sender PIN code (Metadata is applicable if Country
No
Code Agent = India)
Sender Agent
Locality of the sender Agent No Free text with length 5 -255
Locality
Use the State ID downloaded from the
Sender Agent
State of the Sender Agent No metadata for state from ‘Learning and
State
Resources’
Use the District ID downloaded from the
metadata for district from ‘Learning and
Sender Agent
District of the Sender Agent No Resources’
District
Note – The district id in combination with
the state id will be unique
Use the City ID downloaded from the
Sender Agent City City / Village / Town of the
No metadata for city from ‘Learning and
/ Village / Town sender Agent
Resources’
Special Characters are not allowed with
exception to below
Beneficiary Name Name of the entity Yes
a) apostrophe '
2. Numbers are not allowed.
10 Digit Numeric (If country = India)
Free length, Numeric (If country != India)
Beneficiary Mobile number of the Yes
Mobile No beneficiary (Threshold)
1. All 10 digits cannot be the same
2. "1234567890" not allowed
Beneficiary ID ID used by the beneficiary Yes List of values will be the Metadata for
Type of the reported funds (Threshold) identifier Type(Individual)

Financial Intelligence Unit – India (FIU-IND) P a g e | 96

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

ID Number of the
Beneficiary ID Yes Validations as applicable for the
beneficiary of the reported
Number (Threshold) selected "Beneficiary ID Type"
funds
Beneficiary
Beneficiary Address Line 1 No Free text with length 5 -255
Address Line 1
Use the Country ID downloaded from the
Beneficiary
Beneficiary Country No metadata for country from ‘Learning and
Country
Resources’
Beneficiary PIN PIN code (Metadata is applicable if Country
Beneficiary PIN Code No
Code = India)
Beneficiary
Beneficiary Locality No Free text with length 5 -255
Locality
Use the State ID downloaded from the
Beneficiary State Beneficiary State No metadata for state from ‘Learning and
Resources’
Use the District ID downloaded from the
metadata for district from ‘Learning and
Beneficiary
Beneficiary District No Resources’
District
Note – The district id in combination with
the state id will be unique
Use the City ID downloaded from the
Beneficiary City / Beneficiary City / Village /
No metadata for city from ‘Learning and
Village / Town Town
Resources’
What instrument/channel
Acceptable values are
Pay-Out Mode was used to conduct the Yes
Cash/Cheque/DD/Card/Transfer
transaction
Account Number of the
Pay-Out Account
account the final Pay-out Yes Alphanumeric
Number
was made to
Account IFSC code of the
Value will be validated against IFSC code
Pay-Out IFSC account the final Pay-out Yes
metadata.
was made to
Pay-Out Date Date of the Final Pay-out Yes Acceptable format DD/MM/YYYY
Pay-Out Address Address Line 1 of the Pay-
Yes Free text with length 5 -255
Line 1 Out
Use the Country ID downloaded from the
Pay-Out Country Country of the Pay-Out Yes metadata for country from ‘Learning and
Resources’
PIN code (Metadata is applicable if Country
Pay-Out PIN Code PIN Code of the Pay-Out Yes
= India)
Pay-Out Locality Locality of the Pay-Out Yes Free text with length 5 -255
Use the State ID downloaded from the
Pay-Out State State of the Pay-Out Yes metadata for state from ‘Learning and
Resources’
Use the District ID downloaded from the
metadata for district from ‘Learning and
Pay-Out District District of the Pay-Out Yes Resources’
Note – The district id in combination with
the state id will be unique
Use the City ID downloaded from the
Pay-Out City / City / Village / Town of the
Yes metadata for city from ‘Learning and
Village / Town Pay-Out
Resources’

Financial Intelligence Unit – India (FIU-IND) P a g e | 97

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

ID of the Agent who made
Payee Agent ID Yes NA
the final pay-out
Payee Agent Agent who made the final
Yes NA
Network pay-out
Payee Agent Address Line 1 of the Payee
Yes Free text with length 5 -255
Address Line 1 Agent
Use the Country ID downloaded from the
Payee Agent
Country of the Payee Agent Yes metadata for country from ‘Learning and
Country
Resources’
Payee Agent PIN PIN Code of the Payee PIN code (Metadata is applicable if Country
Yes
Code Agent = India)
Payee Agent
Locality of the Payee Agent Yes Free text with length 5 -255
Locality
Use the State ID downloaded from the
Payee Agent State State of the Payee Agent Yes metadata for state from ‘Learning and
Resources’
Use the District ID downloaded from the
metadata for district from ‘Learning and
Payee Agent
District of the Payee Agent Yes Resources’
District
Note – The district id in combination with
the state id will be unique
Use the City ID downloaded from the
Payee Agent City /
City of the Payee Agent Yes metadata for city from ‘Learning and
Village / Town
Resources’
Acceptable values are
Report Type Enter the report type Yes
STR
Non Indian Pin code as part of the PIN code (Metadata is applicable if Country
No
Sender Pincode address = India)
Non Indian
Sender Agent Pin code as part of the PIN code (Metadata is applicable if Country
No
Pincode address = India)

Non Indian
Pin code as part of the PIN code (Metadata is applicable if Country
Beneficiary No
address = India)
Pincode
Non Indian Pay- Pin code as part of the PIN code (Metadata is applicable if Country
No
Out Pincode address = India)
Non Indian
Payee Agent Pin code as part of the PIN code (Metadata is applicable if Country
No
Pincode address = India)

Free Text
Sender State Sender State Name as part No If the country is not India, use this field for
Name of sender address. Sender Address. If the country is India,
leave this field as blank.
Free Text
Sender District Sender District Name as No If the country is not India, use this field for
Name part of sender address. Sender Address. If the country is India,
leave this field as blank.
Free Text
Sender City /
Sender City Name as part of No If the country is not India, use this field for
Village / Town
sender address. Sender Address. If the country is India,
Name leave this field as blank.

Financial Intelligence Unit – India (FIU-IND) P a g e | 98

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Free Text
Sender Agent Sender Agent State Name as No If the country is not India, use this field for
State Name part of sender address. Sender Agent Address. If the country is
India, leave this field as blank.
Free Text
Sender Agent Sender Agent District Name No If the country is not India, use this field for
District Name as part of sender address. Sender Agent Address. If the country is
India, leave this field as blank.
Sender Agent Free Text
City / Village / Sender Agent City Name as No If the country is not India, use this field for
part of sender address. Sender Agent Address. If the country is
Town Name
India, leave this field as blank.
Free Text
Beneficiary Beneficiary State Name as No If the country is not India, use this field for
State Name part of sender address. Beneficiary Address. If the country is India,
leave this field as blank.
Free Text
Beneficiary Beneficiary District Name as No If the country is not India, use this field for
District Name part of sender address. Beneficiary Address. If the country is India,
leave this field as blank.
Beneficiary City Free Text
/ Village / Town Beneficiary City Name as No If the country is not India, use this field for
part of sender address. Beneficiary Address. If the country is India,
Name
leave this field as blank.
Free Text
Pay-Out State Pay-Out State Name as part No If the country is not India, use this field for
Name of sender address. Pay-Out Address. If the country is India,
leave this field as blank.
Free Text
Pay-Out District Pay-Out District Name as No If the country is not India, use this field for
Name part of sender address. Pay-Out Address. If the country is India,
leave this field as blank.
Pay-Out City / Free Text
Village / Town Pay-Out City Name as part No If the country is not India, use this field for
of sender address. Pay-Out Address. If the country is India,
Name
leave this field as blank.
Free Text
Payee Agent Payee Agent State Name as No If the country is not India, use this field for
State Name part of sender address. Payee Agent Address. If the country is India,
leave this field as blank.
Free Text
Payee Agent Payee Agent District Name No If the country is not India, use this field for
District Name as part of sender address. Payee Agent Address. If the country is India,
leave this field as blank.
Payee Agent City Free Text
/ Village / Town Payee Agent City Name as No If the country is not India, use this field for
part of sender address. Payee Agent Address. If the country is India,
Name
leave this field as blank.

Financial Intelligence Unit – India (FIU-IND) P a g e | 99

 User Manual - FINGate 2.0 - Reports Version 1.1

3.1.26 PTR -Property Transaction -Bulk Template

The name of the file is PTR and should not be changed. This file is used to capture the details of property
transactions.

Column Description Mandatory Validation Rules

Report All transactions to be grouped under
Reference Report Reference Number Yes one report should have the same
Number report reference number.
Property
Unique property ID No
Registration ID
Unique
Unique Transaction Record
Transaction Yes
Number
Record ID
Property
Property Address Line 1 Yes Free text with length 5 -255
Address 1
Property
Property Address Locality Yes Free text with length 5 -255
Address Locality
Use the Country ID downloaded from
Property Country as part of Property
Yes the metadata for country from
Address Country Address
‘Learning and Resources’
Property
Pin code as part of Property PIN code (Metadata is applicable if
Address Pin Yes
Address Country = India)
Code
Use the State ID downloaded from the
Property
State as part of Property Address Yes metadata for state from ‘Learning and
Address State
Resources’
Use the District ID downloaded from
the metadata for district from
Property
District as part Property Address Yes ‘Learning and Resources’
Address District
Note – The district id in combination
with the state id will be unique
Use the City ID downloaded from the
Property
City as part of Property Address Yes metadata for city from ‘Learning and
Address City
Resources’
Mode of What instrument/channel was Acceptable values are Cash/ Cheque/
No
Transaction used to conduct the transaction DD/ Card/Others
Acceptable format DD/MM/YYYY

Transaction Date Date of the transaction Yes Note: While using Excel to edit csv,
please ensure that the date format is
saved as DD/MM/YYYY
Transaction
Amount of the transaction Yes
Amount
Transaction
Yes Free text with length 5 -255
Address 1
Transaction
Transaction Address Line 1 Yes Free text with length 5 -255
Address Locality
Use the Country ID downloaded from
Transaction Country as part of registered
Yes the metadata for country from
Address Country address
‘Learning and Resources’
Transaction
Pin code as part of registered PIN code (Metadata is applicable if
Address Pin Yes
address Country = India)
Code

Financial Intelligence Unit – India (FIU-IND) P a g e | 100

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

Use the State ID downloaded from the
Transaction
State as part of registered address Yes metadata for state from ‘Learning and
Address State
Resources’
Use the District ID downloaded from
the metadata for district from
Transaction District as part of registered
Yes ‘Learning and Resources’
Address District address
Note – The district id in combination
with the state id will be unique
Use the City ID downloaded from the
Transaction
City as part of registered address Yes metadata for city from ‘Learning and
Address City
Resources’
If Entity Type = Individual
Name of the entity selling the
Seller Name Yes 1. Special Characters are not allowed.
property
2. Numbers are not allowed.
PAN
PAN Number of the entity
PAN of the entity selling the Format : 10 Digit. (AAAAA)(NNNN)(A) .
Seller PAN No A = Alphabet and N = Number
property

(NNNN) - Cannot be 0000

If the Seller
Declaration (If PAN is not
If the Seller PAN of the individual is
seller PAN is not available,
not available, this becomes
available) enter NA.
mandatory
Else leave it
blank.
PAN exemption Number of the Mandatory if "Not Available" is
Seller PEKRN No
seller declared in the PAN field
Acceptable values are Individual/
Seller Entity
Entity Type of the seller Yes Company/ Firm/ HUF/ Government
Type
Office/ Others
Seller Address 1 Yes Free text with length 5 -255
Seller Address
Seller Address Line 1 Yes Free text with length 5 -255
Locality
Use the Country ID downloaded from
Seller Address
Country as part of Seller Address Yes the metadata for country from
Country
‘Learning and Resources’
Seller Address PIN code (Metadata is applicable if
Pin code as part of Seller Address Yes
Pin Code Country = India)
Use the State ID downloaded from the
Seller Address
State as part of Seller Address Yes metadata for state from ‘Learning and
State
Resources’
Use the District ID downloaded from
the metadata for district from
Seller Address
District as part Seller Address Yes ‘Learning and Resources’
District
Note – The district id in combination
with the state id will be unique
Use the City ID downloaded from the
Seller Address
City as part of Seller Address Yes metadata for city from ‘Learning and
City
Resources’
If Entity Type = Individual
Name of the entity purchasing the
Buyer Name Yes 1. Special Characters are not allowed.
property
2. Numbers are not allowed.

Financial Intelligence Unit – India (FIU-IND) P a g e | 101

 User Manual - FINGate 2.0 - Reports Version 1.1

Column Description Mandatory Validation Rules

PAN
PAN Number of the entity
PAN of the entity purchasing the Format : 10 Digit. (AAAAA)(NNNN)(A) .
Buyer PAN No A = Alphabet and N = Number
property

(NNNN) - Cannot be 0000

Declaration (If If the Buyer PAN is not available, Yes, If Buyer

buyer PAN is not Either of Buyer PAN or Buyer PAN Not
declaration needs to be if it is not PAN is not
available) Available is mandatory
available available
PAN exemption Number of the Mandatory if "Not Available" is
Buyer PEKRN No
Buyer declared in the PAN field
Acceptable values are Individual/
Buyer Entity
Entity Type of the buyer Yes Company/ Firm/ HUF/ Government
Type
Office/ Others
Buyer Address Buyer Address Line 1 Yes Free text with length 5 -255
Buyer Address
Buyer Address Locality Yes Free text with length 5 -255
Locality
Use the Country ID downloaded from
Buyer Address
Country as part of Buyer Address Yes the metadata for country from
Country
‘Learning and Resources’
Buyer Address PIN code (Metadata is applicable if
Pin code as part of Buyer Address Yes
Pin Code Country = India)
Use the State ID downloaded from the
Buyer Address
State as part of Buyer Address Yes metadata for state from ‘Learning and
State
Resources’
Use the District ID downloaded from
the metadata for district from
Buyer Address
District as part of Buyer Address Yes ‘Learning and Resources’
District
Note – The district id in combination
with the state id will be unique
Use the City ID downloaded from the
Buyer Address
City as part of Buyer Address Yes metadata for city from ‘Learning and
City
Resources’

Financial Intelligence Unit – India (FIU-IND) P a g e | 102

 User Manual - FINGate 2.0 - Reports Version 1.1

3.2 Acronyms and Abbreviations

Sr. No. Acronym Definition

1. AML Anti-Money Laundering
2. APO Alternate Principal Officer
3. ATM Automated Teller Machine
4. CAPTCHA Completely Automated Public Turing test to tell Computers and Humans Apart
5. CBDT Central Board of Direct Taxes
6. CBWTR Cross Border Wire Transfer Reports
7. CCR Counterfeit Currency Report
8. CIN Company Identification Number
9. CSV Comma-separated values
10. CTR Cash Transaction Report
11. DD Designated Director
12. DIN Director Identification Number
13. DQR Data Quality Report
14. DSC Digital Signature Certificates
15. FCRN Foreign Company Registration Number
16. FIU-IND Financial Intelligence Unit, India
17. FLLPIN Foreign Limited Liability Partnership Identification Number
18. GoS Grounds of Suspicion
19. GSTIN Goods and Services Tax Identification Number
20. GSTN Goods and Services Tax Network
21. ID Identification Document
22. KYC Know Your Customer
23. LLPIN Limited Liability Partnership Identification Number
24. MCA Ministry of Corporate Affairs
25. MSP Managed Service Provider
26. MTSS Money Transfer Service Scheme
27. Non-PO Non Principal Officer
28. NTR Non-Profit Transaction Reports
29. OTP One Time Password
30. PAN Permanent Account Number
31. PMLA Prevention of Money Laundering Act
32. PO Principal Officer
33. PTR Property Transaction Reports
34. RBI Reserve Bank of India
35. RE Reporting Entity
36. SMS Short Message Service
37. STR Suspicious Transaction Report
38. UCC Unified Communication Centre

Financial Intelligence Unit – India (FIU-IND) P a g e | 103