There is a growing emphasis on replacement of existing information systems that are aged or do not meet all of management's reporting needs with new, more flexible information systems. The resulting projects to develop or obtain computer software for internal use can differ from traditional capitalizable software because: 1) the projected budgets are more significant in dollar amount, and 2) capitalizable cost can include the cost of third party consultants as well as the payroll-related cost of Duke employees with time devoted to the projects.
Recognizing the growing magnitude of cost involved in such systems, generally accepted accounting literature provides guidelines for capitalization of computer software developed or obtained for internal use. This procedure defines internal use computer software, outlines the three stages of computer software development and provides guidance on capitalization of such cost. G/L account 667700, Major Computer Software is used to capitalize costs that meet these guidelines.
Internal use software is software having the following characteristics:
There are three stages of software development. The stages and their related processes are:
Internal and external costs incurred in the Preliminary Project Stage and the Post-Implementation Stage are expensed. Certain internal and external costs of the Application Development Stage are capitalizable and are discussed in the next section.
The Application Development Stage begins upon completion of the Preliminary Project Stage. Capitalization should begin when management, with the relevant authority, implicitly or explicitly authorizes and commits funding to the project and it is probable that the project will be completed. Costs that are capitalized include the following:
General and administrative cost and overhead cost is not capitalized as cost of internal-use software. Likewise, any activity during this stage devoted to end-user training or change management is not capitalized.
Capitalization ceases no later than the point at which a computer software project is substantially complete and ready for its intended use. This generally occurs after all substantial testing is completed.
Note that computer software developed or obtained for internal use can consist of more than one component or module. For example, an accounting software system may have several modules: a general ledger, accounts receivable subledger, accounts payable subledger, payroll, etc. The guidance in this procedure should be applied to individual components or modules.
Throughout Duke (e.g. within the Office of Information Technology) there may be many ongoing projects where computer software is being developed or obtained for internal use. This Procedure addresses specifically identified and approved projects of a large nature. Duke will only apply these software capitalization policies to projects with estimated or actual expenses of $2 million or more. Capitalizable costs should be charged to G/L account 667700, Major Computer Software.
For projects having estimated or actual expenses, less than $2 million and meeting the definition of computer software developed or obtained for internal use, costs are capitalized to the extent that they are consistent with G/L account 667600, Computer Software. The cost of any third party consultants as well as the payroll-related cost of Duke employees with time devoted to projects should be expensed as incurred. G/L account 677700 Minor Developed Computer Software should be used for any third party non-capitalizable expenses.
Similar to software developed or obtained for internal use, there is a growing emphasis on development of internet web sites to be used for various purposes. The stages for web site development are similar in nature and accounting treatment to the software development stages outlined above. Web site development stages are:
Costs incurred in the operation stage that involve providing additional functions or features to the web site should be accounted for as, in effect, new software. That is, costs of upgrades and enhancements that add functionality should be expensed or capitalized based on the guidelines of the Application Development stage.
| GAP History | |
| Issued: | January 2000 |
| Revised: | September 2001 |
| Revised: | July 2003 |