Fixed-asset subledgers rarely fail loudly. They drift — a disposal here that was never booked, a machine moved between plants without a transfer, a scrapped unit still depreciating on the books. Nobody notices until a year-end close won’t tie, or an auditor asks to see the asset behind a line and it isn’t there. This is a controller’s field guide to why registers drift, why it always surfaces at audit, and the remediation playbook that fixes it for good.
How a fixed-asset subledger drifts from reality
Drift is cumulative and quiet. It happens because physical change on the floor outpaces the bookkeeping behind it. Four vectors do most of the damage:
- Unbooked disposals and retirements. Equipment is scrapped, sold, or replaced, but the retirement journal entry is never made — so the asset keeps depreciating and stays on the books. See our asset write-off & retirement guide and fixed-asset disposal guide for the entries this leaves undone.
- Unrecorded transfers and relocations. Assets move between locations, cost centers, or legal entities without a transfer record, so the register’s location and ownership fields go stale.
- Ghost assets. The accumulated result — line items for equipment that no longer physically exists. They overstate asset value and depreciation and distort property tax and insurance. See ghost asset detection.
- CIP left in limbo. Construction-in-progress is placed in service but never capitalized and reclassified, so depreciation never starts and the balance sits unmoved.
Individually, each is a small omission. Compounded over a few reporting periods — often across a leadership change or an ERP migration — they produce a subledger that no longer reflects what is on the floor, and no longer ties to the general ledger.
Why drift always surfaces at audit
A drifted register is invisible in day-to-day operations but unavoidable at audit, because the two assertions auditors care most about for property, plant & equipment are precisely the two that drift breaks:
- Existence. Does the asset behind each line still physically exist? Ghost assets fail this test directly. See our piece on the PP&E existence assertion.
- Completeness and accuracy of the roll-forward. Auditors reconcile the opening balance, additions, disposals, and depreciation to the closing balance. Unbooked disposals and stalled CIP make the fixed-asset roll-forward fail to foot.
The trigger is usually a hard deadline: a financial statement audit, a fixed-asset audit, an ERP cutover, or a transaction that puts the balance sheet under a microscope. By then the drift is years deep and the finance team is trying to remediate it in the same window they are trying to close.
The three-layer fix — and why most firms only do one
Here is the thesis, and it is where most remediation efforts go wrong: a drifted register is a physical problem, an accounting problem, and a systems problem at the same time. Fixing one layer and not the others leaves the register wrong. Durable remediation needs all three:
- Floor (physical). An independent physical verification establishes what actually exists — floor-to-book to catch ghost assets, book-to-floor to catch unrecorded additions. Without it you are reconciling assumptions, not reality.
- Book (accounting). The disposal and write-off journal entries, with the correct gain or loss, and the reconciliation of the corrected subledger to the general ledger. See how to reconcile fixed assets.
- System (ERP). The retirements and reclassifications actually posted in the asset module — not just proposed in a spreadsheet. See our guide to EAM/ERP fixed-asset reconciliation and SAP asset management integration.
A physical-inventory vendor typically stops after the floor. An accounting firm typically stays in the book. Neither, alone, leaves you with a register that is verified, corrected, and posted. That gap is exactly why drift recurs after a “cleanup.”
The controller’s remediation playbook
A remediation that holds runs in sequence, each step feeding the next:
- 1. Scope & freeze. Define the population, the cutoff, and the target close/audit date; freeze new activity where practical.
- 2. Verify on the floor. Independent physical verification, tagging each item and flagging found / not-found / wrong-location / wrong-condition.
- 3. Identify disposals & retirements. Every not-found and scrapped item becomes a documented disposal candidate.
- 4. Prepare the entries. Disposal and write-off journal entries with the correct accumulated depreciation reversal and gain/loss.
- 5. Reconcile to the GL. Tie the corrected subledger to the general ledger and resolve the variance.
- 6. Post in the ERP. Retirements, transfers, and CIP reclassifications posted in the asset module — ideally as a controlled bulk upload.
- 7. Produce the roll-forward. A clean opening-to-closing schedule that foots, plus the tagged, evidence-backed register your auditors will test.
The deliverable that matters: not a spreadsheet of proposed changes, but an evidence-backed register that ties to the GL, is reflected in the ERP, and comes with the physical verification and roll-forward an auditor can test without a single “where is this asset?”
Where CPCON fits — and the honest boundary
CPCON runs all three layers as one engagement: independent physical verification and tagging on the floor, the disposal and reconciliation entries in the book, and support for the retirement postings and roll-forward in the ERP. We bring audit and controller experience to the accounting treatment and 25+ years of physical verification across 2,500+ organizations to the floor — which is why our remediations tie out and stay tied. Explore our fixed-asset inventory and count & tagging services.
The honest boundary: CPCON is not your auditor and does not provide audit opinions or legal advice. Final accounting treatment rests with your finance leadership and your auditors; this article is general guidance, not accounting or legal advice. What we provide is the verified, corrected, posted evidence base that makes the audit straightforward.
Frequently asked questions
Why does a fixed-asset subledger drift out of sync with reality?
Because change happens on the floor faster than it is recorded. Assets are disposed, scrapped, or retired without a journal entry; equipment moves without a transfer record; items are lost or damaged and never written off; and CIP is placed in service but never capitalized. Over a few years those unrecorded events accumulate into ghost assets and a register that no longer ties to the GL or the ERP.
What are ghost assets?
Line items on the register for equipment that no longer physically exists — disposed, scrapped, or replaced, but never removed from the books. They overstate asset value and depreciation, distort property tax and insurance, and are a leading existence-assertion finding at audit.
How do you remediate a fixed-asset register before an audit?
Scope and freeze the population, verify it physically floor-to-book and book-to-floor, identify every disposal and retirement, prepare the write-off entries with the correct gain or loss, reconcile the corrected subledger to the GL, post the retirements in the ERP, and produce a clean roll-forward — an evidence-backed register that ties out and stands up to testing.
Why isn't a physical count alone, or accounting cleanup alone, enough?
A count tells you what exists but leaves the books wrong. Accounting cleanup fixes the ledger against assumptions, not verified reality. Durable remediation requires all three layers — floor, book, and system — which is why single-layer “cleanups” drift again.
Does CPCON audit or certify the register?
No. CPCON is not your auditor and does not issue audit opinions or legal advice. We perform the physical verification, prepare the disposal and reconciliation entries, and support the ERP postings and roll-forward that make the register audit-ready — the evidence your auditors then test. Confirm accounting treatment with your own finance leadership and auditors.
Stop the drift — remediate the register once, properly
CPCON remediates drifted fixed-asset registers end to end — independent physical verification and tagging, the disposal and reconciliation entries, and the ERP postings and roll-forward that make it audit-ready. Floor, book, and system in one engagement, with 25+ years of asset verification and audit-grade discipline — without ever acting as your auditor.
Talk to CPCON about register remediation
