PMLA Compliance: CTR, STR & Risk Monitoring for Co-op Banks
Current · Source: Reserve Bank of India · RBI/2007-2008/381 · issued 25 Jun 2008 · ~2 min read
Quick answerRBI mandates co-operative banks to electronically file CTR/STR to FIU-IND, maintain transaction records in hard and soft copies, and deploy software for transaction alerts based on customer risk profiles. CTR must be submitted by the 15th of the succeeding month, with integrally connected cash transactions where debit or credit summation exceeds ₹10 lakh in a calendar month reported (excluding transactions below ₹50,000).
The rule, in the simplest words
Banks must send a Cash Transaction Report (CTR) to the government's financial crime office (FIU-IND) by the 15th of the next month.
If a customer does many cash deals in one month that add up to more than ₹10 lakh (1 million rupees), the bank must report it, but deals under ₹50,000 (50 thousand rupees) can be skipped.
Banks need special computer software that gives a warning when a customer's cash activity doesn't match their risk level (like if a low-risk person suddenly does big cash deals).
If a bank finds fake or counterfeit money, it must tell FIU-IND right away using a special form called CCR.
Branches must send their cash transaction details to the bank's main compliance officer every month, not every two weeks.
How it plays out — a real example
Ravi, a co-operative bank branch officer in Indore, checks his branch's cash transactions for the month. He sees that a customer who usually takes small loans has deposited ₹9 lakh in cash across several visits. Ravi's software alerts him because this doesn't match the customer's low-risk profile, so he reports it as a suspicious transaction (STR) to FIU-IND immediately, following the rule to act when something seems off.
What changed
RBI clarified that cash transaction reporting by branches to the Principal Officer must be monthly, not fortnightly. For integrally connected cash transactions, banks must consider all individual cash transactions in an account during a calendar month where debit or credit summation exceeds ₹10 lakh, but need not report transactions below ₹50,000. Banks must also report forged/ counterfeit currency transactions to FIU-IND using the CCR format.
What it means for you
Banks must strengthen their transaction monitoring systems to detect suspicious patterns aligned with customer risk profiles. The monthly CTR deadline tightens reporting discipline, and the ₹10 lakh threshold for integrally connected transactions requires careful aggregation. Non-computerized branches must still feed data electronically via FIU-IND utilities, increasing operational burden but ensuring compliance.
What you must do
Ensure all branches submit cash transaction details to the Principal Officer on a monthly basis, not fortnightly.
Deploy or upgrade software to generate alerts for transactions inconsistent with customer risk categorization and updated profiles.
File CTR electronically with FIU-IND by the 15th of the succeeding month; for non-computerized branches, use FIU-IND's editable utilities. STRs should be filed immediately when suspicion arises.
Report all forged or counterfeit currency transactions to FIU-IND immediately using the CCR format (Annex II-III, with electronic data structure in Annex IV).
Review and aggregate integrally connected cash transactions per account monthly, reporting only those where debit or credit sum separately exceeds ₹10 lakh, excluding individual transactions below ₹50,000.
Who it affects
State and Central Co-operative Banks, Principal Officers of co-operative banks, Branch managers handling cash transactions, Compliance and AML teams
❓ Common questions
What is the new deadline for submitting Cash Transaction Reports (CTR)?
CTR must be submitted to FIU-IND for every month by the 15th of the succeeding month. Branches must report to the Principal Officer on a monthly basis, not fortnightly.
How should banks handle integrally connected cash transactions for CTR?
Banks should consider all individual cash transactions in an account during a calendar month where either total debits or total credits exceed ₹10 lakh. However, individual transactions below ₹50,000 need not be reported in the CTR.
What should banks do if they have non-computerized branches?
The Principal Officer must manually collect transaction details from non-computerized branches and feed the data into an electronic file using the editable utilities provided by FIU-IND on their website.
📜 Read the original circular — full text as issued by RBI
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2007-2008/381 · issued 25 Jun 2008. The plain-English explanation above is BankPulse’s own independent summary.
Ensure all branches submit cash transaction details to the Principal Officer on a monthly basis, not fortnightly.
File CTR electronically with FIU-IND by the 15th of the succeeding month; for non-computerized branches, use FIU-IND's editable utilities. STRs should be filed immediately when suspicion arises.
Report all forged or counterfeit currency transactions to FIU-IND immediately using the CCR format (Annex II-III, with electronic data structure in Annex IV).
💻 IT / Systems
Deploy or upgrade software to generate alerts for transactions inconsistent with customer risk categorization and updated profiles.
📜 Compliance
Review and aggregate integrally connected cash transactions per account monthly, reporting only those where debit or credit sum separately exceeds ₹10 lakh, excluding individual transactions below ₹50,000.
Grouped from the action items above — a single circular may involve more than one team.
Worked example & action-note template
Example: if you are a Branch Manager at a bank this circular applies to (State and Central Co-operative Banks, Principal Officers of co-operative banks, Branch managers handling cash transactions, Compliance and AML teams), your first concrete step on “PMLA Compliance: CTR, STR & Risk Monitoring for Co-op Banks” is: “Ensure all branches submit cash transaction details to the Principal Officer on a monthly basis, not fortnightly.” (RBI issued this 25 Jun 2008).
Action required: Ensure all branches submit cash transaction details to the Principal Officer on a monthly basis, not fortnightly.
Action required: Deploy or upgrade software to generate alerts for transactions inconsistent with customer risk categorization and updated profiles.
Action required: File CTR electronically with FIU-IND by the 15th of the succeeding month; for non-computerized branches, use FIU-IND's editable utilities. STRs should be filed immediately when suspicion arises.
Action required: Report all forged or counterfeit currency transactions to FIU-IND immediately using the CCR format (Annex II-III, with electronic data structure in Annex IV).
Action required: Review and aggregate integrally connected cash transactions per account monthly, reporting only those where debit or credit sum separately exceeds ₹10 lakh, excluding individual transactions below ₹50,000.
Owner: ____________ Target date: ____________
Board/committee approval needed? Y / N
Evidence filed in compliance register on: ____________
Built only from this circular’s own published fields — not legal advice; always confirm against the official RBI source.
💬 Banker Discussion
Discuss this circular with fellow bankers — reply, upvote what helps, report what doesn’t belong. Be professional; no client data. Views are the commenter’s own, not BankPulse’s.
BankPulse Compliance Evidence Pack — generated 05 Aug 2026 · status cross-checked against RBI’s official withdrawal register (refreshed weekly). Official RBI source: https://www.rbi.org.in/Scripts/NotificationUser.aspx?Id=4255&Mode=0 — Plain-English summary by BankPulse (bankpulse.ai), reviewed by our expert reviewer, CA Amit Jain. Independent platform, not affiliated with the Reserve Bank of India; is our own plain-English paraphrase, not RBI’s original wording.
Help us keep this accurate
Found an inaccuracy or have an improvement? Tell us. Every report is reviewed by our team before any change is made — nothing goes live unverified.
Public beta — plain-English informational summaries. Always verify against the official RBI source (circular number cited on every page) before making compliance, credit, treasury, audit, or operational decisions. · Join our WhatsApp channel ↗
BANKPULSE · FREE DAILY BRIEF
Get RBI updates for your role
Every important RBI update, decoded in plain English — for your career, exams & financial awareness.
We collect only your email, name and role, used solely to send your brief — never sold or shared. Withdraw anytime via the unsubscribe link in any email. Independent platform, not affiliated with the RBI. Information, not legal advice.
REPORT AN ERROR · BETA
Spotted an error? Earn 500 BankPulse Credits
Help us stay accurate. If your correction is verified true and approved by our founder, you earn 500 BankPulse Credits — redeemable when the platform monetises.
Reviewed by a human before any credit is awarded. We never change the site from crowd input without verification.
WANT A NEW FEATURE · BETA
What would make BankPulse more useful for you?
Tell us what to build next — a tool, a data view, a role page, anything. We read every suggestion.
Thank you — your ideas directly shape what we build.