Software a company buys or builds for its own use is an intangible asset, but only some of the spending gets capitalized. This lesson covers internal-use software, how to tell a software license from a cloud service contract, and what to do with the costs of implementing a cloud service.
License or service contract
The first question for any hosted software is whether the customer has acquired software at all. A hosting arrangement includes a software license only if both are true:
- the customer can take possession of the software at any time during the hosting period without significant penalty (no significant cost and no significant loss of value or use); and
- it is feasible for the customer to run the software on its own hardware or to have a party unrelated to the vendor host it.
If so, the license is an intangible asset accounted for as internal-use software, with a liability for any fees not yet paid. If not, the arrangement is a service contract: the fees are an expense over the service period. Software developed to be sold, leased or marketed is outside these rules (ASC 985-20).
Internal-use software: which costs to capitalize
Until ASU 2025-06 takes effect, internal-use software costs follow three project stages:
| Stage | Examples | Treatment |
|---|---|---|
| Preliminary project | Evaluating alternatives, choosing a vendor | Expense |
| Application development | Design, configuration, coding, installation, testing | Capitalize qualifying costs |
| Post-implementation | Training, routine maintenance | Expense |
Capitalization starts when the preliminary stage is complete, management commits to funding, and it is probable that the project will be completed and the software will be used to perform the function intended. It stops when the software is substantially complete and ready for its intended use, after all substantial testing. Qualifying costs are external direct costs of materials and services, payroll costs of employees working directly on the project (for the time they spend on it), and interest under ASC 835-20. Training and data conversion are expensed whenever they occur, except software built or bought to convert old data, and general, administrative and overhead costs are never capitalized. Upgrades that add functionality follow the same rules; maintenance is expensed.
Capitalized software is amortized, usually straight-line, once it is ready for its intended use, and tested for impairment under ASC 360. If a project in progress is no longer expected to be completed, it is written down to fair value less costs to sell, which is presumed to be zero.
Coming change: ASU 2025-06, effective for annual periods beginning after December 15, 2027 (early adoption permitted), removes the stages. Capitalization will start once management has authorized and committed to funding the project and completion is probable, a threshold not met while significant development uncertainty remains. It also moves website development costs (ASC 350-50) into ASC 350-40.
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.
On the exam
Decide license or service contract first. Then sort costs by nature: development work is capitalized; selection, training, data cleanup and overhead are expensed. Cloud implementation costs go over the hosting term, including reasonably certain renewals and periods the customer is reasonably certain not to cancel, starting at go-live.