STR Filing in India: FIU-IND Reporting Requirements, Process and Penalties
FIU-IND & India AML

STR Filing in India: FIU-IND Reporting Requirements, Process and Penalties

STR filing in India is a core duty for every reporting entity under the Prevention of Money Laundering Act, 2002 (PMLA). Once a reporting entity concludes that a transaction is suspicious, its Principal Officer must report it. The report goes to the Financial Intelligence Unit-India (FIU-IND). The deadline is short, there is no minimum value and attempted transactions count too. So a weak STR process can quickly turn into a regulatory finding.

This guide explains what counts as a suspicious transaction and the filing timeline. It also shows how STR filing in India works in practice and covers tipping off, record keeping, penalties and common gaps in STR processes.

Key takeaways on STR filing in India

  • A reporting entity must file an STR promptly. The outer limit is seven working days after it concludes that a transaction is suspicious.
  • There is no minimum amount. The definition also covers attempted transactions.
  • The Principal Officer files STRs with FIU-IND. However, the Designated Director remains responsible for overall compliance.
  • Reporting entities must not tip off the customer about an STR.
  • FIU-IND can impose a fine of ₹10,000 to ₹1 lakh (INR one hundred thousand) for each failure, as well as other measures.

Who is responsible for STR filing in India?

Every reporting entity under the PMLA must report suspicious transactions. That includes banks, NBFCs, payment system operators, securities and insurance intermediaries and virtual digital asset (VDA) service providers. It also includes certain designated businesses (DNFBPs), as notified under the PMLA. For example, dealers in precious metals and stones can qualify in respect of cash transactions of ₹10 lakh (INR 1 million) or more. Real estate agents can also qualify where they fall within the relevant notification.

First, though, an entity needs to know whether it is a reporting entity at all. Our guide to FIU-IND registration explains who must register.

What counts as a suspicious transaction for STR filing in India?

The PML Rules define a suspicious transaction broadly. It includes an attempted transaction, whether or not made in cash. A transaction is suspicious if, to a person acting in good faith, it:

  • gives rise to a reasonable ground of suspicion that it may involve proceeds of a scheduled offence, whatever the value;
  • appears to involve unusual or unjustified complexity;
  • appears to have no economic rationale or bona fide purpose; or
  • gives rise to a reasonable ground of suspicion that it may involve terrorist financing.

Two points stand out. First, there is no monetary threshold. Second, the definition covers attempted transactions. For example, a customer may abandon a transaction once staff ask for identity documents. In that case, the reporting entity should still consider an STR. However, abandonment alone does not make a transaction suspicious. The entity must assess the surrounding circumstances against the definition.

The deadline for STR filing in India

Rule 8(2) of the PML (Maintenance of Records) Rules, 2005 requires reporting entities to report suspicious transactions promptly. In any case, they must report not later than seven working days after they become satisfied that a transaction is suspicious. FIU-IND’s reporting entity FAQs set out the same timeline.

The clock starts when the reporting entity concludes that the transaction is suspicious. It does not start on the transaction date or when the system generates an alert. The Rules do not set a separate deadline for internal investigations. However, that is no reason for slow reviews. Alert reviews should follow defined internal timelines, so that delays do not push back the point at which suspicion is formed.

How STR filing in India works: five stages

A sound process for STR filing in India usually moves through five stages.

1. Detect

Potentially suspicious activity may be identified through transaction monitoring alerts, frontline staff observations, screening results, unusual customer behaviour or information received from law enforcement authorities. None of these automatically warrants an STR, but each should be assessed appropriately. Reporting entities should establish documented internal escalation procedures enabling frontline staff, business units and monitoring teams to promptly refer potentially suspicious activity to the compliance function and Principal Officer. These procedures should also cover attempted transactions and suspicious activity identified outside automated monitoring systems.

2. Investigate

The compliance team reviews the alert or internal report, examining the customer’s profile, transaction history, expected activity, source of funds, purpose of transactions and any related parties or accounts. The assessment should consider whether the activity is consistent with the customer’s known profile and whether there are any unusual patterns, unexplained transactions or other suspicious indicators. The objective is to determine whether the circumstances meet any of the criteria for a suspicious transaction under the PML Rules.

3. Decide and document

The compliance function assesses the available information in accordance with the entity’s internal escalation and decision-making framework. The Principal Officer is responsible for ensuring that information relating to suspicious transactions is furnished to FIU-IND within the prescribed timeline. The grounds for suspicion and the basis for the reporting decision should be documented. As a recommended control, decisions not to file an STR should also be documented, including the rationale for concluding that the activity does not meet the reporting criteria. Examiners and auditors may review both reporting and non-reporting decisions.

4. File with FIU-IND

The Principal Officer submits the STR electronically through FIU-IND’s FINGate 2.0 portal, which forms part of the FINnet 2.0 reporting system. FINGate 2.0 went live on 22 March 2023, replacing the earlier reporting portal following a transition period that ended on 30 April 2023. The STR should contain relevant details of the customers, accounts, transactions, counterparties and other parties involved. It should also include a clear, factual narrative explaining the nature of the suspicious activity, the reasons for suspicion and the key findings of the investigation.

5. Follow up

After filing, the Principal Officer should retain a copy of the STR and the reporting entity should maintain the supporting investigation and decision records. The entity should also reassess the customer’s risk profile and consider whether enhanced monitoring, further due diligence or other risk-mitigation measures are necessary. Filing an STR does not, by itself, require the reporting entity to freeze, restrict or close the customer’s account. Any such action should be based on applicable legal or regulatory requirements and the entity’s risk assessment. Throughout the process, the reporting entity must maintain confidentiality and avoid tipping off the customer.

Writing a useful STR for FIU-IND

FIU-IND analyses STRs alongside other financial intelligence. A clear, factual and well-structured report helps explain the suspicious activity and the reasons for reporting it. In practice, an effective STR should include:

  • Clear transaction narrative: A concise, chronological account of what happened, highlighting unusual activity, transaction patterns and the grounds for suspicion.
  • Specific supporting details: Relevant dates, amounts, transaction references, counterparties, channels and movement of funds, rather than vague descriptions.
  • Customer profile assessment: An explanation of how the activity differs from the customer’s known profile, stated income, occupation or business activities, where relevant.
  • Relevant identifiers: Available details of the individuals, entities, accounts, counterparties and, for VDA-related transactions, wallet addresses and transaction hashes involved.
  • Objective assessment: Factual observations and the reasons for suspicion, without making unsupported allegations or conclusions about criminal activity. An STR reports suspicion, not proof of guilt.

Tipping off and confidentiality

Reporting entities, their directors, officers and employees must maintain the confidentiality of information furnished to FIU-IND and must not disclose the fact that an STR has been filed or that related information has been reported. Section 12(2) of the PMLA requires information maintained, furnished or verified by reporting entities to be kept confidential. Rule 8(6) of the PML Rules also addresses confidentiality regarding the furnishing of information to FIU-IND. FIU-IND’s guidelines for VDA service providers further reinforce the prohibition on tipping off.

In practice, this affects customer communication. For example, staff should not tell a customer that an STR has been filed or that a transaction is being reviewed because of a suspicious activity report. Reporting entities should establish clear confidentiality procedures and provide frontline staff with appropriate, neutral responses to customer enquiries.

Section 14 of the PMLA provides protection against civil or criminal proceedings for reporting entities, their directors and employees in respect of furnishing information under Section 12(1)(b), subject to the qualification contained in that section. This protection is not blanket immunity and does not prevent FIU-IND from taking regulatory action under Section 13 for failures to comply with PMLA obligations.

Record keeping for STR filing in India

Reporting entities must keep records of prescribed transactions, including suspicious transactions, for five years from the date of the transaction. Identity records must generally be kept for five years after the business relationship ends or the account closes, whichever is later. Under Rule 7(2), the Principal Officer must also keep a copy of the information furnished to FIU-IND. As good practice, firms should also keep the supporting investigation and decision records, whether or not they filed.

Penalties for STR filing failures in India

Under Section 13 of the PMLA, the Director of FIU-IND can impose a fine of not less than ₹10,000 and up to ₹1 lakh for each failure. The fine can apply to the reporting entity, its designated director or its employees. The Director can also issue written warnings and directions to comply. In addition, under Rule 8(4) of the PML Rules, each day of delay in reporting a transaction, or in correcting a misreported one, counts as a separate violation. So fines for systemic lapses can add up quickly.

Enforcement has followed. For instance, in 2015 FIU-IND fined State Bank of India ₹5 lakh (INR five hundred thousand) for five failures after a media sting operation. The order found that the bank had failed to detect and report attempted suspicious transactions at five branches. More recently, in March 2024, FIU-IND imposed a ₹5.49 crore (INR 54.9 million) penalty on Paytm Payments Bank for multiple PMLA compliance failures, not STR failures alone.

Common gaps in STR filing processes

Reporting entities should periodically assess their STR processes for common control weaknesses, including:

  • Inadequate documentation: No documented rationale for closing alerts or deciding not to file an STR.
  • Investigation delays: Backlogs in reviewing alerts and internal reports, potentially delaying the identification and reporting of suspicious activity.
  • Overlooked attempted transactions: Failure to identify and assess attempted transactions for potential STR reporting.
  • Weak STR narratives: Reports that merely reproduce transaction data without adequately explaining the suspicious activity and grounds for suspicion.
  • Inadequate staff guidance: Lack of clear procedures and training for frontline employees on confidentiality and avoiding tipping off.
  • Insufficient independent testing: STR reporting processes, including the quality of reports, investigation timelines and reporting timeliness, not being adequately covered by independent audits or compliance reviews, where applicable.

Our list of common AML audit findings covers related control gaps.

Frequently asked questions

What is the deadline for STR filing in India?

Under Rule 8(2) of the PML Rules, a reporting entity must file promptly. The outer limit is seven working days after it concludes that the transaction is suspicious.

Is there a minimum amount for filing an STR?

No. Reporting entities must report suspicious transactions whatever the value involved. The rules also cover attempted transactions.

Who files the STR with FIU-IND?

The Principal Officer files STRs with FIU-IND. Meanwhile, the Designated Director is responsible for ensuring the entity complies with its PMLA obligations overall.

Can we tell the customer that we filed an STR?

No. Reporting entities and their staff must not tip off the customer that an STR or related information has been, or will be, reported to FIU-IND.

How is an STR different from a CTR?

A cash transaction report (CTR) is threshold-based. Under Rule 3(1)(A) and (B) of the PML Rules, it covers cash transactions of more than ₹10 lakh (INR 1 million), or the equivalent in foreign currency. It also covers a series of cash transactions integrally connected to each other, each individually below ₹10 lakh, where the monthly aggregate exceeds ₹10 lakh. By contrast, an STR depends on suspicion and has no threshold. A transaction can need both a CTR and an STR, as FIU-IND’s FAQs confirm. Our guide for jewellers and the ₹10 lakh cash rule explains cash reporting in more detail.

Need support with STR compliance in India?

Establishing an effective STR reporting framework requires more than identifying suspicious transactions. Reporting entities must also ensure timely escalation, appropriate investigation, well-documented reporting decisions and accurate submissions to FIU-IND.

Compliance7 supports banks, NBFCs, fintechs and VDA service providers with AML/CFT compliance, including:

  • STR reporting framework design and review
  • AML/CFT policy and SOP development
  • Independent AML audits and compliance assessments
  • Transaction monitoring and alert investigation framework reviews
  • FIU-IND registration and regulatory compliance support

If your organisation needs assistance strengthening its STR reporting processes or assessing its AML/CFT controls, contact Compliance7 to discuss your requirements.

Related Compliance7 guides

This article is for informational purposes only and does not constitute legal or regulatory advice. Sector regulators may set additional requirements. For guidance specific to your business, consult a qualified compliance professional.

Ajith Abraham is a Financial Crime Compliance professional with 12+ years of experience in Anti-Money Laundering (AML), Counter-Terrorist Financing (CFT), KYC, Customer Due Diligence (CDD), Enhanced Due Diligence (EDD), Transaction Monitoring, Sanctions Screening and Financial Crime Investigations. He is a Certified Anti-Money Laundering Specialist (CAMS) and Merkle Science Certified Crypto Investigator (CCI). Ajith has worked with Big Four consulting firms and advises Financial Institutions, fintechs, DNFBPs and Virtual Asset Service Providers (VASPs) on AML/CFT compliance, risk assessments, regulatory audits, financial crime risk management, crypto compliance, blockchain investigations and FATF-aligned compliance frameworks through Compliance7 Consulting LLP.