Fixed assets sit at the center of a web. Threads run out to tax, to financial reporting, to insurance, to property tax, to operations, to facilities, to IT, to procurement, and to whoever is building the five-year capital plan. Pull any thread and the whole structure moves.
And in most organizations, nobody owns the center.
How the gap forms
It is almost never a decision. It accumulates.
Fixed assets are usually a fraction of someone's job — a senior accountant who also owns leases, or a manager who inherited the depreciation run. The work is monthly, procedural, and invisible when it goes well. It gets attention only during an audit, an acquisition, or a system conversion, and by then the questions being asked are years older than the answers available.
Meanwhile the surrounding functions each assume someone else has it. Tax assumes finance is maintaining accurate lives. Finance assumes operations is reporting disposals. Operations assumes the register is a finance document that has nothing to do with the equipment on the floor. Everyone is being reasonable, and the register drifts.
What neglect actually looks like
- Ghost assets. Equipment retired, sold, or scrapped years ago, still depreciating. It inflates the balance sheet, inflates insured values, and in many jurisdictions inflates property tax.
- Invisible assets. The reverse: assets in use that were expensed or never recorded. Real exposure, no book value, no replacement planning.
- Lives that were never revisited. Useful lives set at conversion a decade ago and applied to every addition since, regardless of what the asset is.
- Tax and book quietly diverging. Two registers maintained separately, reconciled annually under time pressure, each accumulating its own corrections.
- Descriptions nobody can decode. "MISC EQUIP — 2016 ADDN." No location, no serial, no tie to anything physical. That asset can never be verified, transferred, or retired with confidence.
Individually these are small. Together they mean the fixed asset register — often the largest number on the balance sheet — is the number the organization trusts least.
Untangling it
The instinct is to start with a wall-to-wall physical inventory. Sometimes that is necessary, but starting there is expensive and it fixes a symptom while the mechanism that caused it stays in place. A better sequence:
- Name an owner. Not a committee. One person accountable for the integrity of the register, with the standing to ask other departments for information.
- Fix the inbound path first. If new assets are still arriving with bad data, cleanup is a treadmill. Get acquisition, componentization, and in-service dating right for everything going forward.
- Build a disposal trigger. The single highest-value control in fixed assets. When equipment leaves — replaced, sold, scrapped, or moved out with a closed site — something has to reach the register automatically. Retirements almost never fail because people refuse; they fail because no path exists.
- Clean by materiality, not alphabetically. Target the balances and classes where error carries the most consequence. Perfection across the whole register is not the goal; defensibility is.
- Make it a standing rhythm. A quarterly review with tax, operations, and facilities in the same conversation. Most of the web reconnects on its own once those people talk regularly.
Why this is worth doing before you are forced to
Fixed asset problems surface at the worst possible moments: mid-audit, mid-acquisition, mid-implementation. At those moments the cost is not just remediation, it is credibility and leverage. Cleaning up during due diligence is a materially worse position than arriving with a register that already holds up.
The spider in the middle of the web is not a threat. It is the thing that has been holding the structure together while nobody was looking. It deserves an owner.