Asset Depreciation Under IFRS (IAS 16): A Practical Guide for Finance and Operations Teams

Most depreciation frameworks tell you what to do. IAS 16 tells you what to think about — and then expects you to make a defensible decision.

That is not a criticism. It is actually a more intellectually honest approach to depreciation than prescriptive systems like MACRS or Schedule II of the Indian Companies Act. IAS 16 acknowledges that a hospital's medical equipment and a shipping company's fleet are fundamentally different assets with different consumption patterns, and that the same formula probably should not govern both.

But that flexibility has a cost: you have to make choices, document those choices, review them annually, and be prepared to defend them when an auditor asks why you chose a 10-year useful life for that piece of equipment instead of 8.

This article is a practical guide to what IAS 16 requires, what it leaves to your judgment, and what that means for how you manage and track your assets.

---

What IAS 16 covers

IAS 16 — Property, Plant and Equipment — is the IFRS standard that governs the recognition, measurement, and depreciation of tangible fixed assets. It applies to assets that:

• Are held for use in the production or supply of goods or services, for rental to others, or for administrative purposes
• Are expected to be used for more than one period

It does not apply to biological assets, mineral rights and reserves, or investment property (which is covered by IAS 40). For most organizations managing physical operational assets — machinery, vehicles, computers, buildings, infrastructure — IAS 16 is the relevant standard.

---

The two measurement models

IAS 16 gives organizations a choice between two models for measuring assets after initial recognition. The choice is made per class of asset and must be applied consistently to that entire class.

The cost model

This is the simpler and more commonly used approach. After initial recognition, the asset is carried at:

Cost − Accumulated depreciation − Accumulated impairment losses

Book value under the cost model is entirely driven by the depreciation schedule and any impairment. It does not respond to changes in market value. A building that has appreciated significantly in value will still appear on the balance sheet at its depreciated cost.

Most organizations use the cost model for most asset classes. It is straightforward, auditable, and does not require periodic professional valuations.

The revaluation model

Under the revaluation model, the asset is carried at its fair value at the date of revaluation, less subsequent depreciation and impairment. The asset is restated to fair value regularly enough that the carrying amount does not differ materially from fair value at the reporting date.

When an asset is revalued upward, the increase goes to Other Comprehensive Income (a revaluation reserve in equity) rather than the profit and loss statement. When it is revalued downward, the decrease hits the P&L unless there is a pre-existing revaluation surplus for that asset.

---

The three depreciation decisions IAS 16 requires

Under IAS 16, each depreciable asset (or class of assets) requires three explicit decisions. These are not defaults — they are accounting policy choices that must be documented and reviewed.

Decision 1: Useful life

IAS 16 defines useful life as either the period over which the asset is expected to be used by the entity, or the number of units of production expected to be obtained from the asset.

Two important nuances here. First, useful life under IAS 16 is the entity's expected use, not the asset's theoretical physical life. A machine built to last 20 years but which your organization plans to replace after 8 has a useful life of 8 years for IAS 16 purposes. Second, useful life is not fixed at acquisition. IAS 16 requires it to be reviewed at each financial year-end and revised if expectations have changed.

Factors that affect useful life under IAS 16:

Decision 2: Residual value

Residual value under IAS 16 is the estimated amount the entity would receive from disposing of the asset at the end of its useful life, net of disposal costs, as if the asset were already at the end of its useful life.

This is not what the asset is worth today. It is what you expect it to be worth, in its end-of-life condition, at whatever point in the future you expect to dispose of it — stated in current prices.

Residual value is subtracted from cost to arrive at the depreciable amount:

Depreciable amount = Cost − Residual value
Depreciation only applies to the depreciable amount

Like useful life, residual value must be reviewed at each financial year-end. If it increases, the depreciable amount decreases and future depreciation charges go down. If market conditions suggest lower resale values at end of life, the depreciable amount goes up and depreciation accelerates.

Decision 3: Depreciation method

IAS 16 does not prescribe a specific depreciation method. It requires that the method chosen reflects the pattern in which the asset's future economic benefits are expected to be consumed by the entity.

The standard explicitly recognizes three methods as acceptable:

The method must be applied consistently and reviewed at each financial year-end. A change in the expected pattern of consumption is a change in accounting estimate — it is applied prospectively (from the date of change forward) and does not require restating prior periods.

---

The annual review obligation

This is the part of IAS 16 that organizations most consistently fail to take seriously.

The standard requires that useful life, residual value, and depreciation method are all reviewed at each financial year-end. Not at acquisition. Not when something goes wrong. Every year.

In practice, most organizations set these values at acquisition and revisit them only when an auditor asks, when an asset is clearly nearing end of life, or when someone in finance notices that the depreciation figures look wrong.

The annual review does not have to be elaborate. For most assets in most years, the conclusion will be that no revision is needed. But the review needs to happen, the conclusion needs to be documented, and if a revision is made, the basis needs to be recorded.

What a proportionate annual review looks like:

• For a large portfolio: category-level review rather than asset-by-asset. If you have 200 laptops all in the same category with the same useful life, reviewing the category is reviewing all 200.
• For significant individual assets: a documented assessment of whether the original estimates still hold, with reference to any new information (maintenance records, market data, changes in how the asset is used).
• For the conclusion: a brief note in the working papers recording that the review was performed and whether any revisions resulted.

---

Component accounting

This is an aspect of IAS 16 that catches many organizations by surprise.

When a significant component of an asset has a different useful life from the rest of the asset, IAS 16 requires that component to be depreciated separately.

The standard example is a building: the structure might have a 40-year useful life, the roof a 20-year life, the HVAC system a 15-year life, and the interior fit-out a 10-year life. Each component is depreciated separately at its own rate.

Practical implications of component accounting:

The threshold for separate componentization is significance relative to the whole asset. There is no bright-line percentage in IAS 16 — it is a judgment call. In practice, a component that represents less than 5–10% of the total asset cost is typically not separately componentized.

Component accounting is also relevant for major inspections and overhauls. If a significant inspection is required regularly (every 5 years, for example), the cost of each inspection can be treated as a separate component — recognized when incurred and depreciated over the period until the next inspection.

---

What IAS 16 does not tell you

Given that IAS 16 is a principles-based standard, there are things it deliberately leaves open. This is where judgment and documentation become important.

It does not specify a minimum or maximum useful life. A car can have a useful life of 4 years or 8 years depending on the organization's replacement policy and maintenance approach. Both can be correct under IAS 16.

It does not mandate a residual value floor. Unlike Indian Schedule II which mandates 5%, IAS 16 expects you to estimate the actual likely residual value — which might be 0%, 5%, or 20% depending on the asset type and disposal market.

It does not specify how often to revalue under the revaluation model. "Sufficient frequency" is the guidance. For assets with volatile fair values, that might mean annually. For stable assets, every 3–5 years might be defensible.

It does not define "significant component" with precision. It requires judgment informed by the specific facts of each asset.

This is intentional. IAS 16 is designed to produce financial statements that faithfully represent economic reality, not to produce uniform outputs regardless of the underlying economics. The price of that fidelity is judgment — and the documentation to show that the judgment was applied carefully.

---

IFRS vs other frameworks: a quick comparison

---

The practical takeaway for finance and operations teams

IAS 16 is not difficult to comply with. The concepts — useful life, residual value, depreciation method, annual review — are not complicated. What is difficult is operationalizing them consistently across a large, diverse asset portfolio.

The organizations that do it well have three things in place:

Clear category definitions. Assets with similar characteristics and similar consumption patterns are grouped together. The depreciation configuration — method, useful life, residual value — is set at the category level and applied consistently to every asset in that category.

A documented annual review process. Not elaborate. A brief, structured review of each category's depreciation parameters at financial year-end, with a written record of what was reviewed and what, if anything, was changed.

A system that separates asset data from depreciation calculation. Asset records capture acquisition date, cost, and category. The depreciation calculation runs from those inputs automatically. There is no parallel spreadsheet to maintain and no manual calculation to reconcile against the asset register.

IAS 16 gives you the flexibility to do depreciation properly. The structure above is what turns that flexibility into practice rather than a compliance exercise.

---

For a worked comparison of how SLM, WDV, and DDB perform on the same asset — with the kind of analysis that underpins an IAS 16 method selection decision — see SLM vs WDV vs Double Declining Balance.