{"id":1777,"date":"2026-07-11T10:20:45","date_gmt":"2026-07-11T10:20:45","guid":{"rendered":"https:\/\/trackwizz.com\/knowledge-hub\/?p=1777"},"modified":"2026-08-11T10:22:30","modified_gmt":"2026-08-11T10:22:30","slug":"sanctions-screening-in-india-what-the-law-actually-requires-and-who-it-applies-to","status":"publish","type":"post","link":"https:\/\/trackwizz.com\/knowledge-hub\/sanctions-screening-in-india-what-the-law-actually-requires-and-who-it-applies-to\/","title":{"rendered":"Sanctions Screening in India: What the Law Actually Requires and Who It Applies To"},"content":{"rendered":"<p>Compliance officers in India\u2019s financial sector are familiar with the idea of screening customers against lists. What is less consistently understood is that not all screening obligations carry the same legal weight \u2013 and that confusing a risk-based due diligence requirement with an absolute statutory prohibition can quietly undermine how an institution designs, resources and governs its entire screening programme.<\/p>\n<p>Sanctions screening under Indian law is not a risk-based exercise. It is a binary, non-negotiable obligation. Understanding that distinction is the right place to start.<\/p>\n<h3><strong>Sanctions Screening Is Not PEP Screening and the Difference Is Legal, Not Operational<\/strong><\/h3>\n<p>It is worth separating sanctions screening from PEP and beneficial-ownership screening before going further, because the legal character of the obligation is fundamentally different.<\/p>\n<p>PEP and high-risk customer identification sit within a risk-based framework: the intensity of due diligence scales with assessed risk, and reasonable, documented judgment calls are the currency of a defensible programme.<\/p>\n<p>Sanctions screening against a designated persons list is not risk-based in the same sense \u2013 it is a binary, absolute prohibition. If a customer or transaction matches a person or entity designated under Section 51A of the Unlawful Activities (Prevention) Act, 1967, an Indian reporting entity does not get to weigh risk appetite. It must freeze the relevant funds, financial assets or economic resources without delay. Full stop.<\/p>\n<p>This distinction matters operationally: a PEP alert can sit in a review queue for a reasonable period while an analyst gathers context. A confirmed sanctions match cannot.<\/p>\n<h3><strong>The Indian Legal Foundation<\/strong><\/h3>\n<p>India\u2019s sanctions screening obligations draw from several instruments that together form a coherent, if layered, framework.<\/p>\n<p>The <strong>UAPA, 1967 \u2013 Section 51A<\/strong> empowers the Central Government to freeze, seize or attach funds and assets of individuals or entities designated under UNSC Resolutions \u2013 including 1267, 1373 and their successors \u2013 or under the UAPA\u2019s own Schedules. Reporting entities must ensure no account, policy or asset is held in a designated name.<\/p>\n<p>The <strong>UAPA Schedules I and IV<\/strong> maintain MHA\u2019s list of banned terrorist organisations and banned individuals under India\u2019s own domestic designation process \u2013 separate from UNSC lists and equally binding.<\/p>\n<p>The <strong>WMD Act, 2005<\/strong> extends targeted financial sanctions to persons and entities linked to proliferation of weapons of mass destruction and their delivery systems, per UNSC resolutions on proliferation financing.<\/p>\n<p>The <strong>PMLA, 2002 and PML Rules, 2005<\/strong> give domestic legal effect to UNSC Resolutions 1267 and 1373 on terrorism and terrorist financing, and underpin the freezing, seizure and attachment powers that reporting entities must operationalise.<\/p>\n<p>At the regulatory level, <strong>RBI\u2019s Master Direction on KYC<\/strong> requires reporting entities to ensure no account is held in the name of individuals or entities on UNSC lists circulated under Section 51A, and mandates the freeze-and-report procedure prescribed in the UAPA Order. <strong>SEBI and IRDAI<\/strong> have issued parallel circulars mirroring the same obligation for securities intermediaries, stock exchanges, depositories and insurers \u2013 with the same MHA-driven verification and freezing procedure.<\/p>\n<h3><strong>Two Lists That Are Non-Negotiable<\/strong><\/h3>\n<p>Two lists therefore carry unambiguous legal force for every Indian reporting entity: the United Nations Security Council\u2019s consolidated sanctions list as implemented through UAPA Section 51A, and the Ministry of Home Affairs\u2019 own domestic Schedules of banned organisations and individuals under the UAPA. Both are non-discretionary. Everything else \u2013 OFAC\u2019s Specially Designated Nationals list, the EU\u2019s Consolidated List of Financial Sanctions, the UK\u2019s Consolidated List, and other national sanctions regimes \u2013 sits outside India\u2019s direct statutory mandate.<\/p>\n<p><strong>UNSC lists<\/strong> \u2013 covering ISIL, Al-Qaida, the Taliban, and successive proliferation-related designations \u2013 are transmitted to India\u2019s Ministry of External Affairs, which forwards updates to nodal officers at RBI, SEBI, IRDAI and FIU-IND, who in turn push them to reporting entities. Screening against these lists is a direct statutory obligation, not a risk-based option.<\/p>\n<p><strong>MHA domestic Schedules<\/strong> \u2013 Schedule I listing banned unlawful associations, Schedule IV listing individuals designated as terrorists under India\u2019s own legal process, independent of any UN action \u2013 are equally mandatory for Indian reporting entities and communicated through the same MHA-regulator channel.<\/p>\n<h3><strong>The Judgment-Call Lists: OFAC, EU, UK and Others<\/strong><\/h3>\n<p>Beyond the two mandatory lists, many Indian reporting entities also screen against OFAC, the EU Consolidated List, Interpol, Europol and the UK list, amongst others. None of these carry direct statutory force for a purely domestic Indian entity with no foreign nexus, except perhaps for banks, some reporting entities with overseas exposure and non-residents.<\/p>\n<p>In practice, however, most Indian banks and larger NBFCs screen against OFAC lists for three converging reasons.<\/p>\n<p>US dollar clearing and correspondent banking relationships typically flow through US-linked institutions or the US financial system at some point, exposing an Indian bank to secondary sanctions risk if it deals with an OFAC-designated party. Many Indian reporting entities have US-facing business lines, US-person customers, or group entities with a US nexus that bring direct OFAC jurisdiction into play. And OFAC\u2019s extraterritorial enforcement reach makes voluntary OFAC screening a prudent risk mitigant even where no domestic legal duty exists.<\/p>\n<p>The EU\u2019s Consolidated List binds EU persons, EU-domiciled entities, and anyone transacting through EU financial infrastructure. An Indian reporting entity with a European branch, subsidiary, correspondent relationship, or a material book of EU-connected customers has a genuine compliance reason to screen against it. A purely domestic Indian NBFC with no European exposure generally does not.<\/p>\n<p><strong>The practical rule of thumb:<\/strong> UNSC and MHA lists are non-negotiable for every Indian reporting entity regardless of size or business model. OFAC, EU, UK and other national sanctions lists should be screened in proportion to the reporting entity\u2019s actual cross-border exposure \u2013 correspondent banking, foreign currency business, cross-border payments, foreign clientele, or group presence in the relevant jurisdiction.<\/p>\n<p>A purely domestic microfinance NBFC with no foreign exposure has a materially weaker case for OFAC and EU screening than a scheduled commercial bank running a treasury and trade finance<\/p>\n<p>No \u2013 and Indian regulation itself is built around this proportionality principle, even though the base legal obligation to screen against UNSC and MHA lists is identical for every reporting entity. The difference lies not in whether screening happens, but in its scale, sophistication and supporting infrastructure.<\/p>\n<p>A scheduled commercial bank screening a full customer base, correspondent banks, trade finance counterparties and cross-border wire beneficiaries operates a materially different programme to a small domestic securities broker whose universe is largely retail and whose transactions flow through nominated bank and demat accounts with limited cross-border exposure.<\/p>\n<p>The regulatory expectation, consistent with the risk-based approach embedded in RBI\u2019s KYC Master Direction and SEBI\u2019s AML and CFT Master Circular, is proportionality of control design \u2013 not proportionality of the underlying legal duty.<\/p>\n<p>A small broker cannot decide to screen only annually because its transaction volumes are low. But it can reasonably run a lighter-weight, less continuously staffed screening operation than a scheduled bank with correspondent banking and forex flows, provided its own risk assessment justifies that calibration and the core UNSC and MHA obligation is met without exception.<\/p>\n<p>What proportionality does not excuse, in either case, is the statutory freeze-without-delay obligation once a genuine match is confirmed.<\/p>\n<h3><strong>When a Match Occurs: The Procedure and Its Timelines<\/strong><\/h3>\n<p>India\u2019s UAPA Order prescribes a precise, time-bound sequence once a potential sanctions match arises. This is one of the more prescriptive procedural timelines in Indian financial regulation, and reporting entities should have it committed to institutional memory \u2013 not buried in a policy annexe.<\/p>\n<p><strong>Immediate identification and reporting.<\/strong> On identifying a name or transaction that appears to match a designated individual or entity on a UNSC or MHA list, the reporting entity must without delay verify against the customer\u2019s identification particulars and report the potential match to the relevant regulator and the MHA\u2019s IS-I Division nodal officer through the prescribed channel, within stipulated timelines.<\/p>\n<p><strong>MHA verification \u2013 within five working days.<\/strong> On receiving the particulars, the IS-I Division of MHA causes verification to be conducted by State Police and central agencies to confirm that the individual or entity identified is indeed the one listed and that the reported funds or assets are genuinely held by or for the benefit of that designated party. This must be completed within five working days of receipt.<\/p>\n<p><strong>Freeze order \u2013 within twenty-four hours of verification.<\/strong> If verification confirms the match, a freeze order is issued within twenty-four hours of that verification and conveyed electronically to the reporting entity \u2013 without prior notice to the designated individual or entity.<\/p>\n<p><strong>Segregation of frozen assets.<\/strong> Once frozen, funds should be placed in a separate blocked account and clearly distinguished from the reporting entity\u2019s own funds or unrestricted customer assets.<\/p>\n<p><strong>Handling inadvertent freezes.<\/strong> If a reporting entity freezes assets it believes were caught inadvertently, it must inform the affected party of their right to make a representation to the Central Government and forward full details to the MHA nodal officer \u2013 generally within two working days of the freeze.<\/p>\n<p><strong>Unfreezing on a wrongful-freeze application \u2013 within fifteen working days.<\/strong> On receiving evidence from a party claiming assets were frozen in error, the relevant authority conducts verification and, if satisfied, passes an unfreeze order within fifteen working days.<\/p>\n<p>Two points deserve emphasis for compliance officers designing internal escalation timelines. The five-day and twenty-four-hour clocks govern the MHA\u2019s own confirmatory and formal-order process \u2013 not a licence for the reporting entity to delay its own initial freeze pending government sign-off. And delisting requests must always be routed through the MHA or the UN Ombudsperson for UNSC lists \u2013 never resolved unilaterally by the reporting entity.<\/p>\n<h3><strong>After a Delisting<\/strong><\/h3>\n<p>Delisting does not end a reporting entity\u2019s interest in a name. Historical screening records must be retained for the institution\u2019s audit trail and for the statutory record-keeping period, since supervisors and auditors will test whether the reporting entity acted correctly at the time a name was live on the list \u2013 not only its current status.<\/p>\n<p>Good practice also calls for enhanced due diligence on recently delisted parties for a defined observation period. A delisting does not retroactively establish that the underlying conduct never occurred, and recently delisted individuals or entities can present continuing reputational and residual risk.<\/p>\n<p>Once RBI or the relevant regulator notifies reporting entities of an official UNSC or MHA delisting, any previously frozen account must be promptly unfrozen following the procedure in the UAPA Order \u2013 but the file, screening history and rationale should be retained, not purged.<\/p>\n<h3><strong>The Non-Negotiable at the Centre of It All<\/strong><\/h3>\n<p>For an Indian reporting entity, the sanctions screening question is really two questions wearing one hat.<\/p>\n<p>The first \u2013 UNSC lists and MHA\u2019s own domestic Schedules \u2013 is a fixed, non-discretionary legal obligation identical for every reporting entity regardless of size, with a precise, time-bound freeze-and-report procedure that leaves no room for risk-based calibration once a genuine match is confirmed.<\/p>\n<p>The second \u2013 OFAC, EU, UK and other national lists \u2013 is a risk-based commercial judgment that should scale honestly with the reporting entity\u2019s actual cross-border footprint, exactly as RBI\u2019s and SEBI\u2019s proportionality principles intend.<\/p>\n<p>Getting the first question wrong invites the kind of regulatory and reputational consequence no institution recovers from easily. Getting the second question right \u2013 screening broadly enough to manage real correspondent-banking and reputational exposure, without over-building a programme no domestic-only institution actually needs \u2013 is where genuine sanctions governance, rather than mere list-following, shows itself and reasonably demonstrates compliance.<\/p>\n<hr height=\"1\">\n<p><em>This article is intended for informational and educational purposes. It does not constitute legal or regulatory advice. Institutions are advised to refer to the relevant guidelines issued by the RBI, SEBI, IRDAI, FIU-IND and other regulators for sector specific compliance requirements.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Compliance officers in India\u2019s financial sector are familiar with the idea of screening customers against lists. What is less consistently understood is that not all screening obligations carry the same legal weight \u2013 and that confusing a risk-based due diligence requirement with an absolute statutory prohibition can quietly undermine how an institution designs, resources and [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[98],"tags":[],"class_list":["post-1777","post","type-post","status-publish","format-standard","hentry","category-screening"],"_links":{"self":[{"href":"https:\/\/trackwizz.com\/knowledge-hub\/wp-json\/wp\/v2\/posts\/1777","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/trackwizz.com\/knowledge-hub\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/trackwizz.com\/knowledge-hub\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/trackwizz.com\/knowledge-hub\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/trackwizz.com\/knowledge-hub\/wp-json\/wp\/v2\/comments?post=1777"}],"version-history":[{"count":1,"href":"https:\/\/trackwizz.com\/knowledge-hub\/wp-json\/wp\/v2\/posts\/1777\/revisions"}],"predecessor-version":[{"id":1778,"href":"https:\/\/trackwizz.com\/knowledge-hub\/wp-json\/wp\/v2\/posts\/1777\/revisions\/1778"}],"wp:attachment":[{"href":"https:\/\/trackwizz.com\/knowledge-hub\/wp-json\/wp\/v2\/media?parent=1777"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/trackwizz.com\/knowledge-hub\/wp-json\/wp\/v2\/categories?post=1777"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/trackwizz.com\/knowledge-hub\/wp-json\/wp\/v2\/tags?post=1777"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}