Kestrel Cloud Systems: implementation fees, refund rights and overage options
Kestrel Cloud Systems reports under IFRS with a 31 December year-end. On 1 October FY13 it signed a 36-month contract with a logistics customer containing three priced elements: a non-refundable implementation fee of 300,000 invoiced at signing, a subscription fee of 45,000 per month, and a usage charge of 0.02 per API call above 1,000,000 calls per month. Kestrel's platform cannot host this customer without 14 weeks of custom configuration and data mapping; that configuration has no alternative use to Kestrel and the customer cannot benefit from it without the subscription. Usage above the threshold is priced at the same rate Kestrel charges other customers. A side letter promises a refund of 150,000 if uptime falls below 99.5% in the first 12 months; comparable contracts show a 5% incidence. Kestrel paid a sales commission of 90,000 on signing and incurred 180,000 of implementation cost, of which 60,000 relates to a reusable data-migration tool. Kestrel estimates a 20% chance the customer will exceed 1.5 million calls in a given month.
1. Identify the performance obligations and determine how much revenue Kestrel recognizes in FY13, including the contract liability at year-end and the treatment of the 90,000 commission and 180,000 of implementation cost.
Read the worked answer
Performance obligations. Two candidates exist: the configured hosting service and the overage option. The implementation is not distinct. Kestrel is providing a significant integration service, the customer cannot benefit from the configuration without the subscription, and Kestrel could not redirect the configured platform to another customer. Implementation and subscription therefore form one combined performance obligation satisfied over time.
Transaction price. 300,000 + (45,000 x 36) = 1,920,000, less the expected refund of 7,500 (see second task) = 1,912,500.
FY13 revenue. The combined obligation is a single series delivered evenly, so revenue = 1,912,500 x 3/36 = 159,375.
Contract liability. Cash invoiced in FY13 = 300,000 + (45,000 x 3) = 435,000. Liability at 31 December = 435,000 - 159,375 = 275,625.
Overage. Priced at the standalone rate, so it conveys no material right and is not a performance obligation at inception. Revenue is recognized only when the calls occur; the 20% probability estimate does not enter the transaction price because there is no enforceable right.
Costs. The 90,000 commission is an incremental cost of obtaining the contract: capitalize and amortize over 36 months, giving 7,500 of expense in FY13 and 82,500 carried forward (split current/non-current by expected amortization). Of the implementation cost, 120,000 is directly attributable to fulfilling this contract and is capitalized as a fulfilment asset amortized over 36 months (10,000 in FY13); the 60,000 reusable tool is not contract-specific and is capitalized as an intangible or item of plant on its own useful life, not over 36 months.
2. Evaluate how the uptime refund right and the usage overage should be measured, and state the constraint analysis you would document for each.
Read the worked answer
Refund right - estimate. Expected value = 5% x 150,000 = 7,500. Expected value is appropriate because Kestrel has a portfolio of comparable contracts and the outcome is binary but repeated, so it better predicts the consideration than a most-likely-amount approach.
Refund right - constraint. Because the reversal, if it happens, is 150,000 against a 1,920,000 contract, it is not automatically highly probable that no significant reversal will occur. Two positions are defensible: (i) include the expected value and carry a 7,500 refund liability, reducing FY13 revenue by 7,500 x 3/36 = 625; or (ii) constrain the estimate to zero on the grounds of the 5% history. Whichever is adopted must be applied consistently, supported by the historical claims record, and revisited each period. Documenting both the estimate and the constraint judgement is what an inspector will look for, not the arithmetic.
Overage. The overage is an option for additional services at the standalone price. It gives the customer no discount, so it is not a separate performance obligation and no consideration is allocated to it. The 20% probability of 1.5 million calls is not variable consideration in the contract because the customer has made no enforceable commitment; it becomes relevant only as a demand forecast for capacity planning. If the customer had committed to a minimum annual volume, that minimum would be variable consideration subject to the constraint and would be allocated to the hosting obligation.