Complete Study Notes on PML (Maintenance of Records) Rules, 2005: Part 1 - Record Maintenance & Reporting Framework
The Prevention of Money-laundering (Maintenance of Records) Rules, 2005 (PMLR) establish the operational machinery required to enforce the broad mandates of the Prevention of Money-laundering Act, 2002 (PMLA). While the parent Act provides the statutory and legal framework, the Rules define the specific compliance procedures, thresholds, maintenance standards, and reporting timelines that financial institutions, banking companies, and intermediaries must observe.
This section covers the foundational aspects of the PMLR, 2005, focusing on transaction record-keeping (Rule 3), group-wide sharing (Rule 3A), information standards (Rules 4 and 5), and reporting protocols to the Financial Intelligence Unit-India (FIU-IND) (Rules 7 and 8).
1. Introduction and Constitutional Framework of PMLR, 2005
In the Indian legislative landscape, an Act is the statute passed by the legislature and approved by the President of India. Rules, conversely, are secondary legislation created under powers delegated by the Act. They define how the Act's provisions are to be implemented and performed, offering operational flexibility to adapt to changing environments without needing frequent statutory amendments.
Statutory Authority
The Central Government, exercising powers conferred under Section 73 of the Prevention of Money-Laundering Act, 2002 (15 of 2003) and in direct consultation with the Reserve Bank of India (RBI), enacted the PMLR, 2005.
The 2023 Amendment
The compliance landscape underwent significant tightening via a Gazette Notification dated 7th March, 2023, which introduced the Prevention of Money-laundering (Maintenance of Records) Amendment Rules, 2023. This amendment updated the core compliance requirements to meet evolving global anti-money laundering (AML) and counter-terrorist financing (CFT) standards.
Core Compliance Obligations Under PMLR
The primary objective of these rules, administered by regulators like the International Financial Services Centres Authority (IFSCA), SEBI, and RBI, is to build a secure financial system by mandating four pillars of compliance:
| Pillar | Core Requirement | Purpose |
|---|---|---|
| 🏢 1. Internal Controls | Establish effective policies, systems, controls, and procedures to prevent and detect financial crime. | Create a strong internal framework for AML compliance. |
| 👤 2. Customer Due Diligence (CDD) | Implement robust processes to identify and verify customers and beneficial owners. | Know who the customer is and assess associated risks. |
| 🚨 3. Reporting Suspicious Activities | Promptly identify and report suspicious transactions or activities to the relevant authorities. | Help authorities detect and investigate potential financial crime. |
| 🗂️ 4. Identity Records | Maintain required customer identification and transaction records for the period prescribed by the regulator. | Ensure information is available for monitoring, investigation, and regulatory review. |
- Develop Internal Controls: Formulating and maintaining robust internal policies, procedures, systems, and controls to prevent financial crime.
- Conduct Customer Due Diligence (CDD): Undertaking rigorous verification processes prior to onboarding customers or executing transactions.
- Report Suspicious Activity: Detecting and reporting suspicious financial transactions and other specified activities to the authorities.
- Maintain Client Identity Records: Safeguarding the verification and transaction history of all clients in the manner specified by the respective sectoral regulator.
2. Rule 3: Statutory Classification & Value Thresholds of Transactions
Rule 3 of the PMLR, 2005 details the specific categories of transactions for which reporting entities are legally obligated to maintain exhaustive records and furnish reports to the Director, FIU-IND.
Note on IFSC Jurisdiction: Under the rules, no physical cash transactions are permitted within the International Financial Services Centre (IFSC) ecosystem; all monetary transactions must flow electronically through banking units. However, reporting entities in the IFSC must remain fully aware of these threshold rules as part of their broader compliance framework.
The table below outlines the transactions under Rule 3, their respective threshold limits, and key reporting criteria:
Table: Threshold Limits and Statutory Triggers Under Rule 3
| Rule Clause | Transaction Category | Value Threshold / Trigger Criteria | Primary Regulatory Objective |
|---|---|---|---|
| Rule 3(1)(A) | Cash Transactions | Single cash transaction exceeding Rs. 10 lakh or its equivalent in foreign currency. | To track large physical cash flows into the system. |
| Rule 3(1)(B) | Integrally Connected Cash Transactions | A series of cash transactions individually under Rs. 10 lakh but integrally connected, occurring within one calendar month, where the monthly aggregate exceeds Rs. 10 lakh. | To prevent "structuring" or "smurfing" (breaking down large cash into smaller deposits). |
| Rule 3(1)(BA) | Receipts by Non-Profit Organisations (NPOs) | Any transaction involving receipts by NPOs valued at more than Rs. 10 lakh or its equivalent in foreign currency. | To mitigate the risk of charitable entities being abused as conduits for terrorist financing. |
| Rule 3(1)(C) | Counterfeit or Forged Currency Transactions | All cash transactions where forged or counterfeit currency notes/banknotes are used, or where forgery of valuable securities/documents occurs to facilitate the transaction. | No threshold applies; any instance of fake currency or document fraud triggers immediate reporting. |
| Rule 3(1)(D) | Suspicious Transactions | All suspicious transactions (including attempted ones), whether conducted in cash or otherwise, regardless of value. | Triggers on suspicion of proceeds of crime, unusual complexity, lack of economic rationale, or terror financing. |
| Rule 3(1)(E) | Cross-Border Wire Transfers | All cross-border wire transfers exceeding Rs. 5 lakh or its equivalent in foreign currency, where either the origin or destination of funds is in India. | To monitor international funds transfer corridors for potential illicit flows. |
| Rule 3(1)(F) | Immovable Property Transactions | All purchases and sales of immovable property valued at Rs. 50 lakh or more that are registered by/with the reporting entity. | To combat money laundering integrated into the real estate sector. |
3. Specific Suspicious Transaction Categories Under Rule 3(1)(D)
Suspicious transactions represent the highest risk category of financial activity. Rule 3(1)(D) provides an exhaustive breakdown of the transaction modes and account types that reporting entities must closely monitor for suspicious patterns.
A. Account-Based Deposits and Credits
This includes deposits, credits, or withdrawals into or from any account (maintained in any currency and under any nomenclature) by way of:
- Cheques (including third-party cheques), pay orders, demand drafts, cashier's cheques, or any other physical payment instrument.
- Electronic receipts, credits, electronic payments, and debits.
- Travelers' cheques.
- Internal account transfers within the same banking company, financial institution, or intermediary (including movements to and from Nostro and Vostro accounts).
B. Non-Monetary Accounts
Monitoring must extend beyond standard deposit accounts to include credits or debits in non-monetary holdings, such as:
- Dematerialised (d-mat) accounts.
- Security accounts maintained in any currency with an intermediary.
C. Remittances and Money Transfers
All money transfers or remittances executed in favour of a reporting entity's own clients, or non-client walk-in customers, whether originating from or destined to locations within India or abroad.
D. Investment and Credit-Support Instruments
Any creation, transfer, or execution of credit or liability through:
- Subscription to Debt Instruments: Commercial papers, certificates of deposit (CDs), preferential shares, debentures, securitised participation, interbank participation, or any other investment in securities.
- Commercial Bills: The purchase and negotiation of bills, cheques, and other trade instruments.
- Derivative and Forex Contracts: Foreign exchange contracts, currency swaps, interest rate swaps, commodity derivatives, and other derivative instruments.
- Credit Support Documents: Letters of credit (LCs), standby letters of credit, bank guarantees, comfort letters, solvency certificates, or any other instrument used for financial settlement and credit support.
E. Collection Services
All collection services provided in any currency, including the collection of bills, cheques, or other payable financial instruments.
4. Rule 3A: Group-Wide Information Sharing & AML-CFT Programmes
With the growing complexity of international banking and financial groups, money launderers often exploit information silos between different branches or subsidiaries of the same parent institution. To prevent this, Rule 3A mandates group-wide coordination.
Mandatory Group-Wide Programmes
Every reporting entity that is part of a larger financial or business group must design and implement unified, group-wide AML-CFT programmes. These programmes are designed to handle money laundering and terrorist financing risks systematically across the entire group.
Information Sharing Mechanisms
Group-wide policies must explicitly permit and facilitate the sharing of customer information within the group. This sharing is restricted to:
- Information required for Client Due Diligence (CDD).
- Data and analysis required for money laundering and terrorist financing risk management.
Operational Safeguards
While information sharing is encouraged, it must be balanced with strict confidentiality protections. Group-wide programmes must establish adequate safeguards to ensure:
- Shared information is kept strictly confidential and used solely for compliance purposes.
- The sharing of risk analyses does not result in tipping-off the customer, which would alert them to potential regulatory scrutiny and compromise ongoing investigations.
5. Rules 4 & 5: Content, Procedure, and Manner of Maintaining Information
Reporting entities cannot simply archive raw transaction data; they must preserve records in a structured, searchable, and reconstructible format.
Information to be Maintained (Rule 4)
The records maintained by a reporting entity must contain the following core data points to enable the reconstruction of individual transactions:
| Data Point | What to Record | Examples / Details |
|---|---|---|
| 🔄 1. Nature of Transaction | Record the type and nature of the transaction. | Wire transfer, securities purchase, remittance, etc. |
| 💰 2. Amount & Currency | Record the transaction value and the exact currency code used. | Amount + currency such as INR, USD, EUR, etc. |
| 📅 3. Date of Transaction | Record the precise date on which the transaction was executed. | Exact transaction date. |
| 👥 4. Parties to the Transaction | Record details of all parties involved. | Names, addresses, identification details, and other relevant identifiers. |
Manner of Maintenance (Rule 5)
Rule 5 shifts the operational responsibility onto the reporting entity and its staff to build robust internal storage mechanisms:
- Regulator-Specified Form: Entities must maintain transaction records in accordance with the specific procedure and manner defined by their primary regulator (e.g., IFSCA for entities in GIFT City, SEBI for securities market intermediaries).
- Evolving Internal Mechanisms: Reporting entities must design internal electronic and physical archival systems capable of retrieving this data at prescribed intervals.
- Strict Statutory Duty: It is the explicit, non-delegable duty of every reporting entity, its Designated Director, compliance officers, and employees to observe the record maintenance protocols prescribed by the regulator.
6. Rules 7 & 8: Furnishing of Information to the Director (FIU-IND)
Under the PMLA framework, reporting entities must actively report specified transaction categories to the central agency, Financial Intelligence Unit-India (FIU-IND).
Appointment of Key Officers (Rule 7)
Rule 7(1) requires every reporting entity to communicate the name, designation, and address of two critical compliance officers to the Director, FIU-IND:
- The Principal Officer: An officer at the management level who acts as the central reference point for detecting, processing, and submitting transaction reports to FIU-IND.
- The Designated Director: A person appointed to ensure overall compliance with the obligations under Chapter IV of the PMLA and Rules. This includes managing directors or partners depending on the entity's legal structure.
Role of the Principal Officer in Reporting
The Principal Officer is personally responsible for furnishing the transactions covered under Rule 3 (Clauses A, B, BA, C, D, E, and F) directly to the Director, FIU-IND. To maintain a clear audit trail, the Principal Officer must retain a copy of all submitted information as part of the entity's official records.
Table: Statutory Reporting Timelines to FIU-IND (Rule 8)
| Report Type | Rule Clause Reference | Reporting Frequency & Deadline | Submission Format |
|---|---|---|---|
| Cash & NPO Transactions | Rule 8(1) [referencing Rule 3(1)(A), (B), (BA), (C)] | Monthly: By the 15th day of the succeeding month. | Standard online format via the FINGate 2.0 Portal. |
| Cross-Border Wire Transfers | Rule 8(1) [referencing Rule 3(1)(E)] | Monthly: By the 15th day of the succeeding month. | Electronic standard format. |
| Suspicious Transactions (STR) | Rule 8(2) [referencing Rule 3(1)(D)] | Promptly: Not later than seven working days after the Principal Officer is satisfied that the transaction is suspicious. | Online in writing, by fax, or via secure electronic mail. |
| Immovable Property (IPR) | Rule 8(3) [referencing Rule 3(1)(F)] | Quarterly: By the 15th day of the month succeeding the quarter (e.g., April 15 for Q1). | Standard quarterly electronic format. |
Day-Wise Penalty for Non-Reporting
Timeliness is strictly enforced under Rule 8(4):
- Separate Violations: Each day of delay in reporting a transaction constitutes a separate violation.
- Correction Delays: Similarly, if an entity misreports a transaction, each day of delay in rectifying that error beyond the allowed time limit constitutes an independent, cumulative violation.
Confidentiality and the "Anti-Tipping Off" Provision
To protect the integrity of financial investigations:
- Strict Secrecy: Every reporting entity, its directors, officers, and employees must keep the maintenance of records and the fact of reporting to the Director completely confidential.
- Regulatory Exception: Under the proviso to Rule 8(6), this confidentiality clause does not prohibit the sharing of unusual transaction analyses among group entities under Rule 3A, provided it is done to manage group-wide ML/TF risks and does not tip off the client.
7. Key Terms and Definitions Reference
To ensure clarity for both exam preparation and professional practice, here are the essential definitions established under the PMLA and PMLR:
- Reporting Entity: A banking company, financial institution, intermediary, or a person carrying on a designated business or profession.
- Suspicious Transaction: A transaction (including an attempted one) that gives rise to reasonable grounds of suspicion that it may involve proceeds of crime, appears to have unusual or unjustified complexity, lacks economic rationale/bona fide purpose, or suggests involvement in terrorist financing.
- Principal Officer: A management-level officer designated by a reporting entity to ensure compliance under Section 12 of the PMLA and act as the central reporting link to FIU-IND.
- Designated Director: A person designated by the reporting entity (such as a Managing Director or Whole-time Director in a company) to ensure overall compliance with PMLA obligations.
- Nostro and Vostro Accounts: Interbank accounts held by one bank with another, typically across borders, which are subject to transaction monitoring under Rule 3(1)(D).
8. Exam-Focused Practice Questions
Question 1
Under the Prevention of Money-laundering (Maintenance of Records) Rules, 2005, a Suspicious Transaction Report (STR) must be submitted to the Director, FIU-IND within:
- A) 15 days of the succeeding month
- B) 7 working days of detecting the transaction
- C) 7 working days from the date the Principal Officer is satisfied that the transaction is suspicious
- D) 30 days from the end of the quarter
Answer: C Explanation: Rule 8(2) states that the Principal Officer must furnish suspicious transaction reports not later than seven working days on being satisfied that the transaction is suspicious.
Question 2
Under Rule 3A, a financial group is permitted to share client information internally for which of the following purposes?
- A) To market high-value investment products to the client
- B) For client due diligence (CDD) and managing money laundering/terror finance risks
- C) To inform the client about a pending Suspicious Transaction Report
- D) To bypass the registration requirements on the DARPAN portal
Answer: B Explanation: Rule 3A allows the sharing of information within a financial group specifically for the purposes of client due diligence (CDD) and managing money laundering and terror finance risks, provided adequate confidentiality safeguards are in place.
Question 3
What is the regulatory consequence if a reporting entity delays the rectification of a misreported transaction to FIU-IND?
- A) A flat penalty is levied at the end of the financial year.
- B) The regulator issues a single warning letter regardless of the delay.
- C) Each day of delay beyond the specified limit constitutes a separate violation.
- D) No penalty applies if the original misreporting was unintentional.
Answer: C Explanation: Under Rule 8(4), a delay of each day in rectifying a misreported transaction beyond the specified time limit constitutes a separate violation.