When a US/EU business outsources its software development, IT support, customer service, data processing, or other business functions to an Indian BPO or IT firm, the Service Level Agreement (SLA) is much more than just an operational document; it establishes metrics for the services being provided and what will occur in case of failure to meet the metrics.
An SLA could encompass uptime metrics, response time, incident handling, staffing levels, service availability, security measures, and performance metrics. Failure to meet these metrics could affect operations and cause losses in severe cases.
For an overseas business, the primary issue becomes what should happen if you breach an SLA? The answer depends on the wording of the SLA, the master services agreement, applicable law, dispute-resolution mechanism and evidence of the loss.
An SLA dispute involving an Indian service provider should therefore be assessed as a contractual and cross-border commercial dispute, not simply as an IT performance problem.
Key Takeaways
- An SLA breach can amount to a contractual breach when the SLA forms part of a binding agreement.
- Sections 73 and 74 of the Indian Contract Act, 1872 may become relevant when compensation or a stipulated sum is claimed.
- A contractual penalty does not automatically guarantee recovery of the full amount stated in the agreement.
- Service credits, cure periods, termination rights and liability caps can significantly affect the customer's remedies.
- The governing-law and dispute-resolution clauses should be reviewed before initiating proceedings.
- Arbitration may be the agreed route where the contract contains a valid arbitration clause.
- Evidence showing the SLA failure, notice given to the provider and resulting losses can materially affect the strength of a claim.
Does an SLA Failure Constitute a Material Breach?
The first legal question is not how much compensation can be claimed. It is whether the particular SLA failure actually amounts to a breach of the contractual obligations.
An SLA may be incorporated into a master services agreement, statement of work or outsourcing contract. In that situation, its obligations may have contractual force.
For example, an Indian IT agency may have agreed to maintain 99.9% monthly uptime, respond to critical incidents within 30 minutes or resolve high-priority incidents within four hours.
A failure to meet one of these metrics does not automatically justify termination or a substantial damages claim.
The contract should be examined for:
- the precise SLA commitment;
- applicable performance thresholds;
- exclusions from SLA calculations;
- notice requirements;
- cure periods;
- service credits;
- termination rights;
- liability caps;
- indemnity provisions; and
- dispute-resolution clauses.
Repeated failures may carry greater contractual significance than an isolated technical incident, particularly where the agreement treats persistent SLA failures as a material breach.
Legal and Contractual Consequences of an SLA Breach
The consequences of an SLA failure depend largely on the remedies negotiated between the parties.
Service Credits
Service credits are commonly used in technology outsourcing agreements. A customer may receive a credit against future invoices when the provider fails to achieve an agreed service level. They can provide a relatively straightforward commercial remedy for recurring performance failures.
However, the customer should check whether the agreement describes service credits as the exclusive remedy for the relevant SLA failure. If service credits are the sole remedy, pursuing additional damages may become more difficult. If they are not exclusive, other contractual or statutory remedies may remain available, depending on the circumstances.
Compensation for Contractual Loss
A customer may seek compensation where the applicable law and contract permit recovery of losses caused by the breach.
Under Section 73 of the Indian Contract Act, 1872, compensation may be available for loss or damage that naturally arose from the breach or that the parties knew was likely to result when they entered into the contract. The provision also excludes remote and indirect loss from compensation.
For a US or EU company, this distinction can become important when calculating the financial consequences of an Indian service provider's failure.
For example, documented emergency outsourcing costs may require a different legal analysis from a projected loss of future customers that cannot be directly connected to the SLA failure.
Contractual Penalties
An agreement may contain a specified amount payable when a particular contractual obligation is breached.
Section 74 of the Indian Contract Act addresses contracts that stipulate a sum payable upon breach or contain a penalty clause. The provision contemplates reasonable compensation, subject to the statutory framework and the amount stipulated in the contract.
Therefore, a penalty for breach of contract should not automatically be treated as an assured recovery.
The precise clause, circumstances of the breach, applicable law and evidence of the loss should be examined before making a demand.
Termination
Persistent SLA failures may trigger contractual termination rights. However, termination should normally follow the procedure specified in the agreement. Depending on the contract, this may involve a formal notice, identification of the breach and an opportunity to cure the failure.
A company that terminates prematurely may create a separate dispute over whether the termination itself was contractually valid.
Legal Remedies for SLA Breach by an Indian IT Company
The remedies available to a US or EU customer depend on the contract and the law governing it.
Contractual Remedies
- The agreement may provide for:
- service credits;
- damages;
- reimbursement of specified costs;
- corrective action;
- replacement of personnel;
- additional monitoring;
- suspension of services;
- termination; or
- indemnification.
The customer should identify these remedies before sending a formal demand. A demand that ignores the contractual remedy structure may unnecessarily complicate negotiations.
Compensation Under Indian Contract Law
Where Indian law governs the agreement, the provisions of the Indian Contract Act become particularly relevant.
Section 73 addresses compensation for loss or damage caused by breach, while Section 74 deals with stipulated sums and penalties.
Section 75 also addresses compensation following rightful rescission of a contract.
The applicability of these provisions will depend on the contract, the circumstances of the dispute and the remedy being pursued.
Termination and Transition Assistance
Termination of an outsourcing agreement creates practical obligations beyond simply ending the contract.
A US or EU company may need the Indian provider to return data, transfer source code, hand over documentation, provide system credentials, cooperate with migration and continue certain services during a transition period.
These obligations should be reviewed before termination.
Otherwise, a company may resolve one SLA problem only to encounter a second dispute over data, intellectual property, system access or transition assistance.
Indian Contract Law Governing Compensation for SLA Breaches
There is no single breach of contract section that determines every SLA dispute in India.
Different provisions of the Indian Contract Act, 1872 may become relevant depending on the facts and remedy.
Section 73: Compensation for Loss or Damage
Section 73 provides the general statutory framework for compensation arising from breach of contract.
The focus is not simply on whether the customer suffered some loss after the SLA failure. The customer must consider whether the claimed loss falls within the scope of compensation recognised by the provision.
This makes causation and foreseeability important when assessing a damages claim.
Section 74: Stipulated Sums and Penalties
Section 74 applies where a contract specifies an amount payable upon breach or contains a penalty provision.
The presence of a stated amount does not necessarily mean that the customer can recover that amount automatically.
The circumstances surrounding the breach and the applicable legal principles must be considered when determining reasonable compensation.
Section 75: Compensation Following Rightful Rescission
Where a party rightfully rescinds a contract, Section 75 may become relevant to a claim for compensation.
This can matter in outsourcing arrangements where repeated SLA failures result in lawful termination or rescission under the contractual framework.
Contractual Penalties and Limits on Recovery
An overseas company should not evaluate an SLA claim by looking only at the amount of the alleged loss.
The liability provisions of the agreement may substantially affect recovery.
For example, the contract may contain:
- an overall liability cap;
- a separate cap for specific claims;
- exclusions for consequential losses;
- exclusions for lost profits;
- carve-outs for confidentiality or data protection;
- indemnification obligations; or
- specific treatment of SLA-related claims.
The interaction between these provisions can be more important than the SLA itself.
A customer claiming substantial damages should therefore examine the entire contractual liability structure before commencing proceedings.
Choosing Between Negotiation, Mediation, Arbitration and Litigation
An SLA breach does not automatically require court proceedings.
Many cross-border outsourcing contracts have an escalation procedure that needs to be followed prior to launching any legal process.
Commercial negotiation
A commercial negotiation would be appropriate in cases where the service provider is commercially useful, and the dispute can be sorted out.
Both sides can negotiate on service credits, remediation, service level, etc.
Mediation
Mediation will provide a framework through which one can resolve a dispute without going through adversarial proceedings.
It may be particularly useful where both parties want to preserve their commercial relationship.
Arbitration
The agreement may require disputes to be referred to arbitration.
The arbitration clause should be examined carefully for the:
- arbitral institution;
- seat of arbitration;
- governing law;
- language;
- number of arbitrators; and
- appointment procedure.
These provisions can materially affect how a cross-border SLA dispute is conducted.
Litigation
Court proceedings may be appropriate where the contract permits them and the relevant jurisdictional requirements are satisfied.
The customer should determine the proper forum before filing a claim. The mere fact that the service provider operates from India does not, by itself, answer every question concerning jurisdiction.
Jurisdiction and Commercial Court Remedies in India
Jurisdiction is particularly important when a US or EU company is dealing with an Indian service provider.
The contract may specify:
- governing law;
- exclusive jurisdiction;
- courts having authority over disputes; or
- arbitration as the mandatory dispute-resolution mechanism.
The parties should also consider where contractual performance occurred and whether other jurisdictional connecting factors exist.
The Commercial Courts Act, 2015 provides a framework for specified commercial disputes in India and includes provisions relating to commercial disputes, jurisdiction and pre-institution mediation.
Where court proceedings are contemplated, the applicable statutory requirements should be assessed before filing.
A cross-border claimant should also consider how a judgment or arbitral award will ultimately be enforced against the Indian service provider.
Building and Proving an SLA Breach Claim
A technically obvious SLA failure can still become difficult to prove if the evidence is incomplete.
The following records should generally be preserved.
The Executed Contract
Maintain the signed master services agreement, SLA, statements of work, amendments and relevant schedules.
SLA Performance Records
Preserve uptime reports, incident tickets, response-time records, system logs, service reports and performance dashboards.
Written Communications
Emails, escalation notices, meeting minutes and written complaints may establish that the provider knew about the problem and had an opportunity to rectify it.
Financial Records
Maintain invoices, emergency outsourcing costs, migration expenses and other records supporting the claimed loss.
Evidence of Customer Impact
If the SLA failure affected customers or business operations, preserve contemporaneous records showing the connection between the provider's failure and the resulting impact.
Contractual Notices
Keep copies of all breach notices and proof of delivery. If the contract prescribes a particular notice method, compliance with that procedure should be documented.
Immediate Legal Steps Following an SLA Breach
A controlled response can help preserve both the commercial relationship and the company's legal position.
Establish the breach
Compare actual performance against the exact SLA metric. Avoid relying only on general dissatisfaction with the provider.
Review the agreement
Identify cure periods, service credits, liability caps, termination rights and dispute-resolution requirements.
Preserve evidence
Secure technical reports, incident records, emails and other relevant documents before information becomes difficult to retrieve.
Issue the required notice
Follow the contractual procedure and clearly identify the affected SLA obligations.
Quantify the loss
Separate documented losses from speculative business consequences.
Assess the commercial relationship
Determine whether remediation is realistic or whether continued failures justify considering termination.
Review dispute-resolution options.
Check whether the contract requires negotiation, mediation or arbitration before litigation.
Common Legal and Contractual Errors in SLA Disputes
Treating Every SLA Failure as a Material Breach
A missed performance metric does not necessarily justify immediate termination. The contract should be read before deciding that a failure is material.
Ignoring the Liability Cap
A company's actual loss may exceed the amount it can recover under the contract.
Assuming a Penalty Clause Guarantees Full Recovery
A stipulated amount is not necessarily an automatic entitlement to the entire sum.
Claiming Remote Business Losses Without Analysis
Losses must be assessed against the applicable contractual and statutory rules rather than simply added to the demand.
Starting Proceedings Without Reviewing the Arbitration Clause
A valid arbitration agreement may require the dispute to be handled through arbitration rather than ordinary court proceedings.
Failing to Follow the Notice and Cure Procedure
Even a genuine service failure can become procedurally complicated if contractual notice requirements are ignored.
Why SLA Disputes Require a Contract-Specific Legal Analysis
Generic searches such as types of breach of contract, what are the 4 types of breach of contract, or breach of contract case can help explain basic contractual concepts.
They do not, however, answer the practical questions arising from an international IT outsourcing dispute.
- A proper analysis should identify:
- the contractual obligation;
- the specific SLA metric that was missed;
- whether the failure is material;
- whether a cure opportunity applies;
- the contractual remedy;
- the recoverability of the claimed loss;
- the governing law;F
- the dispute-resolution mechanism; and
- the forum in which relief can be obtained.
The same technical failure can therefore produce different legal outcomes under different contracts.
Managing an SLA Dispute Before It Escalates into a Cross-Border Claim
An SLA conflict between a US or EU company and an Indian BPO firm or IT organisation should be handled keeping in view both the SLA and the legal complications associated with it.
First thing to do in most cases is a thorough analysis of the master agreement and the SLA, along with relevant law and dispute resolution clauses. Then comes establishing the nature of the breach and identifying the extent of loss that can be claimed.
If the relationship is salvageable, then negotiation may make commercial sense. But in case of persistent or serious problems, termination of the agreement, arbitration or even litigation may become necessary.
The important thing to understand is that an SLA breach by an Indian IT company is not just a case of failing on technical grounds but also involves issues of breach, claims for damages, jurisdiction, termination and enforcement of laws across the border.
An initial legal assessment before taking any further action can go a long way in safeguarding your legal rights.
Share:
Share on
×