Most fixed asset audit observations do not come from complicated accounting questions. They come from a small number of avoidable gaps in how the physical verification was planned, carried out and documented — gaps the auditor finds at year end, when there is no time left to correct them.
Under CARO 2020, the statutory auditor reports on whether the company maintains proper records of Property, Plant and Equipment (clause 3(i)(a)(A)) and whether management has physically verified those assets at reasonable intervals, along with how material discrepancies were dealt with in the books (clause 3(i)(b)). The obligation to verify sits with management; the obligation to report on it sits with the auditor. Where the verification is thin, undocumented or inconsistent with the register, that is what the audit report ends up describing.
Below are ten mistakes that commonly appear in fixed asset verification exercises in India, what each one looks like from the auditor’s side, and what to do instead. For the underlying process, see our complete guide to fixed asset verification.
1. Relying on the register instead of walking the floor
What happens: the finance team reconciles the Fixed Asset Register against purchase records and depreciation schedules, and treats that as verification. No one physically locates the assets.
Why the auditor notices: a register reconciled only against itself provides no evidence of existence. Under SA 500, the auditor is looking for sufficient appropriate audit evidence about assets that are recorded, and a desk reconciliation does not supply it.
What to do instead: carry out a physical verification against a frozen register as on a defined cut-off date, recording who verified each asset and when.
2. Verifying in one direction only
What happens: the team starts from the register and ticks off assets as it finds them. Anything not on the list is never looked at.
Why the auditor notices: this tests existence but not completeness. Assets bought on project budgets, received as replacements under warranty, or transferred between units and never capitalised will not surface, because nothing prompts anyone to look for them.
What to do instead: run both directions. Sheet-to-floor starts from the register and finds ghost assets. Floor-to-sheet starts from the physical asset and finds unrecorded ones. The two answer different questions and neither replaces the other — the distinction is set out in floor-to-sheet vs sheet-to-floor.
3. Verifying against a register that was never cleaned
What happens: the register carries duplicates, grouped lines such as “computers — 50 nos.”, generic descriptions like “machinery — various”, and location codes that no longer match any physical area.
Why the auditor notices: where a single register line cannot be traced to a single identifiable asset, the verification cannot conclude anything about that line. Grouped entries are among the most common reasons a count is inconclusive rather than adverse.
What to do instead: sanitise the register before the field team mobilises — split grouped entries, flag duplicates, map location codes to real floors and departments. See pre-verification FAR data cleanup and asset data standardisation.
4. Assets that carry no identification
What happens: rows of near-identical chairs, monitors or motors with nothing to distinguish one from another, matched to register lines by description alone.
Why the auditor notices: without unique identification, the same asset can be counted twice, or matched to the wrong register entry, and neither error is detectable afterwards. The count may be complete and still be wrong.
What to do instead: tag assets during the verification itself, so the exercise becomes the baseline for every later cycle. Asset tagging with barcode, QR or RFID gives each asset a unique link back to its register line.
5. Stopping at the count and never reconciling
What happens: fieldwork finishes, a verified list is produced, and the exercise ends there. The differences are noted but never investigated or posted.
Why the auditor notices: clause 3(i)(b) asks specifically whether material discrepancies were properly dealt with in the books. A discrepancy that was identified and left open is arguably worse than one never found, because the company now has documented knowledge of it.
What to do instead: treat reconciliation as part of the same exercise, not a later project. Each exception is classified, investigated, and cleared with approval and an audit trail. The mechanics are covered in the FAR reconciliation process.
6. No location or custodian mapping
What happens: assets are confirmed to exist somewhere in the company, but the register still shows the location they were bought for rather than where they now sit, and no individual is recorded as responsible.
Why the auditor notices: location drift is what makes the following year’s verification harder, and unassigned custody is a weak point in the internal financial controls reported on under section 143(3)(i) of the Companies Act, 2013.
What to do instead: capture location and custodian as verification fields, and maintain an asset movement register so transfers update the FAR as they happen.
7. Disposed and scrapped assets still in the books
What happens: assets sold, scrapped or written off years ago remain in the gross block and continue to attract depreciation.
Why the auditor notices: this overstates gross block and misstates the depreciation charge. Under AS 10 and Ind AS 16, an asset is derecognised on disposal or when no future economic benefits are expected — not when someone remembers to raise the entry.
What to do instead: run a disposal review alongside the verification, with scrap and obsolescence identified as a distinct exception class rather than folded into “not found”.
8. Thin or missing documentation
What happens: the verification was done, but the evidence is a signed summary sheet and little else — no photographs, no verifier names, no date-stamped records, no location sheets.
Why the auditor notices: under SA 330, the auditor designs procedures responsive to assessed risk, and the quality of management’s own evidence affects how much further work is needed. Where documentation is thin, the auditor does more testing, and the observation often follows anyway.
What to do instead: retain photographs, verifier identity, date and location for each asset, and keep the exception report with its resolution trail. Our fixed asset verification checklist sets out what to keep at each stage.
9. No policy on what gets verified, and how often
What happens: verification happens when the auditor asks, at whatever scope the team can manage that year, with no written basis.
Why the auditor notices: “reasonable intervals” is not defined in CARO 2020, which makes it a matter of management judgement — and a judgement with nothing written behind it is difficult to defend. A documented policy converts the question into a stated position the auditor can assess.
What to do instead: write the frequency into the fixed asset policy and apply it consistently. Movable, high-turnover assets such as IT equipment are commonly verified annually. Plant and machinery at fixed installations is often covered once in two to three years, or on a rolling cycle across locations. These are prevailing practices rather than statutory requirements, and they should be agreed with the statutory auditors.
10. No defined treatment for non-taggable and low-value items
What happens: light fittings, CCTV cameras, cabling, small fixtures and consumable-grade items are either ignored or handled differently at each location.
Why the auditor notices: inconsistent treatment across locations makes the coverage of the exercise unclear. The auditor cannot tell whether an absence means the asset was excluded or was not found.
What to do instead: define taggable, countable and excluded categories in advance, state the value threshold, and record the exclusions in the report. An exclusion that is documented is a scope decision; an exclusion that is not is a gap.
What separates a clean verification from a qualified one
The pattern across all ten is the same. The verification that survives audit scrutiny is the one that was planned before it started — a frozen register, a defined scope, both counting directions, identification on the assets, and evidence retained as the work happens rather than assembled afterwards.
Timing matters as well. Fixed asset verification runs during working hours, since fixed assets do not move with the shift. Once the findings are agreed with the client, the reconciled register follows within about a week. The delay that actually shows up in practice sits on the other side: assets recorded but not located are searched for thoroughly before anyone will write them off the balance sheet, and that search can run a month or more. Building it into the audit timetable is more useful than compressing the fieldwork.
Frequently asked questions
What causes an audit qualification on fixed assets?
Commonly, an absence of physical verification, a register that cannot be traced to identifiable assets, or discrepancies that were identified but never resolved in the books.
Is asset tagging required by law?
No. CARO 2020 requires proper records of Property, Plant and Equipment and physical verification at reasonable intervals; it does not prescribe tagging. Tagging is a practical means of meeting the identification requirement, not a statutory obligation in itself.
How often should fixed assets be verified?
There is no statutory frequency. Movable assets are commonly verified annually and fixed plant less often, sometimes on a rolling cycle. The chosen frequency should be documented in the fixed asset policy.
Can the verification be done in a spreadsheet?
It can, and for a single location it often is. The constraint is transcription: data typed twice is data that can differ, and evidence such as photographs and timestamps has to be attached separately.
What is the difference between verification and reconciliation?
Verification establishes what physically exists and produces the exception report. Reconciliation investigates each exception and corrects the register with approvals. Verification without reconciliation leaves the books unchanged.
TagMyAssets carries out fixed asset verification, asset tagging and FAR reconciliation across India, with 395+ projects, 1,500+ locations and over 10 lakh assets covered to date. To discuss scope for your locations, write to connect@tagmyassets.com or call +91 96500 03293.
