Provisions, onerous contracts and SLA exposures

Fixed-price enterprise SaaS implementations can turn onerous when actual delivery costs (customization, integration, extended professional services) exceed the remaining contract benefits, and SLA commitments with penalty or service-credit clauses create real obligations once a breach is probable, failing to provide for either understates liabilities and delays recognizing losses that are already economically locked in, while over-providing for general future losses (not tied to a present obligation) overstates liabilities and violates the recognition threshold.

Do any fixed-price implementation contracts show unavoidable remaining costs exceeding the remaining contract revenue, indicating an onerous contract? Are there recurring or specific SLA breaches where an outflow of resources is probable, distinguishing a real present obligation from a general future operating loss expectation? Is the provision measured at the best estimate of expenditure required to settle the obligation, using an expected value or most likely outcome approach as appropriate?

1. Confirm a present obligation exists as a result of a past event (a signed contract with committed scope, or an actual, identified SLA breach or shortfall), not merely a future operating loss expectation with no binding commitment.
2. Assess probability: recognize a provision only if it is more likely than not (probable) that an outflow of resources embodying economic benefits will be required to settle the obligation; otherwise disclose a contingent liability if the possibility is not remote.
3. For a potentially onerous contract, compare the unavoidable costs of meeting the remaining obligations (the lower of the cost of fulfilling the contract and any compensation or penalties from failing to fulfill it) against the economic benefits expected to be received under it; if unavoidable costs exceed expected benefits, the contract is onerous.
4. Before recognizing a separate onerous contract provision, first recognize any impairment losses on assets dedicated to fulfilling that contract (e.g., capitalized contract costs or specific fulfillment assets).
5. Assess whether the amount can be reliably estimated; if not (rare, but possible for very early-stage or highly uncertain legal exposures), disclose as a contingent liability rather than recognizing an unreliable provision.
6. For SLA exposures specifically, monitor actual service performance against contractual thresholds throughout the period and recognize a provision as soon as a breach becomes probable, not only once the penalty is formally invoiced or claimed.

Measure the provision at the best estimate of the expenditure required to settle the present obligation at the reporting date: use the expected value (probability-weighted) approach where a range of outcomes exists with many possible scenarios, or the single most likely outcome where the provision concerns a single obligation with essentially binary outcomes. For an onerous contract, measure the provision as the excess of unavoidable costs (direct incremental costs of fulfilling the remaining contract, not an allocation of costs the entity would incur regardless) over the expected remaining economic benefits under the contract. Discount the provision to present value where the time value of money is material (typically for long-dated obligations), using a pre-tax rate reflecting current market assessments of the time value of money and risks specific to the liability.

Disclose: a reconciliation of the carrying amount of provisions at the beginning and end of the period, showing additional provisions made, amounts used, unused amounts reversed, and any unwinding of discount; a brief description of the nature of the obligation and the expected timing of any resulting outflows for each material class of provision; the uncertainties about the amount or timing of outflows and the major assumptions made about future events; the nature of contingent liabilities not recognized as provisions (probability too low or amount not reliably estimable) and an estimate of their financial effect where practicable.

• Recognizing a general provision for anticipated future operating losses across the business rather than a specific present obligation tied to a past event
• failing to recognize an onerous contract provision for a clearly loss-making fixed-fee enterprise implementation until the loss is already fully realized
• measuring the onerous contract loss using fully allocated costs (including costs the entity would incur regardless of this specific contract) rather than the incremental, unavoidable costs of fulfillment
• waiting until an SLA penalty is formally invoiced or claimed by the customer before recognizing an obligation that was already probable and estimable at period end
• disclosing a contingent liability for an exposure that has actually crossed the probable threshold and should instead be recognized as a provision.