Hiring guide

SaaS service credits: from SLA claim to invoice application

By CFO Index · Published

A SaaS outage can create a possible service-credit claim, but a support ticket is not an approved credit and an approved credit is not necessarily a refund. Whether you buy or sell SaaS, give the claim its own evidence trail before it changes a cash forecast. The practical deliverable is an incident-to-invoice register, distinct from a general credit-note register or a prepaid usage wallet.

Confirm the eligible service and governing terms

Record the product, plan, production instance, subscription holder, contract version and relevant service month. Check covered experiences, exclusions, measurement method and claim deadline against the applicable SLA. Your team's outage observation is supporting evidence, not automatic proof that the contractual availability measure failed. Keep the incident timeline, timezone and supplier status references, and appoint an owner to preserve evidence. Ask the appropriate adviser about disputed entitlement; this guide is an operational control, not a legal interpretation of a real claim.

Use a named vendor example without generalising it

Atlassian's SLA, effective 30 April 2026 and reviewed for this article, makes credits conditional on a qualifying failure and a timely claim. Its terms apply awarded credits against a future payment for the affected product, with no cash value for unused credits. Its support guidance distinguishes incident support from a separate compensation request, due by the fifteenth of the following month. Those are Atlassian-specific terms, not a universal SaaS policy. Check the relevant plan and agreement rather than copying the deadline to another vendor.

Keep a state register with evidence for every transition

Use one claim ID linked to its incident evidence, product, service month and supplier ticket. Separate an estimated claim from the amount actually awarded. Record a rejection or expiry explicitly; deleting it hides whether an expected saving disappeared. A received submission acknowledgement proves receipt, not entitlement. Award evidence should identify the product, amount, currency, restrictions and application route.

Suggested SLA claim-to-application register
StateRequired evidenceCash forecast treatment
Potential claimIncident, applicable terms and eligibility reviewUnconfirmed sensitivity, not base cash
SubmittedClaim ticket and submission timestampStill not an awarded credit
AwardedSupplier confirmation and usable amountModel conditional future application separately
AppliedInvoice reference and actual offsetReduce only that invoice's expected cash
Rejected or expiredDecision or deadline evidenceRemove unsupported saving; retain history

Reconcile a small hypothetical claim

Hypothetical example, unrelated to any vendor's compensation tiers: your team estimates a €500 claim, the supplier awards €300, and its next eligible €2,000 invoice actually applies €200. The invoice amount to settle is €1,800 before any other adjustments, assuming the offset is valid. The remaining €100 is an unused awarded balance, subject to its terms. Do not forecast a €300 cash receipt and also pay only €1,800: no refund has been agreed in this example. The unawarded €200 estimate never becomes a confirmed saving.

Trace the actual application route

For a reseller purchase, establish who receives the vendor credit and which document passes the benefit to the customer. Atlassian's SLA routes its service credit to the reseller for onward treatment; do not assume a direct customer balance exists as well. Confirm invoice currency, billing entity, affected product and application timing. A long annual renewal cycle can delay use of a credit even when the award is already known. Any expiry or non-transferability rule must remain visible in the register rather than being treated as unrestricted cash.

Close the loop without inventing accounting treatment

Reconcile opening unused awards plus new awards less invoice applications and confirmed expiries to closing unused awards, by currency. Match every application to the issued invoice and subsequent payment evidence. Investigate unexpected full-price invoices before changing the award record to make totals agree. The accounting and tax owners determine recognition and documentation under the applicable framework; a claim register does not decide those policies. Review missed deadlines separately from vendor rejections so operational follow-up can improve without inflating realised recoveries.

Sources and further reading

Find relevant CFO support