Talk to an Expert
Talk to an Expert ✆ +91 945 945 6700
Stock Audit · 6 min read · Aug 19, 2026

Fixed Asset Verification Checklist: What an Auditor Physically Inspects

CA Sundram Gupta

Fixed Asset Verification Checklist: What an Auditor Physically Inspects - Featured Image
In this guide

    What an Auditor Physically Inspects

    An auditor inspecting fixed assets is establishing four things at each line selected: that the asset exists, what condition it is in, where it actually stands, and who is answerable for it. Existence is the first assertion and the one everything else depends on, so the walk starts from the register and ends at the asset rather than the other way round. Condition matters because an asset that exists but cannot run is still carrying a written down value that assumes it can. Location and custodian matter because an asset nobody is answerable for is the one that goes missing next. Identification is tested alongside all four: whether a tag exists, whether it is readable, and whether the number on it is the number in the register. The work then runs in the opposite direction as well, selecting assets on the floor and tracing them back, which is how uncapitalised equipment surfaces.

    Before the Visit: Register Readiness

    Most of the friction in a verification is created by a register that was not ready, and three things make the difference. Populated fields come first. Every line needs an identifier, a description specific enough to match, a location at a level somebody can walk to, and a custodian. Lines missing any of those cannot be verified, only searched for, and a register with a substantial proportion of incomplete lines converts a counting exercise into a research exercise at counting rates. Location and custodian currency is the second. Fields that were correct at some point in the past are worse than empty ones, because a team sent to the wrong place records an asset as not found and somebody has to investigate a difference that never existed. A quick internal review of locations before the visit removes a large share of the exceptions the visit would otherwise generate. Recent additions and disposals posted is the third. Assets acquired since the last close and not yet capitalised will be found on the floor with no register line; assets disposed of and not yet removed will be looked for and not found. Both are avoidable by closing the register to the cut-off before anybody travels.

    On the Floor: What Gets Checked Item by Item

    For each line selected, the work is a short fixed sequence rather than a general inspection. Tag legibility and match to the register line is first: the label exists, it can be read, and the number on it is the number in the register. Any of those failing is recorded as its own exception type, because an unreadable tag and a wrong tag are different problems with different remedies. Condition and whether the asset is in use follows, and the second half matters as much as the first. An asset in good condition but idle for two years is carrying a value that assumes it generates something, and idleness is an indication that impairment should be tested. Condition is recorded against a defined scale rather than as free text, so the results can be aggregated afterwards. Assets present but not capitalised are captured as the team walks, which requires the walk to run floor-to-register as well as register-to-floor. Anything on the floor with no tag and no obvious line is recorded with its description, serial number, location and a photograph, and investigated afterwards against purchase and repairs records, where most of them are found.

    Capital Work-in-Progress and Assets Not Yet in Use

    Capital work-in-progress is verified differently from completed assets because there is frequently nothing discrete to point at. Stage of completion is compared against the amount capitalised: what has physically been built, delivered or installed, set against what has been accumulated in the account. A balance that has grown while nothing visible has changed on site is the finding this test exists to produce, and it usually resolves into advances paid, costs booked to the wrong project, or a project that stalled without anybody closing it. Items complete but never transferred out are the second and most common exception. An asset that is finished and in use but still sitting in capital work-in-progress has escaped depreciation entirely, which overstates profit for every period since it became available for use, and the correction reaches back. Walking the sites and asking which of these is actually running finds them quickly. Idle and decommissioned assets form the third population. Equipment that has been taken out of service but not disposed of is neither in use nor gone, and it needs an explicit decision: return to use, hold as a spare with the value tested, or write off. Left unresolved it becomes next year's ghost.

    Evidence the Auditor Retains

    The working papers from a verification have to let somebody who was not there reach the same conclusion, which sets what is retained. Count sheets come first, showing what was selected, what was found, who performed the check and on what date, with the selection basis recorded before the walk rather than described afterwards. Photographs support the lines where the finding is contestable: an asset in poor condition, an asset without a readable tag, an asset found at an address the register does not name. A photograph carrying a visible identifier is worth considerably more than one showing a machine that could be anywhere. Exception listings are compiled by class rather than as a single list, because the accounting consequence differs by class and a mixed list forces the analysis to be done twice. Finally, management representations are obtained on the residue: the assets that could not be located and could not be explained. That representation is not evidence of existence and is never treated as such. It records what management asserts about items the verification could not resolve, so the unresolved population stays visible instead of quietly closing.

    Using the Checklist Before the Auditor Arrives

    Running the checklist yourself first turns an audit from a discovery exercise into a confirmation, which is a materially better position to be in. Take a sample weighted toward value, walk it register-to-floor and floor-to-register, and record what you find in the same form the auditor will use. What that produces is a list of differences you knew about before anybody asked. Fix what can be fixed properly: locations corrected, custodians updated, unrecorded assets capitalised with the supporting invoice, tags replaced where unreadable. Disclose what cannot. An unlocated asset disclosed by management, with the search documented, reads entirely differently from the same asset found missing by an auditor. Do not close a gap by adjusting the register to match the floor without evidence, because that converts a record-keeping problem into a documentation one. The gap is too large to correct internally when the exceptions run to a substantial proportion of value, when the register cannot be tied to the ledger, or when the same items were unresolved last year, at which point Fixed Asset Verification Services are the cheaper route.

    Related reading

    Share this guide: Link copied!

    What does an auditor physically look at on an asset?

    Identification tag or serial, physical existence, location against the register, working condition, and who has custody. Where a tag is missing the asset must be identified by description and serial, which is slower and less reliable.

    How are assets in remote locations verified?

    Either by visiting on a rotational basis so each location is covered over the cycle, or by obtaining custodian confirmation supported by photographs and serial numbers. Confirmation alone, without evidence, is weak and is normally reported as a limitation.

    What is checked for leased or hired assets?

    Assets held under lease are identified separately because ownership and balance-sheet treatment differ. Verification confirms the asset is present and matches the lease schedule, so it is not double counted as owned property.

    How are IT assets verified differently?

    IT assets move frequently between users and locations, so verification relies on serial numbers and custodian records more than fixed location. Laptops issued to staff often need a confirmation process rather than a physical sighting.

    What evidence should be retained after verification?

    The signed count sheets, the exception list, photographs of unidentified or damaged assets, custodian confirmations, and the final reconciliation to the register. This is the file an auditor asks for when testing whether verification actually happened.