CARO 2020 Fixed Asset Disclosure: What Auditors Actually Check
Every statutory auditor of an Indian company covered by CARO 2020 must answer a blunt question in their report: has this company physically verified its fixed assets at reasonable intervals, and were material discrepancies dealt with properly? Clause 3(i) doesn't ask whether you have an asset register — it asks whether the register matches reality, and whether you can prove it.
The three sub-clauses that matter
Clause 3(i)(a) — whether the company maintains proper records showing full particulars, including quantitative details and situation of Property, Plant & Equipment. "Situation" means location — an asset register without location data fails this test on its face.
Clause 3(i)(b) — whether fixed assets were physically verified by management at reasonable intervals, and whether material discrepancies were properly dealt with in the books. Note who carries the obligation: management, not the auditor. The auditor's job is to evaluate your verification programme, not run one for you.
Clause 3(i)(c) — whether title deeds of immovable properties are held in the company's name. Separate issue, same clause family.
What "reasonable intervals" means in practice
CARO doesn't define a fixed frequency — but audit practice has converged on a working standard: every asset verified at least once every three years, with high-value or movable assets verified more often. A company that last physically verified its assets four or five years ago will struggle to defend "reasonable intervals," and the auditor's report will say so — in writing, for every lender and investor to read.
The evidence auditors ask for
- The verification plan — which locations, which asset classes, what schedule
- Field evidence — scans, photos, tag IDs, verifier identity, timestamps
- The reconciliation — assets found vs. register, with each discrepancy classified: missing, misplaced, untagged, or ghost
- Board-level treatment — how material discrepancies were adjusted in the books, and who approved it
A signed Excel sheet saying "verification done" satisfies none of this. What auditors increasingly expect is a system-generated trail: who scanned what, where, when — and what happened to every exception.
Ghost assets: the finding that hurts
The most common material discrepancy is the ghost asset — an item on the register that no longer physically exists. Ghost assets overstate the balance sheet, inflate depreciation and insurance, and signal weak controls. Industry experience puts ghost assets at a meaningful share of registers that haven't been physically verified in years — which is exactly why clause 3(i)(b) exists.
Being ready before they ask
Companies that pass clause 3(i) cleanly share a pattern: verification is a standing programme, not a pre-audit scramble. That means a maintained register with locations and custodians (asset management that updates as assets move), a scheduled physical verification cycle with mobile scanning and photo evidence, and a reconciliation report the auditor can test rather than take on faith.
This is the discipline our VTR (Verify · Tag · Reconcile) methodology productises: field teams scan on-site, the system reconciles against the live register, discrepancies are flagged and resolved with an audit trail, and the output is a signed verification report built for clause 3(i) evidence.
The takeaway
CARO 2020 turned physical verification from good housekeeping into a disclosed, reportable audit item. The question isn't whether your auditor will ask — it's whether your answer will be a system-generated evidence pack or an apology. If your last full verification is more than three years old, start there.