The BSDA Opt-Out Consent Field: What NSDL Changed and What We Did About It

NSDL circular NSDL/POLICY/2026/0036 makes it mandatory to capture how and when a BSDA-eligible investor consented to opt out of a low-cost account. KCS incorporated the new UDIFF consent-mode field into DEBOS's client master and opt-out capture screens.

SEBI wants it on record when an investor who qualifies for a low-cost Basic Services Demat Account (BSDA) chooses not to have one. NSDL circular NSDL/POLICY/2026/0036, dated 18 March 2026, is how that requirement reached Depository Participants.

Where it came from

SEBI’s circular of 24 December 2025 asked depositories to make BSDA opt-out an explicit, recorded choice rather than an implicit one. NSDL passed this to Participants first in December 2025, and then followed up in March 2026 with the actual system change: a new field, a new UDIFF catalogue version, and a short window to adopt both.

What the circular asks for

Two things, in plain terms:

  • Consent Mode — a new mandatory field capturing how the investor’s opt-out consent was received: Email, Physical form, or Online/Mobile App.
  • Consent Date — the date that consent was received, now in its own named field (ClntBsdaOptOutDt) instead of a general-purpose reserved column.

Both apply whenever a BSDA-eligible investor opts out, and both had to go into UDIFF Catalogue version 3.0.1.1.

What we did at KCS

This was a BAU regulatory update for us — not a large piece of work, just one that needed to be done carefully and on time.

In DEBOS, we:

  • Parsed and incorporated the new CnsntMode field from the UDIFF catalogue update, alongside the move of the consent date out of the reserved field into its own named one.
  • Added both fields to the client master, so the mode and date of an investor’s opt-out consent are now stored and carried forward as part of the client record — not just noted somewhere and forgotten.
  • Updated the front end where the opt-out is actually captured, so the operator recording the consent selects the mode at the point of entry, at account opening or client modification.

The consent date needed a bit more care, since it was moving out of a reserved field into a named one. Reserved fields are the generic slots a file format sets aside for future use — when a requirement shows up before the format has a proper place for it, the data goes into a reserved column in the meantime. Once that field is formally promoted, older records still carry the value in the reserved column, so both the old and new locations had to be handled correctly rather than just switching over on a given date.

In one line: an investor’s choice to opt out of a BSDA, and how and when they made it, is now captured, stored, and auditable in the client master — not left to a reserved field and a paper trail.