ASC 350-40 Internal-Use Software Costs — Core Rule

ASC 350-40 Internal-Use Software Costs requires capitalization of software development costs incurred during the application development stage, with expensing of preliminary and post-implementation costs; the asset is then amortized over its useful life (ASC 350-40-25-1).

How ASC 350-40 Internal-Use Software Costs Works

• Stage classification determines treatment. ASC 350-40-25-1 identifies three stages: (1) preliminary project stage (expense all costs), (2) application development stage (capitalize eligible costs), and (3) post-implementation/operation stage (expense all costs). The preliminary stage includes conceptual formulation, evaluation of alternatives, and final selection of IT alternatives. Only costs incurred after management commits to the development project and believes it is probable the software will be completed and used are capitalized.

• Capitalized costs include direct labor, purchased software, and external consulting. Under ASC 350-40-25-4 through 25-7, capitalize employee salaries and benefits for personnel directly involved in software development; purchased software used in development; fees paid to external consultants; and infrastructure costs allocable to the project (e.g., hosting, data center capacity). Do not capitalize allocated overhead or IT department salaries for maintenance of existing systems—those are period costs.

• Measurement is at accumulated cost; no revaluation. ASC 350-40-30-1 requires measurement at cost. There is no revaluation to fair value (unlike ASC 350-30 for purchased intangibles). Track cumulative expenditures by project phase to support the preliminary vs. application development boundary.

• Amortization begins when the asset is ready for use. Per ASC 350-40-35-1, begin amortization once the software is substantially complete and ready to be placed in service, even if not yet fully deployed company-wide. Useful life is typically 3–7 years depending on technology risk and business strategy. Estimate useful life separately from hardware assets; software often has shorter lives due to technological obsolescence.

• Impairment testing applies if circumstances change. Under ASC 350-40-35-2, if facts and circumstances indicate an asset may be impaired (e.g., the software is abandoned, or expected cash flows have declined materially), perform an impairment test using the guidance in ASC 360-10-35 (loss on disposal) or ASC 350-30-35 (intangible asset impairment). Common triggers: project cancellation, merger/acquisition, or technology disruption making the software obsolete.

• Cloud-based SaaS and hosting fees are generally expensed. While ASC 350-40 applies to software owned or licensed in-house, fees paid to third parties for cloud services (e.g., Salesforce, Workday) are typically operating expenses under ASC 605-10 or ASC 842 (if a software-as-a-service lease exists), not capitalized as internal-use software.

ASC 350-40 Internal-Use Software Costs — Practical Example

Scenario: TechCorp begins development of a custom inventory management system in January 2024. Costs incurred:

• January–March 2024 (preliminary stage): $150,000 for requirements analysis, vendor evaluation, and architecture planning. → Expense (all costs in preliminary stage).

• April 2024–December 2024 (application development stage): $800,000 for developer salaries ($600,000), purchased software licenses for development tools ($120,000), and external consultant fees ($80,000). → Capitalize (eligible costs in development stage).

• January 2025 (post-implementation): $60,000 for staff training and minor bug fixes. → Expense (post-implementation costs).

The software goes live on February 1, 2025. TechCorp estimates a 5-year useful life.

Journal entries

Balance sheet impact (Feb 1, 2025): Capitalized Software $800,000; Accumulated Amortization ($13,333); Net Book Value $786,667.

ASC 350-40 Internal-Use Software Costs — Common Pitfalls

• Failing to separate preliminary from application stage. Many finance teams capitalize costs incurred during feasibility studies and business case development. The key question: Has management committed to the project and deemed completion probable? If the project is still being evaluated, it's preliminary. Review project governance records and capital approval dates to establish the boundary (ASC 350-40-25-2).

• Capitalizing training, documentation, and post-go-live support. After the software is ready for use, all costs—including end-user training, documentation updates, and bug-fix labor—are expensed. A common audit trap is reclassifying post-implementation labor as "capitalized enhancements" when it should be period expense. The bright-line rule: If the cost does not add functionality or extend useful life, expense it (ASC 350-40-25-8).

• Inconsistent useful life estimates and impairment neglect. Software useful lives often compress due to technology shifts. If your company standardizes a 7-year life but the software uses legacy architecture or depends on deprecated platforms, impairment risk rises. Regularly reassess useful lives during annual planning cycles and document the rationale. Failure to test for impairment when a project is shelved or replaced is a common audit deficiency.

ASC 350-40 Internal-Use Software Costs — Key Paragraphs

• ASC 350-40-25-1 — Three-stage model and when costs are capitalized.
• ASC 350-40-25-4 through 25-7 — Types of costs eligible for capitalization (salaries, purchased software, external fees).
• ASC 350-40-35-1 — Amortization begins when software is ready for use.
• ASC 350-40-35-2 — Impairment testing and abandonment guidance.
• ASC 360-10-35-30 through 35-35 — Asset impairment measurement (referenced in ASC 350-40-35-2).
• ASC 350-40-25-8 — Expensing post-implementation costs (training, documentation, support).