Cheque Bounce in Software Contract: Vendor's Recovery

A milestone cheque from your software client bounces, and eighteen months of work suddenly runs on notice periods and court dates. The awkward part in IT contracts is rarely the dishonour itself. It is the email trail: a half-signed user acceptance test, a list of critical defects raised three days before the cheque was dated, and a client who now says the milestone was never achieved. This guide covers how a cheque bounce software contract case is built under the Negotiable Instruments Act, 1881: what your demand notice must establish, whether defect claims defeat a Section 138 complaint, and how to recover without handing over your source code.

Milestone payments and the cheque terms your contract actually creates

Section 138 of the Negotiable Instruments Act, 1881 punishes the dishonour of a cheque drawn for the discharge, in whole or in part, of any legally enforceable debt or other liability. Three facts decide most software-contract cases: was there a debt, was the cheque issued for that debt, and was it presented within three months of the date written on it.

In an IT contract the debt is created by the contract, the invoice and delivery of the milestone. An acceptance certificate is usually a contractual condition, not a statutory one. If you delivered the module, deployed it to staging and logged the client's silence for three weeks, the invoice is due under most MSAs, and a cheque signed afterwards is for a legally enforceable liability. Read your payment clause closely. "Payable on UAT sign-off" and "payable within 30 days of milestone completion" produce very different defences.

Two limits are worth fixing in your head. First, the cheque amount is the ceiling of a Section 138 case. A ₹10,00,000 cheque issued against an ₹18,00,000 invoice supports a complaint for ₹10,00,000 only; the balance needs a civil suit, arbitration or the MSME route. Second, the presumption under Section 139 means that once the drawer admits the signature, the court presumes the cheque was given for a legally enforceable debt, and the burden of raising a probable defence shifts to the client.

Cheque bounce in a software contract: the notice when acceptance is disputed

The notice is the weakest link in most vendor cases. The bank's return memo is your starting point. From the date you receive information of dishonour, you have 30 days to make a written demand on the drawer. The drawer then gets 15 days from receipt of the notice to pay. If payment does not come, the cause of action arises on the sixteenth day, and the complaint must be filed within one month from that date.

What the notice must establish

  • the cheque number, date, amount, drawee bank and the fact of dishonour;
  • the contract clause and milestone against which the cheque was issued;
  • delivery evidence: deployment logs, UAT emails, invoice with proof of service;
  • a plain statement that the amount is due and a demand for payment within 15 days.

Anticipate the acceptance defence in the notice itself. Attach the emails where your project manager chased sign-off and the client did not respond, and the clause saying deemed acceptance applies after a stated period. A notice that also demands interest or other dues is not fatal, provided the cheque amount is expressly demanded.

Send it to the registered office address in the contract by registered post with acknowledgement due, and replicate it by email and courier. Keep the postal receipts. Where the client has already written a defect letter, reply to it separately and promptly, so the record shows two threads: a quality dispute on one side, an undisputed cheque on the other.

Do software defects defeat a Section 138 case?

Sometimes, but not in the way clients expect. A Section 138 trial is a summary criminal proceeding about dishonour, not a technical audit of your code. The accused can still rebut the Section 139 presumption by raising a probable defence, and a genuine, documented dispute about whether a milestone was delivered is one route to doing so.

Timing carries most of the weight. A defect log sent six weeks before the cheque was issued, with an email saying payment is withheld until fourteen items close, is a strong defence. The same list produced after the return memo looks manufactured. Courts have consistently held that a bare denial of the debt does not displace the statutory presumption; the accused must place material on record that makes the defence probable.

Draw the distinction your contract already draws. Defects that go to acceptance, where the module does not work or data migration fails, question whether the milestone was ever achieved. Defects that are warranty items after go-live, such as a report formatting error, do not undo an accepted milestone or the liability behind its cheque. If the client accepted delivery and then signed a cheque, a later defect list rarely converts a statutory offence into a civil dispute.

Filing against a company or LLP client

When the drawer is a company or an LLP, Section 141 applies. The word company in that section covers any body corporate and includes a firm or other association of individuals, so LLPs fall within it. You must arraign the company as an accused along with the persons who were in charge of and responsible for its business when the cheque was issued. A complaint against directors alone, without the company, is not maintainable; the Supreme Court settled this in Aneeta Hada v. Godfather Travels & Tours (P) Ltd., (2012) 5 SCC 661.

Name the signatory director, the managing director and any officer whose emails show control over the payment decision, and make specific averments about each person's role. Copy-pasting the statutory phrase "in charge of and responsible for the conduct of business" without facts is the most common reason these complaints fail. For LLPs, the designated partners stand in the same position. Verify the signatory's authority through a board resolution or delegation letter before you rely on the cheque, because an unauthorised signature gives the client an easy defence.

Worked scenario

Kaveri Softworks Pvt Ltd, a Bengaluru software vendor with Udyam registration, signed a ₹62,00,000 ERP integration contract with Nimbus Retail Pvt Ltd, Pune. Milestone 3 was invoiced at ₹18,00,000 plus GST after deployment to Nimbus's staging server. Nimbus's finance head sent a part-payment cheque of ₹10,00,000 dated 20 January 2026, signed by a director.

Kaveri deposited the cheque on 10 February 2026. It was returned on 11 February 2026 with the remark "funds insufficient". Kaveri issued a demand notice dated 12 March 2026, inside the 30-day window, by registered post and email, enclosing the deployment log, the UAT email trail and the invoice. Nimbus received it on 14 March 2026. The 15-day period ended on 29 March 2026, the cause of action arose the next day, and Kaveri filed a Section 138 complaint in Bengaluru on 20 April 2026, within the one-month limit, invoking payee-bank jurisdiction under Section 142(2).

Alongside the complaint, Kaveri applied for interim compensation under Section 143A, where the court can direct payment of up to 20% of the cheque amount, here up to ₹2,00,000. For the remaining ₹8,00,000 plus GST and contractual interest, it filed a reference before the MSE Facilitation Council under Section 18 of the MSMED Act, 2006, which also carries compound interest at three times the RBI bank rate under Section 16. Because Kaveri holds Udyam registration, Nimbus cannot claim a deduction for that invoice until it actually pays, under Section 43B(h) of the Income-tax Act, 1961 — a point worth putting in the covering email to the client's CFO.

Recovering dues while protecting source code and IP

The instinct to hold back source code, disable a licence key or switch off a production environment is understandable and usually counterproductive. Unilateral suspension without the notice and cure period your MSA provides is a breach on your side, invites a counter-claim, and hands the defence a reason to argue the debt itself was in dispute.

Use the contract instead. If the MSA allows suspension for non-payment after written notice, follow it exactly and document each step. Where a source code escrow exists, release is governed by the escrow agreement, not by your frustration. Keep licence and deliverables separable so that an unpaid milestone does not automatically revoke a licence you have already granted; the termination clause, not self-help, is the tool that ends the relationship.

A Section 138 complaint and an arbitration can run in parallel. The criminal remedy addresses the dishonour; the arbitration clause in your MSA addresses the unpaid balance, interest and the defect claims. Interim protection under Section 9 of the Arbitration and Conciliation Act, 1996 is available if the client is moving assets or blocking access to data you need for the remaining milestones.

Documents to keep, and common mistakes

  • Original cheque, bank return memo and the bank's dishonour advice.

  • Signed contract with the payment, acceptance and termination clauses.

  • Invoice, proof of service and delivery challans where hardware was supplied.

  • Deployment logs, UAT emails, meeting minutes, ticket closures.

  • Registered post receipts, courier proofs and email headers for the notice.

Three mistakes recur. Presenting a cheque after its three-month validity because the client promised to clear it next week. Sending the notice to a project manager's email instead of the registered office. And filing the complaint in the vendor's home city when the collection bank branch is elsewhere, since the payee-bank rule under Section 142(2) decides territorial jurisdiction.

  • Confirm the cheque date is within three months and deposit it before validity lapses.

  • Collect the return memo and record the exact date you learnt of the dishonour.

  • Issue the Section 138 notice within 30 days to the registered office, by RPAD and email.

  • Attach delivery proof and the relevant contract clause to the notice.

  • Arraign the company or LLP along with the persons in charge, with specific averments.

  • File the complaint within one month of the cause of action, in the payee-bank jurisdiction.

  • Start the MSE Facilitation Council reference in parallel for the unpaid balance.

If a milestone cheque has come back unpaid, the most useful step this week is to freeze the timeline: date the return memo, check the three-month validity of every other cheque in hand, and issue the Section 138 notice to the registered office by registered post and email before the 30-day window closes. Everything else, from arbitration to the MSME reference to the defect argument, follows from that record.

This article is for general information only and is not legal advice. Consult a qualified professional for your specific facts.

Share Now

0 Comments

No comments yet. Be the first to share your thoughts.

Leave a Comment

Learned Counsel
Go Back Top