Continuous Verification Is the New Standard for Fixed Asset Accuracy

Continuous verification is an ongoing process of capturing evidence of asset existence, location, and condition at the moment physical changes occur, rather than relying on periodic audits or annual counts. It replaces the approximation cycle with a governed, real-time control that keeps the fixed asset register accurate between audits, not just at audit time.

Fixed asset registers are wrong more often than finance teams realize. Kroll Advisory, which runs more than 8,000 fixed asset engagements per year, reports that 10 to 30 percent of assets on the average register are ghost assets: fully disposed, fully obsolete, or fully missing, yet still depreciating on the books. Up to 65 percent of fixed asset records contain errors, missing data, or outdated information that makes them unreliable for financial reporting. The organizations most exposed are fixed asset managers, CFOs, and controllers in manufacturing, regulated industries, and enterprise technology, where asset volumes are high and the gap between physical reality and the subledger grows every day the annual cycle is treated as the standard.

What Is Continuous Verification for Fixed Assets?

Continuous verification is the practice of capturing verified evidence of asset status at the time a physical change occurs, rather than waiting for a scheduled audit cycle to detect what has already happened.

The annual physical count has been the default approach for decades. On the day the count is completed, the register reflects physical reality. The problem is what happens the day after. Assets move, get cannibalized for parts, are retired informally, or are written off in a spreadsheet that never reaches the subledger. By the time the next count arrives, the gap between physical reality and the financial record has been accumulating for twelve months.

Continuous verification does not eliminate the audit. It changes what the audit finds when it arrives. Instead of discovering a year's worth of accumulated drift, auditors review a register that has been reconciled continuously, with a documented evidence chain for every change.

Why the Annual Count Falls Short

The annual physical count was not designed as a standard for fixed asset accuracy. It was the most practical approximation organizations could manage with the tools available at the time. Four structural constraints explain why it fails.

1. Episodic audits miss everything that happens between cycles. A count is a snapshot. Changes that occur after the snapshot are invisible until the next count. In high-velocity asset environments, that is twelve months of untracked movement.

2. ERP systems record transactions, not physical reality. SAP, Oracle, and Microsoft Dynamics were designed to record the financial lifecycle of an asset, not to verify that it physically exists. Physical tracking and the financial subledger are not natively connected in any of these platforms.

3. Physical changes require manual journal entries that rarely arrive. When an asset is retired, moved, or cannibalized, someone has to file a journal entry to reflect it in the subledger. In most manufacturing and industrial environments, that entry never gets filed.

4. No structured evidence chain exists per asset. Without a documented record of what changed, when, and who verified it, there is no way to distinguish a current asset from a ghost asset without sending someone to physically check.

Annual Count vs. Continuous Verification

The Real Cost of Register Inaccuracy

Ghost assets on a register do not sit quietly. They carry a running financial cost across multiple dimensions.

• Depreciation: Ghost assets continue generating depreciation charges on assets that provide no return.
• Insurance premiums: Assets that no longer exist continue accruing premiums.
• Property tax exposure: Disposed assets remain on the tax basis until someone corrects the record.
• Impairment testing distortion: Ghost assets inflate asset group carrying values under ASC 360, triggering false impairment signals on assets that are actually performing.
• Migration blockers: In SAP S/4HANA transitions, inaccurate registers surface as reconciliation failures that stall the migration timeline.
• Audit deficiencies: The PCAOB's 2024 inspection data identifies long-lived assets as the number one ICFR deficiency area, even as overall audit quality improved. Long-lived asset inspection deficiency rates were previously 46 percent and improved to 39 percent overall, while inspection rates for long-lived asset controls more than doubled. The improvement in overall rates reflects increased scrutiny, not resolved underlying accuracy problems.
• Fixed asset managers in manufacturing and heavy industry: High asset volumes, frequent movement, and informal retirement practices create the fastest-accumulating drift. Ghost asset rates in these environments consistently reach the upper end of the 10 to 30 percent range.
• CFOs and controllers in regulated industries: Banking, insurance, and utilities face audit scrutiny that makes register inaccuracy a financial reporting risk, not just an operational inconvenience.
• Internal audit teams preparing for PCAOB or external audit: Long-lived assets are now the top ICFR deficiency category. Audit teams that rely on annual count data are presenting auditors with a register that may be eleven months stale.
• IT asset managers in enterprise technology: Large hardware estates with frequent deployments and retirements create the same drift problem as physical plant assets. ERP fixed asset modules were not designed for IT asset velocity.
• Compliance and risk teams navigating SOX, CSRD, or IAS 16: Any framework requiring verifiable asset data creates exposure when the underlying register cannot produce an evidence chain per asset.

“The register is not a record of what you own. It is a record of what you owned the last time someone checked. For most organizations, that is twelve months ago.”

— Tim Harris, CEO, SoloTruth

GAO data on federal contractor property records shows a 43 percent error rate (GAO-25-108052). Private-sector manufacturing is not meaningfully better. The cost is not theoretical. It compounds every day the approximation is accepted as the standard.

Who Is Most Affected?

Register inaccuracy is not evenly distributed. Five groups carry the most exposure.

What to Look For in a Continuous Verification Solution

Not all approaches to fixed asset verification deliver continuous accuracy. When evaluating options, look for six capabilities.

1. Evidence capture at the time of physical change, not at the time of the next scheduled audit. Mobile verification workflows in the hands of the people already operating the equipment is the most scalable way to achieve this. They are already there. They already know what changed.

2. Multi-source evidence combining physical inspection data, GPS or RFID location data, photographs, and document extraction. Single-source verification leaves gaps that auditors will find.

3. Orchestrated workflow governance that routes exceptions automatically to the right reviewer with the right evidence attached and a complete chain of custody. Evidence capture without routing is a folder of photos.

4. Governed human review at financially material decision points. A location update does not require human approval. A ghost asset retirement that removes $2 million from the depreciation schedule does. The standard is governed automation, where decisions that touch the balance sheet are reviewed and approved by the people accountable for the balance sheet.

5. Direct ERP subledger reconciliation so verified, approved data writes back to the system of record without manual journal entries or spreadsheet handoffs. Human error in the transfer step eliminates the value of the verification.

6. Audit-ready output with a documented evidence chain per asset. Auditors need to trace every change back to its source evidence, not just review a count or a summary report.

What Good Looks Like

Organizations that have moved from annual approximation to continuous verification share five operating practices.

1. Asset operators capture condition and existence data during normal workflow. Verification is embedded in the work, not added as a separate audit event. The people closest to the assets generate the evidence.

2. Exceptions route automatically without manual coordination. When a discrepancy is detected, it routes to the right person with the right context. No one has to remember to follow up.

3. Financially material approvals require a named human sign-off. The approval is recorded in the evidence chain, not just the outcome. Auditors can trace the decision back to the person who made it.

4. Approved changes write directly to the ERP subledger. The physical record and the financial record stay consistent by design, not by periodic reconciliation effort.

5. The audit trail is native, not reconstructed. When auditors arrive, the evidence chain already exists. The team is not spending the week before audit recreating documentation that should have been captured continuously.

Common Misconceptions About Continuous Verification

Several assumptions slow adoption of continuous verification in organizations that would benefit most from it.

Misconception: The annual count is the industry standard.

Reality: The annual count is the most common practice, not the standard. It became the default because it was the most practical option available before mobile verification workflows existed. PCAOB deficiency data shows it is not meeting the accuracy standard auditors require.

Misconception: The ERP handles this if configured correctly.

Reality: ERP fixed asset modules record financial transactions. They do not verify physical existence. This is a design constraint, not a configuration problem. SAP, Oracle, and Microsoft Dynamics were not built to do what continuous verification does. No configuration change closes that gap.

Misconception: Continuous verification requires replacing the ERP.

Reality: Continuous verification adds the layer that was always missing between physical reality and the financial subledger. It does not replace the ERP. It reconciles to it.

Misconception: This is only relevant for large enterprises.

Reality: Ghost asset rates of 10 to 30 percent apply across organization sizes. A mid-market manufacturer with $50 million in gross fixed assets and a 20 percent ghost asset rate carries $10 million in phantom depreciation. The financial exposure does not require enterprise scale.

Frequently Asked Questions

What is the difference between asset tracking and continuous verification?

Asset tracking records where an asset is. Continuous verification produces an evidence chain confirming that the asset exists, in what condition, at a specific location, as of a specific date, reviewed and approved by a named person. Tracking without verification does not produce audit-ready output.

How often should fixed assets be physically verified?

At the time a physical change occurs, not on a fixed schedule. Scheduling verification independently of change events guarantees that some changes are missed. Verification triggered by change events captures the full picture in real time.

Why does my ERP have inaccurate fixed asset records?

Because physical changes require manual journal entries that rarely get filed. ERP systems record what they are told. When an asset is retired informally, cannibalized, or moved without a corresponding ERP entry, the register drifts. The ERP is not at fault. The process design is.

What is a ghost asset?

A ghost asset is a fixed asset that appears in ERP records but no longer physically exists or cannot be located. Ghost assets continue to depreciate, generate insurance premiums, and accrue property tax exposure. Kroll reports they represent 10 to 30 percent of the average fixed asset register.

How does fixed asset verification connect to ERP reconciliation?

Verification produces the evidence. Reconciliation closes the loop between that evidence and the subledger. Without verification, reconciliation is comparing one estimate to another. Without reconciliation, verification produces accurate field data that never reaches the financial record.

What industries have the most exposure to ghost asset risk?

Manufacturing, heavy industry, utilities, and regulated financial services carry the most exposure. High asset volumes, frequent movement, and informal retirement practices create the fastest-accumulating drift. Enterprise technology organizations with large hardware estates face the same structural problem at higher velocity.

The Approximation Has Accumulated Long Enough

The annual physical count was a practical solution for a slower asset world. In most asset-intensive operations today, it is producing a running financial misstatement that compounds every day it goes uncorrected.

Continuous verification is not a premium upgrade. It is the operating standard that PCAOB auditors are already expecting to find evidence of, and that most fixed asset registers are not yet meeting.

SoloTruth Asset Relationship Management (ARM) is the physical-to-financial control platform that closes this gap. ARM verifies the existence, location, and condition of physical assets and reconciles that data with ERP systems, replacing episodic audits with continuous verification using mobile inspections, RFID, GPS, and document intelligence.

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

Last Updated: June 2026