Fixed Asset Physical Verification: A How-To Guide

Physical verification is the moment a fixed asset register meets reality. Every company carries a list of machines, vehicles, laptops, furniture and fit-outs on its books; verification asks whether each of those items still exists, where it is, who has it, and what condition it is in. Done well, it is a routine control that gives auditors comfort and gives finance an accurate base for depreciation. Done badly, it is a spreadsheet exercise every March that nobody trusts and nobody can reproduce.

Why it matters to auditors

For companies covered by the Companies (Auditor’s Report) Order, 2020 (CARO 2020), the statutory auditor reports on fixed assets in clause 3(i): whether the company maintains proper records showing full particulars, including quantitative details and situation of its property, plant and equipment; whether those assets have been physically verified by management at reasonable intervals; and whether any material discrepancies were noticed and properly dealt with in the books. CARO does not apply to every company, and the exemptions and wording should be checked against the current text of the Order, but for most mid-sized and large companies the practical point is the same: the auditor will ask to see the verification, not just hear that it happened.

"Reasonable intervals" is not defined as a fixed period. Many companies verify every asset once a year; others run a rolling programme that covers high-value or mobile assets more often and static, low-value items over two or three years. What matters is that the programme is written down, approved, followed, and evidenced.

Step 1: Get the register ready before anyone counts

Most verification problems start in the register, not on the floor. Before a campaign begins, fix the record you will be counting against.

• One line per countable item. A single line for "office furniture – ₹12 lakh" cannot be verified; twenty desks, forty chairs and six cabinets can.
• A unique asset code on every line, matched to a physical tag.
• Location and custodian for every asset: the branch, floor or site, and the person responsible for it.
• A cut-off date. Freeze additions, transfers and disposals for the period of the count, or record them separately so the count is compared against a known snapshot.

Step 2: Tag what you own

Durable labels with a QR code, barcode or Data Matrix code turn verification from reading serial numbers aloud into scanning. Tag at capitalisation, so new assets never enter the register untagged, and re-tag anything whose label has worn off during the count itself. Where an asset cannot carry a label, such as buried pipelines or software licences, record how it will be verified instead: an engineer’s certificate, a site photograph, a licence statement.

Step 3: Run the count as a campaign

Treat each verification as a campaign with a scope, a team and a deadline rather than an open-ended request to "please check your assets".

• Split the scope by location so each counter has a defined area.
• Count blind where you can: counters scan what they find rather than ticking off a printed list, which stops people confirming assets they never saw.
• Capture evidence at the point of count: a photograph, the condition, and the custodian’s confirmation.
• Allow offline counting. Warehouses, basements and remote sites rarely have reliable signal, and a count that fails when the network drops will be abandoned.

Step 4: Reconcile, investigate, then adjust

At the end of the count every asset falls into one of four buckets, and each needs a different response.

• Found as recorded: no action beyond keeping the evidence.
• Found elsewhere: update the location or custodian through an approved transfer, not a silent edit.
• Not found: investigate before writing off. Check recent disposals, transfers to other branches, assets out for repair, and items with worn tags.
• Found but not on the register: decide whether it should be capitalised, was expensed, or belongs to someone else, such as a lessor or customer.

Only after investigation should discrepancies reach the books, and then through approved adjustments that record the reason: a write-off with its loss, a reinstatement, or a correction of location. The approval trail is part of what the auditor will test.

Step 5: Keep evidence that someone else can follow

The output of a verification is not a tick mark; it is a file. Keep the approved scope, the counted list with timestamps and counters, photographs, the reconciliation, the investigation notes for every discrepancy, and the approvals for every adjustment. A reviewer who was not in the room should be able to reconstruct what happened from that file alone.

How FixedAsset Pro runs a verification

FixedAsset Pro treats verification as a campaign on the same record that finance uses for depreciation. Assets carry QR, barcode or Data Matrix labels printed from the register. Counters use the Android or iOS app to scan tags, count offline, and capture photos, comments and signatures; desktop (LAN) users can count with a USB scanner, a webcam or count sheets. Differences go to reconciliation and sign-off, adjustments pass through approval chains, and the evidence lands in an evidence vault with a sealed audit trail. Verifiers see assets without values, because only users with finance rights see amounts.

A verification is only as good as the register it is counted against and the evidence it leaves behind. Fix the register first, count blind, and never write off what you have not investigated.

Frequently asked questions

How often should fixed assets be physically verified in India?

There is no single statutory period. CARO 2020 asks the auditor whether management has verified property, plant and equipment at reasonable intervals. Many companies verify every asset annually; others run a documented rolling programme that covers high-value and mobile assets more often and low-value static assets over two to three years. The programme should be written, approved and evidenced.

What should we do with assets that are not found during verification?

Investigate before adjusting the books. Check recent disposals, inter-branch transfers, assets out for repair or with vendors, and items whose tags have worn off. Only after investigation should a write-off be proposed, and it should pass through an approval with the reason and the loss recorded, so the auditor can follow the trail.

Do we need QR or barcode tags for physical verification?

Tags are not legally required, but they make verification faster and more reliable because counters scan a code instead of reading serial numbers. Tag assets at capitalisation, re-tag worn labels during counts, and document an alternative method, such as certificates or photographs, for assets that cannot carry a label.

Can physical verification be done without internet access?

Yes, if the tool supports offline counting. Warehouses, basements and remote sites often have poor connectivity, so the counting app should record scans, photos and comments offline and sync them when a connection returns. The FixedAsset Pro mobile app supports offline counting for this reason.