BAR chapter covering software capitalization, research-versus-development distinctions, amortization, and classification errors.
This chapter covers a technical area where classification decisions drive recognition, amortization, and disclosure. The main BAR issue is knowing when spending creates an asset, when it stays an expense, and how the answer changes across software and research contexts.
Software and R&D questions depend on project stage and intended use. Costs that look similar in ordinary business language can receive different accounting treatment if the activity is research, application development, post-implementation maintenance, or software developed for sale.
| Cost issue | What to decide first | Common BAR trap |
|---|---|---|
| Internal-use software | Which project stage the cost belongs to. | Capitalizing preliminary project or post-implementation training costs. |
| Software for sale | Whether technological feasibility or the relevant capitalization threshold has been met. | Using internal-use rules for external-sale software. |
| Research activity | Whether the activity is exploratory rather than a qualifying development cost. | Capitalizing research merely because management expects future value. |
| Amortization and impairment | When capitalized costs begin amortization and whether recoverability is impaired. | Stopping at capitalization without tracking later expense recognition. |
| Step | BAR question to ask | Accounting effect |
|---|---|---|
| 1. Identify the project purpose | Is the software for internal use, external sale, hosting, or broader research activity? | The applicable capitalization model depends on intended use. |
| 2. Locate the project stage | Is the cost preliminary, application-development, post-implementation, research, or after technological feasibility? | Similar spending can be expensed or capitalized depending on timing. |
| 3. Separate direct and indirect costs | Which labor, vendor, testing, training, data-conversion, or overhead costs qualify? | BAR often tests whether the candidate capitalizes only eligible costs. |
| 4. Determine amortization timing | When is the asset ready for use or available for sale, and over what benefit period? | Capitalization is incomplete without later expense recognition. |
| 5. Evaluate impairment or disclosure | Do changed expectations, obsolescence, or uncertainty affect carrying amount or reporting? | Software and R&D issues often combine measurement with user-facing disclosure. |
| Checkpoint | Ask before capitalizing | Accounting consequence |
|---|---|---|
| Intended use | Is the software internal-use, external-sale, hosting-related, or part of research activity? | The applicable model changes with intended use. |
| Project stage | Is the cost preliminary, application-development, post-implementation, after technological feasibility, or maintenance? | Stage often decides whether a similar cost is expensed or capitalized. |
| Cost type | Is the amount direct labor, vendor cost, training, data conversion, overhead, testing, or support? | Only eligible costs belong in the capitalized asset. |
| Readiness date | When is the software ready for intended use or available for sale? | Amortization begins when the asset is ready, not when cash is paid. |
| Obsolescence risk | Has technology, expected use, market demand, or recoverability changed? | Capitalized software may require impairment analysis or disclosure. |