UCBs: RBI Tightens AML/CFT Compliance on STRs and CCRs
Current · Source: Reserve Bank of India · RBI/2009-10/221 · issued 13 Nov 2009 · ~2 min read
Quick answerRBI has directed all Primary Urban Co-operative Banks to urgently file pending Suspicious Transaction Reports and Counterfeit Currency Reports with FIU-IND, citing non-compliance despite available tools. Banks must strengthen detection systems, adhere to KYC norms, and train staff to avoid penalties under the Banking Regulation Act.
The rule, in the simplest words
File all pending Suspicious Transaction Reports (STRs) and Counterfeit Currency Reports (CCRs) with FIU‑IND right away using the electronic tools the RBI has made available.
Install or improve anti‑money‑laundering (AML) software that automatically flags suspicious activity so the bank can send a report quickly.
Follow the RBI’s Know‑Your‑Customer (KYC) rules and include any “integrally connected cash transactions” (cash that is part of a larger transaction) in the Cash Transaction Reports (CTRs).
Keep a close eye on credit‑card payments, wire transfers (both domestic and overseas) and accounts of charitable organisations, and report any odd activity.
Train all staff who handle transactions on how to spot and file STRs and CCRs, and make sure every report sent to FIU‑IND is error‑free.
How it plays out — a real example
A gold‑loan officer in Indore notices a customer depositing a large amount of cash that looks suspicious. Using the new AML software, he flags the transaction, files a Counterfeit Currency Report (CCR) with FIU‑IND, and explains to the customer why the bank must report such activity, feeling proud to keep the bank compliant.
What changed
RBI issued a circular on November 13, 2009, reminding UCBs of their obligations under the Prevention of Money Laundering Act, 2002, following concerns from FIU-IND that many UCBs have not filed STRs and CCRs despite available utilities and training support. The circular lists six specific actions UCBs must take, including using AML software and monitoring credit card and wire transfer transactions.
What it means for you
UCBs face increased regulatory scrutiny and potential penalties for non-compliance with AML/CFT guidelines. Banks must prioritize filing error-free reports and training staff to detect suspicious transactions. This reinforces the need for robust internal controls to avoid contravention of the Banking Regulation Act.
What you must do
File all pending STRs and CCRs with FIU-IND immediately using available electronic utilities.
Implement or strengthen AML software to generate alerts for suspicious transactions.
Ensure strict adherence to KYC guidelines and include integrally connected cash transactions in CTRs.
Monitor transactions from credit cards, wire transfers, and charitable organizations for suspicious activity.
Conduct sensitization programs for operating staff on AML/CFT, focusing on STR and CCR filing.
Who it affects
Primary Urban Co-operative Banks (UCBs), Compliance officers and AML teams at UCBs, FIU-IND reporting staff
❓ Common questions
What reports must UCBs file with FIU-IND?
UCBs must file Cash Transaction Reports (CTR), Suspicious Transaction Reports (STR), and Counterfeit Currency Reports (CCR). Cash transactions involving forgery of valuable security or documents should also be reported.
What are the consequences of non-compliance?
Any contravention or non-compliance of guidelines under Section 35A of the Banking Regulation Act, 1949 and Prevention of Money Laundering Rules, 2005 will attract penalties.
What specific transactions need monitoring?
Banks must meticulously monitor credit card transactions, domestic and cross-border wire transfers, and accounts of charitable organizations for suspicious activity.
📜 Read the original circular — full text as issued by RBI
RBI/2009-10/221
UBD. CO. BPD. PCB.Cir. No. 20/ 12.05.001/2009-10
November 13, 2009
The Chief Executive Officers of
All Primary (Urban) Co-operative Banks
Madam/Dear Sir
Prevention of Money Laundering Act, 2002 – Obligation of banks in terms of Rules notified there under - Urban Co-operative Banks (UCBs)
Please refer to our circular UBD.CO. BPD. (PCB) No. 1/12.05.001/2008-09 dated July 02, 2008 on the captioned subject wherein banks have been advised to submit Counterfeit Currency Reports (CCR) along with Cash Transaction Reports (CTR) and Suspicious Transaction Reports (STR) to Financial Intelligence Unit - India (FIU-IND). UCBs wee also advised that the cash transactions where forgery of valuable security or documents has taken place may also be reported to FIU-IND.
2. It has been reported by FIU-IND that many UCBs are yet to file STRs and CCRs despite availability of utilities for preparing electronic CTRs/STRs/CCRs, user friendly website, extending faculty support for the training by FIU-IND, etc. In view of the concerns raised by FIU-IND, UCBs are advised to take prompt action on the following:
i) To strengthen the system for detection of suspicious transactions and reporting the same to FIU-IND. UCBs may also examine the possibility of installing AML software for alert generation on STRs,
ii) To strictly adhere to the KYC guidelines issued by Reserve Bank of India from time to time,
iii) To invariably include ‘integrally connected cash transactions’ as explained in Annex I of circular UBD.CO. BPD. (PCB) No. 1/12.05.001/2008-09 dated July 02, 2008 in CTRs,
iv)
To monitor transactions through credit cards, domestic as well as cross border wire transfer, accounts of charitable organisations etc. meticulously and to report suspicious transactions amongst them, if any,
v) To cover maximum number of operating staff in the sensitization programmes on AML/CFT issues, particularly on filing of STRs and CCRs, and
vi) To ensure that error free reports are submitted to FIU-IND.
3. UCBs are advised to note that any contravention / non-compliance of the guidelines issued under Section 35A of the Banking Regulation Act, 1949 (AACS) and Prevention of Money Laundering Rules, 2005 shall attract penalties.
Yours faithfully,
(S. S. Barik)
General Manager
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2009-10/221 · issued 13 Nov 2009. The plain-English explanation above is BankPulse’s own independent summary.
Implement or strengthen AML software to generate alerts for suspicious transactions.
📜 Compliance
File all pending STRs and CCRs with FIU-IND immediately using available electronic utilities.
Ensure strict adherence to KYC guidelines and include integrally connected cash transactions in CTRs.
Monitor transactions from credit cards, wire transfers, and charitable organizations for suspicious activity.
Conduct sensitization programs for operating staff on AML/CFT, focusing on STR and CCR filing.
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 Compliance officer at a bank this circular applies to (Primary Urban Co-operative Banks (UCBs), Compliance officers and AML teams at UCBs, FIU-IND reporting staff), your first concrete step on “UCBs: RBI Tightens AML/CFT Compliance on STRs and CCRs” is: “File all pending STRs and CCRs with FIU-IND immediately using available electronic utilities.” (RBI issued this 13 Nov 2009).
Circular: RBI/2009-10/221 -- UCBs: RBI Tightens AML/CFT Compliance on STRs and CCRs
Issued: 13 Nov 2009
Action required: File all pending STRs and CCRs with FIU-IND immediately using available electronic utilities.
Action required: Implement or strengthen AML software to generate alerts for suspicious transactions.
Action required: Ensure strict adherence to KYC guidelines and include integrally connected cash transactions in CTRs.
Action required: Monitor transactions from credit cards, wire transfers, and charitable organizations for suspicious activity.
Action required: Conduct sensitization programs for operating staff on AML/CFT, focusing on STR and CCR filing.
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 03 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=5369&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.