TL;DR: SLA service credits are the price reductions a supplier owes you when it misses a service level, but most providers do not apply them automatically. You have to spot the SLA breach, prove it the way the contract measures it, and file a service credit claim before a short claim window closes, often one or two months after the billing month. This guide explains how SLA service credits are calculated, which clauses decide whether you get paid, how deadlines work at major providers, and a step-by-step process to recover every credit your contracts already allow.
Why SLA Service Credits So Often Go Unclaimed
Every service level agreement makes a promise: the service will be available, fast or fixed within a set time, and if it is not, the customer gets something back. That something is usually a service credit, a percentage off a future invoice. On paper, it is a clean mechanism. In practice, a large share of SLA service credits are never collected.
The reason is simple. Credits are earned automatically, but they are not paid automatically. Microsoft’s own guidance on reading SLAs is blunt about it: service providers don’t usually apply service credits automatically, and the customer must detect outages that breach the SLA, document them, and submit claims within the deadline. The same page warns that if you miss the deadline, you forfeit the credit regardless of the severity of the outage.
That puts the burden on the customer, and the customer is usually not organised to carry it. The people who notice an outage (IT operations, a service desk, end users) are rarely the people who own the contract (procurement or legal) or pay the invoice (accounts payable). By the time a monthly service report arrives, nobody has checked it against the SLA schedule, and nobody knows the claim window is already running.
Three patterns show up again and again:
- Nobody owns the claim. The SLA breach is visible in a ticket or a status page, but no team is responsible for turning it into a service credit claim.
- The contract is hard to read in the moment. Service levels, exclusions, measurement periods and credit tables sit in a schedule that few people have open when an incident happens.
- Deadlines are short and different for every supplier. One provider gives you weeks, another gives you two months, and a bespoke outsourcing contract may set its own notice rules.
None of these are legal problems. They are process problems, which is good news: a disciplined process recovers SLA service credits that are already yours under the contract. This guide is written for procurement, finance, accounts payable, IT and vendor management, and legal and contracts teams who want to build that process.
What SLA Service Credits Are and How They Emerged
A service credit is a contractual adjustment that reduces what the customer pays when the supplier fails to meet a defined service level. ObligaAI’s glossary defines service credits as contractual adjustments a customer may receive when a supplier fails to meet specified service commitments, and the closely related SLA credit as the financial remedy written into a contract for a missed service target.
Credits only make sense inside a service-level agreement: the part of a contract, or a document attached to it, that sets measurable performance targets and states what happens when they are missed. Typical targets include monthly availability, incident response time, resolution time and support responsiveness.
From outsourcing schedules to cloud SLAs
Service credits grew up in IT outsourcing and managed-services contracts, where a customer paid a fixed monthly charge and wanted a predictable consequence when performance slipped. The idea moved into telecoms, facilities management and, at scale, into cloud services.
Cloud made SLAs more standardised and more public. In June 2014, guidelines on standardising cloud service level agreements were presented to the European Commission to help business users save money and get the most out of cloud computing services. In 2018, the US National Institute of Standards and Technology published NIST SP 500-307, a model for describing cloud service metrics, noting the value of data on measurable capabilities such as quality of service, availability and reliability.
International trade lawyers followed. The UNCITRAL secretariat’s 2019 Notes on the Main Issues of Cloud Computing Contracts describe service credits as an often-used mechanism to compensate the customer for non-performance by the provider, typically on a sliding scale tied to how far performance fell short.
Why a credit is not the same as a refund
Service credits are usually framed as a reduction in price, not a payment of damages. The AWS Amazon Compute SLA covered in the next section, for example, states that AWS will apply service credits only against future payments for the affected service, and that credits do not entitle the customer to any refund or other payment. That distinction matters for finance teams: an unclaimed credit never shows up as a receivable, so it is easy for it to disappear without anyone noticing.
How SLA Service Credits Are Calculated
Most SLA service credits follow the same three steps: measure performance over a defined period, compare it with the committed service level, and look up the credit percentage in a tiered table. The details in each step decide the amount.
The uptime formula most SLAs use
Availability SLAs usually express performance as a monthly uptime percentage. Microsoft’s guide to reading SLAs uses an illustrative formula of this form: Monthly Uptime Percentage = (Total Billable Minutes − Downtime) ÷ Total Billable Minutes × 100. The terms that matter are hidden in the definitions: what counts as a “billable minute”, what counts as “downtime”, and which minutes are excluded.
Microsoft’s page also makes a point every buyer should remember: a 99.9% SLA doesn’t guarantee that the service always remains available. An SLA is a promise about compensation, not a guarantee of uptime, and narrow definitions mean a service can have problems that affect your users without violating the SLA.
Tiered credit tables
Once you have the measured percentage, the credit comes from a table. The AWS Amazon Compute SLA is a clear public example. For its region-level commitment of 99.99%, the published tiers are (AWS):
| Monthly uptime percentage | Service credit |
|---|---|
| Less than 99.99% but at least 99.0% | 10% |
| Less than 99.0% but at least 95.0% | 30% |
| Less than 95.0% | 100% |
Microsoft notes that service credits are typically a percentage of the monthly service fee for the affected service. Bespoke contracts vary more: some use fixed amounts per missed service level, some use points that convert into a percentage of charges, and many apply an overall cap.
A worked example with illustrative figures
Take an illustrative managed-hosting contract with a $20,000 monthly fee, a 99.9% monthly availability commitment, and a credit schedule of 5% of the monthly fee below 99.9%, 10% below 99.5% and 25% below 99.0%.
- A 30-day month has 43,200 minutes.
- At 99.9%, the supplier may be down for about 43 minutes before breaching.
- Suppose the month had 260 minutes of qualifying downtime. Availability is (43,200 − 260) ÷ 43,200 × 100 ≈ 99.40%.
- 99.40% is below 99.5% but above 99.0%, so the 10% tier applies: a credit of $2,000.
Now change one fact. Suppose 120 of those minutes fell inside a scheduled maintenance window the contract excludes. Qualifying downtime drops to 140 minutes, availability rises to about 99.68%, and the credit falls to the 5% tier: $1,000. Same outage, half the credit. This is why the definitions and exclusions deserve as much attention as the headline percentage.
The SLA Clauses That Decide Whether You Get Paid
Before you can file a service credit claim, you need to read the SLA the way the supplier will read it when they assess your claim. Five groups of clauses do most of the work.
Measurement, exclusions and service scope
- Service level definitions. Is availability measured per service, per region, per instance or per user? A breach in one component may not count if the SLA measures something broader.
- Measurement period. Monthly is common, but some contracts measure quarterly, which can average a bad week away.
- Exclusions. Scheduled maintenance, customer-caused issues, force majeure events, third-party networks and beta features are often excluded. Check whether maintenance requires advance notice to qualify for exclusion.
- Whose data counts. Some SLAs rely on the supplier’s monitoring; others accept customer evidence. Know which before an incident, not after.
Credit rates and caps
Credit rates may be tiered by severity, applied per missed metric, or calculated per incident. UNCITRAL’s notes record that a sliding scale may apply and that an overall cap for service credits may also apply (UNCITRAL). A typical cap limits total credits in a month to a percentage of that month’s fees. When several service levels are missed in the same month, the cap often decides the final number.
Claim conditions and the claim window
This is where most credits are lost. Look for:
- How to claim. A support ticket, a portal form, a formal notice to a named address, or a request through a reseller.
- The claim window. The deadline, and the event it runs from: the incident, the end of the billing month, or the date you became eligible.
- Evidence required. Incident IDs, timestamps, affected resources, logs, or proof that users were affected.
- What happens if you miss it. Usually the credit is forfeited outright.
Treat the claim window as an obligation with a date, the same way you would treat a contract notice period before a renewal.
Remedy and termination wording
Check whether credits are described as the sole and exclusive remedy, a “sole financial remedy”, or one remedy among others. Check for chronic-failure rights: the right to terminate or escalate if the supplier misses service levels repeatedly. These clauses do not change how you claim a credit, but they decide what else you can do. They are covered in more detail later in this guide.
Claim Windows and Deadlines at Major Providers
Deadlines vary widely, so the only safe rule is to read each contract. Two of the largest providers show the range clearly.
| Provider and service | How to claim | Deadline |
|---|---|---|
| AWS, Amazon Compute (EC2) | Open a case in the AWS Support Center | By the end of the second billing cycle after the incident |
| Microsoft Azure (via CSP partner) | Partner creates a support ticket in Partner Center | Within two months from the end of the billing month of the incident |
| Other Microsoft online services (via CSP partner) | Partner creates a support ticket in Partner Center | Within one month from the end of the billing month of the incident |
Sources: AWS Amazon Compute SLA and Microsoft Partner Center.
Microsoft’s general SLA guidance notes that common timeframes range from 30 to 60 days after the end of the billing month, and that each service provider sets its own deadline. Smaller providers and bespoke contracts can be far shorter; some require a support ticket within a day of becoming aware of an incident before a later claim is valid.
Two practical consequences follow. First, the claim window often starts running before anyone has the monthly service report in hand. Second, if you buy through a reseller or partner, the reseller may need to file for you, which adds a step and eats into the time. Microsoft’s Partner Center page, for example, states that credit requests are accepted only from CSP direct and indirect providers, not from indirect resellers.
A Step-by-Step Service Credit Claim Process
A reliable process does not need special tools to start. It needs ownership, a calendar, and a habit of comparing evidence with the contract every month.
Step 1: Build an SLA register
List every supplier contract with service levels. For each one, record the service levels, measurement period, credit table, cap, exclusions, claim method, claim window and the evidence required. Link each entry to the clause it came from, so anyone checking a claim can see the source. This is a core part of contract obligation management: turning clauses into tracked obligations with owners and dates.
Step 2: Assign owners across teams
Name one owner per contract for SLA review, usually in procurement or vendor management, with named contacts in IT operations (evidence), accounts payable (applying credits to invoices) and legal (disputes). Agree who files the service credit claim and who approves it.
Step 3: Collect performance evidence every period
Gather the supplier’s service reports, your own monitoring data, incident tickets and status-page records for each measurement period. Providers often set precise evidence rules. AWS requires the dates, times and affected region of each incident, the resource IDs, and request logs documenting the errors, and states that failure to provide them will disqualify you from receiving a Service Credit (AWS). Microsoft requires the customer tenant’s GUID, the outage incident identifier and proof that the customer encountered the outage, and says the customer email submitted as evidence must come from the domain of the affected tenant (Microsoft Partner Center).
Step 4: Compare performance with the clause, not the headline
Recalculate each service level using the contract’s own definitions and exclusions. Flag every SLA breach, the tier it falls in, the credit amount after any cap, and the date the claim window closes. Do this as soon as the report arrives, not at quarter-end.
Step 5: File the claim in the required format
Use the exact channel, subject line and evidence the contract or SLA specifies. Quote the clause, state the measured performance, the credit calculation and the amount. Keep a copy of everything you send and the timestamp of submission.
Step 6: Track the response and apply the credit
Log the supplier’s response, the credit approved and the invoice it will appear on. Accounts payable should check that the credit actually lands; a credit that is approved but never applied is still leakage. If the claim is rejected, compare the reason with the clause, and escalate through the dispute process if you disagree.
Step 7: Review patterns quarterly
Repeated misses tell you more than any single credit. Track breaches by supplier and service, check whether chronic-failure rights have been triggered, and feed the record into renewal negotiations.
How ObligaAI Helps You Catch and Claim SLA Service Credits
The process above works, but it is manual, and it is exactly the kind of work that slips when teams are busy. ObligaAI’s SLA leakage product is built around the same steps. Its stated purpose is to compare service performance with the SLA terms in your contracts, helping teams identify missed targets and review potential credits before they expire.
Your clauses, interpreted. ObligaAI reads service-level and credit clauses (availability, response and resolution times, credit rates, exclusions, claim windows and caps) and turns them into plain-language obligations, each with a confidence score and a link to the exact passage in the contract. That is the SLA register from Step 1, built from the contracts themselves and traceable to the source.
Three kinds of record go in, one answer comes out. The product page describes three inputs: contracts and SLA schedules, service reports and tickets, and monthly invoices. The output is the clause, the breach, the credit due, its dollar value and the date to claim by. That covers Steps 3 and 4: evidence compared with the clause, not the headline.
Deadlines tracked. ObligaAI’s page notes that service credits often come with a limited claim period, and that every claim window is calendared so earned credits are not lost to timing. Its illustrative example shows April availability of 99.4% against a 99.9% target, a $1,000 credit due, and a 30-day window to claim it.
Advisory first, your team decides. ObligaAI does not file claims on your behalf. In the product’s own words, it shows the breach, the clause and the amount, and reminds you of the deadline; your team makes the claim. Nothing changes a payment, an invoice or a contract until someone in your organisation decides it should. It also works beside the contract, ERP and billing systems you already run, rather than replacing them.
SLA credits are one form of contract value leakage, alongside supplier overbilling and unbilled revenue. If you want to see what is leaking in your own contracts, you can start free with a few real contracts and service reports.
Sole Remedy Clauses, Penalties and the Legal Limits of Credits
Service credits are a contractual remedy, so their effect depends on the wording of the contract and the law that governs it. This section is general background, not legal advice; take advice on specific contracts.
Sole and exclusive remedy wording
Many supplier-drafted SLAs state that credits are the customer’s only remedy for missed service levels. The AWS Amazon Compute SLA quoted earlier, for example, says that it sets forth your sole and exclusive remedies for unavailability. UNCITRAL’s notes explain the consequence: fixing service credits as the sole and exclusive remedy may limit the customer’s rights to other remedies, including suing for damages or terminating the contract (UNCITRAL).
The difference between “sole and exclusive remedy” and narrower wording, such as “sole financial remedy” or a remedy “without prejudice to other rights”, can decide whether a customer can terminate for repeated failure. Read the remedy clause together with termination rights.
Penalties, liquidated damages and price adjustments
In common-law systems, a clause that punishes a breach rather than protecting a legitimate interest can be unenforceable as a penalty clause. In England and Wales, the UK Supreme Court restated the penalty rule in Cavendish Square Holding BV v Makdessi, decided on 4 November 2015, framing the question around whether a clause is out of all proportion to the innocent party’s legitimate interest. Service credits are usually structured and described as price adjustments for a lower level of service, rather than as liquidated damages, partly to stay clear of penalty arguments.
UNCITRAL’s notes add the other side of the same coin: excessive service credits may be unenforceable if they have been considered an unreasonable approximation of harm. Suppliers resist high credits for commercial reasons; very high credits can also invite legal challenge.
When a limited remedy fails
In the United States, Uniform Commercial Code § 2-719 provides that where circumstances cause an exclusive or limited remedy to fail of its essential purpose, other remedies may be available, and that consequential damages may be limited or excluded unless the limitation is unconscionable (Cornell Legal Information Institute). Article 2 of the UCC governs sales of goods, so whether and how this reasoning applies to service and software contracts depends on the contract and the state. It is a reminder that remedy clauses are read against background law, not in isolation.
The Limitations of Relying on Service Credits
Service credits are useful, but they are a narrow tool. Keep their limits in view.
- Credits are small compared with business impact. A credit is a percentage of the fee for the affected service, not of the revenue you lost. A severe outage may cost far more than the monthly fee.
- Caps cut off the worst months. The months with the biggest failures are often the months where the cap applies.
- The burden of proof sits with you. You must detect, document and claim, in the supplier’s format, within the supplier’s deadline.
- Definitions can exclude real problems. Narrow downtime definitions and broad exclusions mean degraded performance may not count as an SLA breach at all.
- Credits reduce future spend, not past spend. If you leave the supplier, unused credits may be worth nothing unless the contract says otherwise.
- Claiming has a cost. Gathering evidence and chasing claims takes time from IT, procurement and finance. Without a process, the effort can exceed the credit on small contracts, which is one reason claims are skipped.
The answer is not to ignore credits, but to treat them as one control among several: performance reviews, escalation paths, chronic-failure exits and renewal leverage.
Negotiating Stronger Service Credit Terms at Renewal
The best time to fix a weak SLA is before you sign or renew. Large public-sector templates show how seriously service levels can be treated: the UK government’s Model Services Contract, published by the Cabinet Office and Government Legal Department, is designed for high-value, complex services and has been developed for services contracts valued over £20 million. Most commercial contracts are smaller, but the same questions apply.
Points worth negotiating:
- Longer claim windows, running from the date you receive the service report rather than the date of the incident.
- Automatic credits, applied by the supplier on the next invoice when its own report shows an SLA breach.
- Customer evidence accepted, not only the supplier’s monitoring.
- Clear, narrow exclusions, with scheduled maintenance limited to agreed windows and advance notice.
- Meaningful tiers and a realistic cap, sized to the importance of the service.
- Chronic-failure rights, such as termination or escalation after repeated misses, that survive any sole remedy wording.
- Reporting obligations, requiring monthly service reports in a usable format within a set number of days.
Bring evidence. A record of every SLA breach and every credit claimed or missed over the contract term is the strongest argument for better terms, and it is a by-product of the process described above.
Turning Earned Credits Into Recovered Contract Value
SLA service credits are not a windfall. They are money the contract already says you are owed when a supplier under-delivers. The gap between credits earned and credits claimed is created by process: no owner, no register, no calendar, and evidence that arrives after the claim window has closed.
Close that gap in order. Build the register, assign owners, compare evidence with the clause every period, file in the required format before the deadline, and confirm that credits actually land on invoices. Then use the record at renewal to negotiate longer windows, automatic credits and stronger remedies.
Teams that want to run this without building spreadsheets by hand can use ObligaAI to read SLA clauses, compare them with service reports and invoices, and flag each breach with the clause, the credit due and the date to claim by, while people stay in charge of every claim.
Frequently Asked Questions About SLA Service Credits
What are SLA service credits?
SLA service credits are contractual price reductions a supplier owes when it misses a service level defined in a service level agreement, such as monthly availability or response time. They are usually a percentage of the monthly fee for the affected service, set by a tiered table, and are normally applied against future invoices rather than paid as cash refunds.
Are SLA credits applied automatically?
Usually not. Most providers require the customer to detect the outage, document it and submit a claim within a deadline, and Microsoft’s guidance notes that providers don’t usually apply credits automatically. Some negotiated contracts do require the supplier to apply credits on the next invoice when its own report shows a breach, so check the SLA wording.
How long do I have to file a service credit claim?
It depends on the contract. AWS requires Amazon Compute claims by the end of the second billing cycle after the incident; Microsoft’s Partner Center page sets two months after the billing month for Azure and one month for other services. Smaller suppliers and bespoke contracts can be much shorter, so record each claim window in a calendar.
What evidence do I need to claim SLA service credits?
Expect to provide incident dates and times with time zones, the affected services or resource IDs, incident or ticket references, and logs or monitoring data showing the impact. Some providers require evidence in a specific form, such as Microsoft’s rule that customer email evidence come from the affected tenant’s domain. Missing evidence is a common reason for rejection.
How do I calculate a service credit?
Calculate performance for the measurement period using the contract’s definitions, subtract excluded time such as scheduled maintenance, and compare the result with the committed service level. Then find the tier in the credit table, apply the percentage to the fee for the affected service, and check whether a monthly or annual cap reduces the amount.
What happens if a supplier rejects my claim?
Compare the stated reason with the SLA clause, especially definitions, exclusions and evidence rules. If you disagree, respond with the clause reference and your calculation, and escalate through the contract’s dispute or governance process. Keep records of every submission and response; repeated rejections and breaches are useful evidence at renewal.
Are service credits my only remedy for an SLA breach?
Only if the contract says so. Many supplier SLAs describe credits as the sole and exclusive remedy, which can limit claims for damages or termination. Other contracts preserve additional rights, such as termination for chronic failure. The effect depends on the exact wording and the governing law, so take legal advice for specific disputes.
Can service credits be unenforceable?
Potentially, depending on governing law. In common-law systems, a clause that operates as a penalty rather than protecting a legitimate interest can be unenforceable, and UNCITRAL notes that excessive service credits may be unenforceable as an unreasonable approximation of harm. Credits are usually drafted as price adjustments for a lower level of service, which reduces that risk.
Start Recovering the Service Credits You Have Earned
Every month that passes without a review is a month of SLA service credits that may expire. Start with your highest-value supplier contracts: list their service levels and claim windows, compare last month’s service reports with the clauses, and file for any credit that is still inside its window.
If you would rather see what is already leaking across your contracts, ObligaAI compares your SLA terms with service reports and invoices and shows each breach with the clause, the credit due and the date to claim by. Start free with ObligaAI (no credit card required), or start a conversation with the team about your contracts.