These standards establish when software-related costs must be expensed immediately and when they must be capitalized as assets. They also define what qualifies as internal-use software and how long capitalized software should be amortized.

The University System of Maryland (USM) follows national accounting standards for how costs related to internally developed or purchased software must be recorded.

USM has adopted Statement of Position (SOP) 98-1, Accounting for the Costs of Computer Software Developed or Obtained for Internal Use, issued by the American Institute of Certified Public Accountants (AICPA). This guidance was endorsed by the National Association of College and University Business Officers (NACUBO) as the industry standard for public not-for-profit higher education institutions.

This policy applies to all public higher education institutions and ensures consistent, compliant financial reporting across the industry.

Internal-Use Software

Software qualifies as internal-use software if:

  • It is developed internally or modified solely to meet the institution’s internal needs; and
  • During development or modification, no substantive plan exists to market the software externally.

Stages of Software Development

Accounting treatment depends on the stage of the project.

Examples include:

  • Conceptual formulation of alternatives
  • Evaluation of alternatives
  • Determination of needed technology
  • Final selection of alternatives

Accounting Treatment:
All internal and external costs incurred during this stage must be expensed.

Examples include:

  • Design of chosen path (including software configuration and interfaces)
  • Coding
  • Installation to hardware
  • Testing (including parallel processing)
  • Data conversion (if necessary for new system access)

Accounting Treatment:
Internal and external costs incurred during this stage must be capitalized.

Capitalization begins only when:

  1. The preliminary project stage is complete; and
  2. Management commits to funding the project and it is probable the project will be completed and used as intended.

Examples include:

  • Training
  • Application maintenance

Accounting Treatment:
All costs incurred during this stage must be expensed.

Capitalizable Costs

Only the following costs may be capitalized during the application development stage:

  • External Direct Costs

    • Fees paid to third parties for development services
    • Costs to obtain software from third parties
    • Travel costs directly associated with software development
  • Payroll and Payroll-Related Costs

    • Salaries and benefits for employees directly involved in coding and testing
    • Only the portion of time spent directly on the software project may be capitalized
  • Interest Costs

    Interest incurred during development may be capitalized in accordance with Financial Accounting Standards Board (FASB) issued October 1979.

    Read Statement No. 34, Capitalization of Interest Cost

Non-Capitalizable Costs

The following costs must not be capitalized:

  • General administrative costs
  • Overhead costs
  • Training
  • Ongoing maintenance

Upgrades and Enhancements

Costs for upgrades or enhancements may be capitalized only if it is reasonably assured that the expenditure will result in additional functionality.

If no additional functionality is added, costs must be expensed.


Useful Life

Internal-use software shall be assigned a useful life of 10 to 15 years for amortization purposes.


Significance

Adoption of SOP 98-1:

  • Promotes industry-wide comparability
  • Provides clear guidance on capitalization practices
  • Ensures consistent asset treatment across public higher education institutions
  • Supports accurate financial reporting of software assets within Capital Equipment Inventory / Asset Management