Software and Computer Systems Capitalization Policy

Capitalization, Depreciation, and Disposal of Software and Computer Systems.

  1. Policy Overview

The purpose of this policy is to communicate consistent guidance in this specialized area of accounting; promote University compliance with specific guidelines issued by the Financial Accounting Standards Board (FASB); and promote proper accounting for University assets and expenses in conformity with generally accepted accounting principles (GAAP).

  1. Capitalization
  2. Non-capitalizable Expenses

Costs incurred during the preliminary project stage must be expensed as incurred. Preliminary project stage includes the following activities: Conceptual formulation of alternatives, evaluation of alternatives, determination of existence of needed technology, and final selection of alternatives.

  1. Definition of Capitalized Costs

Costs that have an estimable future benefit that are included on the Statement of Financial Position as assets, and amortized or depreciated over their estimated useful lives.

  1. Classification of Capital Costs

Software Development: Costs incurred for the development or acquisition of software for the University computer systems (such as procurement, payroll, student services, general ledger, and others), including software upgrades and new releases, may be capitalized if they:

  • Are an integral part of the system, or
  • Identifiably enhance the functionally of the system because of their direct relationship to it.

A major computer system becomes an asset of the University upon capitalization and will be recorded in the same manner as other assets and amortized over its estimated useful life. In addition, the total costs of a computer system must be reasonable and should accurately reflect the value of the system.

Computing Infrastructure Applications and Systems: May support multiple computer modules and integrated systems. These applications may be characterized as separate systems and therefore subject to the capitalization principles set forth in Software Development.

Implementation Stage: Costs incurred to implement the chosen technological solution, including planning, may be capitalizable if they relate to a system that fulfills the criteria for capitalization in accordance with this policy. This stage generally encompasses the following activities:

  • Design of chosen path, including software configuration and software interface;
  • Technical software coding
  • Installation of hardware
  • Testing
  • Data conversion (programs and tools only);
  • Other related costs; and
  • Equipment

Specific types of costs generally incurred during the implementation stage are:

  • Purchased Software:The cost to purchase software.
  • Personnel Costs: Large-scale computer projects may entail the use of both employees and external consultants to design and implement the system. (The costs of both directly allocable internal employees and external consultants who are directly dedicated to the development and implementation of the computer project may be capitalized.)
  • Travel, Lodging, and Other Similar Expenses:To qualify for capitalization, travel, lodging and similar expenditures will be directly allocable to a specific system or application that meets the University’s criteria for capitalization.
  • Interest expense: Interest expense will be capitalized on software development projects consistent with the University’s policy for interest capitalization on long-term projects.
  • Training:Training costs incurred to develop or implement internal-use computer software/applications during the application development stage can be capitalized. Training in post-implementation/operation stages should not be capitalized, since such training programs should be conducted on a continuous basis, and the related costs should be recognized as an integral component of the University’s operating budget.
  • General and Administrative Expense: General and administrative expenses are not to be allocated and capitalized as part of the cost of a software development project.
  • Maintenance, Service and Warranty Contract Costs: These are not considered as capitalized costs. Extended maintenance and warranty contracts entered into at time of purchase must be treated as prepaid assets and expensed over the time period for which the benefits of such maintenance and warranty contracts extend.
  • Software License Agreements: These are not capitalized unless ownership is indicated within the license agreement. Software license agreements not indicating ownership should be expensed.
  • Equipment: Equipment should be purchased, managed and capitalized in accordance with the University equipment policy. A major computer system implementation may have many smaller pieces of equipment that individually may not be capitalized but as a group form an integral part of a system implementation and can be capitalized as part of that system.

Useful Life of Software

In determining the estimated useful life over which the costs incurred for internal-use computer software will be amortized, departments should consider the effects of obsolescence, technology, competition, and other economic factors on useful life. Departments should consider if rapid changes are occurring in the development of software products, software operating systems, or computer hardware, and whether the University intends to replace any technologically obsolete software or hardware.

Amortization of Software

Amortization of the computer software should start once the software is put into live mode or active status. The software should be amortized based on the estimated useful life on a straight-line basis.

Impairment

Impairment in the value of the cost basis of internal use computer software can occur when:

1) Internal-use computer software is not expected to provide substantive service potential;

2) A significant change occurs in the extent or manner in which the software is used or is expected to be used;

3) A significant change is made to the software program;

4) Costs of developing or modifying internal-use computer software significantly exceed the amount originally expected to develop or modify the software.