Unique Client Code
Also written UCC · Unique Client Code (UCC) · Client code
The 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.
In plain language
A broker deals with thousands of clients and enters orders for all of them into the same exchange terminal. Without a code attached to each order, there would be no way to prove afterwards whose trade was whose — and every loss-making trade could quietly be moved onto a client who did not place it.
The unique client code closes that gap. It is allotted once, at account opening, and is the client's identity with that broker for as long as the relationship lasts. SEBI additionally requires it to be mapped to the client's PAN, so the code cannot be detached from a real, taxable, identified person.
Because the exchange validates the code at the moment the order is entered, an order for an unregistered client simply does not go through.
How it works
SEBI made unique client codes compulsory for brokers in 2001 (circular SMDRP/Policy/CIR-39/2001 dated 18 July 2001, reinforced in September 2003). The broker must give the exchange the UCC and the client's PAN before entering any trade for that client, and exchanges validate UCC and PAN for all orders in all markets — both PRO (proprietary) and CLI (client) — at the time of order entry against the details uploaded by the member.
The code does not stop at the exchange. Exchanges share UCC data with the depositories — PAN, segment, TM/CM code and UCC — so that the code is mapped to the client's demat account. Brokers also upload the client's name, mobile number, correspondence address and email, and the exchange sends trade alerts by SMS and email directly to the investor at the end of the trading day, bypassing the broker.
One narrow exception exists on the trading side: for investors who must settle by delivery only and cannot trade without funds or securities to their credit, a broker may allot up to two trading client codes — one for buys, one for sells — so the two legs are not netted. Both still map to the same UCC.
A worked example
A broker onboards a new retail client in Pune.
| Step | What is recorded | Timeline from the Investor Charter |
|---|---|---|
| KYC completed and uploaded to KRA and CKYCR | KYC identification number | 3 working days of account opening |
| UCC allotted and uploaded to the exchange | UCC mapped to PAN and demat account | Before trading |
| Client onboarding complete | Trading enabled | Immediate, not later than one week |
| Copy of client registration documents given | Acknowledgement obtained | 7 days from upload of the UCC to the exchange |
| First trade: 300 shares at Rs 1,840 = Rs 5.52 lakh | Contract note issued under that UCC | 24 hours of execution |
Suppose the dealer types the wrong code and the Rs 5.52 lakh buy lands in another client's account. The exchange permits a client code modification for a non-institutional trade only to rectify a genuine error in code entry, conducts a special inspection of the member to check the modifications are being made against strict objective criteria, and levies a penalty that is credited to the Investor Protection Fund unless the member can prove the error was genuine.
Why NISM asks about it
Chapter 3 (Introduction to Securities Broking Operations, section 3.2.1.5) is the home of the UCC, and section 3.2.4 on trade modification is where the penalty consequences appear. The examinable points are the PAN mapping, the fact that validation happens at order entry for both PRO and CLI, the "before trading" timeline in the Investor Charter, and the two-trading-codes-one-UCC exception. The UCC also reappears in Chapter 4, where client-level collateral and the Market Wide Position Limit are both measured UCC-wise.
Common exam traps
- Two trading codes, one UCC. The delivery-only concession splits the trading code, never the unique client code. A question offering "two unique client codes" as an option is offering a wrong answer.
- Proprietary trades can never be modified into client trades, or the reverse. The prohibition is absolute; there is no genuine-error exemption for it.
- Institutional code modification is not automatically penalised. A change between two institutional codes is free of penalty only where both are schemes or sub-accounts of, or managed by, the same institution. Between two unrelated institutions it attracts penalty.
- Shifting a trade into the broker's error account is not a client code modification — provided the trades in the error account are subsequently liquidated in the market and not shifted to another code.
- Separate mobile number and email per client is the rule. The same contact may be used for more than one client only on the client's specific written request, and only within one family or for an authorised person of an HUF, corporate, partnership or trust.
- The UCC is broker-specific. The same investor has a different UCC at every broker; what ties them together is the PAN.
Where this is taught
- Series IV · Chapter 6: Trading Mechanism in Exchange Traded IRDintroduced here
- Series XVI · Chapter 10: Codes of Conduct and Investor Protection Measuresintroduced here
- Series I · Chapter 6: Trading Mechanism in Exchange Traded Currency Derivativesintroduced here
- Series VIII · Chapter 10: Sales Practices and Investor Protection Measuresintroduced here
- Series III-A · Chapter 12: SEBI (Stock Brokers) Regulations, 2025introduced here
- Series VII · Chapter 3: Introduction to Securities Broking Operationsintroduced here
Related terms
- Investor CharterSEBI's published statement of what an investor is entitled to from an intermediary — the services, the rights, the dos and don'ts, and a table of activities with the timeline each one must be completed in.
- Contract noteThe legal record of a trade a stock broker executed for a client on an exchange, issued within 24 hours in the exchange-prescribed format, physically or as a digitally signed electronic contract note.
- Margin pledgeThe only permitted way for a client to give securities as margin — a special pledge created in the depository system that leaves the shares in the client's own demat account instead of transferring them to the broker.
- Central KYC RegistryThe Government's central digital store of KYC records for the whole financial sector, operated by CERSAI, which de-duplicates records and issues each client a unique KYC Identifier.
- Custodial participantA client allowed to trade through several trading members while clearing and settling through a single clearing member, identified by a unique CP code; its CM must confirm the trades.
- Client Unpaid Securities Pledgee AccountA separate account a TM/CM opens, in whose favour an auto-pledge marked "unpaid" is created when pay-out securities go to a client who has not paid for them.
- Market transactionSettlement of a trade executed on a stock exchange, moving through a Clearing Corporation/House and the seller's and buyer's clearing member accounts — as opposed to an off-market transaction settled person-to-person.
- UCC mappingThe 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.
- Tipping offTelling a client that a suspicious transaction report about them has been or will be filed — illegal, and the reason the broker reports to the Financial Intelligence Unit in silence.
- Officially valid documentsThe alternatives to Aadhaar accepted as identity evidence for KYC — driving licence, passport, voter ID and the NREGA job card — all of which the client supplies voluntarily.
- Sham transactionsTrades entered into without intending to perform them or to change ownership of the security — deemed a manipulative, fraudulent or unfair trade practice under regulation 4(2) of the PFUTP Regulations.
- Early warning signalsIndicators that stock exchanges, depositories and clearing corporations monitor to catch a stock broker's deteriorating finances or diversion of client securities early, triggering joint preventive action.
- Kill switchA pre-trade facility that lets a trading member cancel every one of its outstanding orders with a single command — the emergency brake for a malfunctioning terminal or algorithm.
- Authorised personTwo different entities share this name: under SEBI, an agent appointed by a stock broker to give clients access to the trading platform; under FEMA, a dealer authorised by RBI to deal in foreign exchange.
- Suspicious Transaction ReportA report a SEBI intermediary must file with FIU-IND within 7 days of concluding that a transaction or connected series of transactions is suspicious — and must never disclose to the client.
- Trading accountThe account you open with a SEBI-registered stock broker to buy and sell securities on a stock exchange. You get a Unique Client Code, a contract note within 24 hours of each trade, and alerts.
- Risk reduction modeThe restricted state a stock broker is put into when 90% of its collateral is used up by margins: pending orders are cancelled, only IOC and margin-checked orders pass, until utilisation falls below 85%.
- Direct Market AccessA facility, introduced by SEBI in 2008 for institutional investors, that lets a client send orders straight into the exchange trading system through the broker's infrastructure without manual intervention by the broker.
- Front runningUsing non-public knowledge of a substantial impending order to trade ahead of it in the same or related securities or derivatives, expecting the price to move once the order becomes public.
- TradeThe binding transaction created the moment a buy order and a sell order are matched on the exchange, after which it can be modified only in narrow, regulated ways and never simply cancelled.