Your Depreciation Schedule Is Built on Assumptions, Not Data

What Is Depreciation Schedule Accuracy?

Depreciation schedule accuracy is the degree to which the assets you depreciate on your books still exist, still sit where the register records them, and still match the condition assumed when they were capitalized. Most schedules are never re-tested against those three facts after acquisition.

The schedule itself is not the weak point. The formula runs the same way every period, which is exactly the problem. It was built from a snapshot taken on capitalization day, and it runs that snapshot forward whether or not the asset behind it has changed. Fixed asset register entries do not update themselves when a machine is moved, a component is swapped, or a unit is scrapped.

Consider a manufacturer that capitalizes a packaging line at $180,000. Over three years, two drive modules fail and are replaced during routine maintenance, and one conveyor section is scrapped and never rebuilt. The physical asset on the floor is now materially different from the one on the books. The subledger still shows the original composite, and depreciation still runs on all $180,000. The number is confident. It is also wrong.

Introduction

For CFOs, controllers, and fixed asset managers, the depreciation schedule is treated as one of the most reliable numbers in the close. It is often one of the least verified.

Kroll Advisory, the firm that runs 8,000 fixed asset engagements a year across 36 countries, reports that 10 to 30 percent of assets on the average fixed asset register are ghost assets that no longer physically exist. Kroll also finds that up to 65 percent of asset records contain errors, missing data, or outdated information.

Every one of those records still depreciates on schedule. The math is precise. The inputs are not. That gap between the register and the floor is where earnings quality erodes, period after period, until an audit forces the correction.

Why Depreciation Schedules Drift From Reality

Depreciation schedules drift because the events that change an asset almost never generate the accounting entry that would update it. Four root causes do most of the damage.

1. Verification is episodic.

Physical counts happen once a year at best. Every move, replacement, or disposal between counts is invisible to the schedule until the next cycle, if it is caught at all.

2. The ERP was not built to connect physical reality to the ledger.

Every major ERP shares the same design constraint. The physical tracking modules for maintenance and logistics are not natively connected to the fixed asset subledger. This is true in SAP, Oracle Financials Cloud, and Microsoft Dynamics 365. It is how the platforms are built, not a setting someone forgot.

3. Field changes happen without journal entries.

When a component is replaced or scrapped on the floor and no one files a retirement entry, the record survives its own asset. This creates partial ghost assets, where the physical unit changes but the financial record does not. IAS 16 componentization is rarely handled natively in ERP asset accounting, so depreciation keeps running on parts that are already gone.

4. The handoffs are manual.

Retirements and transfers depend on someone remembering to tell finance. Every manual step is a place where the subledger and the floor come apart.

Episodic reconciliation vs. continuous verification

The Real Cost of an Inaccurate Depreciation Schedule

The cost of a stale schedule is larger than the depreciation line itself, because a phantom asset generates expense in several places at once.

Kroll's 10 to 30 percent ghost asset range is not an accounting curiosity. Each of those assets keeps depreciating, keeps accruing property tax, and keeps drawing insurance premiums until someone catches it. The PCAOB's 2024 inspection data adds the audit dimension: long-lived asset deficiencies at large firms doubled from two to four, even as overall audit deficiency rates improved from 46 percent to 39 percent. Fixed assets are the one area going the wrong direction while everything else gets better.

“A depreciation schedule is only as honest as the last time someone checked the floor. For most companies, that was a year ago, and the schedule has been quietly compounding the difference ever since.”

— Tim Harris, CEO, SoloTruth

Cost categories from an inaccurate schedule:

• Misstated earnings and asset value. Ghost assets keep depreciating, understating income in the wrong periods while overstating carrying value on the balance sheet.
• Overpaid property tax and insurance. Companies pay tax and premiums on assets that no longer exist, every year, until the record is corrected.
• Late impairment charges. Without captured condition data, ASC 360 impairment is recognized in an audit finding rather than when the asset actually degraded.
• Audit labor. Reconciling the register by hand for audit is one of the largest recurring costs of a stale schedule, and on its own it often covers the cost of continuous verification.

Our ROI model, built on Kroll, Manufacturers Alliance, and PCAOB data, points to a payback period of under six months in most cases. The figures are modeled, not customer results, but every input is drawn from verified sources. The point is less the size of any single number and more that the cost recurs every period the schedule goes unverified.

Who Is Most Affected

• Manufacturers and heavy industry. Large, componentized equipment estates where field maintenance constantly changes the physical asset without touching the ledger.
• CFOs and controllers in regulated industries. Banking, insurance, and utilities face PCAOB-inspected or external audits where fixed asset accuracy is now under specific scrutiny.
• Internal audit teams. Groups preparing for audit inherit the reconciliation burden the schedule should have carried all year.
• Logistics and warehousing operators. Assets move across multiple sites faster than any annual count can track, so the register is stale almost immediately.

What to Look For in a Solution

Not every approach to fixed asset verification produces a schedule you can trust. When evaluating options, look for six capabilities.

• Continuous evidence capture rather than periodic snapshots. Annual or quarterly cycles miss the changes that actually move the numbers.
• Multi-source evidence combining physical inspection, GPS or RFID location data, photos, and document extraction. Single-source verification leaves gaps an auditor will find.
• Orchestrated workflow governance that routes, delegates, and approves evidence through a defined process without manual coordination at every step.
• Human-in-the-loop remediation at the specific points where a person must decide, such as approving a retirement, flagging a discrepancy, or signing off before data reaches the ledger.
• Direct ERP reconciliation so verified changes post to the fixed asset subledger without manual journal entries or spreadsheet handoffs.
• Audit-ready output with a documented evidence chain per asset, so every change traces back to its source rather than to a summary count.

What Good Looks Like

A well-run fixed asset process treats the schedule as a live record, not an annual chore.

• Continuous, not periodic. Existence, location, and condition are confirmed as part of normal operations, not once a year on audit day.
• Every physical change ties to an entry. Retirements and component replacements generate a journal entry at the component level, consistent with IAS 16.
• The subledger is reconciled on a defined cadence. The register is matched to physical reality on a schedule, and exceptions are worked, not ignored.
• Condition drives impairment reviews. Captured condition data triggers ASC 360 impairment testing when degradation happens, not eighteen months later.
• Every asset carries an evidence chain. Dated, source-level evidence for each asset means an auditor can trace any change end to end.

Common Misconceptions

• Misconception 1: Our ERP already tracks all of this. ERPs record accounting transactions, not physical reality. The maintenance and logistics modules that see asset changes are not natively linked to the fixed asset subledger, so the schedule never hears about most changes.
• Misconception 2: The annual audit catches ghost assets. Annual counts are usually sampled and point-in-time. They miss changes that happen between cycles, which is why Kroll still finds 10 to 30 percent ghost assets on registers that pass audits.
• Misconception 3: Depreciation is a formula, not a data problem. The formula is only as accurate as its inputs. If existence, location, and condition are wrong, a perfectly executed calculation still produces a misstated number.

Frequently Asked Questions

How often should fixed assets be physically verified?

Continuously, as part of normal operations, rather than once a year. Annual counts miss the moves, replacements, and disposals that happen between cycles and drive most schedule inaccuracy.

Why is my depreciation schedule inaccurate if my ERP is up to date?

Because ERPs track transactions, not physical reality. The maintenance and logistics modules are not natively connected to the fixed asset subledger, so physical changes rarely reach the schedule.

What is a ghost asset and how does it affect depreciation?

A ghost asset is a record for an asset that no longer physically exists. It keeps depreciating every period, understating income and overstating carrying value until someone catches it.

What is a partial ghost asset?

A partial ghost asset occurs when a component is replaced or scrapped in the field without a journal entry. The physical asset changes, the financial record does not, and depreciation runs on parts that are gone.

How does an inaccurate depreciation schedule create audit risk?

PCAOB data shows long-lived asset deficiencies at large firms doubled in 2024 even as overall audit quality improved. An unverified schedule is exactly the exposure auditors are now examining more closely.

What is the difference between asset tracking and asset verification?

Tracking records where an asset is supposed to be. Verification proves it exists, confirms its location and condition with evidence, and reconciles that proof to the ledger.

Conclusion

A depreciation schedule built on a capitalization-day snapshot grows less accurate every period. A schedule built on continuous verification is a live financial record that reflects what is actually on the floor.

The difference is not the formula. It is whether the existence, location, and condition behind every asset are proven or assumed.

That is the gap SoloTruth Asset Relationship Management (ARM) is designed to close.

SoloTruth is the evidence-grade Asset Relationship Management (ARM) platform that verifies the existence, location, and condition of physical assets and reconciles that data with ERP systems. It replaces episodic audits with continuous verification using RFID, GPS, mobile inspections, and document intelligence to create a verifiable system of truth.

Book a 30-minute strategy call at calendly.com/tim-harris-solotruth/30min to see how continuous verification changes what your fixed asset register is actually capable of.

Last Updated: July 2026