Compliance10 min read

Reconciling the Financial Fixed-Asset Register and EAM Register Under ISO 55001 & ISO/TS 55010

Finance and operations almost never see the same asset base. Here's why, what ISO/TS 55010:2024 recommends, and the real, quantified cost of leaving it unreconciled.

Jarred Wakefield
Jarred Wakefield
Managing Director
July 14, 2026
Controller and asset manager comparing a financial ledger against a maintenance system report

Almost every asset-intensive organization runs two asset registers that don't agree with each other: finance's fixed-asset register (FAR) and operations' EAM/CMMS register. ISO/TS 55010:2024 is the guidance standard built specifically to close that gap — and the financial cost of not closing it is larger than most finance teams realize.

What ISO/TS 55010:2024 actually is

ISO/TS 55010:2024 is a non-certifiable technical specification from ISO/TC 251, revised from a 2019 first edition, giving guidance on aligning financial and non-financial asset management functions to improve internal control and value realization. It's aimed at asset managers, CFOs, and finance teams, and emphasizes "vertical alignment" (asset information consistent from strategic capital-budget decisions down to individual-asset operations) and "horizontal alignment" (finance, engineering, maintenance, and risk sharing a common understanding of the asset base). It adds no new ISO 55001 certification requirements — it's a companion guide, not an audit checklist. For the certifiable clause that actually requires this alignment, see clause 7.6 in our information requirements & documented information guide.

Why the two registers diverge

  • Assets are dynamic, registers are episodic: the CMMS reflects daily operational reality; the FAR often updates only on discrete financial events, and only if finance is actually told.
  • Different objectives and thresholds: the FAR groups components for depreciation; the CMMS tracks individual pumps, motors, and sensors — creating one-to-many mismatches.
  • Disposals and communication failures: physical disposals are visible in the CMMS but not always communicated to finance, so scrapped or stolen assets keep depreciating on the books — the direct mechanism that creates ghost assets.
  • System migrations and manual processes: ERP/CMMS migrations at different times and inconsistent identifier schemes across finance and operations make reconciliation hard.
  • Organizational silos: finance (compliance, cost control) and operations (reliability, safety) rarely challenge each other's register.

The real cost of an unreconciled register

Industry ghost-asset research consistently finds that 12-30% of assets on a typical fixed-asset ledger don't physically exist, with a 2025 Institute of Asset Management study estimating this costs U.S. companies roughly $2.3 trillion annually across unnecessary tax overpayments, insurance waste, depreciation distortion, and audit penalties. A detailed cost-breakdown analysis estimates, per $1 million of ghost-asset value: property tax overpayment of 1.8-3.5%, insurance waste of 0.8-1.5%, depreciation distortion of $50,000-$200,000, audit penalties of $25,000-$100,000, and maintenance-budget waste of $15,000-$40,000 — summing to roughly $156,000-$470,000 in unnecessary annual cost per $1 million of ghost assets. One documented case: a healthcare network discovered $47.2 million in ghost assets — 9.7% of its total register value — and achieved $8.3 million in annual savings after reconciliation and physical verification. World-class organizations are benchmarked at keeping ghost-asset rates below 2%, typically through rolling quarterly verification.

A practical reconciliation framework

The unique asset identifier should be the reconciliation backbone — ideally the same physical tag ID is cross-referenced in both the FAR and the CMMS, not two separate numbering schemes with no mapping. Physical audits should involve both finance and operations: finance shouldn't finalize annual depreciation without a physical-verification report, and operations shouldn't mark anything "disposed" in the CMMS without triggering a finance disposal transaction. This is exactly where an independent, third-party wall-to-wall verification and reconciliation program fits — it produces the physical baseline both functions can reconcile against, rather than each trusting its own self-reported data. See our general guide to reconciling fixed assets for the practical mechanics.

CPCON's honest fit

CPCON's wall-to-wall counts and register reconciliation produce the independent physical baseline both ISO 55001 and ISO/TS 55010 assume exists behind the numbers. CPCON doesn't decide capitalization policy, doesn't make the accounting entries, and doesn't configure system integrations between the FAR and CMMS/EAM — that's the client's finance and IT function. CPCON supplies the evidence-backed reconciliation report — found, missing, relocated, untagged — that finance and operations act on together.

Frequently Asked Questions

What is ISO/TS 55010?

ISO/TS 55010:2024 is a non-certifiable technical specification giving guidance on aligning financial and non-financial asset management functions to improve internal control and value realization. It does not add new ISO 55001 certification requirements — it is guidance, revised from a 2019 first edition.

Why don't financial and operational asset registers match?

Assets are dynamic but registers update episodically; finance and operations use different capitalization thresholds and componentization; disposals often aren't communicated to finance; and the two functions frequently use uncoordinated identifier schemes with no cross-reference.

How much do ghost assets typically cost a company?

Industry ghost-asset research finds 12-30% of assets on typical fixed-asset registers don't physically exist, with a 2025 Institute of Asset Management study estimating this costs U.S. companies roughly $2.3 trillion annually in taxes, insurance, depreciation distortion, and audit penalties.

How often should financial and operational registers be reconciled?

World-class organizations are benchmarked at keeping ghost-asset rates below 2%, typically through rolling verification of about a quarter of the asset population each quarter for full annual coverage. At minimum, a full reconciliation cycle tied to year end is recommended.

Does ISO 55001 require reconciling the FAR and CMMS?

ISO 55001:2024's data and information clause (7.6) requires alignment and traceability between financial and non-financial asset data. ISO/TS 55010 provides the guidance on how to achieve that alignment in practice.

Get an independent, reconciled baseline for both registers

CPCON's wall-to-wall verification and reconciliation programs give finance and operations a shared, evidence-backed asset baseline — closing the gap ISO/TS 55010 is designed to address.

Explore CPCON's fixed-asset count & tagging services
Share this article:
Jarred Wakefield

Jarred Wakefield

Managing Director

Expert in fixed asset management and compliance with over 15 years of experience helping organizations optimize their asset verification processes.

Need Expert Help?

CPCON's asset management specialists can help you implement effective verification processes and ensure compliance with all regulatory requirements.

Talk to CPCON About Register Reconciliation

Related Articles