How to File a Legal Suit for Breach of Contract in India: Recovering Damages and Service Level Agreement (SLA) Failure

How to File a Legal Suit for Breach of Contract in India: Recovering Damages and Service Level Agreement (SLA) Failure

Author: SAUMYA

Abstract

In the modern business environment, companies heavily depend on IT services, cloud computing, and Software-as-a-Service platforms. At the heart of these digital transactions is the Service Level Agreement, which dictates technical standards like system uptime and response times. When a vendor fails to meet these metrics, it does not automatically trigger an absolute statutory breach of contract under Indian law; rather, the actionability of the failure depends strictly on the materiality of the breach, contractual exclusions, force majeure, liability limits, and the specific facts of the case. This article breaks down the legal options available to affected businesses. It covers the core provisions of the Indian Contract Act, 1872, including how courts calculate reasonable compensation under Sections 73 and 74. It details the specialized fast-track route provided by the Commercial Courts Act, 2015, and highlights how to handle digital logs under Section 63 of India’s new evidence law, the Bharatiya Sakshya Adhiniyam, 2023. Ultimately, this article provides a direct, accessible roadmap for businesses seeking to resolve tech contract disputes through mediation, arbitration, or commercial litigation.

I. Introduction

Modern businesses run on digital systems. From retail stores using digital payment apps to large enterprises relying on cloud databases, companies cannot operate without steady tech infrastructure. When a software provider’s server crashes or an external IT database fails, the financial impact on a business is immediate and severe.

Because of this, the Service Level Agreement has become one of the most important documents in corporate legal planning. The agreement acts as a clear rulebook, changing technical goals like 99.9 percent uptime or a four-hour system fix window into binding legal duties. When a provider misses these targets, it is not just a minor IT inconvenience, it can lead to a formal breach of contract under the eyes of the law.

Even though digital services are built on modern code, contract disputes in India are still settled using a classic law: the Indian Contract Act, 1872. Resolving a service agreement dispute today means connecting this foundational law with modern electronic data. To protect their financial interests, businesses must navigate a structured process involving specialized commercial courts, mandatory mediation, and updated digital evidence rules. This article provides a clear guide on how to spot a breach, calculate your losses accurately, and file a legal suit for a technical failure in India.

 

 

II. Understanding Breach of Contract

Before starting a legal claim against a tech vendor, you must establish that you had a legally binding agreement and that a statutory breach occurred.

The Legal Definition of a Contract

Under Section 2(h) of the Indian Contract Act, 1872, a contract is simply an agreement enforceable by law. For any tech service contract or service agreement to be valid, it must meet all the strict rules set out in Section 10 of the Act:

Offer and Acceptance: The vendor offers a specific service with clear performance rules, and the client accepts those exact terms.

Lawful Consideration: The service provider supplies the software or infrastructure, and the client pays the subscription fees.

Competency: Both entities must be legally authorized to enter into business contracts, meaning they are properly incorporated companies.

Free Consent: The agreement must be signed voluntarily, without fraud, pressure, or misrepresentation.

Lawful Object: The purpose of the technology or data handling must be entirely legal.

What Counts as a Breach?

Under Section 37 of the Act, both parties are legally obligated to perform what they promised in the contract. A breach happens when a vendor fails to deliver on their promises without a valid legal excuse, such as an active Force Majeure clause that covers unforeseeable external events.

In digital agreements, a service failure generally happens in one of two ways:

This takes place when a party completely fails to deliver on their promise at the exact time it was due. For example, a payment app crashes completely for hours during a busy holiday sale, or a server goes down for a whole day, breaking the guaranteed uptime metrics.

Governed by Section 39 of the Act, this happens when a provider makes it clear through their words or actions that they will not fulfill their future duties. For instance, a cloud host sends an email stating they are turning off a database next week, even though the client paid for a year-long license, or a software development team stops answering emails and leaves a project entirely unfinished before the deadline.

Your Choices Under Section 39: When an anticipatory breach happens, the innocent party can choose to end the contract right away and sue for damages, or they can wait until the actual delivery date passes to see if the vendor performs, keeping the contract active in the meantime.

III. Understanding Service Level Agreements

A Service Level Agreement is the document that outlines exactly what a successful service looks like under the primary contract. It strips away guesswork by using clear, measurable metrics.

Key Details in a Standard Agreement

Service Scope: A precise list of the software systems, networks, or databases the vendor must maintain.

Uptime Guarantees: The exact percentage of time the system must be active, typically written out as 99.9 percent or 99.99 percent uptime.

Response and Resolution Times: How fast the help desk must acknowledge a problem and fully repair the system breakdown.

Key Performance Indicators: Standards for processing speeds, page load times, and user capacities.

Penalty Clauses: The financial compensation due if targets are missed, which is usually given as service credits that reduce the client’s next invoice.

Reporting: How the performance numbers are tracked and shared with the client.

Common Failures That Lead to Disputes

System Downtime: A complete system crash that blocks business operations and causes an immediate loss of revenue.

Delayed Support: The vendor misses their fix windows repeatedly, leaving critical operational software broken.

Security Breaches: Poor database security that allows unauthorized third parties to access or leak sensitive client data.

Chronic Slowdowns: The software is technically online, but runs so slowly that the client’s team or customers cannot use it.

IV. Legal Framework Governing Breach of Contract

When a service agreement is broken, your legal strategy will rely on a comprehensive framework of Indian substantive and procedural laws:

This Act sets the rules for financial recovery and operational timelines, which are split across several key sections:

Section 55 (Time as the Essence): When a specific time for performance is specified and a party fails to adhere to it, the contract becomes voidable at the option of the promisee, provided the parties intended time to be of the essence. In commercial contracts, time is typically presumed to be of the essence, as reinforced by the Supreme Court in WelspunSpecialty Solutions Ltd. v. ONGC (2022).

Section 56 (Doctrine of Frustration): A contract becomes void if an act becomes impossible or unlawful to perform after the contract is made. This statutory frustration must meet aexceptionally high threshold, as commercial hardship alone does not excuse performance.

Sections 62 & 63 (Novation and Remission): Parties can choose to substitute, alter, or rescind the original contract (Section 62), or dispense with or remit the performance of a promise (Section 63). If a senior executive waives an SLA failure via text or email, it can severely handicap subsequent litigation.

Section 65 (Obligation of Person Receiving Advantage): When an agreement is discovered to be void, or when a contract becomes void, any person who has received any advantage under such agreement or contract is bound to restore it, or to make compensation for it, to the person from whom he received it.

Section 73 (Compensatory Damages): If the contract does not list a specific penalty for a breach, Section 73 allows you to claim compensation for losses that naturally arose from the problem. It explicitly prevents you from claiming remote or indirect losses unless the vendor knew about those specific financial risks when you signed the contract.

Section 74 (Liquidated Damages): If your agreement contains a built-in penalty clause, Section 74 applies. Under Indian law, you do not automatically get the exact amount written down. The court treats that number as a maximum limit and awards reasonable compensation based on the actual harm suffered.

Section 75 (Compensation for Rightful Rescission): A person who rightfully rescinds a contract is legally entitled to compensation for any damage which he has sustained through the non-fulfillment of the contract.

If financial compensation cannot fix the issue such as when a vendor controls unique, custom software that you cannot buy anywhere else you can request specific remedies:

Specific Performance: The Specific Relief (Amendment) Act, 2018, restructured Section 10 to state that the court shall enforce specific performance of a contract, subject to specific statutory exclusions. While this expanded the availability of specific performance, it is not an absolute or standard right. As established in M.L. Devender Singh v. Syed Khaja (1973), specific performance cannot be granted if a party chooses “substituted performance” under Section 20, if the contract involves performance of a continuous duty which the court cannot supervise under Section 14(b), if it relies on personal volition under Section 14(c), or if the contract is by its nature determinable under Section 14(d).

Injunctions: A court order stopping a vendor from taking a harmful action, such as blocking a vendor from cutting off your live database access while a dispute is being worked out.

Tech contract disputes between businesses are classified as Commercial Disputes under Section 2(1)(c) of this Act. If the value of the dispute hits the Specified Value threshold which is set at a minimum of three Lakh rupees the case goes directly to a specialized Commercial Court. This framework features:

Strict Deadlines: The time limits for filing defenses and completing steps are fixed and cannot be extended indefinitely.

Mandatory Mediation: Under Section 12A, you are legally required to try Pre-Institution Mediation first before filing a lawsuit, unless you need an emergency interim court order to protect your business operations from being shut down. As held by the Supreme Court in Patil Automation Pvt. Ltd. v. RakhejaEngineers Private Ltd. (2022), Section 12A is completely mandatory, and any suit filed without complying with this provision or without seeking genuine urgent interim relief is liable to be rejected under Order VII Rule 11 of the CPC.

Commercial Courts Rules: Special rules govern the exact case formatting, timelines, and costs within this framework.

While the Commercial Courts Act keeps cases moving quickly, the basic rules for drafting your initial claim and executing court judgments are guided by this Code, with specialized commercial amendments:

Order VII CPC (Plaint Structure) & Order XI CPC (Disclosure of Documents under Commercial Courts): The plaintiff must file a list of all documents in their power, possession, control, or custody relating to the suit at the time of filing the plaint. No subsequent documents can be introduced without specific leave of the court.

Order V CPC (Summons): In a commercial suit, the defendant must file their Written Statement within 30 days of receiving the summons. This can be extended up to a maximum of 120 days, after which the defendant’s right to file a defense is permanently extinguished.

Order XIIIA CPC (Summary Judgment): Either party can apply for a Summary Judgment after the summons has been served but before issues are framed. The court can pass a judgment without oral evidence if it is satisfied that the defendant has no real prospect of successfully defending the claim.

Order XVA CPC (Case Management Hearing): The court must hold a Case Management Hearing within four weeks of the written statement being submitted to establish a strict, binding timeline for arguments, witness cross-examinations, and final judgments.

V. Procedure for Filing a Legal Suit

Filing a commercial suit for a contract breach requires following a clear, step-by-step process. Skipping a step can result in the court dismissing your case.

Review the Contract: Read the primary agreement and the service terms carefully. Check for mandatory arbitration clauses, liability caps, and rules regarding how much advance notice you must give the vendor to fix an issue. Litigators must closely inspect the contract for cure periods, ensure that technical text messages or emails do not accidentally trigger a waiver or novation under Section 62/63, and anchor exclusive jurisdiction to prevent lengthy multi-city venue battles under Section 20 of the CPC.

Gather Your Evidence: Secure all technical records of the failure. Download server logs, system downtime history, support tickets, and email exchanges with the vendor’s engineers.

Calculate the Financial Loss: Work out the exact losses caused by the breakdown. Gather records of lost transaction values, alternative hosting fees, or employee wages paid while operations were halted. Clearly segregate general damages from liquidated damages to preserve alternative pleadings in court.

Send a Formal Legal Notice: Issue a clear legal notice to the vendor. State the exact metrics they missed, point out the broken contract terms, list your calculated financial losses, and give them a clear deadline of fifteen to thirty days to settle the matter.

File for Pre-Institution Mediation: If the vendor does not resolve the issue, you must apply for mandatory Pre-Institution Mediation through the District Legal Services Authority under Section 12A of the Commercial Courts Act.

Draft and File the Suit: If mediation fails to produce a settlement, draft your formal lawsuit. File it in the appropriate Commercial Court along with a signed Statement of Truth and your technical evidence.

Court Proceedings: The court sends a summons to the vendor, who has a maximum of 120 days to file their defense statement. The court sets a strict schedule, reviews documents, takes evidence, and hears final arguments.

Judgment and Execution: The court delivers its final judgment and issues a decree. If the vendor refuses to pay the awarded compensation, you file an Execution Petition under Order 21 of the Code of Civil Procedure to recover the funds from their company bank accounts or assets.

VI. Jurisdiction: Choosing the Right Court

You must file your lawsuit in a court that has the correct legal authority. Jurisdiction is settled by looking at three simple areas:

Under Section 20 of the Code of Civil Procedure, you file the case in the area where the vendor operates their main corporate office, or where the cause of action took place. In tech disputes, the cause of action can be where the contract was digitally signed, where the broken software was being used, or where the financial harm occurred.

Forum Selection Clauses: Most business-to-business contracts state that both parties agree to use one specific city’s courts. Indian courts respect these terms as long as the chosen city has a genuine connection to the business transaction.

This is the total monetary value of your claim. The size of your calculated damages dictates whether your case goes to a lower-level civil judge or directly to a higher District or High Court commercial bench.

To stay in the fast-track Commercial Courts, your claim must be a commercial matter and meet the Specified Value threshold of at least three Lakh rupees. Claims worth less than this must be filed as regular civil suits.

VII. Recovering Damages: The Section 73 and 74 Framework

The primary goal of a breach of contract lawsuit is to recover the money needed to balance out the financial harm caused by the vendor’s failure. Indian law recognizes different types of damages to cover these losses:

Compensatory Damages: This refers to the loss that naturally happens due to the breach. For example, it includes the direct cost of paying a backup host to keep your business online while the main vendor is down.

Liquidated Damages: This is a fixed penalty amount written directly into the contract text, such as a term stating that every hour of downtime triggers a fixed credit fee of twenty thousand rupees.

Consequential Damages: This covers indirect loss that was anticipated by both sides when signing. A common example is the lost revenue from a third-party client who canceled their deal with you because your software failed.

Nominal Damages: This is a tiny, symbolic payment awarded when a breach occurred but caused no actual financial loss, such as a system outage that lasted just five minutes late at night and caused zero business disruption.

The Legal Rule on Recovering Damages

To win a claim under Indian law, your evidence must follow the strict guidelines set out by the Supreme Court.

Section 73 and Indirect Losses

Section 73 is based on the historic legal case of Hadley v. Baxendale. The law states that courts cannot award compensation for remote or indirect losses. If you are suing for consequential damages like a major loss of secondary business profits, you must show that you explicitly warned the software vendor about these specific financial risks before signing the agreement. Recent authorities such as Nabha Power Ltd. v. Punjab State Power Corporation (2018) caution against loosely implying terms into commercial contracts, forcing parties to rely strictly on explicit terms.

Section 74 and Pre-Agreed Penalties

Under Section 74, just because a fixed penalty or credit amount is written into your contract does not mean you automatically receive that amount. The judicial perspective on Section 74 has evolved significantly across several landmark rulings. In FatehChand (1963) and Maula Bux (1969), the Supreme Court established that courts will only award “reasonable compensation” not exceeding the named sum, striking down punitive penalties. Later, in ONGC Ltd. v. Saw Pipes Ltd. (2003), the Court clarified that if a contract lists a specific liquidated damages charge, the court should enforce it directly if the parties genuinely pre-estimated the loss and the actual damage is impossible or difficult to prove, unless the opposing party proves the amount is completely unreasonable.

The definitive rules were refined by the Supreme Court of India in Kailash Nath Associates v. DDA (2015). The Supreme Court laid down these core principles:

The contractually agreed penalty serves as an absolute ceiling. The court will award reasonable compensation up to that limit, but it will not allow punitive payouts.

Damage or loss is a sine qua non for the applicability of Section 74. If a party suffers zero actual loss, they are entitled to zero compensation.

If your actual losses can be calculated using financial records, you must prove the exact math in court. You cannot use the language of the penalty clause to avoid showing your real data.

The court will only award a pre-fixed contract penalty without itemized proof if the financial damage is so complex that calculating the exact loss is genuinely impossible or exceptionally difficult.

This strict approach is reinforced in public utility and infrastructure breaches, as seen in BSNL v. Reliance Communications Ltd. (2011) and Construction & Design Services v. DDA (2015), where courts apply deep judicial discretion to award reasonable percentages of pre-estimated losses when exact public damage is hard to quantify. Furthermore, in cases like Associate Builders v. DDA (2014) and PSA SICAL Terminals Pvt. Ltd. v. Board of Trustees (2021), the Supreme Court reaffirmed that an arbitrary re-writing of a contract’s explicit damage clauses by an adjudicator violates public policy and amounts to patent illegality.

VIII. Alternative Dispute Resolution

Litigation can take time, which is why modern tech agreements usually rely on Alternative Dispute Resolution to settle issues outside the courtroom.

The Impact of an Arbitration Clause

If your agreement includes a valid arbitration clause, Section 8 of the Arbitration and Conciliation Act, 1996, mandates that courts must step aside and refer the parties to arbitration. A standard court will refuse to hear the case if a valid arbitration agreement is in force.

Why Choose Alternative Options for Tech Disputes?

Expert Arbitrators: You can choose an arbitrator who understands cloud architectures and software code, rather than a general civil judge.

Privacy: Unlike public court proceedings, arbitration occurs in private settings, protecting your company’s proprietary data and reputation.

Speed: Under Section 29A of the Arbitration Act, arbitrators must deliver their final decision within twelve to eighteen months, offering a much faster resolution than traditional litigation tracks.

IX. Landmark Judicial Decisions

Every successful contract lawsuit in India depends on following these foundational Supreme Court rulings:

The Case: A dispute arose over a delay in delivering industrial pipes, triggering a contractually specified liquidated damages clause.

The Ruling: The Supreme Court held that if a contract lists a specific liquidated damages charge, the court should enforce it directly unless the opposing party proves that the amount is completely unreasonable or an unfair penalty.

SLA Relevance: This is a vital case for plaintiffs arguing that pre-agreed hourly service credits or downtime fees should be awarded directly by the court without requiring an exhaustive calculation of every single rupee lost during a technical breakdown.

The Case: The DDA canceled a buyer’s deposit due to a delayed payment, even though the DDA later resold the property for a much higher price, suffering no real financial loss.

The Ruling: The Supreme Court clarified that Section 74 cannot be used to pocket a penalty if no real harm occurred. If a party suffers zero actual loss, they are entitled to zero compensation.

SLA Relevance: This serves as a strong shield for tech vendors. If a system goes down briefly but the client suffers no drop in business or operational disruption, they cannot use the contract text to demand unfair, punitive payouts.

X. Practical Challenges in Contract Litigation

Winning a service breach case requires navigating a few distinct, real-world hurdles:

Proving a Direct Connection: Showing that a software breakdown was the exact, singular cause of a drop in your corporate profits is difficult, as business revenues fluctuate due to many changing market conditions.

Weak Templates: Many businesses use generic contract templates found online. If an agreement leaves out clear definitions of how uptime is calculated, or contains a low liability cap, your options for recovery will be heavily limited.

Handling Electronic Evidence: You cannot prove a software failure without digital records. Under Section 63 of India’s new evidence law, the Bharatiya Sakshya Adhiniyam, 2023, introducing digital files like server logs or support chat histories requires strict authentication. The statute lays down a precise mechanism split into two parts within its Schedule: Part A must be signed by the person in lawful management or control of the device or server to prove its proper operation, and Part B must be signed by an independent technical expert to verify hash values and file integrity. If your IT team does not properly secure and verify these electronic logs with this formal certification at the time of the crash, the court can rule your evidence inadmissible, weakening your entire claim.

 

 

XI. Critical Analysis and Suggestions

As India’s digital economy grows, the legal landscape must adapt to handle modern software and cloud transactions smoothly. The historical rules of the Indian Contract Act can be enhanced with a few practical strategies:

Specialized Technical Panels: The government should set up dedicated technical mediation boards under the Commercial Courts Act. Resolving complex code or data disputes before a mediator and a neutral IT expert can settle issues in days, keeping them out of courts completely.

Clear Standards for Agreements: Regulatory bodies should establish baseline rules for business tech agreements, ensuring that massive technology providers cannot use extreme liability caps to completely escape accountability for major systemic failures or data negligence.

Automated Legal Tracking: Indian businesses should use modern contract tools to track compliance. These systems can monitor performance metrics in real time, automatically issue formal legal notices the moment an uptime rule is broken, and secure clean, authenticated server logs for use in future court proceedings.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

XII. Conclusion

A technical failure can put a company’s daily operations and financial stability at serious risk. Recovering your losses from a breach of contract in India requires maintaining clean business documentation, ensuring precise technical tracking, and following established statutory procedures.

By using the specialized fast-track routes of the Commercial Courts Act, 2015, securing all electronic records under Section 63 of the new Bharatiya Sakshya Adhiniyam, and framing your claims accurately around the Section 73 and 74 guidelines, your business can navigate legal hurdles effectively. In today’s digital economy, keeping your contracts tight and enforceable is a vital step for corporate safety and commercial survival.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

XIII. Mandatory SEO Frequently Asked Questions (FAQs)

A breach of contract occurs under Indian law when a party to an agreement fails to perform their obligations, performs them late, or performs them defectively without a valid legal excuse. Substantively governed by the Indian Contract Act, 1872, a breach can be actual (occurring at the time of performance) or anticipatory (where a party declares in advance that they will not perform).

Yes, you can sue for breach of a Service Level Agreement (SLA) in India, provided the SLA failure constitutes a material breach under the terms of your contract. If the contract explicitly states that certain SLA metrics are vital or if the failure disrupts the core objective of the agreement, it qualifies as an actionable breach. However, if the contract states that “Service Credits” are the sole and exclusive remedy for an SLA failure, your claim may be restricted to those credits rather than general damages.

Jurisdiction is determined by the Commercial Courts Act, 2015, and Section 20 of the CPC. A dispute can be filed where the contract was executed, where the breach took place, or where the defendant resides or carries on business. If the dispute meets the “Specified Value” threshold (currently ₹3 Lakhs or above) and falls under commercial criteria, it must be filed in the specialized Commercial Court of that jurisdiction.

Under Section 73, damages are calculated based on the actual financial loss naturally arising from the breach. The plaintiff must lead evidence to prove the exact loss and show that the damages are not remote. Under Section 74, if the contract contains a liquidated damages clause, the court treats it as the maximum upper limit and awards “reasonable compensation.” Following Kailash Nath Associates, the plaintiff must still prove that some actual loss or injury occurred to claim the liquidated sum.

Yes. Under Section 12A of the Commercial Courts Act, 2015, pre-institution mediation is completely mandatory for any commercial suit that does not seek urgent interim relief. As confirmed by the Supreme Court in Patil Automation (2022), failing to undergo this mediation will lead to an immediate rejection of the suit at the threshold stage.

 

 

References