ValkyaEditorial
Supreme Court

Bank of Bihar v. Damodar Prasad: the surety's liability is immediate and co-extensive

Decided on 8 August 1968, the Supreme Court set aside a trial-court direction that a bank could enforce a decree against a surety only after exhausting its remedies against the principal debtor. Under section 128 of the Indian Contract Act, 1872, the surety's liability is co-extensive with the principal debtor's and, absent a contract to the contrary, immediate — not deferred, not conditional, and not contingent on the creditor's success or failure against the borrower first.

Valkya Editorial· Legal Intelligence··6 min read
Court
Supreme Court of India
Citation
AIR 1969 SC 297; 1969 SCR (1) 620
Bench
R.S. Bachawat, J., S.M. Sikri, J., K.S. Hegde, J.
Decided
8 August 1968

Bank of Bihar Ltd. v. Damodar Prasad is the case Indian courts still reach for first whenever a surety, sued on a guarantee, tries to buy time by insisting that the creditor go after the borrower first. The Supreme Court's answer, delivered in 1968, is short and has never needed revisiting: that is not how a guarantee works, and a court has no business rewriting a decree to say otherwise.

A guarantee, a default, and a trial court's condition

The Bank of Bihar had lent money to Damodar Prasad. Paras Nath Sinha stood as surety on a guarantee bond dated 15 June 1951, undertaking to pay and satisfy the borrower's liabilities within two days of demand. The debt fell into default, and by the time the Bank sued, the outstanding sum stood at roughly Rs. 11,723.56 towards principal and Rs. 2,769.37 towards interest.

The Bank sued both the borrower and the surety in the Court of the Subordinate Judge at Patna and obtained a decree against both. But the trial court attached a condition to the decree against the surety: the Bank would be at liberty to enforce it against Paras Nath Sinha only after it had first exhausted its remedies against Damodar Prasad. The Patna High Court, on appeal, left that condition in place. The Bank carried the matter to the Supreme Court, challenging the condition itself — not the decree, not the amount, not the existence of the guarantee, but the sequencing the courts below had imposed on its enforcement.

What the Court held

The Court set aside the direction imposed by the trial court and affirmed by the High Court. The Bank was entitled to enforce its decree against the surety without first exhausting its remedies against the principal debtor — the condition had no basis in the contract of guarantee, which contained no such stipulation, and none in the general law, which affirmatively points the other way.

Why the sequencing question actually matters

It is easy to read the holding as a technical point about decree execution and miss why the case became a landmark. A guarantee exists, commercially, precisely so that the creditor does not have to run the principal debtor's insolvency gauntlet before getting paid. If a court can graft onto a guarantee decree a condition that the creditor must first chase the principal debtor to exhaustion — through attachment, sale, insolvency proceedings, however long that takes — the guarantee stops functioning as security and starts functioning as a second, delayed claim that only matters after the first one has failed. That defeats the instrument's entire commercial purpose: a bank lends against a guarantee because the guarantee gives it an immediate, parallel claim, not a claim that ripens only once the primary debtor has been proven unable to pay.

Bank of Bihar draws the line cleanly. The surety's liability is co-extensive — equal in extent, not subordinate in priority — to the principal debtor's, and it is immediate. The one carve-out the Court preserved is textual and deliberate: parties are free to write a different sequence into the guarantee itself. Section 128 says "unless it is otherwise provided by the contract," and a guarantee that expressly requires the creditor to proceed against the principal debtor first, or that caps the surety's exposure, or that makes the surety's liability conditional on some other event, will be enforced on its own terms. What a court cannot do is impose that sequencing where the contract itself is silent.

The doctrine's continuing life

More than half a century on, Bank of Bihar remains the starting citation whenever an Indian court is asked to determine whether a guarantor can insist on the creditor exhausting remedies against the borrower first — a question that recurs constantly in bank-guarantee litigation, SARFAESI enforcement against guarantors, and, more recently, personal-guarantor insolvency under the Insolvency and Bankruptcy Code, 2016. The proposition that a resolution plan approved for the corporate debtor does not, by itself, discharge the personal guarantor rests on the same footing: the guarantee is an independent contract, and the surety's liability under section 128 is not extinguished merely because the principal debtor's liability has been compromised, restructured, or discharged by an involuntary process of law. Courts examining that question continue to trace the co-extensive, immediate character of surety liability back to this 1968 judgment before applying it to the resolution-plan or moratorium context in front of them.

For lenders, the practical lesson has not changed since 1968: a guarantee is worth drafting carefully if a different sequence — creditor-exhausts-principal-first, a liability cap, a time limit on demand — is actually wanted, because absent that language, the default rule favours the creditor's freedom to proceed against whichever party it chooses, in whichever order it chooses, the moment the principal debtor defaults. For sureties, the lesson is equally direct: signing a guarantee without a contrary stipulation means accepting exposure that is immediate and full, not a fallback position that only matters if the principal debtor cannot pay.

Sources

  1. SCC OnLine Blog — on the co-extensive nature of guarantor liability under section 128: https://www.scconline.com/blog/post/2017/10/30/liability-guarantor-co-extensive-principal-debtor-borrower-right-recover-dues-guarantor/
  2. SCC OnLine Blog — on continuation of proceedings against guarantors independent of the principal debtor's insolvency: https://www.scconline.com/blog/post/2020/11/02/del-hc-is-the-liability-of-principal-borrower-and-guarantor-co-extensive-court-reiterates-scs-position-on-continuation-of-sarfaesi-proceedings-against-guarantor-by-banks/

Related reading

Supreme CourtSupreme Court of India

Lalit Kumar Jain v. Union of India: personal guarantors, conditional legislation, and the surety's independent liability

On 21 May 2021 a two-judge bench of the Supreme Court, in Lalit Kumar Jain v. Union of India, upheld the Central Government's MCA Notification of 15 November 2019 selectively bringing Part III of the Insolvency and Bankruptcy Code into force for personal guarantors of corporate debtors as valid conditional legislation, and held that approval of a resolution plan for a corporate debtor under Section 31 does not, of itself, discharge a personal guarantor — surety liability rests on the independent footing of Section 128 of the Contract Act. A close reading of the judgment authored by Justice Ravindra Bhat, the doctrinal architecture of the Section 60(2) common-forum design, and the doctrinal arc through Dilip B. Jiwrajka.

Valkya Editorial··13 min
Supreme CourtSupreme Court of India

Vijay Rajmohan v. State (CBI): the s.19 sanction time-limit is mandatory, but delay does not quash the prosecution

On 11 October 2022 a two-judge Bench of the Supreme Court answered two questions on the sanction to prosecute a public servant under Section 19 of the Prevention of Corruption Act 1988. It held that the three-month period for deciding a sanction request — extendable by one month where legal consultation is required — is mandatory, yet that a failure to sanction in time does not vitiate or quash the prosecution. The consequence of delay is the accountability of the defaulting officer, subject to judicial review and CVC action, not the acquittal of the accused.

Valkya Editorial··8 min
Supreme CourtSupreme Court of India

Vanshika Yadav v. Union of India (2024): the NEET-UG paper-leak case and the systemic-breach threshold

Following disclosures of a paper leak at examination centres in Patna and Hazaribagh during the NEET-UG 2024 examination, a batch of writ petitions sought cancellation of the entire examination and a fresh test for the roughly 23.3 lakh candidates who had appeared. The Supreme Court declined to order a re-test. It held that a leak had in fact occurred, but that the material on record — including a CBI status report and a data-analytics comparison across examination years — did not establish that the breach was systemic or that it had vitiated the integrity of the examination as a whole. The Court separately resolved a disputed Physics answer-key question through an IIT Delhi expert panel, directed the National Testing Agency to revise results and ranks accordingly, and constituted a high-level committee to recommend structural reforms to examination conduct.

Valkya Editorial··9 min
Research this line of authority in Valkya

Trace how this proposition has been treated across Indian courts — citations, bench strength, and subsequent history — in one workspace built for litigators.

Open Valkya →