← Back to Blog

The asset truth gap is the distance between what an enterprise's fixed asset register says exists and what is actually on the floor. It is not caused by poor management. It is the predictable output of any verification system that only looks once a year.

Most controllers and fixed asset managers believe their records are reasonably accurate. They run annual audits. They rely on ERP systems. They assume the gap between the register and physical reality is small.

Consider the contrast. If the CEO asked “What is our cash balance right now?” and the CFO replied “As of nine months ago it was $1.2 million. We’ll update it when we do the annual audit in three months.” That would end careers. Yet that is effectively how most companies treat fixed assets.

That assumption is the problem. Kroll Advisory runs more than 8,000 fixed asset engagements per year across 36 countries and consistently finds that 10 to 30 percent of assets on the average register are ghost assets. Records that are incomplete, inaccurate, or outdated show up at rates far higher than most finance teams expect.

The cause is structural, not operational. Fixed asset records drift whenever a physical change happens and no one files the corresponding journal entry. In a facility where assets move, degrade, get repurposed, and disappear continuously, that happens all the time. Annual verification cannot keep up with continuous physical change.

 

What Is the Asset Truth Gap?

The asset truth gap is the accumulating distance between a fixed asset register and physical reality, caused by changes between audits that never reach the system of record.

Every organization with a fixed asset register has one. It is not a failure of management or process. It is what happens when a periodic model is applied to a world that changes continuously.

The gap takes two forms:

  • Ghost assets. Items recorded in the register that no longer physically exist. The organization pays depreciation, property taxes, and insurance premiums on assets that have been scrapped, cannibalized, or informally decommissioned.
  • Zombie assets. Items on the floor that are not in the register. Unrecorded capital with no depreciation schedule and no insurance coverage. They surface during audits and create reconciliation work that could have been avoided.
  • Phantom depreciation charges. Every ghost asset on the register generates a depreciation charge on something that no longer exists or provides no return.
  • Property tax overpayments. Assets still on the books in a jurisdiction get taxed, regardless of whether they are still there.
  • Insurance premiums on non-existent assets. Coverage is calculated from register values. Ghost assets inflate the insured base.
  • Inflated carrying values. Ghost assets in an asset group inflate carrying value, which can trigger false Step 2 fair value measurements under ASC 360 impairment testing.
  • Audit remediation cost. When auditors find discrepancies, organizations spend unplanned time on reconciliation, documentation, and restatement. Budget that was never allocated.
  • Heavy manufacturers with active maintenance programs. High asset counts, continuous equipment movement, and frequent component replacements create drift faster than most organizations can track. Annual audits reset the clock. They do not prevent the next year's accumulation.
  • Organizations mid-S/4HANA migration or ERP transition. Data migration from legacy systems imports historical errors at scale. Ghost assets that existed in the old system arrive in the new one. A pre-migration physical verification is not standard practice. It should be.
  • Asset-intensive businesses subject to external audit. PCAOB long-lived asset deficiencies doubled from 2 to 4 between 2023 and 2024. Auditors are paying closer attention to fixed asset assertions. Organizations that rely on annual counts and ERP records as their only evidence are increasingly exposed.

Both compound silently between audits. An annual verification resets the register to physical reality on one day. Drift begins again immediately after.

 

Why Asset Records Drift Between Audits

Every physical change to an asset requires a human to file a journal entry. Most do not. Here are the specific mechanisms:

  1. Moves between facilities. Equipment relocated during a shutdown or reorganization rarely generates a formal transfer record. The asset stays on the books at its original location.
  2. Informal decommissioning. A machine breaks and gets pushed to a corner. No disposal entry is filed. Depreciation continues.
  3. Parts cannibalization. Components are removed from one asset to repair another. The donor asset stays on the register, now missing a part. So does the recipient, with an undocumented modification.
  4. Vendor removals. A maintenance contractor removes a motor or replaces a component. The work order closes. No asset record is updated.
  5. Theft and shrinkage. Small, portable, high-value assets disappear without a disposal entry. They continue depreciating on paper.
  6. Continuous evidence capture rather than periodic snapshots. Annual or quarterly cycles miss changes that happen between counts. The verification model needs to operate on the same timeline as the physical world.
  7. Multi-source evidence combining physical inspection, GPS or RFID location data, photos, and document intelligence. Single-source verification leaves gaps that auditors will find.
  8. Orchestrated workflow governance that handles routing, delegation, notification, and approval automatically, moving evidence through a defined process without manual coordination at every step.
  9. Human-in-the-loop remediation at decision points where a human must act, not just observe. Flagging discrepancies, approving exceptions, triggering corrective actions, and signing off before data reaches the system of record.
  10. Direct ERP reconciliation so verified data flows to the subledger without manual journal entries or spreadsheet handoffs. Manual transfer steps are where verification value gets lost.
  11. Audit-ready output with a documented evidence chain per asset, not just a count or summary report. Auditors need to trace every change back to its source evidence.
  12. Verification tied to physical events, not calendar cycles. Asset moves, maintenance activities, and decommissions trigger verification workflows automatically, not on a preset schedule.
  13. Evidence collected at the point of change. Inspectors, technicians, or automated sensors capture location, condition, and identification data when a physical event occurs, not after a quarterly review.
  14. Structured exception handling. Discrepancies between register and reality go into a governed remediation workflow with clear ownership, not a spreadsheet or a general queue.
  15. ERP reconciliation that closes automatically. Verified physical data flows directly to the fixed asset subledger. No manual journal entries, no spreadsheet intermediaries, no reconciliation lag.
  16. A defensible evidence chain per asset. Every asset has a timestamped record of inspections, location changes, condition assessments, and the humans who verified each step. This is what auditors and regulators actually ask for.

None of these events are unusual. All of them are routine. In a facility with thousands of assets, they happen continuously.

 

Annual Verification vs. Continuous Verification

 

 

Annual Verification

Continuous Verification

Frequency

Once per year

Ongoing — triggered by physical events

Evidence type

Point-in-time snapshot

Timestamped record per change

Accuracy between cycles

Degrades as assets change

Maintained at point of change

Audit readiness

Current on one day per year

Current at any point in time

ERP subledger accuracy

Resets on audit day, then drifts

Updated when physical change is verified

 

The Real Cost of the Asset Truth Gap

Ghost assets and stale records generate costs across multiple line items, most of which stay invisible until an audit or a restatement forces the issue.

 

"Any fixed asset verification system built on annual cycles is structurally guaranteed to produce drift between audits. The gap is not a management failure. It is a design constraint of the model." — Tim Harris, CEO, SoloTruth

 

What the Data Shows

Ghost assets are not rare outliers. They are the normal output of periodic verification applied to a physical world that changes continuously.

Kroll Advisory's data, drawn from thousands of engagements across 36 countries, puts ghost asset prevalence at 10 to 30 percent of the average fixed asset register. In one manufacturing client engagement, more than 15 percent of recorded assets were no longer in active service.

Celtic Bank encountered the same accuracy problem from a lender's perspective. As an SBA lender underwriting asset-backed loans, they could not rely on borrowers' own asset records. Celtic Bank required independent physical verification. Working with SoloTruth, they processed more than 1,000 asset inspections. Loan closing time dropped approximately four days. The SBA validated the process as exceeding all SBA SOP requirements.

The implication: if a regulated financial institution cannot trust an unverified asset register, the accuracy problem is not industry-specific. It is structural.

 

Who Is Most Affected?

The asset truth gap affects any organization with a large, active fixed asset base. Three profiles carry the most concentrated risk:

 

What to Look For in a Fixed Asset Verification Solution

Not all approaches to fixed asset verification deliver audit-grade accuracy. When evaluating options, look for six capabilities:

 

What Good Looks Like

Organizations that manage the asset truth gap effectively share five practices:

 

Common Misconceptions About Fixed Asset Accuracy

Three beliefs lead most organizations to underestimate their exposure.

Misconception: Our ERP updates in real time, so our records are current.

Reality: ERP updates depend on someone logging the change at the moment it happens. ERP systems are designed to record transactions accurately. They are not designed to detect physical changes that go unreported. The assumption that real-time ERP equals real-time physical accuracy is exactly where drift starts.

Misconception: We do cycle counts, so we are better than annual.

Reality: More frequent point-in-time checks shrink the window of uncertainty. They do not close the structural gap. A cycle count is still a snapshot. Between counts, the same drift dynamics apply. The underlying question is not how often you look. It is whether verification produces a continuous evidence record or just a more frequent point-in-time snapshot with the same structural limits.

Misconception: Ghost assets are a sign of poor financial controls.

Reality: Ghost assets are the predictable output of a verification model that only looks once a year. They appear in well-run organizations and poorly-run ones at similar rates. This is a structural problem, not a management failure.

 

Frequently Asked Questions

What is the asset truth gap?

The asset truth gap is the distance between what an enterprise's fixed asset register says exists and what is actually on the floor. It is the structural output of any periodic verification system applied to assets that change continuously.

What is a ghost asset?

A ghost asset is an item recorded in the fixed asset register that no longer physically exists. The organization pays depreciation charges, property taxes, and insurance premiums on an asset that has been scrapped, cannibalized, or informally decommissioned. Ghost assets accumulate silently between physical audits.

How common are ghost assets?

Kroll Advisory, which runs more than 8,000 fixed asset engagements per year across 36 countries, finds that 10 to 30 percent of assets on the average fixed asset register are ghost assets.

Does an annual physical count fix the problem?

Temporarily. An annual count resets the register to physical reality on one day per year. Drift begins again immediately. For the remaining 364 days, the organization operates on data that is at best an approximation of physical reality. The annual count is a useful reset, not a continuous control.

Why doesn't ERP solve this?

ERP fixed asset modules are accounting engines. They record financial transactions accurately. They were not designed to verify that the assets they track physically exist. The ERP reflects what people report to it. Changes that go unreported do not appear in the register.

What are the financial consequences of ghost assets?

Ghost assets generate phantom depreciation charges, property tax overpayments on non-existent property, and insurance premiums on assets that require no coverage. They also inflate asset group carrying values, which can create false impairment signals under ASC 360 testing.

What is fixed asset verification?

Fixed asset verification is the process of confirming that assets recorded in a fixed asset register physically exist, are located where the register says they are, and are in the condition reflected in the accounting records. Verification differs from asset tracking: tracking monitors location; verification produces audit-grade evidence of existence, condition, and accuracy.

What is asset relationship management?

Asset relationship management, or ARM, is the discipline of maintaining accurate, continuous relationships between physical assets and the systems that govern them, including the fixed asset register, ERP subledger, maintenance systems, and insurance records. ARM replaces periodic reconciliation with continuous, evidence-based verification.

 

The Asset Truth Gap Is Structural. So Is the Fix.

Fixed asset records do not stay accurate on their own. Between purchase and disposal, assets move, degrade, get repurposed, and disappear. Any verification system built on annual cycles is structurally guaranteed to produce drift. The gap is not a sign of poor management. It is the predictable output of a model that only looks once a year.

Closing it requires a different model. One that captures evidence when physical change happens, not when the calendar says to look. One that routes exceptions through a governed process rather than a spreadsheet. One that writes verified data directly to the subledger rather than staging it for a manual reconciliation step.

That is what continuous, evidence-based fixed asset verification looks like in practice. And it is what SoloTruth Asset Relationship Management (ARM) was built to deliver. ARM verifies the existence, location, and condition of physical assets and reconciles that data with ERP systems, replacing episodic audits with a governed, always-current evidence layer.

 

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: May 2026

Share this article: