No longer current — withdrawn, no replacement on file yet
Source: Reserve Bank of India · RBI/2010-11/175 · issued 23 Aug 2010 · ~1 min read
Quick answerRBI advises StCBs/DCCBs to consider FATF statement (June 25, 2010) regarding jurisdictions called upon to complete action plans. Banks must consider this info in their KYC/AML processes and have their Principal Officer acknowledge receipt.
What changed
FATF issued a statement on June 25, 2010 calling upon listed jurisdictions to complete action plan implementation. RBI now advises all banks and All India Financial Institutions to consider the information in that statement.
What it means for you
Cooperative banks should integrate FATF's updated information into their KYC/AML frameworks. The Principal Officer's acknowledgment is required to confirm receipt.
Historical instruction — do not use for current compliance. This is what was required at the time; it no longer reflects current RBI requirements. If no replacement rule is linked above, that only means none is recorded on our register yet — it does not prove no later applicable rule exists. Confirm on the official RBI source below.
What banks were required to do at the time
Review the enclosed FATF statement (June 25, 2010) for listed jurisdictions.
Consider the information in your bank's KYC/AML processes.
Ensure Principal Officer acknowledges receipt of this circular to RBI's Regional Office.
Who it affects
State Cooperative Banks (StCBs), Central Cooperative Banks (DCCBs), All India Financial Institutions, Principal Officers of cooperative banks
❓ Common questions
Regulatory timeline
Decoded by BankPulse2026-06-19 04:31 IST
repealed_by — Consolidation of Regulations — Withdrawal of circulars (28 Nov 2025)
Status change: withdrawn03 Aug 2026, 04:00 IST
Built from our lineage records — each fact carries its provenance; missing history simply is not shown (never guessed).
What is the FATF statement about?
FATF identified certain jurisdictions with strategic AML/CFT deficiencies and called upon them to complete implementation of their action plan within a timeframe.
Do we need to report back to RBI?
Yes, the Principal Officer of your bank must acknowledge receipt of this circular to the concerned RBI Regional Office.
What if we already have KYC/AML procedures?
You must still consider the FATF statement's information in your existing procedures.
📜 This document’s life story (1 recorded event, each backed by RBI’s own words)
Repealed byRBI/2025-26/100 — Consolidation of Regulations — Withdrawal of circulars (28 Nov 2025)
RBI’s words: “Official withdrawal register entry #1615: RPCD.CO.RF.AML.No.2308/07.02.12/2010-11 — "Know Your Customer (KYC) Norms / Anti-Money Laundering (AML) Standards / Combating of Financing of Terrorism (CFT)"”
📜 Read the original circular — full text as issued by RBI
RBI/2010-11/175
RPCD.CO.RF.AML.No.2308/07.02.12/2010-11
August 23, 2010
The Chairmen / CEOs of all State / Central Co-operative Banks
Dear Sir,
Know your Customer (KYC) Norms / Anti-Money Laundering (AML) Standards / Combating of Financing of Terrorism (CFT)
As part of its ongoing review of compliance with the AML/CFT standards, the Financial Action Task Force (FATF) has identified certain jurisdictions which have strategic AML/CFT deficiencies.
2. FATF, vide its statement dated June 25, 2010 ( copy enclosed ) has called upon jurisdictions listed in the statement to complete the implementation of their action plan within the timeframe. The FATF, in the statement has called upon its members to consider the information given in the statement.
3. All banks and All India Financial Institutions are accordingly advised to consider the information contained in the enclosed statement.
4. Please advise Principal Officer of your bank to acknowledge receipt of this circular letter to our concerned Regional Office.
Yours faithfully,
(B.P.Vijayendra)
Chief General Manager
Encl: As above
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2010-11/175 · issued 23 Aug 2010. The plain-English explanation above is BankPulse’s own independent summary.
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=5955&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.