Compliance8 min read

IAS 16.51: The Annual Useful-Life Review Most Companies Skip

IFRS requires residual value and useful life to be reviewed at least every financial year-end. It is not a recommendation, and most registers have never had one.

Jarred Wakefield
Jarred Wakefield
Managing Director
July 29, 2026
IFRS reporting team performing the annual review of residual value and useful life under IAS 16

Most of the IFRS requirements around property, plant and equipment get attention because they change a number. IAS 16.51 gets ignored because it only requires you to look.

It is nonetheless a requirement, it recurs every year, and in our experience it is the most consistently unmet obligation in fixed-asset accounting.

The requirement

IAS 16.51 requires that the residual value and the useful life of an asset be reviewed at least at each financial year-end. Where expectations differ from previous estimates, the change is accounted for as a change in an accounting estimate in accordance with IAS 8.

Two things follow from that sentence, and both are routinely missed.

First, the review is mandatory and periodic. It is not triggered by an event. It happens annually, whether or not anything looks different. A conclusion of "no change required" is a valid outcome — but it is an outcome, which means a review has to have occurred to produce it.

Second, residual value is in scope alongside useful life. Residual values are very often set to zero as a register convention and never revisited. For assets with real resale or scrap value — vehicles, plant, IT hardware in some markets — that systematically overstates depreciation.

Why nobody does it

The requirement is not obscure. The reason it goes unmet is structural, and worth naming plainly:

  • Nothing fails if you skip it. No control breaks, no reconciliation goes out, no system throws an error. The register simply keeps depreciating on assumptions nobody has tested.
  • It cannot be done from a desk. A meaningful review of remaining life needs to know the asset's condition and duty cycle. That information lives on the floor, not in the ledger.
  • It is nobody's job. Finance owns the register but not the assets. Operations owns the assets but not the depreciation. The review sits in the gap.
  • The perceived downside is a restatement. Teams avoid opening the question because they expect the answer to force an adjustment to prior periods. It does not — the treatment is prospective, as we cover in re-assessing useful life does not reopen your books.

The compounding cost of skipping it

A register left unreviewed does not stay merely stale. It drifts in ways that touch several statements at once:

  • Assets fully depreciated but still in service. Carrying amount nil, productive life continuing. The balance sheet understates the asset base a lender or underwriter is pricing against.
  • Assets still depreciating that no longer exist. Ghost assets keep charging earnings every period until a physical verification retires them.
  • Lives set by convention rather than evidence. A blanket five-year life across a class where actual service runs twelve years overstates depreciation for the whole period, in every one of those years.
  • Residual values stuck at zero. Depreciable amount overstated by the full recoverable value at end of life.

None of these are exotic. They are what an unreviewed register looks like after a few years, and they all move in the same direction: depreciation too high, asset base too low.

What a review that satisfies IAS 16.51 looks like

The standard does not prescribe a method, which leaves preparers to design something defensible. In practice a review holds up when it produces:

  • Confirmation the asset exists. The first question in any remaining-life assessment is whether there is still an asset. This is where a physical verification does double duty.
  • A condition and duty-cycle observation, dated, for material classes.
  • A residual value conclusion, explicitly — including where it remains zero, with the reason.
  • A remaining-life conclusion per class, with the basis recorded.
  • A written outcome even where nothing changes. "Reviewed, no change required, on the following basis" is the evidence that the review happened.

Sampling is legitimate for large populations provided the approach is defensible and documented; the review does not require touching every unit every year, but it does require a basis for the conclusion drawn.

A note for groups reporting under both frameworks

US GAAP has no annual interval. ASC 360-10-35-22 is trigger-based — review when events or circumstances indicate the existing estimate is no longer appropriate. Groups that report under IFRS in some jurisdictions and US GAAP in others often run the whole estate on the looser standard by default.

That is a mistake in one direction only. Running the annual IFRS discipline across the group satisfies both, and produces the evidence file that makes any subsequent revision clearly a change in estimate rather than a correction. Running the trigger-based approach everywhere leaves the IFRS entities non-compliant.

The bottom line

IAS 16.51 asks for an annual review of residual value and useful life. The outcome is often "no change," and when there is a change it is applied prospectively with no comparative restated. The cost of compliance is low and the cost of neglect compounds quietly for years.

If the honest answer to "when were these lives last reviewed?" is that nobody knows, that is the finding — and the review is overdue rather than optional.

Frequently asked questions

What does IAS 16.51 actually require?+

That the residual value and the useful life of an asset be reviewed at least at each financial year-end, and that where expectations differ from previous estimates, the change be accounted for as a change in an accounting estimate in accordance with IAS 8.

Is the annual review optional if nothing seems to have changed?+

No. The review itself is required at least annually. Its outcome may legitimately be that no change is needed, but that conclusion has to be reached and, in practice, evidenced. 'Nothing appeared to change' without a review is not compliance.

Does US GAAP have the same annual requirement?+

Not as a fixed interval. ASC 360-10-35-22 requires review of depreciation estimates and adjustment of useful life when events or changes in circumstances indicate the current estimate is no longer appropriate. It is trigger-based rather than calendar-based, which in practice means many US registers go unreviewed for longer.

What happens if we have never performed the review?+

The reassessment itself is still normally a change in estimate applied prospectively under IAS 8.36. But a long-unreviewed register weakens your ability to demonstrate that the original lives remained supportable, which is the evidential question that separates a change in estimate from a prior-period error.

Does the review have to cover residual values too?+

Yes. IAS 16.51 names residual value alongside useful life. Residual values are frequently set at zero by convention and never revisited, which understates the carrying amount of assets with genuine resale or scrap value.

Share this article:
Jarred Wakefield

Jarred Wakefield

Managing Director

Expert in fixed asset management and compliance with over 15 years of experience helping organizations optimize their asset verification processes.

Need Expert Help?

CPCON's asset management specialists can help you implement effective verification processes and ensure compliance with all regulatory requirements.

Run a Documented Annual Review

Related Articles