Supreme Court of India · 2016
Pegasus Assets Reconstruction Pvt Ltd v. Haryana Concast Ltd
(2016) 4 SCC 47
Court
Supreme Court of India
Bench
2-Judge Bench
Date
2016
Citation
(2016) 4 SCC 47
Background & Facts
Haryana Concast Ltd — a steel manufacturing company — had availed substantial credit facilities from a consortium of banks. When the account was classified as Non-Performing, the lead bank and consortium members assigned the debt along with the underlying security interests to Pegasus Assets Reconstruction Pvt Ltd, an Asset Reconstruction Company (ARC) registered with the Reserve Bank of India under Section 3 of the SARFAESI Act. Pegasus paid acquisition consideration for the NPA account and received an assignment deed conveying all rights, title, and interest in the debt and the security.
Pegasus then issued a notice under Section 13(2) of the SARFAESI Act as the new secured creditor. Haryana Concast challenged the SARFAESI enforcement on multiple grounds: (i) that the assignment of the debt to an ARC was invalid without the borrower's consent; (ii) that the ARC did not have the same enforcement rights as the original bank; and (iii) that procedural defects in the assignment vitiated the entire SARFAESI action. The DRT entertained these objections under Section 17.
The Supreme Court was called upon to definitively settle the legal status of ARCs in SARFAESI proceedings and the extent to which a borrower can raise the assignment itself as a defence to enforcement. Given the large volume of NPA portfolio acquisitions by ARCs (totalling tens of thousands of crores of rupees annually), this judgment has enormous practical significance for the Indian debt recovery market.
Key Issues Before the Court
Holdings of the Court
Holding 1 — ARC Steps into Original Secured Creditor's Shoes
The Supreme Court held that upon valid assignment of an NPA account to a registered ARC, the ARC steps fully and completely into the shoes of the original secured creditor. All rights, powers, privileges, and remedies available to the original bank — including the full range of SARFAESI enforcement rights under Section 13 — vest in the ARC upon assignment. The ARC becomes the "secured creditor" for all purposes of the SARFAESI Act from the date of assignment. There is no need for any fresh registration of the mortgage or security interest in the name of the ARC.
Holding 2 — Borrower's Consent Not Required for Assignment
The Court held that the assignment of a debt from a bank to an ARC does not require the borrower's prior consent. Under Section 5 of the SARFAESI Act, a bank or financial institution is entitled to transfer financial assets by way of assignment in favour of a registered ARC without any need to obtain the borrower's agreement or approval. The assignment is effective upon execution and need not be communicated in advance to the borrower, though notice of the assignment is necessary for the borrower to pay to the correct party going forward.
Holding 3 — Borrower Cannot Challenge Assignment in SARFAESI Proceedings
The Court held that a borrower cannot raise the validity of the debt assignment as a substantive defence to SARFAESI enforcement proceedings under Section 17 before the DRT. The borrower's remedy in respect of any grievance about the assignment is a separate civil suit — it is not a matter that can delay or defeat the SARFAESI enforcement action. This holding is significantly adverse to borrowers, as it forecloses one of the most commonly raised defences against ARC enforcement, limiting the Section 17 challenge to the manner of enforcement rather than the entitlement to enforce.
Holding 4 — Procedural Compliance with RBI Guidelines Is Mandatory
While broadly upholding ARC rights, the Court emphasised that the assignment process must comply with the SARFAESI Act (Chapter II), RBI guidelines on securitisation and asset reconstruction, and the terms of the Security Receipt issued by the ARC. An assignment that is procedurally defective — such as one executed without proper board authorisation, without an appropriate due diligence, or without compliance with RBI regulations — may be vulnerable to challenge. ARCs must ensure complete procedural compliance at the time of NPA acquisition to insulate their enforcement from legal attack.
Practical Implications for Creditors
Pegasus is the definitive authority confirming that ARCs can enforce SARFAESI rights after NPA acquisition with the same power as the original bank. Banks selling NPA portfolios to ARCs can do so without borrower consent, and the ARC acquirer can immediately issue Section 13(2) notices upon completing the assignment. ARCs should maintain a complete paper trail of the assignment — including the assignment deed, security receipt, board resolution, and RBI compliance — to defend any procedural challenge.
For borrowers, this judgment narrows the defences available when facing enforcement by an ARC. However, ARCs must still comply with all SARFAESI procedural requirements in the enforcement process itself — including the 60-day notice period, valuation requirements, and auction procedure. Borrowers can challenge enforcement actions by ARCs under Section 17 on the ground of non-compliance with the enforcement procedure, even if they cannot challenge the assignment itself in those proceedings.
Relevant Statutory Provisions
Practical Application Note
If you are an ARC that has acquired NPA accounts and requires enforcement support, or if you are a borrower/promoter facing SARFAESI enforcement by an ARC (such as Phoenix ARC, Edelweiss ARC, or JM Financial ARC), Unified Chambers has the expertise to advise you on both sides. We regularly advise ARCs on enforcement strategy and borrowers on mounting the most effective Section 17 challenge against procedurally defective ARC enforcement.