Every bank, NBFC and financial institution in India is legally barred from holding an account for anyone named on the United Nations Security Council’s terrorism sanctions lists. These lists name individuals and groups linked to ISIL (Da’esh), Al-Qaida and the Taliban, and the UN revises them regularly: adding names, correcting details, removing entries. Each time, the Ministry of External Affairs informs sectoral regulators, and they circulate the change to every regulated entity.
Most institutions meet this duty the same way. They screen a customer’s name against the lists when the account is opened. It feels logical. The customer is checked, the result is clean, the file is closed.
The difficulty is that the lists keep moving after the file is closed. Picture a customer who passes screening in 2023. In 2026, the UNSC adds a person with the same name, date of birth and nationality. Nobody re-screens the customer, and the account stays open. On paper, the institution followed its process. In law, it now maintains an account in a listed person’s name.
That is the flaw in the onboarding-only screening model. It checks a customer against the world as it was on one day, while the obligation applies to the world as it is today.
What the Law Actually Says
Section 51A of the Unlawful Activities (Prevention) Act, 1967, implemented through the UAPA Order of 2 February 2021 and paragraph 51 of RBI’s KYC framework, requires regulated entities to ensure they do not have any account in the name of individuals or entities on the UNSC lists. That applies for every regulator’s directions/guidelines. The wording is about having accounts, not about opening them. An obligation to hold no listed account cannot be met by a check that happens once.
The same logic applies to proliferation financing. Under Section 12A of the WMD Act, 2005, regulatory circulars direct regulated entities to verify the UNSCR 1718 (and any other such resolution) list daily and to act on designations without delay.
The List Moves Faster Than Most Programmes Assume
RBI circulates UNSC list changes under Section 51A as a steady stream, not a quarterly event. Recent examples:
- 19 June 2025: one entry added.
- 14 November 2025: two entries delisted.
- 2 March 2026: one entry delisted.
- 27 March 2026: two individuals added.
- 1 April 2026: one individual added.
- 22 May 2026: seven entries removed.
- 9 July 2026: one entry amended.
Also, SEBI issues its own parallel circulars. On 20 August 2026 it communicated amendments to 21 entries on the ISIL (Da’esh) and Al-Qaida list. The list changed repeatedly within a single year, and each change is a fresh obligation. A programme that screens once, at onboarding, has not screened against any of these updates.
Five Ways Onboarding-Only Screening Fails
- New listings catch existing customers. A customer who was clean at onboarding can be designated later. Only re-screening the existing base finds them.
- Amendments create matches that did not exist before. Many circulars amend existing entries by adding aliases, dates of birth, nationalities or identifiers. An amendment can turn a previously unresolvable near-match into a confirmed one. A customer you correctly cleared last year may match this year’s improved entry.
- Delistings need action too. When an entry is removed, the circular directs institutions to update their records and screening data. Without a re-screening workflow, delistings get missed and customers stay wrongly restricted.
- Customer data changes after onboarding. Names are corrected, spellings standardised, dates of birth added to records that lacked them. Each change can alter the result of a screening check, but only if the check is run again.
- Near Matches. Names can be deliberately altered in marginal ways such as an alphabet missing, use of cyrillic characters etc., in order to obscure the criminal’s identity. A match score is probably useful where certain critical data fields such as date of birth, passport number, complete address with country and pin code included are used for matching sanctioned names. Depending on the percentage of match and an acceptable tolerance threshold, a complete investigation must be carried out for such cases and elimination must be recorded, double verified using a maker – checker mechanism
Why Teams Still Rely on Onboarding Screening
The reasons are practical, not careless. Re-screening millions of records for a one-entry update feels disproportionate. Customers sit across core banking, lending, cards and wallets, often with different identifiers. Records created through co-lending partners or business correspondents may sit outside the main screening perimeter. And teams fear that more screening simply means more false positives.
All of these are real. None of them removes the obligation. They are reasons to design the process better.
What an Effective Re-Screening Process Looks Like
Screen the change first. When a list update lands, extract only the added or amended entries (the delta) and screen them against the full customer base. A one-entry update becomes a small, fast job instead of a full-database run. This answers the volume objection directly, and it means same-day screening is realistic even for large institutions.A full database run is however the most ideal solution, using high-tec solutions to speed up matches
Then run full re-screens on a schedule. Delta screening catches list changes. It does not catch customer-data changes, such as a corrected spelling or a newly captured date of birth. A periodic full re-screen, plus a fresh check whenever a customer’s name or identifiers are updated, closes that gap. How often depends on your size and risk, but it should be a documented decision, not a default.
Do not let the vendor’s pace set yours. If you buy a consolidated sanctions feed, remember that the regulatory clock starts when the circular is issued, not when your provider refreshes. Know your vendor’s lag, and have a way to load a critical update yourself.
Make each list update an event with an owner. The workflow runs from circular received, to list loaded, to delta screened, to alerts reviewed, to action taken. Every stage needs a named owner and a timestamp, including weekends and holidays, because circulars do not wait for working days.
Use secondary identifiers to cut noise. Date of birth, nationality, address and ID numbers resolve most name-only matches quickly. The more of these your records hold, the lighter the review burden per update.
What Belongs in the Screening Scope
A re-screening programme is only as good as the population it covers. Four groups are routinely under-covered:
- Dormant and inoperative accounts. They are still accounts you maintain, so they belong in every run.
- Related parties of corporate customers. Directors, authorised signatories and beneficial owners can be listed even when the company is not. Screening only the account holder misses them.
- Partner-originated customers. Records sitting with co-lending partners, agents or business correspondents need to come inside the perimeter, or be covered by an explicit arrangement.
- Records with missing data. Customers with no date of birth or only a partial name are the hardest to clear and the easiest to ignore. Track how many you have. That number is a risk in itself.
When Re-Screening Produces a Hit
A re-screening run will generate alerts, and they fall into three groups. Most will be clear false positives: a common name, a mismatched date of birth or nationality. A smaller set will be potential matches that need more information to resolve. A very few may be confirmed matches. Create a triage pipeline for them with timelines to clear.
For a confirmed match, the UAPA Order sets out the procedure: restrict activity on the account, inform the designated nodal officer, file a suspicious transaction report with FIU-IND, and keep full records of what was done and when. Teams that have never worked a real hit tend to lose precious hours working out who decides what. A short, rehearsed playbook, with named decision-makers and contact details for the nodal officers, removes that hesitation.
Potential matches need the same discipline in a gentler form: a defined way to request more information, a deadline for resolving the alert, and a recorded reason for the final decision.
The Evidence Behind Every Run
Each re-screening run should leave a record that answers three questions an inspector will ask. When did the circular arrive? When was the list loaded and the base screened? What were the results, and who resolved each alert?
The gap between the first two answers is the most closely examined number in the process. The obligation is to act without delay, and an internal standard such as same-day screening shows that the timing is managed, not accidental.
From a One-Time Check to a Standing Control
Seen this way, sanctions screening stops being something that happens to a customer once and becomes something the institution does continuously. The customer base is a moving population, the lists are a moving target, and the obligation sits where the two meet.
The practical shift is small. Treat every UNSC circular or a MHA update as a trigger, screen what changed against everyone you hold, resolve what comes back, and keep the proof. Institutions that do this find the work lighter than expected, because the delta is usually tiny and the process, once built, runs the same way every time.
The institutions that struggle are the ones that learn about a listed customer from someone else. The first is a routine day in the compliance calendar. The second is an inspection finding.
Most importantly, make this rigour the culture!