Ghost assets: when disposed equipment stays on the fixed-asset register

The most common failure is the ghost asset: equipment scrapped or lost that sits in the fixed-asset register and keeps depreciating. It starts when disposals happen on the floor without a retirement reaching accounting. Physical counts and reconciliations expose it. The fix pairs a write-off with a disposal trigger.

How it starts

Asset additions are well controlled almost everywhere. A purchase order, an invoice and a capitalisation threshold all push a new item into the register. Retirements have no such engine behind them.

A machine breaks and a technician strips it for parts. A laptop is lost and replaced through the service desk. A site closes and its furniture goes to a scrap dealer who pays cash or nothing at all. Each event is real. None of them generates a document that lands with the fixed-asset accountant.

The policy usually says a disposal form must be raised. In practice the form lives on an old intranet page, needs a signature nobody remembers to chase, and asks for an asset tag that fell off years ago. So it never gets filled in.

Transfers make it worse. When equipment moves between sites or cost centres without a transfer entry, the master data points to a location where the item no longer exists. Later, when it is thrown out, nobody at the new site knows it was ever on the books.

Why nobody notices at first

The ledger stays internally consistent. Depreciation runs on schedule against every live record, and the subledger agrees with the general ledger because both are equally wrong. A clean reconciliation proves only that the two systems match each other. It says nothing about whether the asset is on a shelf somewhere.

Fully depreciated items hide best of all. Once net book value reaches zero, a ghost costs nothing in the profit and loss, so it attracts no attention. Its gross cost and accumulated depreciation still inflate the balance sheet and distort any ratio built on them.

How it is spotted

The physical inventory is the usual discovery point. Counters arrive with a list and cannot find a chunk of it. Sometimes the reverse happens too: items on the floor with no record, often replacements bought for the very things that vanished.

Other clues surface elsewhere. Insurance schedules built from the register quote premiums on equipment that is long gone. Tax teams find property tax or capital allowance claims that do not match what a site manager describes. An auditor samples assets from the ledger and asks to see them. A maintenance team keeps a separate equipment list that disagrees with finance.

A quieter signal is a register where retirements are rare compared with additions. Equipment wears out. If the books show almost nothing leaving, something is leaving unrecorded.

Fixing the register

Start with the count results, and resist writing everything off at once. Missing items need a short investigation. Some will turn up under a different tag or at another site, which calls for a transfer entry and a master data correction. Some were sold, so there may be proceeds sitting in a suspense or miscellaneous income account that belong against a gain or loss on disposal.

What remains unfound gets retired with a documented approval from someone with authority over the asset class. Record the retirement in the period the loss was identified unless the actual disposal date can be evidenced. Reverse depreciation only where the system ran it after a known disposal date and the amounts matter.

After the entries post, reconcile the subledger to the general ledger again, and pass corrected data to the tax and statutory reporting teams so their schedules move with the books.

Stopping it coming back

Put the trigger where the physical event happens. Link the retirement step to the processes that already touch the asset: scrap dealer collections, IT asset returns, site closure checklists, and maintenance work orders that mark equipment beyond repair. If an asset can be swapped out through the service desk, the service desk ticket should create the retirement request.

Make the form easy. Allow lookup by serial number or description, so a missing tag does not stop it.

Count on a rotating basis by location or asset class instead of saving everything for one large exercise. Small, frequent counts catch ghosts while someone still remembers what happened.

Questions to ask the people who run it

• When a piece of equipment is thrown away, who actually does it, and what do they write down?
• Where do scrap or resale proceeds get booked today?
• How often does a disposal form reach accounting without being chased?
• Does maintenance or IT keep its own asset list, and when was it last compared with the register?
• What happens to the record when equipment moves between sites?
• During the last count, what did the team do with items they could not find?
• Which asset classes do counters skip because they are hard to reach or identify?
• Who is allowed to approve a write-off, and do they know that?

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.