Home › Circulars › RBI/2009-10/313

UNSCR 1267/1822 Terrorist List Update for UCBs

Current · Source: Reserve Bank of India · RBI/2009-10/313 · issued 10 Feb 2010 · ~2 min read
Quick answerRBI issued a corrigendum to UCBs correcting an Arabic script error in the UNSCR 1267/1822 terrorist list entry for Al-Qaida in the Arabian Peninsula (AQAP). Banks must update their records and ensure compliance with the corrected list.
Sanctions-list safety note. This circular refers to a specific UN Security Council / UAPA designated-entities list update as it stood on the date above — sanctions lists change often, and a newer update almost certainly exists today. Never use this page, or any single dated circular, as your current screening list. Always screen against the live, current list at the official UAPA proscribed-organisations list and the UN Consolidated List, and confirm the obligations for your bank on the official rbi.org.in source below.
The rule, in the simplest words
How it plays out — a real example

A co-operative bank branch officer in Indore, Mr. Kumar, was reviewing a customer's transaction history when he noticed a match with the corrected AQAP entry. He immediately reported the match to the Financial Intelligence Unit (FIU-IND) and updated the customer's records to ensure compliance with UN sanctions.

What changed

RBI forwarded a corrigendum from the Government of India (Ministry of External Affairs) regarding a technical error in the Arabic script of one name in the UN Security Council's 1267 Committee list. The error was in the entry for Al-Qaida in the Arabian Peninsula (AQAP) (QE.A.129.10) from the note dated January 19, 2010. This circular updates the previous circular UBD (PCB) CO.BPD. Cir.No. 43 /14.01.062/2009-10 dated February 9, 2010.

What it means for you

UCBs must immediately incorporate the corrected Arabic script into their screening systems to avoid misidentification or non-compliance with UN sanctions. Failure to update records could lead to regulatory action for not adhering to anti-terrorist financing measures. This is a routine but critical update to ensure accuracy in sanctions screening.

What you must do

Who it affects

All Primary (Urban) Co-operative Banks (UCBs), Compliance and AML/KYC teams at UCBs, Branches handling international transactions or remittances

❓ Common questions

What is the significance of the Arabic script correction?

The correction fixes a technical error in the Arabic script of the name for Al-Qaida in the Arabian Peninsula (AQAP) in the UN sanctions list. Accurate script is essential for proper name matching in screening systems to avoid false positives or missed hits.

Do we need to re-screen all existing customers?

Yes, you should re-screen existing customers and transactions against the corrected list to ensure no matches were missed due to the earlier error. This is a standard precaution for sanctions compliance.

What happens if we don't update our records?

Non-compliance with UNSCR 1267 and 1822 can lead to regulatory penalties, including fines or restrictions on operations. It also increases the risk of facilitating terrorist financing.

📜 Read the original circular — full text as issued by RBI
RBI/2009-10/313 UBD (PCB) CO.BPD. Cir. No. 44 /14.01.062/2009-10 February 10, 2010 The Chief Executive Officers of All Primary (Urban) Co-operative Banks Dear Sir / Madam, List of Terrorist individuals / organizations – under UNSCR 1267 (1999) and 1822(2008) on Taliban / Al-Qaida organisation Please refer to our circular UBD (PCB) CO.BPD. Cir.No. 43 /14.01.062/2009-10 dated February 9, 2010. 2. Please find enclosed a copy of the corrigendum received from Government of India (Ministry of External Affairs) as forwarded by the Chairman of UN Security Council's 1267 Committee regarding a technical error in the Arabic script of one of names referred to in the note dated January 19, 2010 {Al-Qaida in the Arabian Peninsula (AQAP) (QE.A.129.10)} for information and necessary action. Yours faithfully (Monisha Chakraborty) Deputy General Manager Encl: As above.
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2009-10/313 · issued 10 Feb 2010. The plain-English explanation above is BankPulse’s own independent summary.
🧰 Tools — save, print, templates & related
Most relevant forCompliance TeamKYC / AML AnalystBranch Manager — PSU / Co-op / RRB (sanctioning powers)Branch Operations (Accounts / FD / CASA)Teller / Cashier / Customer Service OfficerNRI Relationship Manager
🛠 Banker’s toolkit — checklists & reply templates →
Related circulars · Department of Regulation
SFB Pillar 3 Disclosure Norms Aligned with BaselUCB Deposit Rate Disclosure & Uniformity Rules UpdatedLAB Deposit Rate Disclosure & Uniformity Rules TightenedPayments Banks: Interest Rates Must Match Disclosed ScheduleRBI Updates Bulk Deposit Rate Rules and Disclosure Timing
Browse all departments →
Worked example & action-note template

Example: if you are a Compliance officer at a bank this circular applies to (All Primary (Urban) Co-operative Banks (UCBs), Compliance and AML/KYC teams at UCBs, Branches handling international transactions or remittances), your first concrete step on “UNSCR 1267/1822 Terrorist List Update for UCBs” is: “Update your internal terrorist list database with the corrected Arabic script for the AQAP entry.” (RBI issued this 10 Feb 2010).

  1. Circular: RBI/2009-10/313 -- UNSCR 1267/1822 Terrorist List Update for UCBs
  2. Issued: 10 Feb 2010
  3. Action required: Update your internal terrorist list database with the corrected Arabic script for the AQAP entry.
  4. Action required: Re-screen existing customers and transactions against the corrected list to identify any matches.
  5. Action required: Ensure compliance with UNSCR 1267 and 1822 requirements by reporting any matches to the Financial Intelligence Unit (FIU-IND).
  6. Action required: Acknowledge receipt of this circular and confirm action taken to the concerned RBI regional office.
  7. Owner: ____________ Target date: ____________
  8. Board/committee approval needed? Y / N
  9. 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.

Loading comments…
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=5499&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.
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 ↗
—