Fixed-asset accounting: what each role knows and where the gaps hurt

The accountant knows the ledger but not the floor. Site staff know where assets sit and what state they are in, but rarely tell anyone when something moves or dies. Engineers know what a repair really did. Tax knows the rules. Trouble starts where these meet without talking.

Who holds which piece

The fixed-asset accountant owns the register. They know cost, useful life, depreciation method and which general ledger account each asset rolls into. They usually do not know whether the asset still exists.

Site managers and asset custodians know that. They know which machine was cannibalised for parts, which laptop went home with a leaver and never came back, which forklift was lent to another plant. To them this is daily life, not accounting news.

Maintenance and engineering teams know what work was done on an asset. A new motor might extend a press's life by years. A coat of paint does nothing for it. The invoice often looks the same either way.

Procurement and payables see the purchase first. They know the supplier, the price and the delivery address. They tend not to know whether the item is capital or expense, and the coding on the purchase order is often a guess made under pressure.

Project managers running construction or large installations know when an asset is actually ready for use. Finance only learns this if someone remembers to say so.

The tax team knows the allowance rules, which differ from book depreciation and change over time. They depend on the register for their figures but often keep a parallel spreadsheet because they do not trust it.

Where the gaps cause trouble

Ghost assets are the most common symptom. Equipment is scrapped, sold or lost on site, nobody raises a disposal form, and the register keeps depreciating something that is gone. The gain or loss on disposal never gets recorded. Insurance and property tax may be paid on it too.

The opposite also happens. Items arrive, get coded to an expense line by a busy buyer, and never reach the register. Later a physical count finds tagged equipment with no record.

Repair versus enhancement is a judgement that sits with the wrong person. Accountants decide classification from an invoice description. Engineers know the answer but are not asked. The result is capitalised maintenance in some places and expensed upgrades in others, with no consistency between sites.

Construction in progress lingers. Projects go live, the plant runs for months, and the balance still sits unallocated because no one told finance the in-service date. Depreciation starts late and then has to be caught up at period end, which distorts results.

Transfers between cost centres or legal entities move physically long before they move on paper. One site's budget carries the depreciation for a machine another site is using. Managers argue about it at review meetings without realising the cause.

Book and tax registers drift apart quietly. Each fix made in one is not made in the other. By the time a return is prepared, reconciling them becomes its own project.

Why physical counts expose everything at once

A count is the one moment when the custodian's knowledge and the accountant's records are laid side by side. Missing tags, wrong locations, unrecorded disposals and phantom additions all surface together. Teams often treat the count as an audit exercise to survive. It is better used as evidence of which handoffs are broken, since the pattern of exceptions points straight at them.

Questions to ask the people who run it

What is documented and what is done tend to differ here more than in most finance processes. Ask directly:

• When a machine is scrapped on site, who finds out, and how?
• Who decides whether an invoice is capital or expense, and what do they look at?
• How does finance learn that a project has gone into service?
• Is there a capitalisation threshold, and do buyers actually know it?
• When equipment moves between sites, what paperwork follows it, if any?
• Does the tax team keep its own register? Why?
• What happened to the exceptions from the last physical count?
• Which assets does nobody want to be responsible for?
• Are leased items and software treated by the same people as owned hardware?
• When the register and the general ledger disagree, who fixes it and where?

The answers to the last few usually reveal more than the first few. People are candid about orphaned assets once asked.

Where to put effort when changing the process

Most fixes are about routing information, not about accounting. A disposal trigger built into the site's own workflow catches more than a policy reminder sent from head office. Asking engineering to tick a box on large maintenance invoices does more for classification than any new accounting rule.

Tie the in-service date to something project teams already do, such as a handover sign-off, so finance does not depend on memory.

Keep book and tax adjustments flowing from one source. Where two registers must exist, reconcile them on a fixed cycle so differences stay small and explainable.

Finally, give custodians a reason to care. If their budget carries depreciation for assets they no longer have, they will report disposals quickly once they see it.

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.