RRBs: PMLA Compliance – CTR, STR, and KYC Software Mandate
Current · Source: Reserve Bank of India · RBI/2007-2008/372 · issued 18 Jun 2008 · ~2 min read
Quick answerRBI mandates RRBs to file Cash Transaction Reports (CTR) and Suspicious Transaction Reports (STR) electronically to FIU-IND. Banks must use software to flag transactions inconsistent with customer risk profiles. CTR must be submitted monthly by the 15th, covering all cash transactions exceeding ₹10 lakh in a month, including integrally connected ones.
The rule, in the simplest words
Banks must file Cash Transaction Reports (CTR) every month by the 15th to FIU-IND.
If a customer's total cash deposits or withdrawals in a month cross ₹10 lakh, all those cash deals must be reported in CTR.
Small cash deals below ₹50,000 can be left out of the CTR report.
Banks need a computer system that automatically warns them when a customer's deals don't match their risk profile.
If fake currency notes are found, the bank must tell FIU-IND right away using a special form (CCR).
How it plays out — a real example
Rajesh, the Principal Officer of a rural bank, notices that a customer's monthly cash deposits total ₹12 lakh. He ensures the branch reports all cash transactions (except those under ₹50,000) in the CTR by the 15th. He also checks that the bank's software flags any unusual activity, like a sudden large withdrawal from a low-risk account.
What changed
RBI clarifies that 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. However, transactions below ₹50,000 need not be reported in CTR. Also, banks must now report counterfeit currency cases to FIU-IND using a specific format (CCR).
What it means for you
RRBs must tighten transaction monitoring by deploying software that alerts on mismatches with customer risk profiles. Non‑computerized branches must still feed data electronically for CTR/STR filing. The monthly CTR deadline (15th) is firm, and Principal Officers are responsible for compliance. Non‑compliance would be contrary to RBI guidance.
What you must do
Ensure all branches submit cash transaction data monthly (not fortnightly) to the Principal Officer.
Deploy or upgrade software to generate alerts for transactions inconsistent with customer risk profiles.
File CTR and STR electronically to FIU-IND by the 15th of each month; use FIU-IND's editable utilities for non-computerized branches.
Report counterfeit currency cases immediately to FIU-IND using the CCR format (Annex II/III).
Review customer risk categorization periodically and update profiles accordingly.
Who it affects
Regional Rural Banks (RRBs), Principal Officers of RRBs, Branch managers and compliance teams, IT/software vendors for RRBs
❓ Common questions
What is the threshold for reporting cash transactions in CTR?
All cash transactions in an account during a calendar month where either total debits or total credits exceed ₹10 lakh must be reported. Individual transactions below ₹50,000 can be excluded from the CTR.
What should we do if some branches are not computerized?
The Principal Officer must manually collect transaction details from non-computerized branches and feed them into an electronic file using FIU-IND's editable utilities for CTR/STR.
How should we report counterfeit currency?
Report immediately to FIU-IND using the Counterfeit Currency Report (CCR) format provided in Annex II and III of the circular. Include cases where forged notes or documents were used.
📜 Read the original circular — full text as issued by RBI
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2007-2008/372 · issued 18 Jun 2008. The plain-English explanation above is BankPulse’s own independent summary.
Ensure all branches submit cash transaction data monthly (not fortnightly) to the Principal Officer.
File CTR and STR electronically to FIU-IND by the 15th of each month; use FIU-IND's editable utilities for non-computerized branches.
Report counterfeit currency cases immediately to FIU-IND using the CCR format (Annex II/III).
💻 IT / Systems
Deploy or upgrade software to generate alerts for transactions inconsistent with customer risk profiles.
📜 Compliance
Review customer risk categorization periodically and update profiles accordingly.
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 (Regional Rural Banks (RRBs), Principal Officers of RRBs, Branch managers and compliance teams, IT/software vendors for RRBs), your first concrete step on “RRBs: PMLA Compliance – CTR, STR, and KYC Software Mandate” is: “Ensure all branches submit cash transaction data monthly (not fortnightly) to the Principal Officer.” (RBI issued this 18 Jun 2008).
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=4246&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.