All Courses are free for limited time.
NISM Professor

Settlement number

A unique identifier tagging a trade or batch of trades to a particular settlement cycle and date, used by brokers, clearing corporations and depositories to match and reconcile obligations.

In plain language

Every trading day produces its own set of obligations, and the market may run more than one settlement type at once. Something has to label which settlement a trade belongs to, or a depository could apply a delivery against the wrong day's obligation.

That label is the settlement number. The workbook describes it as a unique identifier that tags a specific transaction or batch of transactions to a particular settlement cycle. It links a trade to a specific settlement date, so that pay-in and pay-out of funds and securities happen on the correct day.

It travels with the settlement type / market type, which says under which category the trade was executed (for example normal or auction) and so which settlement rules apply.

How it works

What it does (Chapter 6, section 6.4.1)

  • Brokers, clearing corporations and depositories use it to reconcile their records and confirm each member's cumulative obligations for that cycle.
  • With the settlement/market type, it is one of the "crucial identifiers" in equity settlement, used for accurate matching, processing and finalisation of trades.
  • The market type decides whether trades settle in demat or physical form (the latter now rare, for limited physical markets) and whether settlement is gross (trade-for-trade) or netted.
  • Clearing corporations periodically publish settlement numbers and settlement/market types.

Why it matters for margins (Chapter 4, section 4.1.1.1). VaR and extreme loss margins are collected on the member's gross open position, and there is no netting of positions across different settlements. MTM positions are likewise not netted across two settlements such as T+1 and T+0. Positions are therefore grouped by settlement number before being grossed.

Net settlement of cash and F&O (Chapter 6). When physical settlement obligations of expiring stock derivatives are netted with Capital Market obligations, the net obligation is settled in the settlement/market type and settlement number of the Capital Market segment.

A worked example

This is the workbook's own illustration in Chapter 4 (values in Rs).

ClientSecuritySettlement No.Net value
AX2005001−100
AY2005002450
BZ2005001−150
BY20050021,350
CX20050012,100
CZ2005002−3,450
ProprietaryY2005001−950
ProprietaryZ20050021,050

The member's gross position is built security by security and settlement number by settlement number, adding absolute values:

  • X, 2005001: 100 + 2,100 = 2,200
  • Y, 2005001: 950
  • Z, 2005001: 150
  • Y, 2005002: 450 + 1,350 = 1,800
  • Z, 2005002: 3,450 + 1,050 = 4,500
  • X, 2005002: 0

Security Z appears in both settlements (150 and 4,500). Because positions are not netted across settlement numbers, both count in full: 4,650 in total, not 4,500 − 150.

Why NISM asks about it

Chapter 6, section 6.4.1 (Settlement through the Depository Clearing System) defines the settlement number and settlement/market type. Chapter 4 (section 4.1.1.1) uses settlement numbers in the gross open position table for VaR margin, and Chapter 6 (sections 6.4.1 and 6.6.3) says the net cash/F&O obligation settles under the Capital Market segment's settlement number. Expect a definition question and the "no netting across settlements" rule.

Common exam traps

  • Settlement number = which cycle/date. Settlement type/market type = which category and rules (normal, auction, gross or netted). They are different identifiers.
  • No netting across different settlements when computing VaR, ELM or MTM on gross open positions.
  • Net cash/F&O obligations use the Capital Market segment's settlement number, not an F&O settlement number.
  • Clearing corporations publish settlement numbers periodically; members do not create them.

Where this is taught

Free preparation for NISM Series VI

Related terms

← All terms
Something look wrong? Report it