Most physical verification exercises fail quietly. A finance executive walks the floor with a printed list, ticks what she finds, and the ticked list goes in a file. Nobody reconciles the untried lines, the auditor cannot rely on it, and next year it starts from zero. Here is the method we use, written so you can run it yourselves.

1. Fix the scope before anyone walks

Decide, in writing: which entities, which locations, which asset classes, and the cut-off date for the register you will verify against. Freeze additions and disposals in the register from the cut-off until the exercise closes, or you will be chasing a moving target. Agree the schedule with each site head so stores, server rooms and locked labs are accessible.

2. Clean the register you are verifying against

Export the register as at the cut-off. Before fieldwork, remove the obvious problems: duplicate entries, assets with no location, lines that are clearly expenses capitalised in error (annual maintenance contracts, software subscriptions), and assets below your capitalisation threshold. Flag anything with no description that could be recognised on the floor. Doing this before fieldwork saves days on site.

3. Tag before you count

If assets are not uniquely tagged, verification cannot be repeated and discrepancies cannot be traced. Tag first — a tamper-evident polyester or metal label with a QR code and a human-readable number — and record tag number, photo, location and custodian at the moment of tagging. Where assets are already tagged, check tag condition as you go; unreadable tags are replaced and the mapping recorded.

4. Count by location, not by register

Walk every room, bay and yard in the scope and scan every asset you find, whether or not it is on the list. This is the opposite of walking the list and looking for assets, and it is the only way to find surplus assets — things physically present that were never capitalised or were written off and are still in use. Record condition (in use, idle, damaged, under repair) at the same time.

5. Reconcile into four buckets

Match scans to the register. Every line ends in exactly one of:

  • Found, as recorded — tag, location and description agree.
  • Found, moved — asset exists but is in a different location, department or custodian than the register says. Update the register; no accounting entry.
  • Not found — on the register, not located anywhere in scope. Investigate before writing off: it may be at a location outside scope, out for repair, or disposed without paperwork.
  • Surplus — found on the floor, not on the register. Trace to a purchase or transfer; capitalise or record as a non-asset (e.g. customer-owned equipment).

6. Resolve, approve, record

Each "not found" and "surplus" item gets a cause, a resolution, an approver and — where there is an accounting effect — a journal entry reference. This is the variance register, and it is what the auditor will read under CARO clause 3(i)(b). Approvals should follow your delegation of authority: a plant head can approve the write-off of a ₹12,000 chair; a ₹30 lakh machine needs the CFO.

7. Report

The closing report states: scope and cut-off; locations covered and dates; number of assets on the register in scope, number verified, number moved, number not found, number surplus; value of each; resolutions and open items; and the method and evidence used. Attach the variance register. Keep the scan data — timestamps, photos, GPS where available — as the evidence base.

How long it takes

A trained two-person team tags and captures roughly a few hundred assets a day depending on asset size and access. A single large site of several thousand assets is typically two to three weeks from survey to report. Multi-branch organisations run sites in parallel. After the first full cycle, annual re-verification with phone-based scanning is a fraction of the effort, because the tags and the baseline exist.

If you'd rather not build this capability in-house, this is the service SBC FIX-TAG provides — tagging, verification and the reconciliation report, with the platform to keep it current afterwards.