ARM: The Orchestration Layer Between Workforce, ERP, and Maintenance

Asset relationship management is the layer that turns a single field verification into two trustworthy records: one for finance in the ERP, and one for operations in the maintenance system. It closes the gap between what a company's books say it owns and what condition that equipment is actually in on the floor.

Most asset-intensive operations run two blind spots at once. The fixed asset register drifts from physical reality between annual counts, and equipment condition drifts between scheduled maintenance windows. Kroll Advisory, the firm that runs 8,000 fixed asset engagements a year across 36 countries, reports that 10% to 30% of assets on the average fixed asset register are ghost assets, and that up to 65% of asset records contain errors, missing data, or outdated information. For CFOs, controllers, and operations leaders in warehousing, 3PL, cold chain, and manufacturing, those two blind spots share one root cause and one fix.

What Is Asset Relationship Management?

Asset relationship management is a control layer that verifies the existence, location, and condition of physical assets and reconciles that evidence with the systems that depend on it. It sits above the ERP and the maintenance system rather than replacing either.

Enterprise systems were not built to see the floor. The ERP records what a company should own and how it depreciates. The maintenance system schedules and tracks work orders. Neither one confirms, on any given day, that a specific forklift exists, where it is, or what shape it is in. That confirmation only happens when someone who is close to the asset checks it and the result is routed to the systems that need it.

Consider a 3PL running reach trucks across nine sites. A driver notices a hydraulic leak on Tuesday. In most operations that observation dies in a hallway conversation or waits for the next scheduled inspection. The maintenance system never hears about it until the truck fails, and the asset record never reflects the declining condition at all.

Why the Gap Between Systems Happens

The gap is structural, not a matter of effort. Four causes create it.

1. The ERP tracks accounting transactions and the maintenance system tracks planned work. Both assume the underlying asset data is correct.
2. Annual counts and scheduled maintenance windows are snapshots. Everything that happens between them goes unrecorded until the next snapshot.
3. Location and existence are objective and simple to log. Condition is a judgment, and there is rarely a governed way for a frontline observation to become a work order or a value adjustment.
4. Even where condition is captured, it lands in one place. Finance and operations end up working from different versions of the same asset.

Episodic verification vs. continuous verification

The Real Cost of Untrusted Asset Data

The cost lands on both sides of the house, financial and operational, and it compounds the longer the data stays stale.

• 10% to 30% of the register no longer physically exists, yet continues to depreciate, accrue property tax, and carry insurance.
• components replaced in the field without a journal entry, so depreciation keeps running on parts that are gone. This is an IAS 16 componentization exposure.
• PCAOB data shows long-lived asset deficiencies doubled in 2024 even as overall audit quality improved. Fixed assets are specifically going the wrong direction.
• equipment that is idle, unlocatable, or run on a stale maintenance record. Problems surface as downtime instead of as a scheduled fix.

"You can't run reliability on untrusted asset data."

- Tim Harris, CEO, SoloTruth

The financial exposure is well documented. The operational exposure is harder to put a public number on, because no reliable industry benchmark exists for the cost of late-caught equipment problems in warehousing. That absence is itself the point: the number is specific to each operation, and it is only knowable once the data is trustworthy.

Who Is Most Affected?

The operations that feel this most share one trait: a large, mobile, hardworking base of physical equipment.

• material handling fleets move between sites, get pulled for parts, and wear hard. The record rarely keeps up.
• refrigeration condition is a compliance and spoilage risk, not just an accounting entry.
• they carry the audit, depreciation, and valuation exposure when the register is wrong.
• they inherit the downtime and the reactive firefighting when condition data never reaches the maintenance system in time.

What to Look For in an Asset Verification Approach

Not every approach to asset data closes both the financial and the operational gap. When evaluating options, look for six capabilities.

1. by the people already near the assets, rather than periodic audits that miss everything between cycles.
2. Location is the easy half. The harder and more valuable half is a governed way to record what condition an asset is in.
3. that routes each finding by judgment: routine wear updates the record, a functional fault opens a work order, and a serious issue is escalated before it becomes downtime.
4. at the decision points. Condition is subjective, so a person reviews and approves before a finding changes a ledger or a work queue.
5. Verified data should update the ERP for finance and open a ticket in the maintenance system for operations, from one verification event.
6. per asset, so every change can be traced back to the observation that caused it.

What Good Looks Like

When the layer between the workforce and the systems of record is built for this, the daily reality changes.

1. Checking an asset is a quick step in the normal job, not a separate audit event.
2. A defect found in the morning is a work order by the afternoon, not a surprise at the next service.
3. Nothing subjective reaches a system of record without review, so finance and maintenance both trust the output.
4. One verification updates both, so operations and finance stop working from different numbers.
5. Depreciation, useful life, and valuation run on current data, not on a schedule set at purchase and never revisited.

Common Misconceptions

Misconception: We already capture asset data, so we are covered.

Capture is solved for most operations. RFID, scanners, and inspection apps collect plenty. What is usually missing is the layer that triages the data and routes it to the right system, which is where the value is created.

Misconception: Condition tracking is just maintenance software.

Maintenance systems manage work orders but do not reconcile physical condition against the financial record. Condition data that never reaches finance leaves depreciation and valuation running on assumptions.

Misconception: This is only a finance problem.

The same drift that distorts the books also drives downtime and reactive maintenance. Early condition capture serves operations first, then flows to finance as a downstream benefit.

Frequently Asked Questions

What is asset relationship management (ARM)?

Asset relationship management is a control layer that verifies the existence, location, and condition of physical assets and reconciles that evidence with the ERP and the maintenance system, replacing episodic audits with continuous verification.

How is condition data different from location data?

Location is objective and easy to log. Condition is a judgment about wear, damage, or fault severity, so it needs governed human review before it can trigger a repair or adjust an asset's recorded value.

Does this replace my ERP or maintenance system?

No. ARM sits above both. It feeds verified data to the ERP for finance and opens work orders in the maintenance system for operations, without replacing either system of record.

How does a field observation become a work order?

An operator flags a condition finding during normal work. The platform triages it by severity, and a functional or safety issue creates a one-way ticket in the maintenance system, reviewed and logged before it is sent.

What does continuous verification improve for finance?

It keeps the fixed asset register aligned with physical reality, which supports accurate depreciation, useful-life estimates, and impairment testing, and reduces the audit exposure that comes from a register that drifts between counts.

Why is condition capture the under-told half of the story?

Most asset data efforts stop at existence and location. Condition changes constantly between service cycles and is where avoidable downtime and stale book values originate, so capturing it early is where much of the operational value sits.

Capture Is Solved. Orchestration Is the Answer.

The hard part of asset truth was never collecting data. It was routing a single verification to everyone who needs it, under governance both finance and operations can trust.

This is the gap was built to close. ARM puts the people already closest to the assets to work as a continuous verification layer, triages what they find, opens the work order in the maintenance system, and reconciles the verified data back to the ERP, so one observation keeps both the floor and the books honest.

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

Last Updated: July 2026