Credit notes and SLA service credits issued after revenue recognition

A credit note, goodwill refund, or SLA-breach service credit issued after revenue has already been booked is not a new expense, it is evidence that the original transaction price was overstated, and it must be reflected as a reduction of revenue in the period the entitlement to the credit arose, not merely expensed when the credit note is cut. Getting this wrong overstates historical revenue and can mask a recurring pattern of SLA failures that should have been constraining variable consideration from day one.

Does the credit compensate for a shortfall in the original performance obligation (e.g., an SLA uptime breach), or settle an unrelated separate dispute? If related to the original obligation, is it treated as a reduction of the original transaction price (variable consideration) in the period the entitlement arose, not as a new expense? Does the pattern or frequency of credits issued suggest the original constraint on variable consideration was insufficiently conservative and needs revisiting? Is a refund liability recognized at period end for credits the entity expects to issue in future periods based on breaches already occurring?

1. Identify the nature of the credit: does it compensate for a shortfall in the service already promised under the contract's performance obligation (SLA uptime breach, service-level penalty), or does it settle a separate dispute unrelated to the original promise (e.g., a one-off gesture for an unrelated complaint)?
2. If the credit relates to the original performance obligation, treat it as variable consideration that reduces the transaction price, not as an operating expense.
3. Recognize a refund liability at the point the SLA breach or shortfall event occurs (not when the credit note is later issued), estimating the amount using the expected value or most likely amount method.
4. Apply the constraint: if a pattern of SLA credits is emerging, incorporate that experience into the estimate for the current and future periods rather than treating each credit as a one-off surprise.
5. When the credit note is issued and applied against an invoice, reduce the refund liability (and receivable/cash), with no further P&L impact if the liability was properly estimated in advance.
6. Reassess the refund liability estimate at each reporting date using actual credit-issuance experience, adjusting revenue in the current period for any difference.

Measure the refund liability at the amount the entity expects to credit back to the customer, using the expected value method when a range of credit outcomes is plausible (e.g., varying uptime shortfall severities) or the most likely amount when the credit is a fixed, defined percentage triggered by a binary SLA breach. Present the liability separately from trade payables, and reduce revenue (not record an expense) both when the liability is first recognized and when it is subsequently trued up.

Disclose: policy for classifying SLA and goodwill credits as revenue reductions versus expense; nature and drivers of significant credit note or service-credit activity during the period; effect on reported revenue where material; refund liability balance and roll-forward; basis for estimating the refund liability (expected value or most likely amount) and any constraint applied; whether a recurring pattern of credits prompted a change in the variable consideration estimate.

• Booking SLA credits and discretionary refunds as an operating or '
• customer success'
• expense instead of a reduction of revenue
• recognizing the revenue reduction only when the credit note is administratively issued rather than when the SLA breach or shortfall event actually occurred
• failing to update the variable consideration estimate for future periods once a recurring pattern of credits emerges, effectively repeating the same estimation error quarter after quarter
• treating a discretionary goodwill credit as unrelated to revenue simply because it was not contractually mandated, when in substance it compensates for the same service shortfall
• netting credits against unrelated revenue lines instead of the specific contract or performance obligation they relate to.