Closure date

A pledge is not meant to last forever without confirmation. The pledgor, when creating it, states roughly how long the arrangement is expected to run.

That expected duration is entered on the Pledge Request Form as the closure date. It is not a hard, automatic expiry that cancels the pledge on its own. Instead, it sets a deadline for the pledgee's DP to confirm the pledge before that date passes.

This rule works a little differently at NSDL than at CDSL.

When the pledgor submits the Pledge Request Form, it includes the closure date of the pledge/hypothecation, which the workbook describes as "indicative of the duration of pledge/hypothecation", alongside the securities details, the agreement number and the pledgee's details.

Only 1 closure date is entered per Pledge Request Form, and the pledgee's DP must confirm creation of the pledge before that date passes — with the specific carve-out that this confirmation deadline is not applicable in the case of NSDL.

The closure date reappears at the un-pledge stage too: one of the listed reasons a pledgee may reject a closure request is "Un-pledge / Closure date not accepted", meaning the date entered on the closure instruction does not match what the pledgee's own records or agreement expect.

Mr Iyer pledges 600 shares worth Rs 2,88,000, at Rs 480 each, on 1 April, entering a closure date of 30 June on the Pledge Request Form to indicate he expects the loan, and the pledge, to run for roughly three months.

If this pledge is being processed through a depository where the confirmation deadline applies, the pledgee's DP must confirm creation of the pledge before 30 June — if it fails to do so, the pledge request lapses unconfirmed. Had Mr Iyer's pledge instead been processed through NSDL, this deadline simply would not bind the pledgee's DP at all, since NSDL is expressly carved out of the rule.

When Mr Iyer later repays the loan and submits a closure request quoting a different closure date than the one recorded on the original pledge, the pledgee's DP can reject the closure specifically on the ground of "closure date not accepted".

Chapter 9, section 9.2.2, introduces the closure date as a field on the Pledge Request Form, and section 9.2.3's discussion of pledge confirmation ties it directly to the pledgee DP's confirmation deadline, with the explicit NSDL exception. Section 9.2.4's rejection-reasons list then repeats it as a specific ground for rejecting an un-pledge request.

Expect a question on what the closure date represents (the indicative duration of the pledge, used as a confirmation deadline) and on the NSDL carve-out — the confirmation deadline tied to the closure date does not apply there.

• The closure date is "indicative", not an automatic self-cancelling expiry — its main legal effect is as a deadline for the pledgee's DP to confirm the pledge.
• The confirmation-deadline rule tied to the closure date does not apply in NSDL — a detail the workbook states explicitly and that examiners like to test.
• A mismatched closure date is a specific, named ground for rejecting a closure/un-pledge request, distinct from a mismatched agreement number, which is a separate rejection ground on the same list.
• Do not confuse closure date with execution date, which is the date a specific instruction is to be carried out, not the expected overall duration of the pledge.