Your ERP Validates. It Doesn't Verify. There's a Difference

There is a word problem at the center of fixed asset management. The same language gets used for two completely different activities. And because nobody has distinguished them, the gap between financial records and physical reality has been widening for decades.

The word is "verify."

When a controller says the fixed asset register has been verified, they usually mean the accounting process was followed. A purchase order was issued. An asset was capitalized. Depreciation was calculated according to policy. The transaction chain is intact. In accounting terms, this is validation: confirming that a process was executed correctly.

Verification is something different. Verification asks whether the physical asset described in that record actually exists. Is it still in the building? Is it in the condition assumed? Has it been scrapped, moved, or cannibalized since the last time anyone looked?

ERP systems are excellent at validation. They were designed for it. What they cannot do is verify.

Why the Distinction Matters

A validated record is not the same as a verified one. This is not a semantic point. It has direct financial consequences.

Consider a compressor that was retired during a planned shutdown three years ago. The maintenance crew removed it from service. No one filed the journal entry. The asset record stayed active. For three years, your ERP has been calculating depreciation on an asset that does not exist, posting those charges to your income statement, and carrying the net book value on your balance sheet. Your auditors tested the process. The process was clean. Nobody asked whether the asset was still there.

That is a validated record. It is not a verified one.

Kroll Advisory estimates that 10 to 30 percent of fixed asset records at a typical enterprise are ghost assets. Up to 65 percent contain errors of some kind. These are not organizations with broken accounting processes. Their validation is fine. Their verification does not exist.

The Design Boundary ERP Was Never Built to Cross

This is not a criticism of ERP systems. SAP FI-AA, Oracle Fixed Assets, and Microsoft Dynamics 365 are transaction engines. They record financial events with precision. They are not physical inventory systems, and they were never designed to be.

The physical tracking modules in major ERP platforms sit in logistics and maintenance, not in the fixed asset financial subledger. In SAP, the Plant Maintenance module handles work orders but does not write back to FI-AA by default. In Oracle Financials Cloud, Inventory Management and Fixed Assets are separate modules with no automatic connection. In Dynamics 365, physical asset counting requires a third-party add-on.

The financial subledger and the physical world have no automatic link. The ERP records what it has been told. It has no mechanism to go find out if what it was told is still true.

This means every fixed asset register starts accurate and drifts from the day it is built. Assets move between facilities. Equipment gets cannibalized for parts. Vehicles get retired informally. Servers get decommissioned. Each event that happens without a journal entry widens the gap between the record and reality. The ERP does not know it is wrong. It keeps calculating, keeps posting, keeps reporting.

The Annual Count Is Not a Solution

The standard answer to this problem is the annual physical count. Once a year, a team walks the floor, scans barcodes, and reconciles what they find against the register. Discrepancies get resolved. The register gets corrected. And then the drift begins again.

The annual count provides one verified snapshot per year. For the other 364 days, the organization is operating on a register that is, at best, an approximation of physical reality.

For most companies, this has been acceptable. Auditors sample the register, not the floor. Controllers close the books with what the system says. The gap is real, but it is invisible.

That is changing. The PCAOB's 2024 Staff Update found that audit deficiencies related to long-lived assets doubled between 2022 and 2024. CSRD and ESRS requirements are expanding what European companies must disclose about physical assets. Insurance underwriters are asking harder questions about declared asset values. The standard for what constitutes adequate documentation is moving, and the annual count is not keeping up.

Closing the Gap Requires a New Layer

Better validation does not solve a verification problem. Tightening the journal entry process, retraining field staff, or upgrading to a newer ERP module will not close the gap between records and physical reality. The problem is architectural, not behavioral.

What closes it is a continuous verification layer between the physical world and the financial record. One that captures physical evidence through IoT sensors, mobile inspection workflows, and intelligent document processing. One that compares that evidence against the financial record in near real time and routes discrepancies for resolution before they compound.

That is what SoloTruth ARM is built to do. Not to replace ERP. To verify what ERP validates.

Your accounting process may be clean. That is not the same as your register being right.

Book a 30-minute strategy call at https://calendly.com/tim-harris-solotruth/30min

SoloTruth — Evidence-based fixed asset management

solotruth.com