Asset Verification Is a Function, Not an Annual Project

Continuous asset verification is the practice of confirming that a capitalized asset exists, sits where the record says, and remains in working condition, as an ongoing function rather than a once-a-year project. It produces the physical input that a fixed asset subledger depends on and cannot generate for itself.

Every company with a material fixed asset base already runs asset verification. It runs once a year, as a project, with a start date and a team pulled off other work. That is the job. The open question is how often it runs.

The cost of running it annually is measurable. Kroll Advisory, which runs more than 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, and that up to 65 percent of asset records contain errors, missing data, or outdated information. Those records were accurate on the day of the last count.

For CFOs, controllers, fixed asset managers, and internal audit teams, the useful question is not whether the register drifts. It is whether verification stays a project that decays for eleven months, or becomes a function running against work the business already does.

What Is Continuous Asset Verification?

Continuous asset verification is a standing function that confirms physical existence, location, and condition against the fixed asset record, delivering evidence rather than a count total.

The function exists because two systems describe the same equipment and only one of them can see it. The fixed asset subledger is the financial system of record. It tracks acquisition cost, depreciation method, useful life, and net book value, and feeds those figures to the balance sheet. Within that scope it is excellent.

It does one thing by design that is easy to miss. It records what it is told. The subledger will accept a correction originating on the floor. It will not go and find one. That is correct architecture, and it is why verification is a separate job rather than a feature request.

The vendors document this themselves, and their wording is worth reading closely. Oracle Assets includes a Physical Inventory feature, and Oracle states that to use it you must first take physical inventory of your assets, describing that as a process in which a company takes inventory by manually looking at all assets to ensure they exist as recorded, are in the appropriate locations, and consist of the recorded number of units. SAP documents a physical inventory that the director of the organization orders, carried out by a commission that posts any differences into Asset Accounting afterwards. Microsoft says that to verify recorded assets exist and sit in the correct location, you should reconcile physical inventory, with the verification data entered or imported.

Every major platform therefore has a reconciliation path. What none supplies is the field evidence that path consumes. SAP's ABAVN and ABAON retirement transactions also operate on whole assets, so component-level retirement still needs a manual journal entry.

Consider a $180,000 stamping press. In year four the drive motor fails and maintenance replaces it for $40,000. The work order closes cleanly. No journal entry reaches the subledger, so the original motor keeps depreciating as part of the press for another six years, and the new motor never enters the register. Both records are internally consistent. Neither describes the machine on the floor.

Why the Register Drifts Between Counts

The register drifts for structural reasons rather than careless ones. Four causes account for most of it.

1. The verification input arrives once a year. A count establishes what is true on the day it runs. From the following morning the record ages, for another eleven months, before anything checks it again.
2. Physical events and accounting events travel on separate paths. An asset is moved, scrapped, cannibalized, or replaced by people whose job is keeping production running. The accounting consequence depends on somebody remembering to report it through a second, unrelated process.
3. Component-level change has no standard route to the subledger. IAS 16 paragraphs 43 to 47 require material components to be depreciated separately. Standard ERP retirement transactions work on whole assets, so component replacements accumulate as partial ghosts in the record.
4. Disposal is an operational event before it is an accounting one. Equipment leaves the building weeks or months before anyone posts the retirement, and sometimes nobody does.

Annual Physical Count Compared With Continuous Verification

Neither column is wrong. The annual count was the only practical mechanism for most of the time fixed asset accounting has existed, and it still produces a clean attestation on the day it runs. The question is what the record is worth on the other 364 days. None of these causes is carelessness. They are what happens when continuous change is checked on a discontinuous schedule.

What Accurate Asset Data Is Worth

The return on a verified register does not land in one place. The same input feeds several records usually maintained separately.

• Depreciation accuracy. Charges stop running on assets that no longer exist, and components replaced in the field enter the schedule at the right cost and the right remaining life.
• Audit support. Long-lived assets became the number one internal control over financial reporting deficiency area at large firms in 2024, even as overall PCAOB deficiency rates improved from 46 percent to 39 percent. Fixed assets moved the wrong way while audit quality improved elsewhere.
• Property tax exposure. Business personal property filings are built from the asset listing, and the filing standard is physical rather than accounting. California's 2026 business property statement instructs that equipment retired but not removed from the site must still be reported. An accounting retirement does not by itself change the taxable position.
• Insurance schedules. A statement of values is a warranty the insured provides. It is normally assembled from the same register, and it is rarely verified independently.
• Impairment testing. ASC 360 requires recognition when evidence shows carrying value exceeds fair value. Condition evidence turns that from a judgment call into a documented one.
• Maintenance and capital planning. Replacement decisions improve when the condition record reflects the equipment now rather than at capitalization.

"Ghost assets aren't the problem. The annual audit cycle is. Ghost assets are just what happens when you only look once a year."

Tim Harris, CEO, SoloTruth

Only the first two of those categories have defensible published figures attached. Property tax and insurance overpayment are real and widely acknowledged, and no reliable public benchmark exists for either. Any number offered for them should be built from a company's own register rather than borrowed from someone else's.

Who Gets the Most From Closing This Loop

The return scales with how much of the balance sheet sits in physical assets and how often those assets move.

• CFOs and controllers in asset-heavy industries. Manufacturing, energy, utilities, and transport carry enough gross fixed assets that a few points of register error becomes material to the statements.
• Fixed asset managers in manufacturing and heavy industry. Equipment moves between lines and sites, components are swapped during maintenance, and tooling is consumed. The register assumes none of that happens quietly.
• Internal audit teams. Continuous evidence turns the annual exercise from discovery into confirmation, a materially cheaper way to spend audit hours.
• Companies partway through an S/4HANA migration. Master data quality drives migration cost, and asset records carry inaccuracies into the new system unless resolved before conversion.
• Warehousing, third-party logistics, and cold storage operators. Material handling equipment moves constantly, often between customer sites, and fleets are large enough that annual reconciliation is difficult.

What to Look For in a Verification Layer

A verification layer earns its place by feeding systems a company already runs. Look for six capabilities.

1. Direct reconciliation into the existing subledger. Verified data should reach the fixed asset record through a defined path, not through a spreadsheet and a manual journal entry. The transfer step is where accuracy is usually lost.
2. Continuous capture rather than periodic snapshots. The value comes from shortening the interval between a physical change and its accounting consequence, which a faster annual cycle does not achieve.
3. Multi-source evidence. Physical inspection, location signal, photographs, and extracted document data each cover a different failure mode. Single-source verification leaves gaps that an auditor will find.
4. Component-level granularity. Whole-asset verification cannot support IAS 16 component accounting. If the layer cannot describe what changed inside an asset, it cannot fix the partial ghost problem.
5. Human-in-the-loop remediation at defined decision points. A person needs authority to act on a flagged discrepancy, not merely visibility into it, and the rationale for that decision needs to be recorded.
6. An audit-ready evidence chain per asset. Auditors need to trace a change back to its source evidence. A count total and a summary report do not survive that request.

What Good Looks Like

Six practices separate a verification programme that holds from one that decays after the first quarter.

1. Verification rides on work already happening. Operators, technicians, and drivers move through the facility every shift. A programme that depends on new headcount walking the floor will be cut in the first budget cycle that gets tight.
2. Every field event carries evidence. A status update with no photograph, location, timestamp, or identified author is an assertion. Evidence is what makes it usable in an audit.
3. Exceptions route to a named owner with a deadline. A flagged discrepancy with no owner is a discrepancy that ages. Aging exceptions are the failure mode that turns a verification record into a liability.
4. The subledger updates through a governed path. Verified changes should reach the fixed asset record through an approved workflow with an audit trail, never through a bulk upload nobody can reconstruct.
5. The annual count becomes a confirmation. When continuous evidence is working, the physical count stops discovering surprises and starts validating a record that was already close. That change in the character of the count is the clearest signal the programme is working.
6. Ownership sits with one named person. A verification function with no owner reverts to a project, because nobody is accountable for the cadence between counts.

Common Misconceptions

Four assumptions come up consistently in conversations with finance and audit teams.

Misconception: We run SAP, so our fixed asset data is accurate.

Reality: the subledger is accurate about every transaction it was given. Accuracy about the physical estate depends on whether physical changes were reported into it, and the platforms do not connect maintenance and logistics activity to the financial asset record automatically.

Misconception: Continuous verification means hiring people to walk the floor.

Reality: the practical designs attach verification to movement that already occurs. A driver, technician, or supervisor already passes the equipment. Capturing evidence at that moment costs seconds rather than a headcount line.

Misconception: A continuous record creates a documented trail of problems we knew about and did not resolve.

Reality: this is the most substantive objection to continuous verification and it deserves a direct answer. An unresolved discrepancy carries risk whether or not it is written down. What a governed record changes is that the discrepancy has an owner, a date, and a resolution path. Where fixed asset existence and disposition are material to the statements, an undocumented verification process makes management's internal control assertion under SOX 404 harder to support (17 CFR 240.13a-15(f)). Exception aging is a control problem with a known solution. Not knowing is not.

Misconception: This means replacing part of the ERP.

Reality: a verification layer sits above the ERP and writes into it. The system of record does not change. What changes is the quality and frequency of what reaches it.

Frequently Asked Questions

What is continuous asset verification?

A standing function confirming an asset exists, sits where the record says, and works, delivering evidence rather than a count total. It supplies the physical input a subledger depends on and cannot produce itself.

Is asset verification a project or an ongoing function?

Most companies run it as an annual project. As a function it happens continuously, tied to work already occurring in the facility, so the record never drifts far from reality.

Why does an ERP fixed asset register become inaccurate over time?

Physical changes happen continuously and reach the register only when somebody reports them through a separate process. Between counts, moves, disposals, and component replacements accumulate with no corresponding accounting entry.

How often should fixed assets be physically verified?

No universal requirement exists. Accuracy is a function of the interval, so verification tied to ongoing field activity produces a more current record than any fixed annual or quarterly cycle.

What is the difference between asset tracking and asset verification?

Tracking answers where an asset was last seen. Verification establishes that it exists, what condition it is in, and produces evidence a third party can review. Financial reporting depends on the second.

Does continuous verification replace the annual physical count?

It changes what the count does. Rather than discovering discrepancies, it confirms a register continuous evidence has already kept close. Most organizations keep the count and find it cheaper to run.

What is Asset Relationship Management (ARM)?

ARM is the software category that verifies the existence, location, and condition of physical assets and reconciles that data with ERP and compliance systems, replacing episodic audits with continuous evidence.

How does verified field data actually reach the ERP subledger?

Through a governed workflow. Field evidence is captured, discrepancies flagged, a person with authority approves the correction, and the change posts to the subledger with its evidence attached.

Verification Is Already a Line in Your Budget

Asset verification is not a new function anyone needs to justify. It is already funded, already staffed for a few weeks a year, and already producing an input everything downstream depends on. The decision is not whether to do the job. It is whether it runs once as a project, or continuously as a function riding on movement already happening in the building.

This is the function SoloTruth Asset Relationship Management (ARM) was built to run. ARM verifies the existence, location, and condition of physical assets using inspections, location signals, and document intelligence, then reconciles that verified data into the ERP through a human-in-the-loop control layer. The system of record does not change. What changes is how often it hears the truth. Our model typically shows payback in under six months.

Book a 30-minute strategy call at calendly.com/tim-harris-solotruth/30min to talk through what running verification as a function would look like against your own asset base.

Last Updated: August 2026