7 Depreciation Mistakes Organizations Make — and How to Fix Them Before Your Next Audit

Depreciation errors rarely announce themselves.

They accumulate quietly — in spreadsheets that have not been updated, in categories configured years ago by someone who has since left, in assets that were never formally retired, in methods applied uniformly to things they were never designed for.

By the time an auditor finds them, they have often been compounding for years. Correcting them is harder than preventing them. And the conversation with leadership about why the books do not reflect reality is not one anyone wants to have.

The good news: the same mistakes appear in organizations of every size, across every industry. They are predictable. Which means they are preventable.

Here are the seven that surface most often.

---

Mistake 1: One method applied to everything

"We use straight line depreciation, 5 years, across all assets."

This is the most common mistake in asset management — and the one with the widest consequences.

A laptop and an office chair are not the same type of asset. A server and a concrete building are not the same type of asset. Applying the same depreciation method and the same useful life to fundamentally different assets produces a financial picture that is wrong by design, not by accident.

What goes wrong: Technology assets depreciate faster in early years. Physical infrastructure depreciates slowly and predictably. Vehicles hold a known market value curve. When you apply a single straight-line rate to all of these, you overstate the book value of some assets (the ones that actually degrade faster) and understate the value recognition on others. The result is a balance sheet that does not reflect economic reality.

The correct approach: Configure depreciation at the asset category level, with the method and useful life chosen to match the actual consumption pattern of that category.

The configuration work takes time once. The benefit is a depreciation picture that will hold up to scrutiny.

---

Mistake 2: Ignoring residual value

Most depreciation implementations depreciate assets all the way to zero. For some assets and some methods, that is correct. For many, it is not — and the difference matters.

Residual value (also called salvage value) is the estimated amount an asset will be worth at the end of its useful life. A vehicle with a 5-year useful life does not become worthless on day one of year 6. A piece of industrial equipment has scrap or resale value. Depreciating to zero overstates the total depreciation charge and understates the ending book value.

The regulatory dimension: Under IFRS IAS 16, residual value must be estimated and reviewed annually. Under Indian Companies Act 2013, Schedule II mandates a 5% residual value floor for all asset classes under WDV. Ignoring residual value is not just an accounting imprecision — in these contexts, it is non-compliance.

What to do: Review your asset categories. For any category using SLM or WDV, confirm whether a residual value is configured. For Indian entities, verify the 5% floor is in place. For IFRS reporting, document the basis for each residual value estimate.

---

Mistake 3: Depreciation tracked in a spreadsheet, separately from the asset register

This is not a calculation error. It is a systems error — and it creates a category of risk that no amount of calculation accuracy can fix.

When depreciation lives in a spreadsheet disconnected from the asset register, four things happen over time:

The spreadsheet falls behind. New assets are added to the register but not to the spreadsheet. Disposed assets remain in the spreadsheet generating phantom depreciation. The two records drift apart, and nobody notices until reconciliation time.

History is lost. Spreadsheets capture current state. They rarely capture why a value changed, who changed it, or what the value was before. When an auditor asks why an asset's depreciation rate changed in 2023, there is no answer.

Calculation errors compound silently. A formula error in a spreadsheet — a wrong cell reference, a copied row that pulled the wrong rate — propagates through subsequent years without any system catching it. The only check is manual review, which rarely happens.

Multiple versions coexist. Finance has one version. Operations has another. The one that was emailed last month is different from the one saved on the shared drive. Which one is the source of truth?

The fix: Depreciation should live in the same system as the asset register — calculated automatically from asset data rather than maintained separately. When an asset is added, updated, or retired, the depreciation picture updates automatically. There is no spreadsheet to maintain, no synchronization to manage, and no divergence to reconcile.

---

Mistake 4: Never retiring fully depreciated assets

An asset reaches zero book value — or its residual value floor — and keeps appearing on the depreciation schedule. Nothing happens. The asset continues to exist in the system. The depreciation report continues to show it, now contributing nothing but clutter.

This is more common than it sounds. In organizations that manage hundreds or thousands of assets, retiring assets from the system requires deliberate action. If that action is not prompted — if there is no workflow for end-of-life — assets accumulate on the register long past the point of relevance.

Why it matters:

• Fully depreciated assets that are still in active use represent hidden value — they generate economic output with zero book cost, which distorts cost-per-use analysis and replacement decisions
• Fully depreciated assets that are no longer in use represent phantom assets — they inflate the asset count, cloud utilization metrics, and create audit questions about assets that cannot be located
• In some jurisdictions, assets must be formally removed from the register and balance sheet when disposed of, with supporting documentation — failing to do so is a compliance issue, not just a housekeeping one

What a proper end-of-life workflow looks like:

Asset reaches residual value
        ↓
System flags as "Fully Depreciated"
        ↓
Operations reviews: Still in use? / Ready for disposal?
        ↓
If disposed: Retirement recorded with date, method, and proceeds
        ↓
Asset removed from active register / Gain or loss on disposal calculated
        ↓
Financial records updated

The flag is the starting point. Without it, the review never happens.

---

Mistake 5: Using the wrong useful life

The useful life assigned to an asset category is often set once — at implementation, by whoever configured the system — and never revisited. Over time, it drifts from reality.

Technology changes faster than useful life estimates do. A useful life of 5 years for servers made sense in 2015. In 2026, refresh cycles are faster and equipment may be obsolete before year 3. Conversely, some physical infrastructure lasts significantly longer than its originally assigned life, and extending the depreciation artificially inflates expenses in later years.

The compounding effect: An incorrect useful life does not just affect one year. It affects every year of the asset's life. An asset assigned a 5-year life instead of a 3-year life will show significantly overstated book values in years 3 through 5 — assets that appear to have residual value on paper but are already obsolete in practice.

A useful life calibration exercise:

Under both IFRS and Indian accounting standards, useful lives should be reviewed at each financial year-end and revised if expectations have changed. In practice, this review rarely happens. Scheduling it deliberately — even as a brief annual category review — prevents years of compounding error.

---

Mistake 6: Confusing book depreciation with tax depreciation

These are different things. They serve different purposes, use different methods, and produce different numbers. Treating them as interchangeable is a persistent source of reconciliation errors.

Book depreciation (also called accounting depreciation) is what appears on your financial statements. It is governed by the accounting standard you follow — IFRS, US GAAP, Indian AS, or equivalent. The method you choose should reflect the actual pattern of economic consumption of the asset.

Tax depreciation is what appears on your tax return. It is governed by tax law — MACRS in the US, WDV under the Indian Income Tax Act, capital allowances under UK law. Tax depreciation methods are often more aggressive than book depreciation, providing larger deductions in early years.

The difference between the two creates a temporary timing difference — the same asset produces different deductions in the same year depending on which calculation you are looking at. Over the life of the asset, total depreciation converges. But year by year, the numbers diverge substantially.

Based on a $100,000 asset, 5-year life, SLM for book, MACRS 5-year for tax.

The risk: Organizations that track only one set of numbers — usually the one in their asset management system — cannot produce the other without reconstruction. When the tax return requires MACRS numbers and the asset register only has SLM, someone has to manually reconcile the difference, often under time pressure at filing time.

The fix: Maintain both, clearly separated. Your asset management system should support configuring the depreciation method independently for book and tax purposes, or at minimum make it straightforward to run the tax calculation alongside the book calculation.

---

Mistake 7: No audit trail on depreciation changes

Someone changes a depreciation rate. Or switches the method on a category. Or adjusts the useful life of a group of assets. The change is made, the numbers update, and there is no record of who made the change, when, or why.

Six months later, an auditor asks why the depreciation rate for office equipment changed in March. Nobody can answer.

This is not a hypothetical. It is a recurring finding in financial audits of organizations that manage depreciation manually or in systems without change tracking. Depreciation rates and methods are accounting policy choices. Changes to them require justification, and that justification needs to be documented at the time of the change — not reconstructed from memory afterwards.

What an audit trail for depreciation should capture:

Without this, a depreciation configuration change is invisible. With it, every change to the depreciation policy is traceable, explainable, and defensible to an auditor.

---

The common thread

Running through all seven mistakes is the same underlying condition: depreciation is being managed as a periodic exercise rather than a continuous operational discipline.

The spreadsheet gets updated before the audit. The useful lives get reviewed when something goes wrong. The asset register gets cleaned up when the discrepancy becomes impossible to ignore.

The organizations that avoid these mistakes have made a different structural choice: depreciation data is maintained in the same system as asset data, automatically, in real time. New assets inherit the correct depreciation configuration from their category. Retired assets are flagged and processed promptly. Changes are tracked. Reports are generated on demand, not reconstructed from notes.

That structure is not complicated to establish. But it requires a deliberate decision to treat depreciation as part of how assets are managed — not as a separate accounting exercise that happens downstream.

---

For a practical starting point on configuring depreciation correctly across different asset types and accounting standards, see which depreciation method is right for your assets.