Most companies believe their Fixed Asset Register is accurate because it is maintained in Excel or in an ERP. A register is not correct until it has been physically verified — and until then, the errors sit there quietly.
A Fixed Asset Register is wrong in predictable ways, and the same five patterns turn up on almost every first verification. This page describes them, what each one does to the financial statements, and how they get fixed.
How Companies Find Out Their FAR Is Wrong
Almost nobody discovers it by reading the register. It surfaces when something forces a comparison with reality:
- A statutory or internal audit asks for verification evidence
- An ERP implementation needs a clean asset master
- An office or plant relocates
- A merger or acquisition triggers due diligence
- An insurance claim requires proof an asset existed at a location
- Someone asks a simple question — how many laptops do we actually have?
The larger the organisation and the longer since the last verification, the wider the gap tends to be.
The Five Ways a Fixed Asset Register Is Wrong
1. Ghost assets — recorded in books, absent on site
The asset appears in the FAR. Nobody can find it. It was scrapped, stolen, cannibalised for parts, or written off in practice but never in the books.
What it does: depreciation continues against equipment that no longer exists, the asset base is overstated, and the auditor has an observation the company cannot answer.
On one multi-location manufacturing engagement, client anonymised, the register carried 19,134 assets. Physical verification located and verified 10,112. The balance, together with other exceptions, was reported to management with a variance of over ₹10.5 lakh identified for action.
2. Unrecorded assets — present on site, absent from books
The reverse case. Equipment is physically there and working, but no line in the register corresponds to it. Usually something bought and expensed rather than capitalised, received against a purchase order that was never completed, or transferred in from another location without paperwork.
What it does: the asset base is understated, the asset is uninsured because it appears on no schedule, and nobody owns it.
3. Duplicates — the same asset recorded twice
“Laptop Dell i5 8GB” and “Dell Laptop i5” are one machine and two register lines. It happens through duplicate serial entry, inconsistent descriptions, or an asset being moved and re-entered at the new location instead of updated.
What it does: inflated asset base, depreciation charged twice on one item, and a reconciliation that can never balance because the physical count will always be lower than the book count.
4. Location mismatch — the asset exists, in the wrong place
The most common finding in corporate offices. Finance asks to see the laptop assigned to HR. IT says it moved to Operations three months ago. Admin says a new joiner has it now.
What it does: nobody can evidence where the asset is, custodial responsibility is unclear, and the location field in the register — which CARO 2020 specifically asks about — is unreliable across the board.
5. Condition mismatch — scrapped or replaced, still active in books
A printer was replaced last year. The new one was capitalised. The old one is still in the register, still depreciating, still shown as in use.
What it does: wrong book value, wrong utilisation reporting, and capital decisions taken against an asset list that includes equipment nobody can use.
What a Wrong Register Affects
An inaccurate FAR is not only an asset-tracking problem. It reaches:
- Depreciation calculations and the net block
- Capitalisation decisions
- Fixed asset schedules and audit documentation
- Insurance schedules, which are usually built from the register
- Internal financial controls
When the errors sit in the books for years, management decisions get taken on the basis of them.
Why Tagging Alone Does Not Fix It
Plenty of companies have tagged their assets. Stickers were printed, pasted, scanned into a spreadsheet, and the exercise was closed. The register is still wrong, because a tag on its own records nothing about whether the asset matched its register line.
What makes verification usable as audit evidence is what gets captured alongside the scan:
- A unique identifier physically fixed to the asset
- A photograph of the asset in position
- Serial, make and model where the asset carries them
- Floor, department or plant location
- Condition and usage status
- Who verified it and when
- An exception list — not found, inaccessible, pending — with reasons
The exception list matters as much as the matches. An auditor working to SA 500 on audit evidence wants to see what could not be verified and why, not just a count of what could.
Where CARO 2020 Fits
The Companies (Auditor’s Report) Order, 2020 places the reporting duty on the auditor, not on the company:
- Clause 3(i)(a)(A) — whether proper records are maintained showing full particulars, including quantitative details and situation, of Property, Plant and Equipment. “Situation” means location, which is why a location mismatch is a records problem and not an administrative one.
- Clause 3(i)(b) — whether PPE has been physically verified by management at reasonable intervals, whether the interval is reasonable, and whether material discrepancies were noticed and properly dealt with in the books.
The verification itself is management’s responsibility. The auditor reports on whether it was done and whether the differences were handled.
What We Commonly Find
Across verification engagements, the recurring findings are:
- Assets present on site and absent from the FAR
- Assets in the FAR that cannot be located
- Duplicate records for one asset
- Wrong locations
- Scrapped assets still depreciating
- Missing serial numbers and unusable descriptions
- Assets transferred between locations without documentation
How to Fix a Wrong Fixed Asset Register
- Clean the register first. Lines reading “furniture — miscellaneous” against a single value cannot be verified individually. Restructuring comes before anyone walks the floor.
- Tag what can be tagged. Not every register line corresponds to a physically taggable asset.
- Verify physically. Scan, photograph, record condition and location, against the register.
- Reconcile. Classify every line: matched, corrected, recorded-not-found, found-not-recorded.
- Act on the exceptions. Write off what is gone, capitalise what was missed, correct the locations.
- Repeat on a defined cycle so the register stays defensible rather than drifting again.
Where an ERP migration is planned, this sequence belongs before it. An ERP stores what it is given — migrating a wrong register produces a wrong register in a new system.
What We Do
We tag and physically verify fixed assets across plants, offices, warehouses and branch networks, and reconcile the findings against your register. We have completed 395+ projects across 1,500+ locations in India, covering 10 lakh+ assets tagged.
Frequently Asked Questions
Why is my Fixed Asset Register wrong?
Because it has been updated in a system but not compared against the assets themselves. Assets move, get scrapped and get replaced faster than the paperwork follows, and the gap only becomes visible when someone physically verifies.
What is a ghost asset?
An asset recorded in the Fixed Asset Register that cannot be located during physical verification. It is still carrying depreciation against equipment that is not there.
Why is a spreadsheet not enough?
A spreadsheet records what someone entered. It carries no photograph, no timestamp, no record of who verified the asset or where it was found. Those are the things an auditor asks for when testing existence.
Does asset tagging help with insurance documentation?
A verified register with photographs, locations and tag references gives the insurer better documentation than a spreadsheet line. Whether a claim is accepted is the insurer’s decision, on the policy terms.
How often should verification be done?
CARO 2020 asks whether the interval is reasonable without prescribing one. Annual is common; some companies run a rolling cycle covering every asset across two or three years with high-value assets seen annually. Relocations, expansions and mergers are worth verifying around regardless of the cycle.
Can an ERP correct FAR errors on its own?
No. An ERP stores the asset data it is given. If incomplete or duplicated records are migrated, the same errors continue in the new system. Verification and reconciliation should be completed before migration.
