Impairment
What is Impairment?
Impairment is a permanent reduction in the value of an asset, recorded when its carrying amount on the balance sheet exceeds the amount the organization expects to recover from it.
Updated November 2026 · 5 min read
Impairment is an accounting adjustment that reduces the recorded value of an asset when that value is no longer recoverable. Assets such as equipment, software and goodwill are carried on the balance sheet at cost less depreciation or amortization. If something happens that makes an asset worth significantly less than that carrying amount, the organization must write it down and record a loss, known as an impairment charge.
Impairment matters for technology because technology assets can lose value suddenly. A software project might be abandoned before completion, a platform might be replaced earlier than planned or hardware might become obsolete when a data center is closed. In each case, the remaining book value may need to be written off, which can create large, unexpected charges. Understanding impairment helps IT finance teams anticipate these charges and explain them to leadership.
Definition of Impairment
An asset is impaired when its carrying amount, the value recorded on the balance sheet, exceeds the amount the organization can recover through using or selling it. Accounting standards require organizations to test assets for impairment when there are signs that their value may have declined, and to record a loss when impairment is confirmed.
Impairment differs from depreciation. Depreciation is a planned, systematic allocation of an asset's cost over its useful life, while impairment is an unplanned reduction caused by a specific event or change in circumstances.
Indicators of Impairment
Organizations test long-lived assets for impairment when events or changes in circumstances indicate that the carrying amount may not be recoverable. Common indicators include a significant decline in the asset's market price, a major change in how the asset is used, physical damage, legal or regulatory changes and a plan to dispose of the asset well before the end of its useful life.
For technology, typical triggers include deciding to replace a system early, abandoning a software development project, closing a data center and migrating workloads to the cloud while owned equipment still has book value.
Testing and Measuring Impairment
Under US GAAP, long-lived assets held for use are tested in two steps. First, the carrying amount is compared with the undiscounted future cash flows expected from the asset. If the carrying amount is higher, the asset is not recoverable, and the impairment loss is measured as the difference between the carrying amount and the asset's fair value.
Internal-use software has specific guidance under ASC 350-40. For example, if it is no longer probable that software in development will be completed and placed in service, it is written down to fair value, which is often zero. Goodwill and indefinite-lived intangibles follow separate impairment rules.
Importance of Impairment in IT Financial Management
Impairment charges can be large and arrive unexpectedly, affecting reported profit and attracting scrutiny from leadership, auditors and investors. Technology decisions, such as replacing platforms or moving to the cloud, are among the most common triggers.
IT finance teams that understand impairment can include its effects when evaluating technology decisions and avoid surprises.
Effects on Financial Results
An impairment charge reduces profit in the period it is recorded, often by the full remaining book value of the asset. It does not involve cash, since the cash was spent when the asset was bought or built, but it can still affect metrics, budgets and perceptions of a project's success.
Once recorded under US GAAP, impairment losses on assets held for use cannot be reversed, even if the asset's value later recovers. After impairment, the asset is depreciated or amortized from its new, lower carrying amount.
Informing Technology Decisions
Decisions to retire systems early, consolidate data centers or move workloads to the cloud often leave owned assets with remaining book value. That value is a sunk cost and should not determine whether the change is worthwhile, but its write-off affects reported results.
Including potential impairment charges in business cases, alongside the total cost of ownership (TCO) of each option, helps leadership understand the full financial effect of a decision and plan its timing.
How to Manage Impairment
Managing impairment involves monitoring assets for indicators, testing them when indicators appear and recording losses accurately, working closely with the accounting team and auditors.
Good asset records and clear communication between technology and finance teams make this process much smoother.
Monitoring Assets and Projects
IT finance teams should maintain accurate records of capitalized technology assets, including their book values and expected remaining lives, linked to the systems and projects they support. Records from IT asset management (ITAM) are an important source.
Changes in technology plans should be communicated to finance promptly. A decision to retire a system early, cancel a development project or exit a data center can trigger an impairment test, and finance needs time to assess it before the period closes.
Planning for Write-Downs
When an impairment is likely, IT finance teams can model its effect on reported results and work with leadership to plan its timing and communication. In some cases, shortening the useful life of an asset that will be retired early spreads the effect over the remaining period through higher depreciation, rather than recording it all at once. This is one situation where accelerated depreciation of the remaining book value better reflects how the asset will actually be used.
Lessons from impairments can also improve capitalization decisions. Repeated write-offs of abandoned software projects, for example, may indicate that projects are being capitalized too early, before completion is genuinely probable.
Examples of Impairment in IT Financial Management
The examples below show how impairment arises from common technology decisions.
Both use illustrative figures and simplified accounting.
In each, the charge reflects a change in plans rather than a failure of accounting, and planning for it reduced the surprise.
An Abandoned Software Project
A company has capitalized $2.8 million of development costs on a new internal billing platform. After a strategy change, it decides to buy a SaaS product instead and stops development.
Because the platform will not be completed or used, its fair value is zero. The company records a $2.8 million impairment charge, reducing profit in that quarter by the full amount, even though no additional cash is spent.
Exiting a Data Center
A company decides to close a data center and move workloads to the cloud over the next six months. Equipment in the data center has a book value of $4 million, and the company expects to recover $300,000 through resale.
The assets are no longer expected to generate cash flows beyond the migration period that would recover their carrying amount. The company writes them down to their fair value of $300,000, recording a $3.7 million impairment charge, and adds this to the business case for the migration.
Conclusion
Impairment is a permanent reduction in the value of an asset, recorded when its carrying amount exceeds what the organization can recover. It is triggered by events such as abandoned projects, early retirement of systems and data center closures, and it is recorded as a non-cash charge against profit.
In IT financial management, impairment is a frequent consequence of technology change. Monitoring assets, communicating changes in plans early and including potential write-downs in business cases help organizations manage impairment and avoid unwelcome surprises in their financial results.
Related terms
ASC 350-40
ASC 350-40 is the US GAAP standard for internal-use software. It sets the rules for when software development and implementation costs are capitalized as assets or expensed as incurred.
Total Cost of Ownership (TCO)
Total Cost of Ownership (TCO) is the full cost of an asset over its useful life. It covers purchase, implementation, operation, support and retirement, not just the contract price.
IT Asset Management (ITAM)
IT Asset Management (ITAM) is the practice of tracking every hardware, software and cloud asset an organization owns or pays for, from purchase to disposal, to control cost, risk and compliance.
Accelerated Depreciation
Accelerated depreciation is any method that records more of an asset's cost as expense in its early years and less later, reflecting faster loss of value and often reducing taxes sooner.