CDSL communiqué CDSL/OPS/DP/POLCY/2026/470, dated 15 July 2026, makes the DARPAN registration ID a mandatory field for certain non-profit demat accounts. Functionality is tentatively scheduled to go live on 07 August 2026.
Where it came from
This traces back to SEBI’s AML/CFT circular of 06 June 2024 — part of the obligations securities intermediaries carry under the Prevention of Money Laundering Act — which CDSL first passed on to Participants in June 2024. That circular required every registered intermediary to register a client’s DARPAN ID on the NITI Aayog portal whenever the client is a non-profit organisation. The July 2026 communiqué is CDSL now building that requirement into the depository system itself, with a defined field and a defined scope of accounts.
What the circular asks for
- DARPAN Registration ID becomes a mandatory field, but only for accounts under two specific Status–Sub Status combinations: Sub-status 264 (Charitable Institution, Non-NPO, linked to Status 29 – Trust) and Sub-status 265 (Charitable Institution, NPO, linked to Status 25 – Corporate).
- For new accounts opened under either category, the field is mandatory at account opening.
- For existing accounts already carrying one of these sub-statuses, the field becomes mandatory the next time the account is modified.
- DPs must retain the DARPAN registration record for five years after the account closes.
- The field enters UDIFF Catalogue version 3.0.1.2.
Worth pointing out
Sub-status 264 is literally labelled “Charitable Institution (Non-NPO),” yet it’s in scope for the same mandatory DARPAN capture as 265, which is labelled “Charitable Institution (NPO).” Read quickly, the “Non-NPO” name suggests it’s out of scope. It isn’t — CDSL’s table lists both. A back office that filters its scope by scanning sub-status descriptions for “NPO” rather than checking the actual code list would miss one of the two categories the circular covers.
What we’re doing at KCS
This is a routine regulatory update, and it’s currently in progress ahead of the tentative 07 August go-live.
In DEBOS, the work is:
- Parsing and incorporating the DARPAN ID field from the UDIFF catalogue v3.0.1.2 update.
- Adding the field to the client master against both sub-status 264 and sub-status 265, so it’s stored as part of the client record and available for the five-year retention CDSL asks for.
- Updating the account-opening and account-modification screens so the field is enforced as mandatory for these two sub-statuses specifically — not applied depository-wide.
In one line: for NPO and charitable-trust accounts under sub-status 264 and 265, DARPAN registration is now a captured, retained field in the client master, not a manual NITI Aayog lookup left outside the system.
