Implementing a cloud service contract
A customer in a service contract applies the internal-use stage rules to its implementation costs as if the arrangement were a software project. Capitalized implementation costs are:
- presented where a prepayment of the hosting fees would be, with their amortization in the same income statement line as the fees, and their cash flows classified like the fees;
- amortized straight-line (unless another pattern fits better) over the term of the hosting arrangement: the noncancellable period, plus periods covered by an option to extend that the customer is reasonably certain to exercise, an option to terminate that it is reasonably certain not to exercise, or any such option the vendor controls;
- amortized for each module from when it is ready for its intended use;
- tested for impairment under ASC 360 as if they were a long-lived asset.
Example: a chain of veterinary clinics signs a 3-year scheduling subscription that starts on April 1, when the system goes live. Its renewal option is not reasonably certain. Costs before go-live:
| Cost | Amount | Treatment |
|---|---|---|
| Consultants comparing vendors | 20,000 | Expense |
| Vendor's configuration work | 90,000 | Capitalize |
| Own staff building interfaces | 30,000 | Capitalize |
| Cleaning and converting old records | 12,000 | Expense |
| Staff training | 15,000 | Expense |
The capitalized 120,000 is amortized over 36 months from April 1: 120,000 / 36 x 9 = 30,000 for Year 1.