KYC/AML/CFT: Risk Categorization & Profile Updation for UCBs
No longer current — withdrawn, no replacement on file yet
Source: Reserve Bank of India · RBI/2012-13/206 · issued 13 Sep 2012 · ~1 min read
Quick answerRBI mandates Primary Urban Co-operative Banks to complete risk categorization and customer profile updation for all existing customers by March 31, 2013, citing lax compliance that exposes banks to operational risk.
What changed
RBI reiterated that banks must complete risk categorization and customer profile updation for all existing customers in a time-bound manner, with a hard deadline of end-March 2013. This follows earlier circulars and the Monetary Policy Statement 2012-13, emphasizing that lax implementation leaves banks vulnerable to operational risk.
What it means for you
Primary Urban Co-operative Banks must urgently prioritize KYC/AML/CFT compliance to avoid regulatory action and mitigate operational risk. The deadline is non-negotiable, and banks need to allocate resources for systematic review and updating of customer data. Failure to comply could lead to supervisory scrutiny and reputational damage.
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
Complete risk categorization and customer profile updation for all existing customers by March 31, 2013.
Establish a system for periodic review of risk categorization and customer identification data.
Ensure monitoring and closure of alerts in accounts as part of KYC/AML/CFT measures.
Review and strengthen internal processes to comply with RBI guidelines in letter and spirit.
Who it affects
Primary (Urban) Co-operative Banks, Compliance and risk management teams, Branch operations staff handling customer onboarding and updates
❓ Common questions
Regulatory timeline
Decoded by BankPulse2026-06-18 18:03 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 deadline for completing risk categorization and profile updation?
The deadline is end-March 2013, as per the circular dated September 13, 2012.
Why is RBI emphasizing this now?
RBI observed laxities in implementing KYC/AML guidelines, which expose banks to operational risk. This circular aims to enforce timely compliance.
Does this apply to all customers or only new ones?
It applies to all existing customers; banks must complete the process for their entire customer base.
📜 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 #1229: UBD.BPD.(PCB).Cir.No.8/14.01.062/2012-13 — "Know Your Customer (KYC) / Anti-Money Laundering (AML) /Combating of Financing of Terrorism (CFT) - Risk Categoriz”
📜 Read the original circular — full text as issued by RBI
RBI/2012-13/206
UBD.BPD (PCB) Cir. No. 8/14.01.062/2012-13
September 13, 2012
The Chief Executive Officer of
All Primary (Urban) Co-operative Banks
Madam/Dear Sir,
Know Your Customer (KYC)/Anti-Money Laundering (AML)/Combating of Financing of Terrorism (CFT) - Risk Categorization and Updation of Customer Profiles – Primary (Urban) Co-operative Banks
Please refer to our circular UBD.CO.BPD (PCB) No. 32/09.39.000/2007-08 dated February 25, 2008 on KYC/AML/CFT.
2. In order to have an effective implementation of KYC/AML/CFT measures, Primary (Urban) Co-operative Banks were advised to put in place a system of periodic review of risk categorization of customers and updation of customer identification data.
3. In this context, a reference is invited to paragraphs 98 and 99 ( extracts enclosed ) of the Monetary Policy Statement 2012-13 announced on April 17, 2012 on Implementation of KYC/AML Guidelines. Banks are aware that risk categorization of customers as also compilation and periodic updation of customer profiles and monitoring and closure of alerts in accounts by banks are extremely important for effective implementation of KYC/AML/CFT measures. It is, however, observed that there are laxities in effective implementation of the Reserve Bank’s guidelines in this area, leaving banks vulnerable to operational risk. Banks should, therefore, ensure compliance with the regulatory guidelines on KYC/AML/CFT both in letter and spirit.
4. Accordingly, Primary (Urban) Co-operative banks are advised to complete the process of risk categorization and compiling/updating profiles of all of their existing customers in a time-bound manner, and in any case not later than end-March 2013.
Yours faithfully,
(A. Udgata)
Chief General Manager-in-Charge
Encl: 1
Extract: Monetary Policy Statement 2012-13
Implementation of KYC/AML Guidelines
98. Risk categorisation of customers as also compilation, periodic updation of customer profiles and monitoring and closure of alerts in accounts by banks are very important for effective implementation of KYC, anti-money laundering (AML) and combating of financing of terrorism (CFT) measures apart from helping their business development. It is, however, observed that there are laxities in effective implementation of the Reserve Bank’s guidelines on KYC/AML measures. Any weakness in the KYC/AML process would leave banks vulnerable to operational risk. Banks should, therefore, ensure compliance with the regulatory guidelines on KYC/AML in both letter and spirit. Accordingly, it is proposed:
to mandate banks to complete the process of risk categorisation and compiling/updating profiles of all of their existing customers in a time-bound manner, and in any case not later than end-March 2013. 99. Detailed guidelines in this regard will be issued separately.
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2012-13/206 · issued 13 Sep 2012. 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=7563&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.