IndiaLaw by assureOffice
When a Customer Deposit Must Come First

When a Customer Deposit Must Come First: Reciprocal Promises under Contract Act Sections 51–54

Read the payment and performance sequence before suspending work. Separate a true first promise from simultaneous obligations and quantify supported loss.

Reviewed by CA Naveen Saraswat · Chartered Accountant | 5+ years in corporate audit & tax compliance | Ex-Big4

Professional prepares a corporate agreement

Identify whether payment really comes first

Sections 51–54 of the Indian Contract Act, 1872 distinguish simultaneous reciprocal promises, the order of performance, prevention and default on a first promise. If a contract makes a customer deposit a true predecessor to the supplier's reciprocal obligation, section 54 may apply when the customer fails to perform first. A payment label such as advance is not enough; read the linked provisions and the actual performance sequence.

Read the applicable text: Indian Contract Act, 1872, sections 51–54 and 73.

Separate the statutory routes

Section 51 provides that a party to simultaneous reciprocal promises need not perform unless the other party is ready and willing to perform its reciprocal promise. Section 52 follows the express order in the contract, or the order required by the nature of the transaction when no order is expressly fixed. Section 53 addresses prevention and makes the contract voidable at the prevented party's option, with compensation for resulting loss. Section 54 applies where one promise cannot be performed, or its performance cannot be claimed, until the other is performed. The promisor who defaults on that first promise cannot claim the dependent performance and must compensate the other party for loss caused by the non-performance.

Apply the analysis to each release

Match the deposit or letter of credit, release authorisation, production start, shipment date and amendments. Determine whether the obligation is conditioned on full funding, a tranche or another milestone. Record any accepted variation or extension and check whether part performance indicates a different agreement. A first-promise default affecting one batch need not resolve independent obligations under another batch.

Prove loss rather than equating it with the unpaid deposit

Keep any debt, security amount, costs and mitigation working separate. Section 73 limits damages to loss arising naturally in the usual course or within the parties’ contemplation at contracting. It excludes remote and indirect loss and requires consideration of available means of mitigating the effects of non-performance. A planned cost avoided, a recovery received and a continuing contractual debt should each be identified; avoid adding the same impact twice.

Document the decision before acting

A reservation notice, updated schedule and record of readiness make the chronology easier to reconstruct. Follow the agreement's notice, cure and dispute terms and obtain transaction-specific review before treating an obligation as discharged. The examples show a working, not an automatic right to suspend all orders or retain every advance.

Six worked illustrations

All facts and amounts are fictional. Calculations illustrate the stated assumptions, not a predetermined legal outcome.

Illustrative example 1: Partial first payment

A contract expressly requires ₹5 lakh cleared before production. Only ₹3 lakh is received. The funding shortfall is ₹2 lakh; check whether the contract or a later variation permits partial release.

Illustrative example 2: Two batches with separate gates

Batch A requires ₹4 lakh and B requires ₹6 lakh. A is funded in full and B has ₹2 lakh paid. The shortfall is ₹4 lakh on B only; check any contractual cross-default separately.

Illustrative example 3: Simultaneous delivery and payment

Goods worth ₹8 lakh are due against immediate payment. ₹5 lakh is ready. The shortfall is ₹3 lakh, but review both sides' readiness under section 51 rather than assuming there is an advance condition.

Illustrative example 4: Condition satisfied late

Cleared funds were required on 4 September and received on 10 September. The difference is six calendar days. Evidence the actual effect on production before attributing six days of loss.

Illustrative example 5: Avoided cost on delay

Assume ₹42,000 in supported delay-related costs before a ₹12,000 saving from rescheduling that has not already been deducted. The net working is ₹30,000, subject to entitlement and causation.

Illustrative example 6: Remove duplicated labour

A claim adds ₹18,000 labour to a ₹62,000 invoice that already contains it. Remove duplication. After a ₹7,000 credit allocated to those costs, the working is ₹55,000.

Ten-step verification table

StepActionEvidence
1Read the relevant purchase termsContract and amendments
2Identify each promiseObligation-by-obligation map
3Determine order of performanceContract wording and transaction facts
4Check payment evidenceBank record or other agreed security
5Check supplier readinessMaterials, staff and production plan
6Review waiver and extensionsAuthorised correspondence and course of dealing
7Apply the notice processNotice, receipt and cure records
8Trace affected batchesRelease log and alternative schedule
9Reconcile causally linked costsCost evidence, savings and recoveries
10Record legal and commercial decisionReviewed working and next release condition

Sixteen practitioner FAQs

1. Is every advance a condition before production?

Only if the agreement and facts establish that sequence.

2. What if the contract fixes no order?

Section 52 then looks to the nature of the transaction.

3. When does section 51 apply?

Where the reciprocal promises are to be performed simultaneously.

4. What does section 54 address?

Default by the promisor who should perform the first dependent promise.

5. Does section 54 govern every customer delay?

No. Identify the actual dependence and other applicable provisions.

6. Does section 53 require a separate factual analysis?

Yes. Establish prevention of performance and the resulting consequences.

7. Does partial payment automatically authorise release?

Read the agreed threshold and any accepted variation.

8. Do later emails matter?

They can evidence a change, waiver or timeline; verify authority and terms.

9. Can a funding failure suspend unrelated orders?

Review their own obligations and any cross-default wording.

10. What if the supplier was not ready anyway?

Assess readiness and causation rather than assigning the full delay to the customer.

11. Is the shortfall the same as damages?

No. Quantify the resulting loss separately.

12. Should avoidable expenditure be included?

Consider mitigation and actual costs under section 73.

13. Can delay days be counted as cash loss without proof?

Tie the delay to supported financial impact.

14. Does the supplier have to preserve payment timestamps?

They help establish the order and actual release date.

15. Can the contract impose notice and cure requirements?

Review and follow the applicable terms before action.

16. What if the parties settle later?

Keep the accepted settlement, remaining obligations and cost allocation separate.

Official sources

Indian Contract Act, 1872, sections 51–54 and 73