Where fixed-asset accounting breaks: handoffs, exceptions and workarounds

Fixed-asset accounting usually breaks where information has to cross between teams. Spend gets coded at the invoice, projects finish without anyone saying so, and equipment leaves a site quietly. Most rework traces back to a late or missing signal. The depreciation arithmetic itself is rarely the cause.

Capitalization decided at the invoice

The first real decision about an asset is often made by whoever codes a supplier invoice in payables. That person may not know the capitalization threshold. They may not know that installation, freight and setup belong in the asset's cost. Something capital ends up in expense, or a pile of small purchases lands in the register as separate assets that should have been grouped.

The evidence shows up later. Large balances sit in repairs or supplies accounts. Fixed-asset staff reclassify entries at period close. The register fills with low-value items that nobody can find.

Construction in progress that never closes

Project costs collect in a work-in-progress account while something is built or installed. The handoff that matters is the moment it goes into use. Operations knows. Finance often does not. Depreciation starts late, and catch-up entries follow.

Watch for project balances that keep growing after the project manager has moved on. Another warning is a building or system in daily use that still has no asset record.

Disposals and transfers nobody reports

Assets get scrapped, sold, traded in or moved to another site. A form is supposed to reach finance. Often it does not, because the person removing the equipment sees no reason to tell accounting. Ghost assets keep depreciating. Transferred items stay charged to the wrong cost centre or legal entity.

Departments disputing depreciation charges are one clue. Sales proceeds booked to miscellaneous income with no matching retirement are another.

Repairs passed off as enhancements, and the reverse

The line between maintenance and an enhancement that extends useful life is a judgement call. Budget pressure bends that judgement. A team short on operating budget may push for capitalization. A team protecting its capital budget may expense a genuine upgrade.

This tends to surface as inconsistent treatment of similar work across sites, along with auditors asking for support on individual additions.

Thin master data

An asset record needs a class, a useful life, an in-service date, a location and a responsible owner. When additions are rushed through at close, those fields get default values or stay blank. Every downstream step inherits the gap, from depreciation to tax reporting.

Sort the register by location or owner and look at the blanks. Defaulted lives that do not fit the asset class are just as telling.

Depreciation run against a moving ledger

Depreciation is calculated on whatever the register holds when the run happens. If additions, disposals or adjustments arrive after the run, someone reruns it, posts a manual true-up, or leaves the difference for next period. Each choice creates its own reconciliation problem.

Repeated reruns, manual depreciation journals and prior-period corrections in the close checklist all point here.

Subledger and general ledger drifting apart

The asset register and the general ledger should agree by account. They drift when journals hit asset accounts directly instead of flowing from the subledger. Revaluations and impairments posted on the ledger side only cause the same drift.

A reconciliation that carries the same unexplained items forward period after period is the clearest sign. So is a spreadsheet bridge that only one person understands.

Physical counts that cannot be matched

Counts fail when tags have fallen off, when locations in the register are out of date, or when the count team and the accountants use different identifiers. Found items with no record and recorded items that cannot be found then sit unresolved, because nobody owns the follow-up.

Ask whether the last count produced adjustments. If it did not, the count may not have been tied back to the register at all.

Tax and statutory books kept on the side

Tax depreciation and local statutory reporting often use different lives and methods. When those books live in separate spreadsheets, every addition and disposal has to be entered again by hand. Differences pile up quietly until a return or a statutory filing forces someone to explain them.

Tax staff rebuilding asset lists at filing time is a strong indicator of this problem.

Questions to ask the people who run it

Written procedures describe the intended flow. These questions uncover what really happens:

• Who decides whether an invoice is capital, and what do they look at when deciding?
• How does finance learn that a project has finished and the asset is in use?
• When equipment is scrapped or moved, who tells accounting, and what happens if nobody does?
• What entries get posted directly to asset accounts outside the register, and why?
• How often is depreciation rerun or corrected by hand?
• Which reconciling items have been carried forward the longest, and who owns them?
• What did the last physical count find, and were those findings booked?
• Where do tax and statutory figures come from, and who keeps them in step with the register?
• Which spreadsheets would stop the close if their owner were absent?
• What do people do at close that appears in no procedure?

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.