Accounting for the Development Costs of Internal-Use Software

In this paper, we evaluate accounting practices for internal‐use software expenditures. Statement of Position No. 98‐1 (SOP No. 98‐1) requires expensing certain costs and capitalizing others. We argue that current accounting practice does not allow enough capitalization, since costs incurred during the systems analysis stage of model‐based systems development are expensed regardless of whether they create future benefits. The quest for uniformity in accounting treatment in the form of a single rule for multiple economic phenomena (i.e., treating all systems acquisition and development methods the same) results in reduced ability to reflect economic differences between systems acquisition and development methods. To illustrate, we provide an example of the differential effects of adopting SOP No. 98‐1 for firms using different development approaches. Under the SOP, “Analysis” costs are expensed. Under model‐based approaches, especially those with downstream effects, these Analysis costs are assets, since t...

[1]  Jacqueline L. Reck,et al.  Market Reaction to ERP Implementation Announcements , 2001, J. Inf. Syst..

[2]  Paul Zarowin,et al.  The boundaries of financial reporting and how to extend them , 1999 .

[3]  Mark W. Nelson Behavioral Evidence on the Effects of Principles- and Rules-Based Standards , 2003 .

[4]  Grady Booch,et al.  Object-Oriented Design with Applications , 1990 .

[5]  B. Lev Intangibles: Management, Measurement, and Reporting , 2001 .

[6]  Leandro Cañibano,et al.  Accounting for Intangibles: A Literature Review , 2004 .

[7]  Fred D. Davis,et al.  Explaining Software Developer Acceptance of Methodologies: A Comparison of Five Theoretical Models , 2002, IEEE Trans. Software Eng..

[8]  Katherine Schipper,et al.  Principles‐Based Accounting Standards , 2003 .

[9]  Warren J. McGregor Accounting for research and development costs , 1980 .

[10]  James C. Wetherbe,et al.  Key Trends in Systems Development in Europe and North America , 1994 .

[11]  D. Eric Hirst,et al.  Evaluating concepts-based vs. rules-based approaches to standard setting , 2003 .

[12]  Kerry Nulty,et al.  Accounting for intangible assets , 1998 .

[13]  B. Lev,et al.  The Value-Relevance of Intangibles: The Case of Software Capitalization , 1998 .

[14]  Birgit Geppert,et al.  The SDL pattern approach - a reuse-driven SDL design methodology , 2001, Comput. Networks.

[15]  Elizabeth A. Eccher Discussion of the value relevance of intangibles: The case of software capitalization , 1998 .

[16]  James A. Largay Commentaries on Principles‐ vs. Rules‐Based Standards , 2003 .

[17]  Jeffrey L. Whitten,et al.  Systems Analysis and Design Methods , 1986 .

[18]  Sridhar P. Nerur,et al.  Revolution or Evolution: A Comparison of Object-Oriented and Structured Systems Development Methods , 2001, MIS Q..

[19]  Joseph H. Callaghan,et al.  Financial Information Systems: Teaching REA semantics within an Information Engineering framework , 2002 .

[20]  R. W. Plyler,et al.  Methodology myths: four tenets for systems developers , 1993 .

[21]  James E. Hunton,et al.  The Reaction of Financial Analysts to Enterprise Resource Planning (ERP) Implementation Plans , 2002, J. Inf. Syst..

[22]  Eileen Souza The Impact of CASE on Software Development , 1991 .