When a technology provider misses the performance targets in a Service Level Agreement, the standard remedy is a service credit, usually calculated as a percentage of your monthly fee and applied as a deduction on your next invoice. Collecting service credits for an SLA breach is rarely automatic. You generally have to detect the breach, document it, and file a formal claim within a short window, all while clearing a list of exclusions the provider has built into the contract. The credit amount is only part of the picture; the cap on your recovery, the exclusive-remedy clause, and the filing deadline usually matter more than the headline percentage.
How the Credit Is Calculated
Most SLAs tie the credit to a tiered percentage of the monthly service fee. A typical structure: uptime below 99.9% but above 99.0% earns a 10% credit; below 99.0% but above 95.0%, a 25% credit; below 95.0%, a 50% credit. On a $10,000 monthly contract, those tiers translate to $1,000, $2,500, or $5,000.
A smaller number of contracts use a per-hour model, granting a fixed credit (often around 5%) for every full hour of downtime past the allowed threshold. That model tends to favor the customer during long outages but can pay less during frequent short interruptions that each stay inside their own measurement window.
The measurement period is the detail people miss. Most SLAs measure performance over a calendar month or billing cycle rather than per incident. Two outages in the same month get combined when calculating whether the provider hit its target. If one falls on March 31 and the next on April 1, they are measured separately, and neither month on its own may trigger a credit.
The Cap and the Exclusive Remedy Clause
Nearly every SLA caps total credits at some percentage of the monthly fee, usually 100%. A catastrophic multi-day outage will not generate a credit larger than what you paid that month. Some contracts cap credits lower, at 25% or 50%, which feels absurd when a three-day outage costs the business far more than the service itself.
The bigger problem is the “sole and exclusive remedy” language in most commercial SLAs. That clause means the credit is all you get. You cannot sue for lost profits, business interruption, or other consequential damages flowing from the outage. Under the Uniform Commercial Code, commercial parties can agree that one specific remedy is the only one available, and courts generally enforce that limitation between businesses.1Legal Information Institute. UCC 2-719 – Contractual Modification or Limitation of Remedy
The practical effect is stark. If a $10,000 monthly cloud service goes down for a week and the outage costs you $200,000 in revenue, the credit tops out somewhere around $10,000. The exclusive-remedy clause blocks the remaining $190,000. Experienced buyers negotiate higher caps or carve out gross negligence and willful misconduct before signing.
When the Exclusive Remedy Can Be Set Aside
There is one meaningful escape hatch. When an exclusive remedy “fails of its essential purpose,” the UCC allows the injured party to pursue the full range of remedies otherwise available under commercial law, including consequential damages.1Legal Information Institute. UCC 2-719 – Contractual Modification or Limitation of Remedy This typically applies when a provider’s failures are so severe or persistent that the credit mechanism no longer provides meaningful compensation. A 10% credit is not a remedy if the service is down more than it is up.
Courts can also treat a limitation on consequential damages as unconscionable depending on the facts, though in commercial settings between sophisticated parties the presumption favors enforcement.1Legal Information Institute. UCC 2-719 – Contractual Modification or Limitation of Remedy If repeated provider failures have made the credit system meaningless, this doctrine is worth raising with a contract attorney before assuming you have no recovery beyond the capped credit.
Exclusions That Can Block Your Claim
Providers do not pay credits for every minute of downtime. SLAs carry exclusion lists that carve out categories of outages the provider treats as outside its responsibility. These exclusions quietly erase what looked like an obvious credit on paper.
- Scheduled maintenance. Planned downtime announced in advance almost always falls outside the uptime calculation. Some contracts require seven or more calendar days of advance notice for maintenance to qualify as scheduled.
- Customer-caused issues. If the failure traces back to your own configuration, misuse of the service, or your third-party vendors, the provider usually owes nothing. Exceeding usage quotas or ignoring the provider’s documented guidance falls into this bucket.
- Force majeure. Natural disasters, government actions, widespread internet disruptions, and similar events outside the provider’s reasonable control are standard exclusions. Check whether the definition is narrow or broad.
- Third-party failures. When the outage originates with an upstream provider or infrastructure outside the vendor’s direct control, most SLAs exclude it.
- Your own security failures. Downtime stemming from compromised credentials on your side or inadequate security practices is typically off the hook.
One exclusion catches customers off guard: many SLAs state you are ineligible for credits if you have unpaid invoices or are otherwise in breach yourself. Withholding payment as leverage during a service dispute can disqualify you from the very credits you are trying to collect.
Documenting the Breach
A credit claim lives or dies on documentation. Providers routinely deny claims that lack specific, time-stamped evidence aligning with the contract’s measurement period.
Pull uptime and downtime reports from the provider’s portal and from any independent monitoring tools you use. Independent monitoring data carries extra weight because it cannot be dismissed as the provider’s own numbers reporting on the provider’s own performance. Save every incident ticket opened during the outage with timestamps showing when you notified the provider. Those tickets often contain the provider’s own acknowledgments, estimated repair times, and root-cause descriptions that are difficult to walk back later. Keep correspondence with technical support, especially emails where an engineer admits the failure or confirms a timeline.
Cross-reference everything against the measurement period defined in your contract. If the SLA uses calendar months, an outage spanning March 31 to April 2 needs to be documented as two separate events across two measurement periods. Organize the evidence chronologically. Screenshots of error messages, latency spikes, and failed connection attempts round out the record. Without this level of detail, providers routinely deny claims for insufficient evidence.
Filing the Claim
SLA credit claims are not self-executing. Even when the provider plainly knows its service went down, you have to file a formal request within a tight deadline. Miss the window and you waive the credit permanently, no matter how clear-cut the breach.
Follow the notice provision in the contract to the letter. It specifies the delivery method (a particular email address, an online portal, or in older contracts certified mail) and the department or role that must receive the claim. Sending to the wrong contact or using the wrong channel gives the provider grounds for a procedural rejection.
Most SLAs give you 30 days from the end of the measurement period in which the breach occurred. Some contracts are more generous; a few are tighter. The clock usually starts at the end of the billing cycle rather than the date of the outage, so a failure early in the month gives you more calendar time than one late in the month. Treat the deadline as immovable.
After you submit, expect a review of roughly 15 to 45 days while the provider’s billing team compares your submission against their internal logs. If approved, the credit almost always appears as a deduction on your next invoice rather than a cash payment. Get written confirmation of the approved amount and track it against your billing records, because credits occasionally fall off during invoice processing and have to be flagged again.
Remedies Beyond Credits
Credits are not the only lever when a provider underperforms. Several non-monetary remedies can matter more than a percentage off next month’s bill, though some have to be negotiated in rather than assumed.
Service extensions add free time to the end of your contract term, compensating for a period when the service was not delivering what you paid for. This works best in fixed-term agreements where you are locked in anyway. In managed-services arrangements, step-in rights allow you to temporarily take over the affected service operations or bring in a third party to do the work at the provider’s cost. Step-in rights are powerful but almost never appear in standard agreements.
Chronic failure provisions carry the real leverage. These clauses let you terminate the contract without paying early-exit fees if the provider repeatedly misses the same service level over a defined period. A common trigger is three or more breaches of the same metric within a rolling six- to twelve-month window, though the exact threshold varies. Termination for cause under a chronic failure clause releases you from remaining payment obligations and, in well-drafted agreements, requires the provider to assist with transitioning your data and services to a replacement vendor. Without a chronic failure clause, a provider can miss targets every month, pay the capped credit, and keep collecting fees on a contract you cannot escape.
Earn-Back Clauses to Watch For
Some providers include earn-back provisions that let them claw back credits already issued if they hit their targets in subsequent months. Under a typical earn-back structure, meeting or exceeding the service level for a defined number of consecutive months after a breach reverses some or all of the credits previously applied to your account.
This is one of the more aggressive terms in the SLA world and fundamentally undermines the credit mechanism. A credit is meant to compensate you for a month of degraded service; allowing the provider to take it back because performance improved later does not undo the harm. If earn-back language appears during negotiation, push to remove it, or at a minimum limit it to partial recovery and require sustained over-performance rather than merely meeting the baseline target.
What to Negotiate Before Signing
Reading about credits after the contract is signed is like reading the insurance policy after the accident. A handful of provisions make an outsized difference in how much protection you actually have.
- Raise the credit cap. Push above 100% of the monthly fee, or negotiate a separate pool of consequential damages for catastrophic outages. Even a modest carve-out for gross negligence gives you leverage the standard contract denies.
- Narrow the exclusions. Force majeure clauses that sweep in “internet disruptions” or “third-party failures” can swallow almost any outage. Push for specificity, and require minimum advance notice for scheduled maintenance to qualify.
- Add a chronic failure trigger. If the contract lacks a termination right for repeated breaches, add one. Define the threshold clearly: how many breaches, of which metrics, over what rolling window.
- Strike earn-back clauses. Credits issued should stay issued. If the provider insists, require sustained over-performance before any reversal.
- Extend filing deadlines. Thirty days from month-end is tight for complex organizations. Negotiate for 60 or 90 days if you can, and ask the provider to self-report breaches rather than putting the entire detection burden on you.
Providers who resist moving on any of these terms are often the ones whose standard SLAs are built to minimize payouts rather than enforce accountability. That is useful information before you sign.