Deep Dive: Direct Payout to Demat

Why this page is structured this way: The change introduced a new pool-account architecture (CUSPA / CSMFA) at the same time as the operational pay-out flow. The page treats both — first the regulatory authority, then the pre-mandate vs post-mandate flow comparison, then the new pool-account types, then chart-of-accounts and reconciliation guidance, and finally the rollout-period failure modes.

TL;DR

SEBI mandated direct payout of securities to client demat accounts under SEBI/HO/MIRSD/MIRSD-PoD1/P/CIR/2024/75 (5 June 2024). The objective: eliminate broker pool-account custody during settlement, reducing the broker as a point of failure.
Operational guidelines were issued by NSCCL via NCL/CMPT/63669 (30 Aug 2024), superseding the initial NCL/CMPT/62339 (Jun 2024) which had targeted 14 October 2024 go-live. ICCL launched a parallel pilot via ICCL 20250214-69 (Feb 2025).
Rollout was phased. Phase 1 (NSCCL): operational from 14 November 2024 for the cash segment under SEBI/HO/MRD/MRD-PoD-2/P/CIR/2024/137 (10 Oct 2024 — operationalisation). Phase 2: NSCCL Feb 2025 (NCL/CMPT/66779 effective 25 Feb 2025 from settlement 2425828); ICCL pilot from 25 Feb 2025; January – February 2025 extensions to additional segments under continuing updates.
Three new pool-account types govern post-mandate custody: TM CUSPA, CM CUSPA, TM CSMFA. Each has a specific permissible-balance rule and reporting requirement.
Custodian-cleared clients excluded from direct payout in both NSCCL and ICCL flows. Internal-shortage valuation = settlement price + 20% mark, payable by noon on settlement day.
A separate primary demat account for proprietary UCC distinct from the DP-ID-Client-ID associated to the NSDL CM pool account is required for direct-payout members (NCL/CMPT/69455 update, 1 Aug 2025).
Chart-of-accounts updates and reconciliation logic changes were the most consequential operational impact for back-office software.

Conceptual overview

Before June 2024, the broker held client-bought securities briefly in a pool account during settlement. The clearing corporation paid out securities to the broker’s pool, and the broker then pushed them to the client’s demat. This created a window — typically a few hours, sometimes up to a day — during which client securities sat in broker custody. SEBI’s June 2024 mandate eliminated this window: pay-out securities now flow directly from the clearing pool to the client’s demat, bypassing the broker’s intermediate pool altogether.

The change was driven by a fairness and risk principle that runs through every recent SEBI broker reform: client assets should never be exposed to broker default risk. The June 2023 client funds upstreaming mandate did this for cash; the June 2024 direct-payout mandate does it for securities. Together, the two cover virtually the entire end-of-day balance sheet a broker historically held against client positions.

For operations, the cutover was non-trivial. The broker pool account did not disappear — it was restructured. Three named account types replaced the legacy pool: TM CUSPA holds securities for unpaid clients, CM CUSPA is the clearing-member equivalent, and TM CSMFA holds securities funded under MTF. Each has different permissible balances, different inflow / outflow rules, different reporting, and different reconciliation logic. Brokers that updated their chart of accounts during the rollout windows had a clean reconciliation; brokers that didn’t faced weeks of settlement-confirmation discrepancies (see the practical notes).

1. Regulatory authority and rollout timeline

1.1 SEBI authority

SEBI/HO/MIRSD/MIRSD-PoD1/P/CIR/2024/75 (5 June 2024): The foundational circular. Mandates Clearing Corporations to directly credit securities to clients’ demat accounts in pay-out, eliminating broker pool-account handling. Broker’s Industry Standards Forum tasked with implementation standards. Effective 14 October 2024 (after extension from earlier date).
SEBI/HO/MRD/MRD-PoD-2/P/CIR/2024/137 (10 October 2024): Operationalises direct payout phased starting 14 Oct 2024 with the final pay-out time extended to 15:30 IST. Full direct payout effective for all settlements from 14 January 2025 in the phase 1 segment.
Master Circular updates. Master Circular for Stock Brokers SEBI/HO/MIRSD/POD-1/P/CIR/2024/118 (Aug 2024) and SE/CC Master Circular Dec 2024 both incorporated direct-payout provisions.

1.2 Clearing-corp operational circulars

NCL/CMPT/62339 (6 June 2024): NSCCL initial implementation circular, originally targeted 14 October 2024 go-live. Superseded.
NCL/CMPT/63669 (30 August 2024): NSCCL full operational guidelines. Mandates the new account-type architecture (TM CUSPA, CM CUSPA, TM CSMFA), discontinues the legacy direct-payout-to-investor-accounts facility (NCL/CMPT/61800 Part C point 6), and provides the release-payout-with-pledge-in-favour-of-CUSPA(Unpaid) / CSMFA(MTF) facility. In-force 11 November 2024.
NCL/CMPT/65100 (14 November 2024): Reiterates that CMs must keep pool accounts active in both NSDL and CDSL at all times even if they opt to receive payout in a preferred depository; non-compliance impacts payout release.
NCL/CMPT/66779 (21 February 2025): Phase 2 — full direct-payout regime from settlement 2425828 (25 Feb 2025), excluding custodian-cleared clients. Gross pay-in to CC required. Internal-shortage valuation = settlement price + 20% with payment due noon on settlement day. Member identifies auction profits at client level.
ICCL 20250214-69 (14 February 2025): ICCL pilot of direct securities payout to client demat accounts; pilot from 25 February 2025 with normal-market settlements from settlement 2425828 onwards. Custodian-cleared clients excluded; gross pay-ins to ICCL; internal-shortage valuation at settlement price + 20% by noon on settlement day.
NCL/CMPT/67947 (9 May 2025) and NCL/CMPT/69455 (1 August 2025): Follow-up clarifications. Direct payout at NSDL is keyed on the CM BP ID and not the DP-ID-Client-ID linked to the NSDL CM pool account; members must open a separate demat account as primary for proprietary UCC, distinct from the DP-ID-Client-ID account associated with the NSDL CM pool account, to avoid mis-mapping during NSDL demat-verification with the exchanges.

1.3 Rollout phasing

Phase	Effective date	Scope	Authority
Pilot (custody only)	Pre-2024 (legacy direct-payout-to-investor-account)	Limited demat credits; discontinued	NCL/CMPT/61800 Part C point 6
Phase 1 — NSCCL go-live	11 / 14 November 2024	Equity cash segment, normal settlement, excluding custodian-cleared	NCL/CMPT/63669, SEBI/HO/MRD/MRD-PoD-2/P/CIR/2024/137
Phase 1 — Full	14 January 2025	All settlements in equity cash segment	SEBI/HO/MRD/MRD-PoD-2/P/CIR/2024/137
Phase 2 — NSCCL	25 February 2025 (settlement 2425828)	Phase 2 expansion; gross pay-in to CC; internal-shortage 120% valuation	NCL/CMPT/66779
Phase 2 — ICCL pilot	25 February 2025 (settlement 2425828)	ICCL parallel pilot	ICCL 20250214-69
Update	9 May 2025 / 1 August 2025	NSDL CM BP ID keying clarification; proprietary-UCC separate demat	NCL/CMPT/69455

2. Pre-mandate vs post-mandate flow

2.1 Pre-mandate flow (legacy, pre-November 2024)

                       T+1 morning
                          │
                 [funds pay-in to CC]
                          │
                          ▼
                   CC nets obligations
                          │
                          ▼
              [securities pay-out from CC]
                          │
                          ▼
         ┌─────────────────────────────────┐
         │  BROKER POOL ACCOUNT (CM)        │
         │  Holds securities briefly        │
         │  Several hours of broker custody │
         └────────────┬────────────────────┘
                      │
                      ▼
         ┌─────────────────────────────────┐
         │  Broker pushes securities to     │
         │  client demat via internal       │
         │  transfer instruction            │
         └────────────┬────────────────────┘
                      │
                      ▼
                CLIENT DEMAT

Issues with the legacy flow:

Window of broker custody. Securities sat in the broker’s pool during the gap between clearing-corp pay-out and broker-to-client push. Broker default during this window could expose those securities.
Internal-process risk. Mis-mapping, file-format errors, or queue delays at the broker could delay client-demat credit.
Pooled accounting. Securities for many clients were briefly comingled in a single pool, complicating client-level tracking.

2.2 Post-mandate flow (current, post-November 2024)

                       T+1 morning
                          │
            [gross funds pay-in to CC; broker pays
             internal-shortage valuation at SP+20%
             by noon on settlement day]
                          │
                          ▼
                   CC nets obligations
                          │
                          ▼
              [securities pay-out from CC]
                          │
                          ▼
         ┌─────────────────────────────────┐
         │  DIRECT to CLIENT DEMAT          │
         │  via depository                  │
         │  Net pay-out delivered directly  │
         │  Based on CC's allocation file   │
         └────────────┬────────────────────┘
                      │
                      ▼
              CLIENT DEMAT (credited)

         [Unpaid clients: securities held
          in TM CUSPA with pledge in favour
          of broker until client pays]

         [MTF clients: securities held in
          TM CSMFA with MTF pledge until
          MTF unwound or squared off]

Key behavioural differences:

No pool transit. Securities never enter a generic broker pool. The CC’s allocation file maps each ISIN-quantity directly to a client’s demat (per primary-demat UCC mapping).
Gross pay-in. Brokers do gross pay-in to the CC under Phase 2 (NCL/CMPT/66779). The CC handles netting.
Conditional retention. Where the client has not paid for purchased securities, the securities flow to the TM CUSPA(Unpaid) with a pledge in favour of the broker — providing the same economic protection as the legacy “unpaid” mechanism, but in a depository-tracked custody.
MTF custody. Securities funded under MTF flow to the TM CSMFA — the broker’s MTF custody account — with the MTF pledge active. The economic substance is the same as the legacy MTF custody, but with a named depository account.
Custodian flow unchanged. Custodian-cleared clients (FPIs / MFs / portfolio-managed accounts) continue with the custodian’s existing flow; the direct-payout regime explicitly excludes them.

3. The three new pool-account types

3.1 TM CUSPA — Trading Member Client Unpaid Securities Pledgee Account

Purpose. Holds securities where the client has not paid in full at settlement. Securities credit directly to client demat, but with a pledge in favour of the broker’s CUSPA(Unpaid). On client payment, the pledge is released. On client default, the broker may invoke the pledge.

Who maintains it. Trading Members (TMs). Required for every TM offering direct-payout flow in cash segment.

Permissible balance. Only unpaid-client securities pending client payment. The pledged securities remain reflected in the client’s demat with the lien recorded.

Reporting. Daily reconciliation against client ledger debit balances; reflected in collateral allocation files to the clearing corp.

3.2 CM CUSPA — Clearing Member Client Unpaid Securities Pledgee Account

Purpose. Same as TM CUSPA but at the Clearing Member layer. Professional CMs (CMs that clear for other TMs, not for their own clients) maintain only CM CUSPA. TM-cum-CM members maintain both TM CUSPA and CM CUSPA.

Maintenance rules per NCL/CMPT/63669:

TMs maintain TM CUSPA only.
TMs that are also CMs (TM-cum-CM) maintain both TM CUSPA and CM CUSPA.
Self-clearing TMs maintain only TM CUSPA.
Professional CMs (CMs clearing only for other TMs, no own client base) maintain only CM CUSPA.
A TM that clears via another CM must open TM pool accounts in both depositories (NSDL and CDSL) per NCL/CMPT/65100.

3.3 TM CSMFA — Trading Member Client Securities Margin Funded Account

Purpose. Holds securities funded under MTF. When a client buys on MTF, the broker funds (typically 75%) the purchase and the client pays the margin (typically 25%). The securities credit directly to the client’s demat with an MTF pledge in favour of the TM CSMFA.

Who maintains it. TMs offering MTF must maintain a CSMFA where the client’s demat resides. If a TM offers MTF to clients across both NSDL and CDSL demats, the TM must maintain a CSMFA in each depository.

Permissible balance. Only MTF-funded securities pledged to the broker as collateral against MTF funding. Cleared on client payment / square-off / unwind.

Reporting. Daily MTF funded-position file; pledge file submitted via depository; collateral file at the clearing corp for the corresponding margin benefit. See the MTF operational deep dive for the full MTF cycle.

3.4 The legacy pool account — what remains

The broker’s legacy “pool account” — sub-status 30 / 31 / 32 in CDSL terminology — does not disappear. It continues to exist for proprietary trading positions (broker’s own account, not client-facing), for failed-settlement remediation, and as a transitional account during corporate actions or internal-shortage close-out. But it no longer serves as the conduit for client securities during normal pay-out.

NCL/CMPT/69455 (Aug 2025) added a further constraint: the broker’s primary demat account for proprietary UCC must be distinct from the DP-ID-Client-ID account that is linked to the NSDL CM pool account. Direct payout at NSDL is keyed on CM BP ID rather than DP-ID-Client-ID, and mis-mapping causes the NSDL demat-verification with the exchanges to fail. Brokers that didn’t separate their proprietary UCC account were forced to re-open a fresh primary demat account in the August – September 2025 window.

4. Chart-of-accounts update guidance

The back-office software houses (TechExcel, Mihir, Aastha, Shilpi, Logo Sarva, ProSarva, etc.) issued patch releases in the August – November 2024 window to add the new account types. Common patterns for the chart-of-accounts update:

4.1 New ledger account heads

Pool — TM CUSPA(Unpaid). Asset account; balance = client unpaid securities pending settlement. Cleared on client payment.
Pool — TM CSMFA(MTF). Asset account; balance = MTF-funded securities; carrying value pledged. Cleared on MTF unwind / square-off / client payment.
Pool — CM CUSPA(Unpaid). Asset account at CM layer (only for CMs).
Pool — Legacy (proprietary / corporate-action / failed-settlement). Continues to exist; balance restricted to non-client flows.

4.2 New reconciliation queries

Daily. Each TM CUSPA / CM CUSPA / TM CSMFA balance vs. the depository’s snapshot for that account and ISIN. Discrepancies are the first sign of a mis-mapping issue.
Daily. Client demat credit confirmation against the clearing-corp allocation file. A pay-out present in the CC’s allocation file but missing from the client’s demat is a high-priority alert.
Daily. Pledged-balance in TM CUSPA matched to the client ledger debit. Mis-match suggests a pledge-creation or pledge-release error.
Per settlement. Internal-shortage clients vs. valuation paid (settlement price + 20%) by noon on settlement day.
Per settlement. Auction profits identified at client level (per NCL/CMPT/66779 Phase 2 — member identifies auction profits at client level).

4.3 New file flows

CC obligation file → broker. Contains client-level direct-payout allocation. Broker validates against expected client positions.
Depository pay-out confirmation file → broker. Confirms client demat credit. Reconciles against CC allocation.
TM CUSPA / TM CSMFA pledge files → depository. Created at pay-out for unpaid clients / MTF clients.
Pledge release files → depository. Created when client pays / MTF unwinds.

4.4 Migration steps (industry-typical implementation)

Open TM CUSPA in CDSL and NSDL (if both depositories used).
Open TM CSMFA in CDSL and NSDL (if offering MTF and serving both depositories).
If CM: open CM CUSPA in both depositories.
Update primary-demat-UCC mapping in the exchange UCC database for every client.
Update broker back-office chart of accounts.
Update reconciliation queries.
Update RMS to recognize TM CUSPA(Unpaid) pledge as offsetting the client’s “unpaid” debit balance for margin purposes.
Update client communication templates — pay-out confirmation messages must reflect direct credit.
Run parallel pre-go-live with the legacy pool flow for at least one settlement cycle (typical practice).
Cut over at the SEBI-mandated date for the relevant phase.

5. Reconciliation patterns

The post-mandate reconciliation is more complex than the pre-mandate model because the flow has more independent points where the broker is a passive observer rather than an active participant.

5.1 Three-way reconciliation

For every settlement, the broker reconciles three sources:

Source	Content	Used to verify
Clearing-corp allocation file	Per-client securities pay-out allocation	What the CC paid out
Depository pay-out confirmation	Per-client demat credit confirmation	What the depository delivered
Broker back-office expected	Per-client expected pay-out based on T+1 obligations	What the broker expected

In the legacy flow, the broker controlled the broker-to-client push and the reconciliation was effectively two-way (CC pay-in to broker pool vs. broker push to client). In the direct-payout flow, the broker reconciles three sources and is a downstream witness rather than an active step.

5.2 Discrepancy types and remediation

Discrepancy	Typical cause	Remediation
CC allocation says credit, depository confirmation absent	Mis-mapped primary demat UCC; client demat closed; ISIN-account-type mismatch	Update UCC mapping; remediate via legacy pool transit; raise depository help-ticket
Depository confirmation says credit, broker back-office expects nothing	Stale broker expectation file; unprocessed trade file from yesterday	Re-process trade file; reconcile
Broker back-office expects credit, both CC and depository show nothing	Client trade not in CC obligation; broker booked-but-not-cleared trade	Investigate trade booking; potentially escalate to CC
Pay-out partial (some clients credited, some not)	Internal-shortage scenario; some clients flagged unpaid	Verify TM CUSPA pledge; confirm SP+20% valuation paid by noon
Direct credit to wrong demat	UCC primary-demat-mapping error in exchange UCC	Critical: contact CC immediately; restitution flow varies

5.3 Internal-shortage close-out

Under Phase 2 (NCL/CMPT/66779, ICCL 20250214-69), the member-internal shortage close-out works as follows:

Settlement day morning: CC publishes allocation file. The broker’s net deliverable may include some clients with unpaid balances (internal shortage).
The broker pays valuation = settlement price × 120% by noon on settlement day to the CC. This is the broker’s internal-shortage close-out cost.
The broker identifies auction profits at client level (per Phase 2 Phase-2 update).
The broker recovers the internal-shortage cost from the relevant client.
Failed-settlement-recovery files are submitted in the back-office reporting cycle.

This replaces the legacy mechanism where the broker held the position briefly in pool and remediated via internal book entries; now the CC sees and charges the close-out directly. See Settlement domain entry SETTLEMENT-009 for the obligation and the Pay-in default + Core SGF deep dive for the failure cascade.

6. Sub-cases / edge cases

6.1 Corporate-action ex-date

Securities crossing the ex-date for a corporate action (split, bonus, dividend) require the EPI / pay-out files to reflect the correct ISIN. Representative example: NCL/CMPT/65498 (10 Dec 2024) for the SHRADHA 5→2 face-value split — EPI on settlement 2024233 in Old ISIN, EPI on Dec 11 for settlements 2024233 and 2024234 in New ISIN. Direct payout must respect the ISIN per the corporate-action effective date.

6.2 Custodian-cleared clients (explicit exclusion)

FPIs, mutual funds, portfolio-managed accounts, insurance company books, and other custodian-cleared clients are explicitly excluded from direct payout. Their flow continues through the custodian’s existing process — securities pay-out to the custodian, custodian-internal allocation, custodian-to-client demat transfer. The exclusion is by client-type, not security-type.

6.3 Buyback / takeover / OTB (Offer-to-Buy) settlements

Buyback (e.g., NCL/CMPT/63561) and takeover settlements via the EPI Market Type “Buyback” / “Takeover” use a different settlement number flow. Direct payout for normal-market settlements; OTB settlements continue with the legacy depository-EPI mechanism (CDSL = direct client pay-in; NSDL = securities earmarking / blocking). See representative buyback / OTB circulars in the clearing-corps circulars page.

6.4 SGB (Sovereign Gold Bond) settlement

SGB tranche settlements (e.g., ICCL 20200706-1) continue to use the existing Equity Cash settlement account funding mechanism with the SGB-specific obligation file flow.

ICCL 20240613-52 (Jun 2024) discontinued the use of pool accounts for non-demat MF redemptions on BSE StAR MF. Demat transactions still flow via AMC/RTA credits to the ICCL bank account; non-demat redemptions credit clients’ bank accounts directly. The direct-payout-to-demat mandate is a separate change from this MF-specific change but reflects the same regulatory direction.

6.6 Mis-mapped UCC

If a client’s primary demat UCC mapping in the exchange UCC database is incorrect, the direct-payout flow attempts to credit the wrong demat. Detection is typically at the depository-pay-out-confirmation reconciliation; remediation requires CC notification, possible re-routing, and a UCC correction filing. Mis-mapped UCC is one of the most common rollout-period issues — see practical notes.

6.7 NSDL CM pool account separation

NCL/CMPT/69455 (Aug 2025): direct payout at NSDL is keyed on CM BP ID, not DP-ID-Client-ID. Members must open a separate demat account as primary for proprietary UCC, distinct from the DP-ID-Client-ID associated with the NSDL CM pool account, to avoid mis-mapping during NSDL demat-verification with the exchanges. CDSL flow is unaffected (CDSL keys on DP-ID-Client-ID natively).

7. Common rollout-period issues

The November 2024 – February 2025 rollout windows surfaced a recurring set of operational issues that brokers and back-office vendors had to remediate. Documenting them here is useful for any broker undergoing a similar regulatory-driven account-structure change.

7.1 Primary-demat UCC mismatch

Symptom: Direct payout file routes to wrong demat or fails verification. Cause: UCC primary-demat-mapping field stale or never populated. Remediation: UCC database update; re-submit primary-demat per client. Most brokers had to run a sweep against their full active-client base in October 2024 to populate / correct the field.

7.2 TM CUSPA / TM CSMFA opened in only one depository

Symptom: Pay-out works for CDSL clients but fails for NSDL clients (or vice versa). Cause: TM CUSPA / TM CSMFA opened only in the broker’s primary depository. Remediation: Open in the other depository per NCL/CMPT/65100 (which reiterates the requirement to keep pool accounts active in both depositories).

7.3 Chart-of-accounts not updated

Symptom: Settlement reconciliation reports show “unaccounted” balances; daily client ledger imbalances. Cause: Back-office still using the single legacy pool account ledger head. Remediation: Chart-of-accounts patch; rebuild reconciliation queries.

7.4 RMS not aware of TM CUSPA pledge

Symptom: Unpaid-client securities marked as “free” in client demat after direct credit; margin computation excludes them despite the pledge. Cause: RMS reading depository demat balance but not the pledge-lien overlay. Remediation: RMS update to subtract pledged quantity from “available” quantity for margin purposes. This is one of the more subtle integration issues; brokers using third-party RMS had to wait for vendor patches.

7.5 Internal-shortage valuation not paid by noon

Symptom: Clearing corp issues penalty / close-out cost; broker’s CM ledger shows unexpected debit. Cause: Manual process for SP+20% valuation; missed noon cut-off. Remediation: Automate the internal-shortage valuation and pay-in within the settlement-day morning batch.

7.6 Pre-CM-pool-separation NSDL setup

Symptom: NSDL demat-verification with exchanges fails for proprietary trades. Cause: Proprietary UCC primary demat is the same DP-ID-Client-ID as the NSDL CM pool account. Remediation: Open a separate primary demat for proprietary UCC; re-submit UCC mapping. The NCL/CMPT/69455 requirement (Aug 2025) surfaced this for many brokers.

7.7 Custodian-cleared clients erroneously included

Symptom: Custodian raises objection; FPI client positions not allocated correctly. Cause: Broker tagged custodian-cleared clients as direct-payout eligible. Remediation: Client-type flag review; explicit exclusion of custodian-cleared CP codes.

7.8 Pledge release lag

Symptom: Client pays for unpaid securities but the pledge in TM CUSPA isn’t released for hours / days. Cause: Manual / batch pledge-release process. Remediation: Automate pledge release on client payment confirmation. The Oct 2025 CDSL automation (IV-EP and IV-RD per SEBI/HO/MIRSD/MIRSD-PoD/P/CIR/2025/82 and the CDSL/NSDL automated pledge mechanism — see CDSL MTF & Pledge primer sections 8.1 – 8.3) automates much of this.

Practical notes

[gotcha] TM CUSPA, CM CUSPA, and TM CSMFA each have distinct sub-status codes at CDSL / NSDL. CDSL CUSPA uses sub-status code 40 per the CDSL MTF & Pledge primer Section 11. The CSMFA account has a separate sub-status. Brokers that didn’t get the sub-status configuration right at account opening had to close and re-open accounts during the rollout window.
[industry typical] Most brokers ran their internal reconciliation in parallel — legacy pool flow and direct-payout flow — for the first one to two settlement cycles after each phase activation, to catch mapping issues. The parallel-run discipline is a standard pattern for regulatory-driven custody changes.
[risk trade-off] The direct-payout regime makes broker default less harmful to client securities but it doesn’t eliminate broker risk entirely. Unpaid-client and MTF balances still sit in TM CUSPA / TM CSMFA, and the broker’s invocation rights on those balances are economically the same as before. Risk shifted, didn’t disappear.
[gotcha] NCL/CMPT/69455 (Aug 2025) — separating the proprietary-UCC primary demat from the NSDL CM pool DP-ID-Client-ID — surfaced an issue many brokers didn’t realise existed until they started having NSDL pay-out verification failures. The fix is a separate demat account; the underlying lesson is that NSDL keys direct-payout differently from CDSL.
[cost optimization] Brokers that did a clean chart-of-accounts cutover in the August – October 2024 window reported settlement reconciliation faster than pre-mandate (gross pay-in to CC + automated reconciliation of CC allocation against depository confirmation, vs. the legacy two-step push). Brokers that delayed the chart-of-accounts work or relied on the back-office vendor’s default mapping had reconciliation breaks for weeks.
[industry typical] The Oct 2025 automated-pledge-release mechanism (IV-EP for invocation of pledged securities for early pay-in; IV-RD for invocation for redemption) under SEBI/HO/MIRSD/MIRSD-PoD/P/CIR/2025/82 is the natural complement to direct-payout: when a client sells a pledged security, the pledge release and the early-pay-in block happen in a single automated instruction rather than via a manual unpledge-then-sell flow. See the CDSL primer Section 8 for the full PR-EP / IV-EP / IV-RD walkthrough.
[gotcha] Internal-shortage close-out under NCL/CMPT/66779 is settlement price + 20% — paid by noon on settlement day. Brokers that processed this manually via cheque or end-of-day NEFT missed the cut-off and faced additional penalties. Automate via the settlement bank’s morning batch or via the CC’s direct debit facility where available.
[industry typical] Client communication templates were updated through the rollout: pay-out SMS / email now references “credited directly to your demat by [depository]” rather than “credited via your broker.” Clients exposed to the change without communication briefly complained about not receiving the legacy broker-side credit confirmation; most brokers added an additional internal email confirming receipt by the broker’s back-office as a transitional courtesy.

Cross-references

Broker Process Narrative — Section 3 (Settlement Cycle) — chronological context
Integration DAG — EOD & settlement — SET-PAYOUT-RECV node detail
Compliance Blueprint — Settlement domain — obligations SETTLEMENT-004 / 005 / 022
T+0 / T+1 settlement deep dive — sibling page on the settlement cycle
Client funds upstreaming deep dive — funds layer counterpart
Payin default + Core SGF deep dive — what happens when the gross pay-in fails
MTF operational deep dive — CSMFA and MTF custody flow
CDSL MTF & Pledge primer — depository-side pledge mechanics
Circulars — SEBI MIRSD — June 2024 direct-payout authority
Circulars — Clearing corps — NSCCL / ICCL operational guidelines

Verified through

2026-05-14

AI-generated and not legal, financial, or compliance advice. See the project README for full disclaimer.

Built by Rakesh Waghela — Technology & Product Consultant

Available for consulting and collaboration on technology, product strategy, and system architecture. Connect on LinkedIn.

Disclaimer: This documentation was generated using Claude Code, an AI-powered LLM by Anthropic, as a research and capability estimation exercise. AI models can hallucinate — information here may be inaccurate, incomplete, or outdated. Any resemblance to the products or documentation of any specific vendor or organization is purely coincidental and unintended. This project is not directly inspired by any particular product, vendor, or proprietary system, and no plagiarism is intended. All content is based on publicly available information. This is not legal, financial, or compliance advice.