PASS Securities Operations and Risk Management Examination Difficulty: Beginner 2 Questions   5 min read
📌 Chapter 7.1 — INTRODUCTION

Consider a Monday morning where your firm receives an automated alert from the SEBI Complaints Redress System (SCORES) regarding a client who claims they never received a credit for a corporate action payout. As a back-office professional, you recognize this is not merely a request for information; it is a live regulatory ticket with a ticking clock.

Under the legacy system, responses were often fragmented, but SCORES 2.0 has transformed this into a unified, digital nervous system designed to eliminate ambiguity in communication between the investor, the intermediary, and the regulator.

SCORES 2.0 integrates auto-routing and auto-escalation features, which means your firm no longer has the luxury of manual delays or misplaced email threads. When a complaint lands in your dashboard, the system categorizes it based on the nature of the issue—be it a trade discrepancy, a ledger mismatch, or an issue with the depository participant.

You must upload your Action Taken Report (ATR) directly into the portal, ensuring that every document, such as contract notes or bank statements, acts as a factual defense. If you fail to resolve the issue within the mandated 21-calendar-day window, the system automatically marks the complaint for escalation to the designated stock exchange.

This framework matters because it shifts the firm from a reactive stance to a proactive, evidence-based culture. In a real-world scenario, if a client alleges that their funds were diverted, your ability to upload a digital trail of the payment gateway confirmation within the SCORES portal is the difference between a closed ticket and an intrusive regulatory audit.

The system forces a standardized workflow, ensuring that no complaint is left in a state of limbo, which protects the firm against the reputational damage of unresolved grievances. For an operations professional, the portal is your primary record-keeping tool that bridges the gap between client expectations and regulatory mandates.

Ultimately, viewing SCORES 2.0 as a burden is a professional mistake; it is a structural protection mechanism. By keeping your internal logs aligned with the portal’s requirements, you ensure that every transaction is transparent and defensible. When you master the nuances of the portal’s timelines, you transform from an administrative clerk into a risk management gatekeeper who preserves the integrity of the capital markets.

Nuance

⚠️ Nuance
Many candidates erroneously assume that SCORES 2.0 is only for client-initiated complaints, failing to realize that it serves as a permanent, searchable compliance audit trail for the regulator. A common pitfall is the belief that a ‘satisfactory’ internal resolution with the client absolves the firm from updating the portal. If you resolve a grievance offline without properly closing the loop in SCORES 2.0, the system treats the matter as pending, which can trigger automatic penalties regardless of the actual client outcome.

Check Your Understanding

Practice Question 1

Your firm receives a complaint via SCORES 2.0 regarding a failed settlement. After resolving the issue directly with the client via a phone call, you verify the funds are credited. What is the mandatory next step in the context of the SCORES 2.0 mechanism?

Practice Question 2

Which feature of SCORES 2.0 is specifically designed to minimize manual oversight and ensure that firms do not exceed the 21-day resolution limit?

This is a companion read for Section 7.1 — INTRODUCTION from PASS Securities Operations and Risk Management Examination by Akhilesh Gururani, available on Amazon Kindle.

Copyright © 2026 `Akhilesh Gururani. All rights reserved.