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.
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:
Both compound silently between audits. An annual verification resets the register to physical reality on one day. Drift begins again immediately after.
Every physical change to an asset requires a human to file a journal entry. Most do not. Here are the specific mechanisms:
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 |
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
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.
The asset truth gap affects any organization with a large, active fixed asset base. Three profiles carry the most concentrated risk:
Not all approaches to fixed asset verification deliver audit-grade accuracy. When evaluating options, look for six capabilities:
Organizations that manage the asset truth gap effectively share five practices:
Three beliefs lead most organizations to underestimate their exposure.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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