All NotesCivil LawIndian Contract Act, 1872 (ICA)

Indian Contract Act, 1872 (ICA)

Contingent Contract vs Absolute Contract

Contingent Contract vs Absolute Contract: When an Obligation Is Immediate and Unqualified, the Rule in Paradine v. Jane, Implied Conditions, and the Relationship with Section 56 of the Indian Contract Act, 1872

An absolute contract is one in which the obligation is immediate and unqualified: the promisor must perform, and the fact that performance has become difficult, expensive or pointless is no answer. A contingent contract makes the obligation depend on a collateral event that may never occur. The distinction determines what a party must do, when he must do it, and what happens when circumstances change. It also explains the historical development of the law of frustration, because the hard edges of the absolute contract rule were softened first by implying conditions into contracts and then, in India, by the positive rule in Section 56.

1. The Two Categories

Point of difference

Absolute contract

Contingent contract

When the obligation arises

Immediately on the making of the contract

Only when the collateral event happens, or its happening becomes impossible under Section 33

Governing provisions

Sections 37 and 51 to 58 on performance and reciprocal promises

Sections 31 to 36

Effect of the event not occurring

Not applicable; there is no event on which the obligation depends

The contract becomes void under Section 32 or Section 35

Effect of non-performance

Breach, sounding in damages under Section 73

No breach where the contingency simply fails; the remedy is restitution under Section 65

Effect of supervening impossibility

The contract becomes void under the second paragraph of Section 56

The contract becomes void under Section 32 if the event becomes impossible

Suit brought before the event

Maintainable once the time for performance arrives

Premature, and liable to be dismissed

Typical example

A sale of goods for cash on a stated date

A sale conditional on a licence being granted

When the obligation arises, and what happens when performance becomes impossible

2. The Strict Rule of Absolute Obligation

📖 Paradine v. Jane, (1647) Aleyn 26

Facts: A tenant was sued for arrears of rent. He pleaded that for a period covering most of the term he had been dispossessed of the land by an invading army, so that he had been unable to take the profits and had derived no benefit from the holding.

Held: The plea was rejected and the tenant remained liable for the rent throughout. Where a party by his own contract creates a duty upon himself, he is bound to make it good notwithstanding any accident by inevitable necessity, because he might have provided against it by his contract. The law will not excuse a party from an obligation he has undertaken in unqualified terms merely because events have made performance valueless or impossible.

Ratio: A contractual obligation expressed in absolute terms is not discharged by supervening events. A party who wishes to be protected against a contingency must stipulate for it.

Two features of the rule should be noted. It rests on risk allocation: the party who undertook the obligation is taken to have accepted the risk of events he did not exclude. And it produces a strong incentive to draft, which is why commercial contracts contain force majeure clauses, conditions precedent and material adverse change provisions. The parties convert what would otherwise be an absolute obligation into a contingent one.

3. The Softening of the Rule

📖 Taylor v. Caldwell, (1863) 3 B & S 826

Facts: The defendants agreed to let the plaintiffs have the use of a music hall and gardens on four specified days for concerts. Before the first of those days the hall was destroyed by fire without the fault of either party. The plaintiffs, who had spent money on advertising and preparations, sued for breach.

Held: The action failed. Where a contract depends on the continued existence of a particular person or thing, and the contract contains no express or implied warranty that the thing shall exist, the parties are taken to have contracted on the footing of an implied condition that the thing shall continue to exist. Its destruction without the fault of either party excuses both from performance. Blackburn J treated the rule in Paradine v. Jane as applying only to obligations that are positive and absolute, and not to those subject to such an implied condition.

Ratio: An obligation is not absolute where the contract presupposes the continued existence of a specific thing. The destruction of that thing without fault discharges both parties by operation of an implied condition.

3.1 The Indian position rests on Section 56

Taylor v. Caldwell worked by implying a condition into the contract, so as to convert what appeared absolute into something conditional. Indian law reached the same practical result by a different route. The second paragraph of Section 56 states a positive rule of law: a contract to do an act which, after the contract is made, becomes impossible or unlawful by reason of some event which the promisor could not prevent, becomes void when the act becomes impossible or unlawful.

The Supreme Court made the point explicitly in Satyabrata Ghose v. Mugneeram Bangur & Co., AIR 1954 SC 44, holding that frustration in India rests on Section 56 and not on the English theories of implied term or of the disappearance of the foundation of the contract, and that English decisions have persuasive value only so far as they illuminate the statutory language. The practical consequence is that in India a court does not ask what term the parties would have agreed; it asks whether the statutory condition is satisfied.

⚠ Frustration and contingency are different mechanisms

Both can result in a contract becoming void, and they are easily confused because the outcome looks the same. A contingent contract was conditional from the outset: the parties identified an event and made the obligation depend on it, and Section 32 makes the contract void if that event becomes impossible. A frustrated contract was absolute when made and became impossible afterwards through an event the parties did not provide for, and the second paragraph of Section 56 makes it void at that point. The difference decides who bears the risk of an event the contract did address: where the parties allocated it by a force majeure clause, the clause governs and Section 56 has no application, as Energy Watchdog v. CERC, (2017) 14 SCC 80 holds.

4. Identifying an Absolute Obligation

  1. The language is unqualified. The promisor agrees to do something, without any words making performance depend on an external event.
  2. Any condition relates to the manner or time of performance, rather than to whether performance is due at all. An obligation to deliver by a stated date is absolute with a time limit, not contingent.
  3. The event relied on is one the promisor could have provided against. Paradine v. Jane treats the failure to stipulate as an acceptance of the risk.
  4. The obligation is to pay money. Payment obligations are almost always absolute, since money is never impossible to obtain in the legal sense, and financial hardship does not excuse.
  5. A party's own act or default cannot create a contingency. An obligation that would otherwise be absolute is not converted into a contingent one because the promisor has made performance difficult for himself.

5. Where the Distinction Matters

  • Maintainability of the suit. A suit on a contingent contract before the event has happened is premature. A suit on an absolute contract lies as soon as the time for performance passes without performance.
  • The remedy. Failure of a contingency produces voidness and restitution under Section 65. Failure to perform an absolute obligation produces a breach and damages under Section 73.
  • Anticipatory breach. An absolute contract may be repudiated before the time for performance under Section 39, and so may a contingent one before the contingency occurs, per Frost v. Knight, (1872) LR 7 Ex 111.
  • Limitation. Time runs from the date fixed for performance in an absolute contract, and from the happening of the contingency where the contract is contingent, which can make a decisive difference to whether a suit is in time.
  • Specific performance. A contingent contract will not be specifically enforced before the contingency occurs, since no obligation has yet arisen to enforce.

6. Drafting: Turning One into the Other

Commercial drafting is largely the business of converting absolute obligations into contingent ones, and the choice of device matters because each produces a different legal result.

Device

Effect

Result if the event occurs or fails

Condition precedent to the contract

No contract comes into existence until the condition is satisfied

If the condition fails there is no contract and nothing to restore beyond deposits

Condition precedent to the obligation

The contract exists but the obligation does not arise until the condition is satisfied

Section 32 applies; the contract becomes void if the condition becomes impossible

Condition subsequent

The obligation exists and is defeated on the happening of the event

Performance is due until the event; on its happening the obligation determines

Force majeure clause

The parties allocate the risk of specified events themselves

The clause governs and Section 56 does not apply, per Energy Watchdog

Best endeavours or reasonable endeavours obligation

The promisor undertakes to try, not to achieve

Failure of the outcome is not a breach if the required efforts were made

7. The Position Stated Shortly

  1. An absolute contract imposes an immediate and unqualified obligation; a contingent contract makes the obligation depend on a collateral event.
  2. Paradine v. Jane: a party who creates a duty by his own contract must make it good, and must provide against contingencies by the contract itself.
  3. Taylor v. Caldwell softened the rule by implying a condition that a specific thing essential to performance shall continue to exist.
  4. India reaches the same result by the positive rule in the second paragraph of Section 56, not by implying a term, per Satyabrata Ghose.
  5. Contingency and frustration differ in timing: the first is built into the contract at the outset, the second overtakes an absolute obligation afterwards.
  6. Where the parties have allocated the risk by a force majeure clause, the clause governs and Section 56 has no application.
  7. A suit on a contingent contract before the event is premature; a suit on an absolute contract lies once the time for performance passes.
  8. Failure of a contingency produces voidness and restitution; failure to perform an absolute obligation produces damages.
  9. Payment obligations are almost always absolute, and financial hardship does not excuse performance.

8. Related Topics and Provisions

Topic or provision

Connection

Contingent Contracts under Sections 31 to 36

The six provisions and their operation

Contingent Contract vs Conditional Promise

Conditions precedent, subsequent and concurrent

Principle of Sanctity of Contract

Why hardship does not excuse performance

Performance of Contracts under Sections 37 to 67

The obligation to perform and its excuses

Section 37, Indian Contract Act

The obligation of parties to perform

Sections 31 to 36, Indian Contract Act

Contingent contracts

Section 39, Indian Contract Act

Refusal by a party to perform wholly

Section 56, Indian Contract Act

Impossible acts and supervening impossibility

Sections 65 and 73, Indian Contract Act

Restitution and damages, the two different remedies