Freight-Retention “Corporate Guarantee” Enforceable as Contract of Guarantee; Bank Must Indemnify Customer via Third-Party Procedure for Erroneous Remittance Contrary to Mandate

A. Precedents Cited

i. Suretyship fundamentals: co-extensive liability; creditor’s election

The Court anchored its guarantee analysis in classic suretyship doctrine:

• Bank of Bihar Ltd. v. Damodar Prasad and others: The Court relied on this to reaffirm that the surety’s liability is immediate and co-extensive (Section 128), and the creditor need not first exhaust remedies against the principal debtor. This directly answered Archean’s implicit contention that the plaintiff should have proceeded against the vessel owner/operator first.
• State Bank Of India v. V. Ramakrishnan and Others: Cited to reiterate the “hallmark” of guarantee—creditor’s ability to proceed against principal debtor or surety “in no particular sequence”—and to place the case within the broader commercial rationale of guarantees.

ii. What qualifies as a guarantee: need for clear undertaking; construing mercantile instruments

• Phoenix ARC Private Limited v. Ketulbhai Ramubhai Patel and Maitreya Doshi v. Anand Rathi Global Finance Limited and another: Archean cited these to argue that Exhibit P11 lacked the unequivocal undertaking required for a guarantee. The Court held these decisions did not help Archean; they merely restate the need for a clear promise to discharge another’s liability on default.
• Asset Reconstruction Co. Ltd. v. Electrosteel Castings Ltd.: Used by the Court to set out the essential ingredients of Section 126 and to distinguish true guarantees from “see to it”/facilitation-type assurances. The Court then applied those criteria to hold that Archean’s documents were not mere facilitation but an enforceable undertaking to pay.

iii. Pleadings control evidence: new factual defences cannot be smuggled via evidence

• Union Of India v. Ibrahim Uddin and another and Ram Sarup Gupta (Dead) by LRs. v. Bishun Narain Inter College and others: The plaintiff invoked these to oppose Archean’s RBI-approval defence and other factual pivots not grounded in pleadings. The Supreme Court applied the principle: no amount of evidence can be looked into absent pleadings.

iv. Dominus litis and non-joinder: plaintiff’s choice of defendants; necessary vs proper parties

• Mumbai International Airport (P) Ltd. v. Regency Convention Centre & Hotels (P) Ltd.: Relied upon to reject Archean’s argument that the vessel owner was a necessary party. The Court emphasized that the plaintiff cannot be compelled to sue parties against whom it seeks no relief unless their presence is indispensable.
• Kanaklata Das And Others v. Naba Kumar Das And Others (with references within to Ruma Chakraborty v. Sudha Rani Banerjee and Anr. and Udit Narain Singh Malpaharia v. Additional Member Board of Revenue, Bihar and Anr.): Reiterated the tests for “necessary” and “proper” parties and reinforced the dominus litis rule.

v. Counterclaim limits and the alternative: third-party procedure

• Rohit Singh & Others v. State of Bihar and SANJAY TIWARI v. YUGAL KISHORE PRASAD SAO & Others: Cited to note that counterclaims are primarily against plaintiffs, and cross-claims among defendants are not the default procedural route.
• The Court then highlighted the procedural solution actually available on the Madras Original Side: Order VIII-A CPC (as incorporated) enabling third-party notices for contribution/indemnity—used here against the co-defendant bank.

B. Legal Reasoning

i. Exhibit P11 construed as a guarantee, not a mere “freight arrangement”

The Court treated the “Corporate Guarantee” (25.04.1998) alongside the earlier letter (22.04.1998) as a single commercial narrative: Archean explicitly assured that the money was “safe with us” and that it “would remit this money directly” to the plaintiff upon the agreed operational milestone (arrival/discharge at Newark).

Applying Sections 126–128 of the Contract Act, the Court held:

• The documents showed a clear undertaking to pay the plaintiff, satisfying Section 126’s requirement of discharging a third party’s liability in default.
• Consideration need not move to the surety; benefit to the principal debtor suffices (Section 127), and the guarantee remains an independently enforceable contract.
• The creditor may sue the surety without suing the principal debtor first (Bank of Bihar principle), defeating the “why not sue the vessel owner” argument.

ii. Estoppel by conduct against reliance on “Charter Party conditions”

Archean argued Exhibit P11 was “subject to Charter Party ... conditions and amendments” and that Clause 30 contemplated freight payment to Royal Swan, with no amendment permitting payment to the plaintiff. The Court held Archean’s own subsequent conduct—processing remittance, seeking approvals, instructing the bank to remit to the plaintiff—showed it did not treat the absence of amendment as disabling. Archean was therefore estopped from denying liability on that basis.

iii. Non-joinder of vessel owner not fatal; defendants cannot shift procedural burden to plaintiff

The Court held the vessel owner was not shown to be a “necessary party.” Further, if defendants believed another party should bear liability, they could have used available procedural tools (including third-party procedure) rather than insisting the plaintiff shoulder that burden. The dominus litis rule controlled.

iv. RBI/FERA-based defence: (a) not pleaded; (b) cannot justify a unilateral remittance to someone else

The bank attempted to justify its conduct under the foreign exchange regime, arguing remittance to the plaintiff required RBI approval. The Court’s reasoning had two distinct strands:

1. Pleadings discipline: such a defence could not be relied upon when not properly pleaded (Ibrahim Uddin; Ram Sarup Gupta).
2. Mandate fidelity: even if approval was required, the bank’s lawful choices were to (a) comply after ensuring approvals, (b) seek clarification, or (c) decline/withhold; it could not unilaterally remit to a different beneficiary contrary to the customer’s instructions.

v. Bank’s third-party liability: wrongful remittance contrary to mandate warrants indemnity

The Court affirmed the Division Bench’s third-party decree: the bank admitted error and failed to remit per mandate. Since Order VIII-A procedure applied on the Madras Original Side, Archean’s indemnity/contribution claim against the co-defendant bank could be resolved in the same suit to avoid multiplicity.

C. Impact

• Commercial certainty in “hybrid” payment undertakings: Even where payment is sourced from retained freight or other commercial flows, a document styled as a “Corporate Guarantee” (and surrounding correspondence) can be enforced as a Section 126 guarantee when it contains a clear promise to pay the creditor upon a triggering event/default. Drafting labels matter less than substantive undertakings and subsequent conduct.
• Bank mandate discipline in cross-border remittances: Banks cannot defend a misdirected transfer by pointing to background contracts (to which they are not parties) or by vaguely invoking regulatory constraints. If compliance concerns exist, banks must seek clarification or refuse/hold the transaction—not pay a different recipient.
• Procedural efficiency via third-party procedure: The judgment reinforces the utility of Order VIII-A-type mechanisms (where adopted) for adjudicating indemnity/contribution claims against co-defendants/third parties within the same litigation, particularly in banking error cases.
• Pleadings remain the gateway: Regulatory defences (including RBI approval requirements) must be pleaded with specificity; courts will not allow post-hoc factual reconstructions via evidence alone.