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.