IT, Software and Service Contract Disputes: Non-Delivery, Scope Fights and Unpaid Bills

What falls under an IT or service contract dispute

It covers any contract to build, supply, host, run or support technology. Think custom software and app builds. ERP and CRM rollouts, SaaS subscriptions, website and digital marketing retainers, cloud hosting, annual maintenance contracts, IT staffing and outsourced back office work are all in. And the same reasoning carries over to most business service contracts where one side works for months and the other pays in instalments.

These fights come in roughly three shapes. In the first, the client says the work never came, came late, or doesn't work. In the second, the vendor says it delivered, the client kept moving the goalposts, and the money is due. And in the third, both agree the project went wrong and the argument is over what's left, meaning the code, the data, the accounts and the domain.

Courts decide them on ordinary contract law, mostly the Indian Contract Act, 1872. The Information Technology Act, 2000 and the Bharatiya Sakshya Adhiniyam, 2023 govern how electronic records are treated and proved. Who owns the software is a copyright question. There's no special tribunal. A Commercial Court hears these like any other contract case, but the evidence looks nothing like a supply dispute. Think commit logs, not lorry receipts.

Which laws apply

Vendors: the client won't pay

Acceptance is usually what your case stands on. Most IT contracts tie payment to milestones, and milestones to user acceptance testing. Some clients dodge the sign-off while running the software live. Look for a deemed acceptance clause (acceptance if no defect list arrives within ten working days, say, or acceptance on go-live) and rely on it. No such clause? Live business use of the system is still strong evidence that the work was accepted.

Sometimes the work is only half done because the client pulled the plug or stopped responding. Then you can claim for what you completed plus the loss of the balance, minus what you saved by not finishing. Time and material contracts are a different exercise. Everything turns on timesheets and whether the client's project manager approved them. Approved timesheets are hard to attack later. Unapproved ones need backing from tickets, commits and meeting notes.

Don't take matters into your own hands. We say this to vendors often. Remotely disabling the client's application, locking it out of its own data or pulling a deployment to force payment can land you with a compensation claim under Section 43 of the IT Act, and in bad cases a criminal complaint. Suspending further work for non-payment is generally safer than switching off what's already been delivered and part-paid. Get a court order instead.

Clients: the vendor didn't deliver

You'll need to show what was promised and by when, and then exactly how the delivery fell short. The promise sits in the contract and statement of work, read with the requirement documents both sides signed off. The shortfall shows up in test reports, defect logs, missed release dates and the vendor's own admissions over email. 'The software is useless' won't get you far. List the defects, and tie each one to a requirement.

If time was of the essence and the vendor missed the date, you can end the contract under Section 55. But if you've kept granting extensions, time may no longer be of the essence, and you'll need a clear written notice fixing a final, reasonable date before you terminate. We regularly see clients terminate in a temper. Over WhatsApp. Then they find the termination itself under attack.

What you can usually claim: your advances back (Section 65, or the refund clause), whatever extra it costs to bring in another vendor to finish, and liquidated damages if the contract has them. Section 20 of the Specific Relief Act, 1963, as amended in 2018, adds something useful. Give at least 30 days' written notice, and you can have the work done by someone else at the defaulting party's cost. That's valuable in IT projects. Courts rarely order a vendor to finish the job itself. Lost business is a harder sell, and it usually fails unless the vendor knew of that loss when the contract was signed and the contract doesn't exclude it.

Scope fights: where most IT cases are won or lost

Scratch almost any software dispute and you'll find a scope dispute underneath. The vendor says a feature was a change request needing a fresh estimate, and the client says it was in the requirement from day one. Both can't be right. The court will read the contract, statement of work, functional specification and change request procedure, and then it'll look hard at how both sides actually behaved.

Say the contract requires changes to be agreed in writing and priced before work starts, and the vendor built the extra feature on the strength of an email saying 'please add this'. The vendor may still recover under Section 70 for work the client accepted and used. Probably at fair value, not the rate card. And if the client approved estimates inside the ticketing tool, those approvals often settle the point.

When Advocate B.K. Singh opens an IT dispute file, the first thing he does is build a table. Each disputed item gets a row, with the document that put it in or out of scope, and the date. More often than not, the table shows the fight is really about a handful of items worth a fraction of the total claim. That's what makes settlement possible. If it doesn't settle, the table becomes the spine of the plaint or written statement.

Who owns the code, the data and the accounts

Paying for software doesn't, on its own, make you the copyright owner. It surprises people. Under the Copyright Act, an outside developer owns what it writes unless it's signed a written assignment, and plenty of small business contracts say nothing about this or only promise a licence. If you're the client, check for an assignment clause and look at its duration and territory. Silent on those points, an assignment is treated as limited to five years and to India.

It gets practical quickly. The vendor's sitting on the repository, the cloud console, the app store developer account, the domain registration or the admin passwords. If your business can't run without them, apply for an urgent interim injunction ordering the vendor to hand over access, or at least to preserve the code and data. Courts usually impose terms, such as a deposit of the disputed amount in court. And urgency like this can justify skipping Section 12A mediation and filing straight away.

It runs the other way too. A former vendor or partner keeps using the client's data, or recycles code written for one client into a product for another. That's copyright and confidential information territory. See our pages on copyright infringement and protecting confidential data and client lists. For future contracts, a source code escrow and an assignment clause that names duration and territory head off most of these problems.

Liability caps, penalties and refunds

Liability caps are standard. The vendor's exposure is often limited to the fees paid in the previous twelve months, with indirect or consequential loss excluded. Between commercial parties of comparable strength, Indian courts generally uphold such clauses, though they read them strictly, and a cap may not protect a party from the results of its own fraud or a deliberate refusal to perform. So read it before you put a number on anything. There's not much point suing for Rs 2 crore of lost profit when the contract caps recovery at Rs 25 lakh and rules out lost profit entirely.

Service credits and penalties for missed service levels are liquidated damages under Section 74. The client can recover reasonable compensation up to the named amount without proving its exact loss. There's a limit, though. A court won't award a sum that's wildly out of proportion to any likely harm.

Refunds depend on how payment was structured. An advance against a milestone that never arrived is usually refundable. Monthly fees for a service you actually used usually aren't, even if the service was poor, and your remedy then is damages for the poor service. Annual SaaS subscriptions paid upfront and ended early are different. It's all in the termination clause.

Confidentiality, data and poaching staff

Side issues about confidential information and people come up a lot. Most contracts have a confidentiality clause that survives termination, and a breach can be stopped by injunction if the information's genuinely confidential and can be pinned down. Saying the vendor 'knows our business' won't do. Name the documents, data sets or code you shared.

Non-solicitation clauses, where each side agrees not to hire the other's staff, are everywhere. But Section 27 of the Contract Act makes agreements in restraint of trade void, and courts have been slow to enforce post-termination restraints that stop a person or business from working at all. A non-solicitation clause that operates during the contract stands a better chance than a sweeping ban afterwards. Go carefully with claims over poached employees.

If customers' or employees' personal data is involved, think about data protection duties before you litigate. Not after. A vendor holding a client's customer database must keep it secure, and return or delete it as the contract and data protection law require. Sitting on personal data to squeeze payment out of a client is a bad idea, legally and commercially.

How an IT dispute moves through the system

This order suits most disputes between businesses. Urgent cases over access, code or data can go straight to step 5.

1. Secure the evidence

   Export email threads, chat groups, ticket history, repository logs, deployment records and timesheets. Copy everything before access is cut. Note who on your team controls each system. They may have to sign the Section 63 certificate later.

2. Build the scope and payment table

   Put each milestone, each disputed feature and each invoice in a table, next to the document that backs your position. This is the work that tells you whether you have a claim worth filing, and what it's really worth.

3. Notice and negotiation

   Send a written notice stating the breach and what you want, whether that's payment, delivery by a final date, handover or a refund. If you plan substituted performance under Section 20 of the Specific Relief Act, the notice has to give at least 30 days. Our page on a legal notice for recovery covers what goes in.

4. Section 12A mediation

   Unless you need urgent interim relief, apply for pre-institution mediation through the Legal Services Authority. Technical disputes settle here surprisingly often. Once both sides see the scope table, each side's lawyers can spot the weak points in their own case.

5. File the suit, ask for interim orders

   File a commercial suit with a statement of truth and every document in your possession. A vendor with signed acceptance and fixed invoices can use a summary suit. A client after a refund and damages files a regular suit, and may ask for an injunction over code, data or access.

6. Pleadings and disclosure

   The defendant has 30 days to file its written statement, extendable to 120 days at most. Then both sides admit or deny documents. Either can seek disclosure and inspection of records the other holds, server logs or internal test reports for instance.

7. Evidence, technical witnesses, judgment

   Evidence goes in by affidavit, followed by cross-examination. IT cases often need a technical witness who can walk the judge through the logs and the code. The court can also appoint a local commissioner to inspect a system and report back.

8. Appeal and execution

   Appeals lie under Section 13, within 60 days. Don't miss it. A money decree is enforced under Order XXI by attaching bank accounts and receivables.

Plenty of IT master services agreements carry an arbitration clause. If yours does, the claim belongs in arbitration, and urgent relief comes under Section 9 of the Arbitration Act. We cover that work on arbitrationlawyer.in.

What each stage costs and how long it takes (general guidance)

Which court hears an IT contract dispute

IT contracts fit the definition of commercial dispute through several doors. Technology development agreements are Section 2(1)(c)(xvi). Management and consultancy agreements, Section 2(1)(c)(x). Outsourcing services come under Section 2(1)(c)(xiii), intellectual property including software under Section 2(1)(c)(xvii), and agreements for the provision of services under Section 2(1)(c)(xviii). Once the specified value, including interest up to filing, reaches Rs 3 lakh, it's a Commercial Court matter.

Delhi splits by value. Suits up to Rs 2 crore are heard by the District Judge (Commercial Court) at whichever district complex is relevant, and above that it's the Commercial Division of the Delhi High Court. That pecuniary limit may be revised, as a change has been under consideration, so don't file without checking it. Noida and Greater Noida, where software firms crowd around Sector 62 and the Sector 135 to 145 stretch, fall under the court designated as Commercial Court for Gautam Buddh Nagar at Surajpur. In Gurugram it's the court designated for that district, and appeals go to the Punjab and Haryana High Court. The details are on our page on which commercial court hears your case.

On place, Section 20 of the Code of Civil Procedure looks at where the defendant carries on business or where the cause of action arose. Remote work muddies this. The contract was signed online, the team sits in Pune, the client is in Gurugram. Look for a jurisdiction clause first. Without one, the usual anchors are where the contract was accepted, where the work was to be delivered and where payment was due. Foreign clients are a separate headache. Service abroad and enforcement need their own planning.

Records to lock down

Proving electronic evidence without tripping up

In an IT case, most of the evidence lives on servers. A printed email, a screenshot of a Slack thread, a CSV pulled from a ticketing tool: each is a copy of an electronic record, and each has to be proved with a certificate under Section 63 of the Bharatiya Sakshya Adhiniyam. Someone in charge of the device or system signs it, describing how the record was produced. The 2023 law also prescribes a format, in the Schedule to the Adhiniyam. One part is for the party. The other is filled in by an expert. Prepare it carefully.

Collect records early and from the original system, in a way that keeps the metadata (dates, senders, edit history). If integrity is likely to be challenged, take a forensic image and note its hash value. Don't tidy up an export. A selective one invites the obvious suggestion that the rest was hidden.

The amended Order XI requires every document in your power and possession that relates to the dispute to be disclosed with the plaint or written statement. That includes the ones that hurt you. Rely later on something you didn't disclose and you'll need the court's permission, which it gives only for reasonable cause. This catches people in IT cases all the time. They hold back an awkward chat thread, then find they need other messages from the very same thread.

Startups, agencies, MSMEs and large companies: how it differs

Startups are usually the client, with one outsourced build that went wrong, thin written specs and a great deal of WhatsApp. What they want first is access to the code and accounts so the business keeps running. Damages come second. Agencies and small software firms usually sit on the vendor side, chasing final milestones and unpaid retainers. If they're registered as micro or small enterprises, the MSMED Act covers services too. That brings the 45-day payment rule, interest at three times the bank rate, and access to the Facilitation Council.

Large companies contract on their own paper. Their MSAs tend to carry liability caps, long acceptance periods, set-off rights, an arbitration clause, and a jurisdiction clause pointing at their head office city. A small vendor suing a big client has to work within those terms. A big client suing a small vendor should ask, before funding a long suit, whether a decree will actually be recoverable.

Lenders and investors in tech businesses often watch contract disputes turn into shareholder or insolvency fights. Keep the contract claim separate, in your head and in your pleadings. Otherwise it gets lost in the bigger battle.

Mistakes that weaken an IT claim

Careless termination does the most damage. A client who terminates without notice, or for a reason the contract doesn't allow, may end up as the party in breach and lose the right to recover advances. A vendor who walks off the project over one late invoice may find the client's claim for completion costs bigger than its own.

Next comes trusting memory over records. Each side remembers the project differently. The court believes the ticket, email or meeting note written at the time. And when a project ends, people delete chat groups and deactivate user accounts. The best evidence goes with them.

Then there's overclaiming. Lost profit, reputational harm and management time get pleaded as big round figures with nothing underneath. In the IT matters Advocate B.K. Singh handles, the claims that survive are the ones with arithmetic behind them. Advances paid. Invoices raised. Quotes from the replacement vendor. The specific cost of the delay.

What to do this week

Get your records out and saved before anyone touches access. Then read the contract, looking for five things: how acceptance works, how changes are handled, when either side can terminate, what the liability cap is, and whether there's an arbitration or jurisdiction clause. Make your table of disputed items and amounts. Until you've taken advice, don't switch anything off. Don't delete data. And don't terminate by message.

If you're owed money, check limitation. It's generally three years, and our guide on the time limit to recover dues explains the count. Check, too, whether your firm is registered as an MSME. If you're the client, decide what you need first. Access to code and data, completion by someone else, a refund. The order you ask for these in shapes the whole case. How damages are worked out is covered on our page on breach of contract claims.

Before you send a notice, or answer one, you can have your contract, statement of work and project records reviewed by Advocate B.K. Singh's team. Share them through the contact page.