A claim, rarely tested
Every fixed asset register makes an implicit claim: this is what the business owns, this is what it cost, and this is where it is. For most of the year, nobody tests that claim against reality — the register just sits there, adding up correctly, generating depreciation, looking entirely trustworthy.
The claim gets tested the moment something forces the question: an auditor picks a sample and asks to see it, an insurer questions a claim on equipment nobody can locate, or someone finally walks the warehouse floor with the register in hand. That's the moment “ghost assets” — entries that exist on paper but not in reality — stop being a theoretical risk and become a very concrete, very awkward conversation.
What makes an asset a ghost
An asset becomes a ghost the moment it physically leaves the business — scrapped, sold, stolen, lost, or simply replaced and discarded — without that event ever being reported to whoever maintains the register. The paperwork that should have triggered a disposal entry either never existed or never made it back to finance.
It's not usually deliberate. A site manager scraps an old machine, replaces it, and moves on without thinking about the register three departments away. Nobody hid anything; the information simply never traveled to the place that needed it.
Why the gap opens in the first place
Almost nobody sets out to let a register drift from reality. It happens gradually, because purchases get reported far more reliably than disposals — an invoice arrives, someone processes it, the asset gets added. A disposal, by contrast, often generates no document at all, especially for equipment that's simply scrapped rather than sold.
A common pattern: a remote site replaces aging equipment on its own initiative, disposes of the old unit locally, and never circles back to tell head office. The purchase of the replacement shows up on the register right on schedule; the disposal of the original never does, and the register quietly grows an entry that no longer corresponds to anything real.
What actually goes wrong
Insurance premiums on assets that no longer exist
A business can spend years paying to insure equipment that was scrapped long ago, discovered only when a claim finally forces the question.
Depreciation expense that overstates the asset base
A ghost asset keeps generating a book value and depreciation charge that no longer relates to anything real.
An audit finding that undermines confidence in the whole register
One sample item nobody can locate raises the question of how many others are in the same state — even if most of the register is fine.
A slower, more expensive insurance claim
Insurers scrutinise claims more closely once an inconsistency between the register and physical reality has already been found.
The third is the one with the widest-reaching cost, and the next section shows what it looks like once someone actually goes looking.
A count, traced
A mid-sized manufacturing business, its first physical count in five years, 210 assets on the register.
| Outcome | Assets | Book value |
|---|---|---|
| Confirmed present | 192 | $3,140,000 |
| Not found — likely ghost | 14 | $186,000 |
| Found but unrecorded | 6 | $41,500 |
Fourteen ghost assets worth $186,000 in book value, and six unrecorded assets worth $41,500 that had been sitting on the floor uninsured and undepreciated the entire time. Neither number is unusual for a first count after several years without one — it's exactly the kind of gap that accumulates quietly when disposals and informal purchases both go unreported.
How to close the gap without a full audit
A full annual physical count is the gold standard, but it's heavy — a business doesn't need to wait for one to start closing the gap. Reconciling the register against the paper trail is a lighter first step that catches a surprising share of the problem before anyone walks a single floor.
Every register entry should have a supporting purchase invoice; every disposal should have a supporting document. Entries without support, and disposals that were reported informally but never logged, are exactly the candidates worth checking first — long before a full physical count becomes necessary to confirm the rest.
Scenario: the insurance claim that revealed the gap
A warehouse fire damages a section of equipment. The business files a claim, and the insurer requests the register entries for the affected items — supported by purchase documentation and, ideally, evidence the equipment was actually in use before the fire.
For most of the claimed items, that documentation exists cleanly. For two, the register shows an entry but no supporting invoice can be located, and nobody can confirm when the equipment was last actually seen in operation. The insurer doesn't deny the claim outright, but the process slows considerably while the business tries to reconstruct records that should have existed from the start.
A register reconciled against its paper trail beforehand would have flagged those two items long before the fire — not as a fire-prevention measure, but as a claims-readiness one, closing exactly the gap an insurer's scrutiny finds fastest.
Scenario: the auditor's sample
An external auditor selects a sample of register entries and asks to see supporting documentation and, for a subset, physical confirmation. One selected item — a piece of equipment purchased four years earlier — can't be located by the site team, and nobody remembers what happened to it.
A single missing item in a sample doesn't automatically fail an audit, but it does prompt a wider question: how many more entries are in the same state? Answering that question well, with a documented reconciliation already in hand, is a very different experience from answering it by scrambling to check the rest of the register under time pressure.
A register maintained with the paper trail intact for every entry turns that follow-up question into a quick, confidence-building exercise rather than a scramble — the auditor sees that the one gap was an isolated case, not a sign of a systemic problem.
What businesses actually do about it
| Situation found | Typical response |
|---|---|
| An entry with no supporting invoice | Search for the original documentation; if none exists, flag it explicitly for the next physical count |
| A confirmed ghost asset | Write it off with a documented reason, and review whether it's still being insured |
| An unrecorded asset found during a count | Add it to the register retroactively, with whatever documentation can be gathered |
| A pattern of disposals not being reported from one site | Fix the reporting process at that site, not just the individual register entries |
None of these responses require rebuilding the entire register from scratch — they're targeted, specific corrections, made possible only once the gap has actually been measured rather than just vaguely suspected.
Three businesses, three levels of verification
The same underlying risk of drift, handled with three different levels of rigour.
| Business | When it discovers a gap | Room to act |
|---|---|---|
| A — no verification | During an audit or an insurance claim | None — decisions made under scrutiny |
| B — occasional informal checks | Sometimes, if someone happens to notice | Limited — little documentation to fall back on |
| C — paper trail reconciled, annual physical count | As soon as an entry looks unusual | Wide — time to correct before it becomes an issue |
Business A carries exactly the same underlying risk as Business C — the difference isn't in the assets themselves, it's in how much time is available to notice and correct a gap before someone outside the business notices it first.
Common mistakes
Treating a physical count as a one-time project
A count that isn't repeated periodically stops reflecting reality the moment the next disposal goes unreported.
Only checking high-value assets
A low-value ghost asset costs less individually, but a pattern of them signals the same underlying process failure.
Writing off a ghost asset without investigating why it wasn't reported
Fixes the symptom without fixing the reporting gap that will produce the next one.
Assuming a clean audit means no ghost assets
An audit sample tests a subset, not every entry — a clean sample doesn't guarantee the rest of the register is equally solid.
Waiting for the annual audit to check the register
By then, a gap has had a full year to grow before anyone notices it.
Building a simple verification routine
None of this requires a full overhaul of how the business manages its assets. A short, written routine covering four points is enough for most businesses to move from “we think it's fine” to a concrete, checkable number.
How every register entry is tied to a supporting invoice, checked as new assets are added.
How disposals get reported, and by whom, so the process doesn't rely on someone remembering to circle back.
How often a physical count happens — annually at minimum, more often for high-turnover or high-risk sites.
Who owns the decision when a discrepancy is found, and what the default action is.
Four sentences, and the difference between a business that occasionally wonders whether its register is accurate and one with a concrete routine for catching drift early.
Why auditors and insurers care
An external auditor reviewing fixed assets isn't just checking that the register adds up — part of the review is confirming that what's recorded actually exists and is being used as claimed, which is precisely the question a well-formatted spreadsheet can't answer on its own.
An insurer asks a related but sharper question at claim time — not just whether the asset was recorded, but whether it can be shown to have existed and been in use right up to the point of loss. A register with a clean paper trail answers that faster and more convincingly than one that relies on recollection.
For a business preparing for a sale or an acquisition, due diligence typically includes exactly this kind of asset verification — a buyer wants confidence that the asset base being valued actually exists, and ghost assets discovered during diligence tend to raise far more concern, proportionally, than their book value alone would suggest.
How this differs by industry
A business with a small, centralised asset base — an office-based professional services firm, for example — faces a relatively contained version of this problem: fewer assets, fewer locations, and a shorter distance between where an asset is purchased and where the register is maintained.
A business with equipment spread across many remote sites — manufacturing, logistics, construction, healthcare with multiple clinics — faces a structurally harder version, because disposals at a distant site are the ones most likely to never make it back to the central register at all. The tracking described in this article isn't optional there — it's the mechanism that keeps distance from becoming an accounting blind spot.
Neither situation calls for a different tool to verify assets — the method stays the same, reconciling every entry against its paper trail. What changes is how much distance and how many hands the reporting chain has to cross before an event reaches the register.
A business that finally traced its assets
A regional healthcare provider running six clinics had never run a coordinated physical count — each clinic managed its own equipment informally, and the central register was updated only when someone remembered to send an invoice through.
Reconciling the register against its paper trail, following the method described above, took a few days the first time — every entry checked for a supporting invoice, every gap flagged. The result surfaced eleven entries with no supporting documentation at all, several dating back more than three years, worth a combined $94,000 in book value.
A follow-up physical count at the two clinics with the most flagged entries confirmed that seven of the eleven no longer existed — replaced years earlier and never reported. The remaining four were located, and their missing documentation was reconstructed from supplier records. The same reconciliation, repeated annually going forward, now catches this kind of drift before it accumulates across years again.
The other direction — assets that exist but aren't recorded
Ghost assets get most of the attention, but the gap runs both ways. An asset purchased informally — bought with a purchasing card, expensed rather than capitalised by mistake, or acquired second-hand without a formal invoice — can exist on the floor for years without ever appearing on the register at all.
An unrecorded asset isn't just a bookkeeping gap. It's usually also an insurance gap — coverage is typically based on what's declared, and equipment that was never added to the register was, in most cases, never declared to the insurer either.
A physical count that only checks whether register entries can be located misses this direction entirely. A count that also asks “what's here that isn't on the list” catches both directions of the gap in a single pass, which is why the worked example earlier in this article deliberately tracked both outcomes rather than just the missing ones.
What a multi-year history teaches you
A single count answers an immediate question: what's the gap right now. A history of counts, repeated over several years, answers a more useful one: is the gap growing, shrinking, or staying roughly constant — and is it concentrated in one site or spread evenly.
Building that history doesn't require a separate project — it's simply the same count, and the same reconciliation, kept as a record rather than discarded once used. Each cycle adds a data point that, added to the ones before it, reveals a pattern a single count in isolation never could.
Businesses that reach three or four years of this kind of record often find the same thing: the gap is disproportionately concentrated at one or two sites, or in one category of low-value equipment that's easy to scrap informally — exactly the kind of pattern that points to a specific process fix rather than a general call for more vigilance everywhere.
That kind of specific, site-level finding is worth more to a controller than a general instruction to “be more careful” — it points directly at where a training conversation, a process change, or simply closer attention would actually make a measurable difference.
Preventing the next gap, not just closing this one
Closing a discovered gap once feels like progress, but it doesn't address why the gap opened in the first place. If a site's disposals routinely go unreported, writing off the ghost assets that resulted from that pattern fixes the register without fixing the process that will quietly produce the next batch of ghost assets within a year or two.
The more durable fix is process-level: a simple requirement that any disposal, however informal, gets logged with the central finance team before or immediately after it happens — not a heavy compliance burden, just a habit that closes the specific gap that produced the problem in the first place.
Weighing the cost of verification against the risk
Not every business needs the same intensity of asset verification. A business with a handful of high-value, centrally located assets faces a much smaller version of this problem than one with thousands of low-value items scattered across remote sites — the right level of investment in verification should reflect that difference, not apply the same routine regardless of actual risk.
A useful way to calibrate is to weigh the annual cost of a verification routine against the size of the register itself and the consequences of a gap — a business heavily reliant on insured equipment, or one preparing for a sale, has a much stronger case for thorough, frequent verification than one whose fixed assets are largely low-value office equipment with minimal insurance exposure.
That calibration is worth revisiting periodically, too — a business that grows its physical footprint or takes on more insured equipment should expect its verification routine to grow alongside it, rather than staying fixed at whatever level made sense when the business was smaller.
Revisiting it annually, alongside the insurance renewal, is often the most natural point to make that call — the two conversations already cover much of the same ground, and a broker will often ask about verification practices directly.
Pairing the two reviews also means neither one gets quietly skipped in a busy year, since each one now has a natural trigger already built into the calendar rather than depending on someone remembering to schedule it separately, which is exactly the kind of thing that slips when everyone is busy.
What we don't do
We don't perform the physical count
We read invoices and documents to build the paper trail a count is checked against — walking the floor and confirming what's there stays a human task.
We don't decide how to write off a ghost asset
That's an accounting and, often, a tax decision that depends on your specific policy and circumstances.
We don't investigate why a disposal wasn't reported
We can show you the gap in the paper trail; understanding the process failure behind it is a management question.
We don't assess insurance coverage
A gap between the register and reality is relevant to your insurer, but reviewing coverage itself is a conversation for your broker.
What we do is the part that has to happen before any of that: an honest, complete reading of every capital invoice, so the register you reconcile against is based on real documents, not an approximation. For that, see fixed asset register from invoices, and for the routine to build it on, see how to build a fixed asset register.
A useful rule of thumb: the sooner a gap between the register and reality is found, the more options remain for closing it calmly. Found during a routine reconciliation, it costs an afternoon. Found during an audit or a claim, it costs a much longer, much less comfortable conversation.