UCC mapping
The SEBI-mandated linking of a client's trading-member-allotted Unique Client Code to their demat account, so exchanges and depositories can jointly detect diversion of client securities.
In plain language
A trading member gives every client a Unique Client Code, or UCC, to identify them at the exchange. A depository, separately, knows the client only through the demat account. Nothing forced these two identifiers to line up, until SEBI stepped in.
As part of an Early Warning Mechanism to catch a broker quietly diverting client securities, SEBI told depositories to map each client's UCC directly onto their demat account, so a mismatch between what a broker reports and what actually moves becomes visible fast.
How it works
From Chapter 4, section 4.9: SEBI, in 2018, directed Market Infrastructure Institutions — stock exchanges, Clearing Corporations, Depositories — to build an Early Warning Mechanism to detect diversion of client securities by a stockbroker early. Under a SEBI circular dated 15 November 2019 (implementation deadline 31 December 2019), DPs were directed to map the UCC allotted by the trading member to the client's demat account. A client trading through multiple TMs has each such UCC mapped to one or more demat accounts.
Stock Exchanges share UCC data — PAN, segment, TM/CM code, UCC — with Depositories: a one-time batch from 30 November 2019, then incrementally on a daily basis for new UCCs. Depositories map this data to the demat account using the PAN in the UCC database. Clients may ask their DP to de-link or add UCC details, validated by the Depository against the Exchange or client before any addition. Exchanges and Depositories must also weed out inactive, non-operational UCCs from client mapping.
A worked example
Mr Oberai trades through two different brokers, Broker A and Broker B, each of which has allotted him a separate UCC. His depository maps Broker A's UCC to his demat account using his PAN, and separately maps Broker B's UCC to the same demat account.
When a mismatch is later found — securities credited under Broker A's pay-out figures do not match what actually landed in Mr Oberai's demat account — the Depository traces the discrepancy back to the exact UCC-mapped trading relationship involved, and reports the mismatch to the concerned Stock Exchange or Clearing Corporation, exactly the early-warning outcome the 2018 directive was built to produce.
Why NISM asks about it
Chapter 4, section 4.9, sets out UCC mapping immediately after the Accreditation of Investors framework. Expect the 2018 origin of the Early Warning Mechanism, the November 2019 circular's implementation deadline, and PAN as the matching field.
Common exam traps
- UCC data reaches the Depository from the Stock Exchange, not from the trading member directly — the exchange is the data source in this workflow.
- Matching happens on PAN, not on client name or UCC number alone.
- The initial UCC data share was a one-time batch; new UCCs are shared daily after that, not in another one-time batch.
Where this is taught
Free preparation for NISM Series VIRelated terms
- Unique Client CodeThe single code a broker assigns to a client once KYC is complete, mapped to that client's PAN and demat account, under which every one of the client's orders must be entered on the exchange.
- Depository participantThe SEBI-registered agent through whom an investor reaches a depository — NSDL and CDSL cannot open investor accounts themselves, so every demat account is opened and operated through a DP.
- Client Master ReportThe depository-system report of a demat account's recorded details - holders, address, bank, contact and other static data - sent to the client on account opening and used as proof of account details.