The GASB Standards For Intangible Assets

Introduction

Governmental Accounting Standards Board Statement No. 51 provides the core framework for recognizing and reporting intangible assets of U.S. state and local governments. Issued in 2007, it remains relevant because governments increasingly rely on software, licenses, easements, water rights, patents, trademarks, and other resources that lack physical substance but provide service capacity beyond a single reporting period (GASB, 2007). Statement 51 generally treats qualifying intangible resources as capital assets and establishes guidance for recognition, internally generated assets, useful life, amortization, and impairment indicators. Application today also requires attention to later standards, particularly Statement No. 96 on subscription-based information technology arrangements. GASB 96 clarifies that perpetual software licenses remain within Statement 51, while qualifying subscription arrangements generally follow a right-to-use model under the newer guidance (GASB, 2020). The practical challenge is therefore not merely identifying something as “software” or “intangible.” Governments must determine what legal or contractual right they control, how long that right provides service capacity, whether development criteria have been met, and which GASB standard applies to the arrangement.

Recognition and Classification of Intangible Assets

Statement 51 defines an intangible asset through three basic characteristics: it lacks physical substance, is nonfinancial in nature, and has an initial useful life extending beyond one reporting period (GASB, 2007). Examples include easements, water and timber rights, patents, trademarks, copyrights, and computer software. The emphasis is on controlled service capacity rather than physical form. Cash, receivables, and investments are financial assets and therefore fall outside this definition even though they may also lack physical substance. A government should begin by identifying the right acquired or created, the period over which the right is expected to support operations, and whether another standard governs the transaction. A patent held to support public-service delivery differs economically from an asset held primarily for investment return, just as a perpetual software license differs from temporary access to vendor-hosted software. Classification affects measurement, amortization, disclosures, and later impairment analysis, so scope questions should be resolved before journal entries are prepared. Capitalization also does not mean that every small item must be recognized; governments may apply reasonable capitalization thresholds consistently when immaterial amounts would not affect users’ decisions.

Internally Generated Assets and Computer Software

Statement 51 gives special attention to internally generated intangible assets because early project spending often occurs before a government knows whether a usable resource will result. Capitalization begins only after the government can identify the specific objective and service capacity, demonstrate technical or technological feasibility, and show an intention and ability to complete or continue development (GASB, 2007). Costs incurred before those recognition criteria are met are expensed rather than retroactively added to the asset later. Computer software requires additional stage analysis. Preliminary activities such as evaluating alternatives are generally expensed, while qualifying application-development work may be capitalized after the recognition point. Training and routine maintenance after implementation are normally expensed, and upgrades are capitalized only when they increase functionality rather than merely preserve existing performance. This distinction makes project accounting dependent on operational evidence. Finance staff need documentation showing when feasibility was established, which activities belonged to each phase, when the software became ready for use, and which employee or vendor costs related directly to development. Without disciplined project records, year-end accounting can become a guess rather than a faithful representation of the underlying asset.

Useful Life, Amortization, and Impairment

Finite-lived intangible assets are amortized systematically over the period in which they are expected to provide service capacity. Legal and contractual terms create an upper boundary, but technological or functional obsolescence can produce a shorter useful life than the formal right. A perpetual license, for example, may remain legally valid while practical usefulness declines because security support ends or systems are replaced. Statement 51 also allows an intangible asset to be treated as having an indefinite life when no legal, contractual, regulatory, technological, or other factor currently limits service capacity; such an asset is not amortized until circumstances establish a finite life (GASB, 2007). Impairment is a separate issue. Statement No. 42 requires governments to evaluate significant and unexpected declines in service utility for capital assets, including qualifying intangible assets, when relevant indicators exist (GASB, 2003). Software abandonment, loss of legal rights, major technological obsolescence, or a canceled development project may therefore require a write-down or expense. The central accounting question is whether the asset still possesses the service capacity reflected in its carrying amount, not whether a newer product happens to exist.

Subscription-Based Information Technology Arrangements

Cloud computing and subscription software created accounting questions that Statement 51 alone did not fully address. GASB Statement No. 96 establishes guidance for subscription-based information technology arrangements, or SBITAs, and generally recognizes a subscription liability together with an intangible right-to-use subscription asset when the arrangement meets the standard’s definition (GASB, 2020). The distinction from Statement 51 depends on substance rather than vendor terminology. GASB 96 explicitly excludes perpetual software licenses because those arrangements represent a purchase and remain subject to Statement 51 as amended. Implementation Guide No. 2023-1 further clarifies that an agreement that automatically renews until canceled is not automatically a perpetual license; an option to terminate at each renewal means the arrangement should still be analyzed as a subscription rather than assumed to be a purchase (GASB, 2023). The guide also confirms that common cloud models such as Software as a Service, Platform as a Service, and Infrastructure as a Service require analysis under the SBITA definition. Governments therefore need contract-level review instead of relying on labels such as “cloud,” “license,” or “subscription.”

Controls, Asset Registers, and Financial Reporting

Accurate intangible-asset reporting depends on controls that operate throughout procurement and project management rather than only at year-end. Contracts for software, easements, licenses, data rights, or internally developed systems should be reviewed by finance, legal, information-technology, and procurement staff before accounting conclusions are finalized. Project managers should identify development stages, track directly attributable labor and vendor costs, record the placed-in-service date, and report abandonment or enhancement decisions promptly. A centralized asset register can document the resource, owner, legal term, acquisition cost, useful life, amortization method, accumulated amortization, restrictions, and supporting contract. Statement 51 disclosures generally follow capital-asset reporting principles, while material policy choices such as capitalization thresholds and useful-life methods should be explained clearly when necessary for users to understand the statements (GASB, 2007). Strong controls are especially important when departments procure technology independently because decentralized buying can produce duplicate subscriptions, unrecorded obligations, inconsistent capitalization, and cybersecurity exposure. The accounting system is most reliable when operational ownership and financial responsibility are connected instead of treated as separate processes.

Conclusion

GASB Statement No. 51 remains the foundation for accounting and financial reporting of qualifying intangible assets held by state and local governments, but modern application requires reading it together with later standards and implementation guidance. The standard establishes the recognition framework for resources that lack physical substance, are nonfinancial, and provide service capacity beyond one reporting period. It also distinguishes exploratory activity from capitalizable internally generated development, requires evidence-based useful lives, and links finite-lived assets to systematic amortization. Statement No. 42 remains relevant when service utility declines significantly and unexpectedly, while Statement No. 96 now governs many subscription-based technology arrangements through a right-to-use model (GASB, 2003; GASB, 2020). The boundary between a perpetual software license and a subscription can be subtle, which is why the 2023 implementation guidance emphasizes contract substance rather than labels (GASB, 2023). A complete governmental accounting process therefore combines technical standards with contract review, project documentation, asset management, and cross-functional controls. Intangible assets may be invisible physically, but poor classification or measurement can materially distort a government’s reported resources and obligations.

References

Governmental Accounting Standards Board. (2003). Statement No. 42: Accounting and financial reporting for impairment of capital assets and for insurance recoveries.

Governmental Accounting Standards Board. (2007). Statement No. 51: Accounting and financial reporting for intangible assets.

Governmental Accounting Standards Board. (2020). Statement No. 96: Subscription-based information technology arrangements.

Governmental Accounting Standards Board. (2023). Implementation Guide No. 2023-1: Implementation guidance update—2023.

Editorial Staff

Academic Master Education Team is a group of academic editors and subject specialists responsible for producing structured, research-backed essays across multiple disciplines. Each article is developed following Academic Master’s Editorial Policy and supported by credible academic references. The team ensures clarity, citation accuracy, and adherence to ethical academic writing standards

Content reviewed under Academic Master Editorial Policy.

This author does not have any more posts.