Finance teams asked to correct the useful lives on their fixed asset register often push back with a sentence that sounds like a contradiction: we want the depreciation to be right, but we cannot have an accounting adjustment.
It is not a contradiction. Those two things are compatible, and the standards are explicit about why. Re-assessing useful life is a change in accounting estimate. It is applied prospectively. Nothing reopens, no comparative period is restated, and the gross cost totals on your register are untouched. What you owe is disclosure — not a correction.
Most teams asking the question have simply never been told that. They are bracing for a restatement that the framework does not ask for.
What the standards actually say
Both frameworks treat the service life of a depreciable asset as a textbook accounting estimate. Estimates are approximations that management is expected to refine as new information arrives — that is their nature, not a defect in them.
Under US GAAP, ASC 250 (Accounting Changes and Error Corrections) names service lives and salvage values of depreciable assets among its examples of items requiring estimation, and ASC 360-10-35-22 directs entities to review depreciation and amortisation estimates and adjust an asset's useful life when circumstances indicate the existing estimate is no longer appropriate. The accounting consequence is set by ASC 250-10-45-17:
A change in accounting estimate "shall not be accounted for by restating or retrospectively adjusting amounts reported in financial statements of prior periods or by reporting pro forma amounts for prior periods."
That is about as unambiguous as the codification gets. The change is recognised in the period of change, and in future periods if it affects them — and nowhere else.
IFRS reaches the same destination through IAS 16. Paragraph 51 requires that residual value and useful life be reviewed at least at each financial year-end, and states that where expectations differ from previous estimates, the change is accounted for as a change in an accounting estimate in accordance with IAS 8. IAS 8.36 then requires the effect to be recognised prospectively — in profit or loss for the period of the change, and future periods if both are affected.
So under IFRS the annual review is not optional. Many registers we are handed have never had one.
What actually changes on the register
This is the part that settles the room. Take an asset at $100,000 cost, no residual value, straight-line over an original ten-year life. Three years in, accumulated depreciation is $30,000 and the carrying amount is $70,000. Fieldwork and maintenance history now support a twelve-year total life.
- Gross cost stays $100,000. Cost records a past transaction. A revised expectation about the future cannot change it.
- Years 1–3 depreciation stays $10,000 per year. $30,000 accumulated, exactly as reported. No comparative is touched.
- Year 4 onward is recalculated: the $70,000 carrying amount is spread over the nine remaining years, giving roughly $7,778 per year.
Shortening works identically in the other direction. Revise that same asset to a five-year total life at the end of year three and the $70,000 is absorbed over two remaining years — $35,000 per year. Higher charge, sooner. Still no restatement.
The register's gross cost column, its historical additions, and every prior filing are all left exactly as they were. Only the forward depreciation schedule moves. If your concern was that fixing the lives would force you to reopen a closed year, it does not.
What you do owe: disclosure
"No adjustment" is not the same as "nothing to report." A material change in estimate carries a disclosure obligation, and it is more specific than most teams expect.
ASC 250-10-50-4 addresses changes in estimate that affect several future periods — and it uses a change in the service lives of depreciable assets as its own example. Where the effect is material, you disclose the effect on income from continuing operations, net income, and any related per-share amounts for the current period. If the change is immaterial this period but reasonably certain to be material later, the change still gets described.
Under IFRS, IAS 8.39 requires the nature and amount of the change to be disclosed where it affects the current period or is expected to affect future periods. IAS 8.40 covers the case where quantifying the future effect is impracticable — you disclose that fact.
None of this reopens a prior period. It tells readers that the depreciation run-rate changed and by how much, which is precisely the transparency that makes a prospective treatment acceptable in the first place. Our guide to the ASC 250-10-50-4 disclosure requirements works through what the note actually has to contain.
The boundary: when it is an error instead
Here is the part a careful controller should insist on, and the part a vendor promising "no adjustment, guaranteed" will not tell you.
The prospective treatment holds because the original estimate was a reasonable, good-faith judgement on the information available at the time. If it was not, the revision is not a change in estimate at all — it is the correction of an error, and errors do restate retrospectively.
ASC 250-10-20 defines an error in previously issued financial statements as one arising from mathematical mistakes, mistakes in the application of GAAP, or oversight or misuse of facts that existed at the time the statements were prepared. IAS 8 frames it as an omission or misstatement resulting from failure to use, or misuse of, reliable information that was available and that could reasonably be expected to have been obtained and taken into account. Where that is what happened, IAS 8 requires retrospective restatement of comparatives, subject to practicability.
The distinction in practice:
- Change in estimate. A ten-year life was set on reasonable assumptions. Usage intensified, technology moved, or maintenance history now points elsewhere. You revise forward. Nothing restates.
- Correction of an error. Manufacturer documentation and internal experience already indicated five years, and a ten-year life was used anyway, without support. That is not a new estimate — it is a misstatement being corrected, and prior periods restate.
The line is drawn by what was knowable then, not by how different the new number is. Which is why the evidence file matters more than the conclusion: a reassessment supported by dated fieldwork, nameplate data, condition assessment, and documented engineering or maintenance input sits clearly on the change-in-estimate side. A revision with nothing behind it invites the question of what management knew and when.
We treat that documentation as the deliverable, not a by-product. The full boundary analysis is in our comparison of a change in estimate against the correction of an error.
One distinction that trips teams up: life versus method
Changing the useful life and changing the depreciation method are not the same transaction, and conflating them creates work that is not required.
A change in life, with the method held constant, is purely a change in estimate under ASC 250-10-45-17. No principle changes, and no preferability assessment is needed.
A change in method — straight-line to units-of-production, say — is what ASC 250-10-45-18 calls a change in accounting estimate effected by a change in accounting principle. It is still applied prospectively, so prior periods still do not restate. But it is formally a change in principle, and ASC 250-10-45-19 requires the entity to justify the new method as preferable, with the disclosures that attach to a principle change. IFRS has no equivalent hybrid category and generally lands such changes in the change-in-estimate bucket.
If your objective is depreciation that reflects reality, you usually need the life fixed, not the method changed — which is the cheaper and lighter of the two. We cover the mechanics in changing depreciation method versus changing useful life.
What this means if your register is out of date
The reason this matters commercially is that the fear of a restatement is usually the thing stopping a register from being fixed. Once that fear is off the table, the calculus changes:
- Ghost assets keep depreciating. Assets that were scrapped or moved but never retired continue to run depreciation against earnings every period, and overstate the balance sheet until someone verifies what physically exists.
- Wrong lives distort every period, not just this one. A fleet held at five years that genuinely lasts twelve overstates depreciation for years and understates the asset base underneath your lender and insurance schedules.
- Under IFRS, skipping the review is itself a gap. IAS 16.51 requires it annually. "We have never reviewed them" is not a neutral position.
A physical verification is what turns a revised life from an assertion into a documented estimate — you cannot credibly re-life an asset you have not confirmed still exists. That is the same fieldwork that resolves ghost assets, and it is why the two exercises are almost always run together. See how to reconcile fixed assets for the reconciliation mechanics.
Frequently asked questions
Does changing the useful life of a fixed asset require a restatement?+
No. A revision to useful life is a change in accounting estimate, and ASC 250-10-45-17 expressly prohibits accounting for it by restating or retrospectively adjusting prior-period financial statements. IAS 8.36 requires the same prospective treatment. Prior-period depreciation stays exactly as reported. The one exception is where the original life was not a good-faith estimate on the information available at the time — that is an error, not a change in estimate.
Is re-assessing useful life a change in accounting estimate or a change in accounting principle?+
A change in useful life alone is purely a change in accounting estimate. ASC 250 names service lives of depreciable assets as a classic example of an accounting estimate, and ASC 360-10-35-22 directs entities to review depreciation estimates and adjust useful life. Because the depreciation method is unchanged, no change in accounting principle occurs and no preferability assessment is required.
Does a change in useful life affect the gross cost of the asset?+
No. Historical cost is a record of a past transaction and is unaffected. What changes is how the remaining depreciable amount is allocated to future periods. Gross cost totals on the register are untouched, accumulated depreciation to date is untouched, and only depreciation from the period of change forward is recalculated.
What do we have to disclose when we change useful lives?+
Under ASC 250-10-50-4, a change in estimate affecting several future periods — and the codification names change in service lives of depreciable assets as its example — requires disclosure of the effect on income from continuing operations, net income, and any related per-share amounts for the current period, when material. Under IFRS, IAS 8.39 requires the nature and amount of the change; IAS 8.40 requires you to say so if the future-period effect is impracticable to estimate.
When would re-assessing useful life actually require retrospective restatement?+
When the revision corrects a prior misstatement rather than reflecting new information. ASC 250-10-20 defines an error as arising from mathematical mistakes, mistakes in applying GAAP, or oversight or misuse of facts that existed at the time the statements were prepared. IAS 8 defines a prior-period error as resulting from failure to use, or misuse of, reliable information that was available. If the original life ignored evidence then available, the correction restates retrospectively.
How often are we required to review useful lives?+
Under IFRS, at least annually — IAS 16.51 requires residual value and useful life to be reviewed at least at each financial year-end. US GAAP has no fixed interval but ASC 360-10-35-22 requires review when events or changes in circumstances indicate the current estimate is no longer appropriate.
The short version
You can have accurate depreciation and leave every closed period closed. Re-assessing useful life is a change in accounting estimate: prospective under ASC 250-10-45-17 and IAS 8.36, no comparatives restated, gross cost untouched, disclosure owed under ASC 250-10-50-4 or IAS 8.39.
The single condition is that it must genuinely be a new estimate rather than the repair of one that ignored what was already known. That is a documentation question, and it is worth getting right — because it is the only thing standing between a prospective adjustment and a retrospective one.
