We use cookies to understand which pages and tools are useful, nothing more — no ad tracking across other sites. You can change this later from the footer.

Skip to content
Lekhya.in

Explainer4 min readPublished

The fixed asset register CARO reporting couldn't rely on

An illustrative, composite walkthrough of a fixed asset register that didn't tie to the ledger, what that meant for CARO's fixed asset clause, and how it was rebuilt.

This is a composite, illustrative scenario built from how a fixed asset register reliability gap typically surfaces during CARO fieldwork, not an account of a named client. The company's fixed asset register recorded a location for every asset, but a sample physical verification found a majority of sampled items in a different location than the register stated — the register had not been updated through two office relocations and a warehouse move over three years. CARO's fixed asset clause requires reporting on whether the company maintains proper records showing full particulars including location, and a register this far out of step with physical reality could not support an unqualified answer to that question without first being brought current.

Why this mattered for CARO specifically, not just the balance sheet

Regulatory requirement

CARO's fixed asset clause asks a specific, narrower question than “do the fixed assets exist and are they correctly valued.” It asks whether proper records are maintained showing full particulars, including quantitative details and location, and whether a reasonable physical verification programme exists. A register that is accurate on cost and depreciation but wrong on location still fails this specific reporting requirement.

What the verification found

  1. 01Sampled assets across all three recorded locationsRoughly 60% of sampled items were physically found at a different location than the register stated — not missing, just relocated without the register being updated.
  2. 02Checked whether any assets were genuinely missing, not just mislocatedTwo items could not be physically traced to any location, which is a separate and more serious finding than a location error.
  3. 03Asked when the register was last fully updatedNot since the register was originally set up, three years and two office moves earlier — individual asset additions had been recorded, but existing assets' locations were never revised when they physically moved.
  4. 04Checked whether a verification programme existed at allNo periodic physical verification cycle existed — this was the first full count the company had done since the register was created.

What it took to make the register reportable on

What was rebuilt, and by whom
StepResponsibility
Full physical verification of every asset, not a sampleClient, with the audit team observing a sample of the recount for evidence
Updated location field for every relocated assetClient's finance/admin team
Investigation of the two untraceable itemsClient, with a written-off or found outcome recorded either way
Establishing a periodic verification cycle going forwardClient, as a control recommendation, since a one-time catch-up doesn't satisfy a “reasonable programme” requirement on an ongoing basis
What was rebuilt, and by whom

What the CARO report actually said

Once the register was rebuilt and the two untraceable items were resolved — one found during the full recount, one genuinely written off as scrapped without the disposal having been recorded — the clause could be answered on the corrected position. The report noted that discrepancies had been identified on physical verification and were properly dealt with in the books, which is itself a standard and expected form of disclosure under the clause, not an adverse finding in itself. What would have been a problem is reporting a clean answer against a register the team knew did not reflect reality.

What went into the file

  • The original sample verification results, showing the location discrepancy rate before any correction.
  • The client's full recount and updated register, used as the basis for the final CARO response.
  • The resolution of both untraceable items, with evidence for each.
  • A management letter point on establishing a periodic verification cycle, distinct from the one-time catch-up exercise.
  • The CARO working paper explicitly linking the clause's requirements to what was tested, not just a conclusion.

How we think about this

A fixed asset register can be correct on cost and depreciation and still fail CARO's specific requirement if location data has silently drifted from reality — which is why a sample physical verification against the register's stated location, not merely confirming the asset exists somewhere, is the test that actually answers the clause.

This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.

Free tools, no signup

Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.