Delhi High Court: A Division Bench of Hima Kohli and Subramonium Prasad, JJ., considered the following question:

Whether a bank/financial institution can institute or continue with proceedings against a guarantor under the Securitisation and Reconstruction of Financial Assets and Enforcement of Security Interest Act, 2002 (SARFAESI Act), when proceedings under the Insolvency and Bankruptcy Code 2016 (IB Code) have been initiated against the principal borrower and the same are pending adjudication?

Respondent 4 was the principal borrower in the present case who had obtained loans from the State Bank of India. Guarantor was the wife of the promoter of the principal borrower. Further, it has been stated that the bank filed an insolvency petition against the principal borrower under the provisions of the IB Code before the NCLT, Delhi.

At the time of pendency of the insolvency proceedings against the principal borrower, bank issued a notice under Section 13(2) of the SARFAESI Act to the petitioner and another notice under Section 13(4) of the SARFAESI Act was also issued. Both the notices were challenged by the petitioner.

The above-stated notices were challenged before Debts Recovery Tribunal but were later withdrawn in light of negotiation talks between the Bank and the Principal Borrower.

Petitioner alleged that without issuing a Notice under Section 1(4) of SARFAESI Act, the Bank issued  Sale Notice under Rule 8 (6) of Security Interest (Enforcement) Rules for sale of her residential house.

In the instant matter, the prime question for consideration was confined to the action of the Bank of initiating proceedings against the petitioner under the SARFAESI Act when insolvency proceedings have been initiated against the Principal Borrower under the IB Code and the same are pending before the NCLT.

Analysis & Decision

Bench referred to the relevant provisions, Sections 14 and 31 of the IB Code and Section 128 of the Contract Act.

Section 14 of the IB code related to Moratorium, Section 31 of the IB Code refers to the approval of the resolution plan and Section 128 of the Contract Act provides the Surety’s liability.

Section 128 of the Contract Act provides that the liability of a Guarantor is coextensive with that of the Principal Debtor.

Bench cited the decision of Industrial Investment Bank of India Ltd. v. Biswanath Jhunjhunwala, (2009) 9 SCC 478.

Court held that since the liability of a guarantor is co-extensive with that of the principal debtor and not in the alternative, it cannot be said that proceedings in the NCLT against the principal debtor can be a bar to institution or continuation of proceedings against the guarantor under the SARFAESI Act.

Bench stated that the question raised with regard to whether the bank can proceed against a guarantor even after initiation of proceedings under the IB Code also stands settled and is squarely covered by the Supreme Court’s decision in SBI v. V. Ramakrishan, (2018) 17 SCC 394.

The above-cited decision holds that Sections 14 and 31 of the IB Code do not bar initiation and continuation of the SARFAESI proceedings against the Guarantor.

View of the Supreme Court amply demonstrated that neither Section 14 nor Section 31 of the IB Code place any fetters on banks/Financial Institutions from initiation and continuation of the proceedings against the guarantor for recovering their dues.

Therefore, Court held that,

“…petitioner cannot escape her liability qua the respondent/Bank in such a manner. The liability of the principal borrower and the Guarantor remain co-extensive and the respondent/Bank is well entitled to initiate proceedings against the petitioner under the SARFESI Act during the continuation of the Insolvency Resolution Process against the Principal Borrower.”

In view of the above, no merit was found in the petition and hence was dismissed. [Kiran Gupta v. State Bank of India, 2020 SCC OnLine Del 1390, decided on 02-11-2020]

Join the discussion

Leave a Reply

Your email address will not be published. Required fields are marked

This site uses Akismet to reduce spam. Learn how your comment data is processed.