1. What is a False Positive in Sanctions Screening?

When your screening engine flags a genuine customer because his name, DOB, or company name partially matches a name on:

• UN Security Council List
• US OFAC SDN List
• EU Consolidated List
• UK OFSI List
• RBI / FIU-IND / NIA / UAPA List

Example: Customer Mohammed Adani Logistics vs Adani flagged for Iranian oil case, or Sanjay Patel vs Sanjay Patel - SDN - Narcotics Trafficker.

Under OFAC 50 Percent Rule, entity owned 50% or more by sanctioned person is itself treated as sanctioned.

Banking workflow says:
Hit -> True Match / False Positive Analysis -> Block / Release

If you treat False Positive as True Match, you commit Wrongful Denial of Service.

2. Why False Positives Are So High

• Fuzzy logic: Mohammed = Mohd, Muhammad, Mohamed
• Transliteration: Arabic / Cyrillic to English
• Common names: Patel, Singh, Kumar, Shah - 1000s of matches
• Incomplete data: SDN list gives only name, no PAN / Aadhaar / DOB to disambiguate

Industry average: 1 real hit per 200-1000 alerts.

3. Legal Framework - India and Global

India:

• PMLA, 2002 Sec 12 - Banks must maintain records, file STR to FIU-IND, but does NOT give express power to freeze account for monitoring. Kerala High Court held monitoring provisions (Clause 2.10 of 2012 Circular) mandate monitoring and filing STR, but do not confer express power to freeze. Freezing is more prejudicial than closure - Gujarat HC in State Bank of India v. Ashvin Chaturbhai Parmar.
• RBI Master Directions on Fraud Risk Management 2024 + Frauds Classification 2016 - Classification as fraud requires audi alteram partem.
• RBI KYC Master Direction 2016 - Risk based approach, not blanket de-risking.

EU / US - Most Important for you as sanctions cases are global:

• EU Payment Accounts Directive (2014/92/ EU) - Every consumer has right to basic payment account
• EU Blocking Regulation (EC) No 2271/96 amended by 2018/1100 - EU banks must not comply with extraterritorial US sanctions without EU approval
• OFAC 50% Rule - 2014 guidance
• EU AML Directive 2015/849 - Requires individual risk assessment, not automatic refusal

4. Landmark Case Laws - This is Where Law Changed in 2026

A. CASE C-81/24 Jenec - Court of Justice of European Union - 11 June 2026 - LANDMARK for False Positive

This is the new global standard, decided 5 months ago.
Facts: Slovenian bank refused to open basic payment account for EU-resident consumer solely because he appeared on US OFAC list, despite no UN, EU or Slovenian sanctions.
Held:

• An EU bank cannot refuse consumer a basic payment account solely because that consumer appears on list maintained by US OFAC.
• OFAC listing alone is not sufficient grounds. Proper individual ML/TF/PF risk assessment required under Directive 2015/849.
• A third-country sanctions listing may be taken into account as ONE factor, not decisive factor.
  Impact: Ends blanket de-risking. Banks must now prove why OFAC hit = EU risk. If your Indian bank has EU operations and denies service only on OFAC false match, you can sue under this principle.

B. Apple Inc. - OFAC Settlement $466,912 - Sanctions Screening Failed to Identify Due to Name Mismatch
Apple's screening failed to identify SIS d.o.o., Slovenian software enterprise blacklisted as foreign narcotics trafficker on SDN list, because of name mismatch. Facilitated interests in violation of FNKSR Sec 598.203. Shows opposite risk - False Negative leads to penalty. So you can't tune system too loose.

C. Adani Group - OFAC Settlement $275 Million - May 2026
Before each LPG cargo, Adani screened ships, operators and sellers. OFAC judged case egregious: 35 cargoes from Dubai trader that were Iranian origin. Red flags - AIS spoofing, dark periods, illogical port calls, frequent changes of name, owner, flag. Adani heard concerns 4 times and failed. Shows screening must look beyond name - behavioural screening required.

D. Kuvera Resources v JPMorgan Chase - Singapore Highest Court - Trade Finance
Interpreted bank's sanctions clause strictly and objectively. Held fear of adverse finding by OFAC did NOT excuse non-payment against complying presentation under Letter of Credit. If document complies, bank must pay even if OFAC risk exists. False positive cannot be used to deny LC payment.

E. State Bank of India v. Rajesh Agarwal, (2023 SCC Online 342) - Supreme Court of India - Natural Justice in Fraud Tag
Held: Principles of natural justice, particularly audi alteram partem, must be read into RBI Master Directions 2016 on fraud classification. Before classifying account as fraud (which often starts from sanctions false positive), bank must give notice, consider representation, pass reasoned order. Borrowers must be given opportunity to be heard.

F. State Bank of India v. Amit Iron Private Limited - Supreme Court 7 April 2026 - Clarification of Rajesh Agarwal
Justices J.B. Pardiwala and K.V. Viswanathan.
Held:

• No borrower right to personal / oral hearing before fraud classification - written representation enough, else banking operations thrown into disarray
• BUT bank MUST furnish entire forensic audit report, not merely conclusions, with narrow redaction allowed. Borrower can show match is false positive only if he sees report.
  This is new compliance standard from April 2026.

G. SBI v. Ashvin Chaturbhai Parmar - Gujarat High Court
Held: Freezing is more prejudicial than closure, as closure returns funds while freezing deprives account holder. So if you block account on false sanctions match, you must follow PMLA procedure and unfreeze quickly.

5. How to Minimize False Positives - Legally Defensible Strategy

SC and EU now require this workflow to avoid liability:

1. Tuning + Scoring, not Binary:
Score 0-100. Example:

• Name 100% + DOB exact + PAN exact = 95 - True Match - Block + STR
• Name 80% + DOB mismatch + different address = 40 - False Positive - Release with memo
  Never auto-clear, but never auto-block. Record match-analysis memo with sources.

2. 4-Point Disambiguation (OFAC recommended):
Check Name + DOB + Place of Birth + Address + ID Number. Indian banks should add PAN, Aadhaar (masked), CIN. If 2+ mismatch, release.

3. Individual Risk Assessment - As per C-81/24 Jenec:
Even if OFAC hit, ask: Is customer EU/India resident? Source of funds India? Transaction domestic INR? If yes, risk low - allow basic account, monitor. Document assessment.

4. Whitelisting / Good Guy List:
After proving false positive, whitelist with approval from MLRO - don't flag same customer again next month. Keep audit trail.

5. Exception Handling - SBI v Rajesh Agarwal Compliance:
Before freezing / reporting fraud, give notice: "Your name matches SDN XYZ, provide proof you are not that person within 7 days". Share forensic report / screening evidence.

Wrong way: Block account on name match, no notice, customer learns after cheque bounces - This is deficiency + violation of Payment Accounts Directive + natural justice - You will pay compensation under Banking Ombudsman + writ petition in HC.

Right way: Hit -> Analyse -> Score 40 -> Memo -> Release booking, keep monitoring, file info STR if needed.