N D Savla & Associates assists banks, NBFCs, and other regulated entities with Financial Intelligence Unit (FIU-IND) Registration and the ongoing anti-money laundering reporting obligations that come with it. FIU-IND is India's national agency for receiving, analysing, and disseminating financial intelligence on suspicious transactions, and every entity classified as a “reporting entity” under the PMLA has to register with it and file specific transaction reports on an ongoing basis, not just when something looks obviously wrong.
This page explains what FIU-IND registration involves, who must register, the different types of reports a reporting entity must file, and what happens when reporting obligations are missed. If your entity has been licensed by RBI, SEBI, or IRDAI and handles customer transactions, this compliance step needs to be in place before you start onboarding.
?? Note: FIU-IND reporting isn't triggered only by suspicious activity. Cash Transaction Reports have to be filed for transactions crossing the prescribed threshold as a routine matter, regardless of whether anything looks unusual about them — treating FIU-IND reporting as an exception-only process is a common compliance gap.
What Is FIU-IND and Why Does Registration Matter?
The Financial Intelligence Unit – India (FIU-IND) is the central national agency responsible for receiving, processing, analysing, and disseminating information relating to suspicious financial transactions, established under the Prevention of Money Laundering Act, 2002. It functions as the hub connecting financial sector reporting entities with law enforcement and regulatory bodies working on anti-money laundering and counter-terrorism financing.
Registration with FIU-IND is the mechanism through which a reporting entity gets access to the FINnet portal, the system used to file the various categories of reports the PMLA requires. Without registration, an entity has no legitimate channel to meet its statutory reporting obligations at all — which means FIU-IND registration typically has to happen very early in a newly licensed financial entity's compliance setup, alongside CKYCR registration and other foundational AML infrastructure.
Who Must Register with FIU-IND?
- Banking companies, including scheduled and cooperative banks handling customer deposits and transactions.
- NBFCs registered with RBI, particularly those engaged in lending, deposit-taking, or money transfer activities.
- Mutual funds, portfolio managers, and other securities market intermediaries regulated by SEBI.
- Insurance companies and insurance intermediaries handling premium payments and policy payouts.
- Payment system operators, money changers, and other entities specifically brought within the reporting entity definition under PMLA rules.
If your entity falls into any of these categories, FIU-IND registration is not optional — it's a statutory requirement that regulators expect to see in place from the point of licensing onward.
What Our FIU-IND Registration & Compliance Services Include
- Registration Assistance: preparing and filing the entity's FIU-IND registration and FINnet portal onboarding application.
- Principal Officer Designation: advising on appointment of the Principal Officer required under PMLA, who acts as the entity's point of accountability for AML compliance.
- Reporting Framework Setup: building the internal process for identifying, compiling, and filing Cash Transaction Reports (CTRs), Suspicious Transaction Reports (STRs), and Non-Profit Organisation Transaction Reports (NTRs) where applicable.
- Ongoing Filing Support: managing the periodic submission of required reports within the timelines prescribed under PMLA rules.
- Internal Policy Drafting: preparing the AML/KYC policy document and escalation procedures FIU-IND and sectoral regulators expect a reporting entity to maintain.
Our FIU-IND Registration Process
- Confirm the entity's classification as a reporting entity under PMLA and identify the applicable reporting categories for its business.
- Designate a Principal Officer and Compliance Officer as required, with clearly defined AML responsibilities.
- Prepare and submit the FIU-IND registration application, including entity and principal officer details, to obtain FINnet portal access.
- Set up internal transaction monitoring processes to flag reportable transactions as they occur, rather than retrospectively.
- Begin periodic filing of CTRs, STRs, and other applicable reports, with an internal review cycle to catch gaps before a regulator does.
Types of Reports Filed with FIU-IND
Cash Transaction Reports (CTR)
Reporting entities must file CTRs for all cash transactions of a value above the prescribed threshold, and for a series of integrally connected cash transactions that together cross that threshold within a month. This is a routine, threshold-based filing rather than a judgment call about suspicious activity.
Suspicious Transaction Reports (STR)
STRs are filed when a transaction, or a pattern of transactions, gives rise to reasonable grounds to believe it may involve proceeds of crime or is otherwise suspicious, regardless of the amount involved. These require a documented internal assessment process, since the standard is judgment-based rather than purely threshold-based.
Non-Profit Organisation Transaction Reports (NTR)
Reporting entities handling transactions of non-profit organisations must file NTRs for transactions crossing the prescribed threshold, reflecting the specific scrutiny applied to NPO fund flows under India's anti-money laundering framework.
Consequences of Non-Registration or Missed Reporting
Failure to register with FIU-IND, or failure to file required reports within prescribed timelines, is treated as a serious PMLA compliance failure. Regulators can impose monetary penalties on the reporting entity and, in cases involving repeated or wilful non-compliance, on the designated Principal Officer personally. Beyond direct penalties, a poor AML compliance record surfaces during regulatory inspections, licence renewals, and investor due diligence, making this one of the compliance areas worth getting right from the entity's very first transaction rather than retrofitting later.
Building an Internal AML Culture Beyond the Filing Mechanics
The entities that struggle most with FIU-IND compliance are usually the ones that treat it as a back-office filing task rather than a frontline responsibility. Transaction monitoring depends heavily on staff at the point of customer interaction recognising patterns worth escalating — structuring of deposits to stay under a threshold, inconsistent explanations for a transaction's purpose, or a customer relationship that doesn't match the volume moving through it. None of that gets caught by a compliance officer reviewing reports after the fact if frontline staff were never trained to notice it in the first place.
We typically pair FIU-IND registration work with staff training on red-flag indicators and a documented escalation pathway from frontline staff to the Principal Officer, since a well-designed reporting framework only functions as well as the people feeding information into it. This is often scoped alongside our broader NBFC Annual Compliance support, so AML monitoring sits inside the entity's regular compliance calendar rather than as a separate, easily forgotten workstream.
What a Regulatory Inspection Actually Looks For
When RBI, SEBI, or IRDAI inspects an entity's AML framework, the review rarely stops at confirming FIU-IND registration exists on paper. Inspectors typically sample actual transactions against the entity's monitoring logs, checking whether transactions that should have triggered a CTR or an STR were in fact identified and reported within the prescribed timeline. A registration certificate with a thin or inconsistent filing history behind it draws more scrutiny than a smaller number of well-documented, properly reasoned reports.
This is why we encourage clients to think of FIU-IND compliance as an evidentiary trail, not a box-ticking exercise — every escalation decision, including a decision not to file an STR after reviewing a flagged transaction, should be documented with the reasoning behind it, since regulators expect to see the judgment process, not just the final filings.
Frequently Asked Questions
Is FIU-IND registration mandatory for all NBFCs?
Yes. NBFCs are classified as reporting entities under the PMLA framework and must register with FIU-IND to obtain FINnet portal access, since this is the only channel through which their statutory transaction reporting obligations can be met.
What is a Principal Officer and why is the role required?
A Principal Officer is a senior official designated by the reporting entity to be accountable for AML compliance, including oversight of transaction monitoring and report filing. PMLA requires this designated role so there is clear individual accountability within the organisation.
What is the difference between a CTR and an STR?
A Cash Transaction Report is filed based on a monetary threshold being crossed, regardless of whether anything seems unusual, while a Suspicious Transaction Report is filed based on a judgment that a transaction may be linked to proceeds of crime, irrespective of the amount involved.
How quickly must reportable transactions be filed with FIU-IND?
Cash Transaction Reports and Suspicious Transaction Reports must be filed within the timelines prescribed under the PMLA rules and FIU-IND's reporting formats, which is why an internal monitoring process that flags transactions promptly matters more than the filing mechanics themselves.
Can a reporting entity be penalised for late FIU-IND filings even without any actual suspicious activity?
Yes. Late or missed Cash Transaction Report filings are a compliance failure in their own right, independent of whether any suspicious activity was actually involved, since CTR filing is a threshold-based statutory obligation rather than a discretionary judgment call.
Does frontline staff training matter for FIU-IND compliance?
Yes. Effective suspicious transaction detection depends on staff at the point of customer interaction recognising red flags early, since a compliance officer reviewing records after the fact cannot catch what frontline staff were never trained to notice during the transaction itself.