Chapter 8: Analysis of PMLA Enforcement: Key Case Studies in Securities Markets (Part 1)

Analysis of PMLA Enforcement: Key Case Studies in Securities Markets (Part 1)

This chapter provides an in-depth examination of the practical application of the Prevention of Money Laundering Act (PMLA) through specific legal cases and adjudicating orders. These cases highlight the critical nature of compliance for "reporting entities" and the consequences of failing to implement robust Anti-Money Laundering (AML) and Combating the Financing of Terrorism (CFT) safeguards. By reviewing these precedents, professionals can better understand how regulatory bodies like SEBI and FIU-IND interpret and enforce PMLA obligations in the securities market.

8.1 Case Study: FIU-IND vs. Way2Wealth Brokers Private Limited

Summary of the Adjudicating Order

The Financial Intelligence Unit-India (FIU-IND) issued Order-in-Original No. 29/DIR/FIU-IND/2022 on November 10, 2022. This case underscores FIU-IND's role in identifying weaknesses in the safeguards of reporting entities to prevent malicious actors from exploiting capital flows in the securities market.

Primary Facts of the Case

The investigation began after a reference from SEBI pointed to alleged non-compliance with PMLA guidelines by Way2Wealth Brokers Private Limited. The case analyzed whether the entity met its obligations under Chapter IV of the PMLA. Key breaches identified included:

  • Transaction Monitoring Failure: The reporting entity failed to properly raise, investigate, and handle alerts related to transactions in December 2021.
  • Failure to File STRs: There was a significant failure to file Suspicious Transaction Reports (STRs) with FIU-IND based on these alerts.
  • Lack of Regulatory Oversight: The entity did not consider adverse SEBI orders when monitoring transactions from an AML perspective.

Findings and Final Order

FIU-IND observed critical deficiencies in the entity's internal mechanism. The following actions were taken:

  1. Monetary Penalty: A fine of Rs. 1 Lac was imposed under section 13(2)(d) of the PMLA.
  2. Compliance Directions: Detailed directions were issued under sections 13(2)(a) and 13(2)(b) to rectify procedural gaps.
  3. Certification Requirement: The entity was required to submit a certification signed by its Designated Director and Principal Officer within 30 days, confirming the implementation of the directed measures.

8.2 Case Study: SEBI vs. SKSE Securities Limited

Background and Allegations

SEBI inspected SKSE Securities Limited to evaluate its AML mechanism and overall compliance. The inspection revealed several systemic failures:

  • Absence of AML Mechanism: The Noticee had fundamentally failed to implement an AML framework as required by law.
  • Lack of Client Categorization: Clients were not categorized into high, medium, and low-risk segments.
  • Due Diligence Failures: Because categorization was absent, the entity could not exercise the mandatory additional due diligence for higher-risk clients.
  • Principal Officer (PO) Delays: The entity failed to appoint a Principal Officer in a timely manner and delayed notifying FIU-IND of the appointment.

Regulatory Findings

SEBI's guidelines (Circular dated January 18, 2006) required all intermediaries to establish a policy framework within one month. SKSE Securities failed to implement this until 2010, nearly four years late. Furthermore:

  • The appointment of the Principal Officer was made on December 14, 2007, which was a delay of approximately two years from the circular's issuance.
  • The appointment was not communicated to the Director of FIU on an "urgent basis," with the notification occurring only in January 2008.

Final Adjudication

For these violations, SEBI imposed a penalty of Rs. 2,00,000 under section 15HB of the SEBI Act. This penalty was deemed commensurate with the failure to adhere to mandatory regulatory timelines.

8.3 Case Study: SEBI vs. Raima Equities Private Limited

Scope of Inspection

SEBI inspected Raima Equities Private Limited for the period of April 2011 to July 2012. The focus was on determining whether the broker adhered to AML and CFT provisions.

Identified Compliance Gaps

The inspection highlighted several alarming deficiencies in the broker's risk management:

  • Arbitrary Risk Classification: There was no logical basis for how clients were assigned to high, medium, or low-risk categories.
  • Limited Risk Scope: The entity's risk management was strictly confined to market risks (payment, delivery, margin) and ignored AML/CFT obligations.
  • Handling of STRs: The system lacked parameters to generate STRs. Alerts received from depositories were closed by the Principal Officer without any written justification.
  • PEP Identification: The entity had no system to identify Politically Exposed Persons (PEPs), erroneously relying on the fact that clients were "known" to directors or introducers.

Outcome of Adjudication

The Adjudicating Officer (AO) rejected the broker's defense, noting that simply knowing a client does not exempt an intermediary from formal PEP identification or risk documentation. Consequently, a monetary penalty of Rs. 2,00,000 was imposed under Section 15HB of the SEBI Act.

8.4 Case Study: SEBI vs. Marfatia Stock Broking Private Limited

Nature of the Allegations

SEBI inspected Marfatia Stock Broking to check if their AML policy was adopted within the 30-day window following the January 18, 2006 circular. The inspection also reviewed their adherence to the Code of Conduct under SEBI (Stock Broker) Regulations, 1992.

Investigative Findings

This case provides a different outcome compared to previous studies, focusing on procedural versus substantive compliance:

  • Policy Documentation: Marfatia admitted to documenting a separate AML policy only in 2009. However, they argued that PMLA requirements were already incorporated into their existing KYC and Risk Management System (RMS) policies. SEBI accepted that while a separate document was late, the core requirements were being followed through other documented processes.
  • Principal Officer Appointment: The inspection team initially thought there was a delay. However, Marfatia produced a letter dated February 13, 2006, and a courier slip proving they had appointed a PO and notified FIU within the correct timeline.

Final Order

The Adjudicating Officer found the observations to be merely procedural. Since no serious violations were found that adversely affected investor interests, SEBI decided not to impose a monetary penalty and disposed of the show-cause notice.

Key Takeaways for Professionals

  • Timely Appointments: The appointment of a Principal Officer and its communication to FIU-IND must be handled on an urgent basis.
  • Documented Rationales: Closing suspicious alerts without a written reason is a major compliance violation.
  • Holistic Risk Management: Intermediaries must expand their risk systems beyond market risks to include AML, CFT, and PEP identification.
  • Substance Over Form: While specific AML policy documents are required, having the necessary checks built into KYC and RMS policies may be considered during adjudication, though it is not a recommended substitute for a formal AML policy.

Important Terms to Remember

  • Reporting Entity: An entity (like a broker or bank) required to follow PMLA obligations.
  • STR (Suspicious Transaction Report): A report filed with FIU-IND when a transaction appears suspicious or lacks economic rationale.
  • Principal Officer (PO): The management-level official responsible for PMLA compliance within an organization.
  • Politically Exposed Person (PEP): Individuals who are or have been entrusted with prominent public functions, requiring enhanced due diligence.
  • Section 15HB (SEBI Act): The section under which SEBI often imposes penalties for procedural or regulatory defaults.

Practice with a Free Mock Test

Ready to test your NISM-Series-24: AML and CFT Provisions in Securities Markets Mock Tests preparation? Start with Test 1 — no payment required.

Notify me when you update the Notes

Free account · No payment needed for Test 1

Create a free PassNISM account

Continue with Google to start a free NISM mock test (Test 1) for this subject, save scores, and compare attempts.

Continue with Google