Free Service Downtime Credit Note Template & Generator

When a hosted service misses its uptime commitment, the credit is not a goodwill number someone picks — it falls out of the outage clock, the minutes the agreement excludes from that clock, and the availability band the remainder lands in. This credit note puts that chain on the page next to the incident ID and the invoice it adjusts, so the customer's AP team can post it without reading the postmortem.

Create this credit note No signup to start · live preview · PDF download

PDF downloads cost $2.29 per document, or are included with Unlimited at $9/month.

Create & preview free. Pay only when you download.

Use-case checklist

What to include in a service downtime credit note

A downtime credit that lands as a bare line reading “SLA credit — $240.00” invites the customer to reopen it. Without the incident window, the minutes you excluded from it, the hours in the billing period, the availability figure, and the clause number, their AP team cannot tell whether you credited the right service, subtracted the right window, or landed in the right band — so the credit sits unapplied, the original invoice ages past due for a balance the customer already considers settled, and someone rebuilds the calculation from Slack a month later. Citing the clause number also lets the note read as the remedy the contract already provides, which is what your customer's finance team is trying to match it against.

  • provider, customer, account, and service
  • incident, SLA, and affected period
  • original invoice and eligible charge
  • credit calculation and reason
  • tax adjustment, total credit, and application method

Example starting lines

DescriptionQtyRate
SLA service credit for downtime1$240

Complete it cleanly

Start from your monitoring record, not the customer's email. Take the verified start and end timestamps, state one time zone, convert the duration to decimal hours, then subtract only what your agreement's exclusion list actually names — and put the raw window and the excluded minutes on separate lines so the customer can reconcile them against their own status page. Divide what is left by the hours in that specific billing period, 744 in a 31-day month and 720 in a 30-day one, to get the availability figure, then read the band off the clause instead of rounding to a number that feels fair. Check whether setup fees, professional services, and usage overage on the same invoice belong inside the credit-eligible base before you multiply, and name the monitoring source on the note — the check, its polling interval, and the timestamps — because a customer who disputes the hours disputes the source first.

Worked example

SLA credit after a maintenance window overran by 7.2 hours

Brackenhill Cloud Ops runs the production environment for Tanner Freight Brokerage on a $2,400-per-month managed plan carrying a 99.9% monthly uptime commitment. A database upgrade inside an announced two-hour maintenance window on July 18, 2026 failed to roll back and left the environment down for another 7.2 hours, and Section 6.3 of their agreement prices the credit as a percentage of the monthly charge by availability band: 10% below 99.9%, 25% below 99.0%, 50% below 95.0%.

Credit-eligible managed hosting charge, invoice INV-4187 (July 2026; the $650.00 migration line sits outside the base)
$2,400.00
Hours in the July 1-31, 2026 billing period
744 hours
Incident INC-2261 end to end, 10:00 p.m. July 18 to 7:12 a.m. July 19 (US Central)
9.2 hours
Less the announced maintenance window, 10:00 p.m. to midnight, excluded under Section 6.4
2.0 hours
Countable unavailability charged against the commitment
7.2 hours
July availability, (744 - 7.2) divided by 744
99.03%
Section 6.3 band for 99.03%: below 99.9%, at or above 99.0%
10% of $2,400.00
Total credit on note CN-0912, applied to account CG-1180 against INV-4187
$240.00

This note settles what the availability clause owes on fees; it is not a refund of the 7.2 hours of service, which pro-rate to $23.23, and the availability section of an SLA usually carries a sole-and-exclusive-remedy sentence, so if yours does, this $240.00 is the whole contractual remedy for the incident rather than a first installment against the customer's own losses. The classic mistake is running the band percentage against the $3,050.00 invoice total instead of the $2,400.00 recurring line, or leaving the excluded window off the note entirely - that window is the difference between the 10% band and the 25% band here, and a customer who cannot see it will assume you rounded in your own favor.

When this document is the right choice

Use this credit note to document a reduction or reversal against an issued invoice. A credit note changes the amount owed on an earlier invoice without deleting the original record. Reference the original invoice and state the exact reason for the adjustment.

Frequently asked questions

How do I credit an outage that runs across the end of a billing period?

Split the clock at the period boundary and score each segment against its own month, because both the divisor and the band can change. A five-hour outage starting at 11 p.m. on June 30 puts 1 hour into June - 719 of 720 hours available, 99.86% - and 4 hours into July, 740 of 744, or 99.46%. Both land in the 10% band, so the outage produces two credits, 10% of June's charge and 10% of July's, not one credit for five hours. Issue one note per invoice, or one note with two calculation blocks that each name the invoice they adjust, because a single blended figure cannot be reconciled against either one.

Does the announced maintenance window really come out of the outage hours?

Only if your agreement's exclusion list says so, so read that list rather than assuming. In the example, Section 6.4 excludes announced maintenance, which is why a 9.2-hour incident is credited as 7.2 hours while the customer's status-page screenshot still says 9.2 - both figures belong on the note as separate lines for exactly that reason. Exclusion lists vary a lot in what they name: customer-side misconfiguration, third-party components, force majeure, and upstream transit failures each appear in some agreements and not others. Watch where the boundary falls, too, since here the excluded window is the difference between the 10% band and the 25% band, which makes it the line the customer challenges first.

The outage was in July but I am issuing the credit in August. Which period does it belong to?

A credit computed from July's availability adjusts July's charge even when the postmortem lands in August, so date the note when you issue it but name INV-4187 and the July 2026 period in the body, so the two can be tied together across months. If July is already closed in your books, your accountant will tell you whether to post the credit in the open period or reopen the closed one, since that call depends on your reporting rather than on the SLA. Watch the surcharge lines as well: if the July invoice carried anything assessed on the recurring charge, such as a state telecom fee or a regulatory surcharge, decide with your accountant whether the credit reduces that base and put the decision on the note, because a blank tax field is what turns a $240.00 credit into a two-week email thread.

A regional outage means credits for dozens of accounts. What does that cost on Invoity?

Building and previewing is free, so you can draft the whole batch and check every availability figure and band before you pay anything. Downloads are $2.29 per PDF, so an incident that produces 24 notes costs $54.96 in one-off downloads against $9 for a month of Unlimited - the batch covers the subscription six times over. Unlimited at $69 a year only beats paying $9 a month once you are issuing credits in eight or more months of the year, so if your incidents cluster into one or two bad quarters, the monthly plan is the cheaper shape.