An asset audit is not a stock count. It is a reconciliation between what the register says, what the floor holds and what finance has capitalised.
Most audits fail before the team reaches the floor, because the register and the physical labels do not agree on what an asset is.
Why audits fail
The first failure is identity. Two rows describe the same laptop, one with a serial number and one without. A third row describes a monitor that was scrapped two years ago.
The second is location. The register says “Head Office” while the asset sits in a service centre. The count finds it, but the reconciliation cannot explain the move.
The third is timing. Assets purchased near the year-end are missing from the register, or capitalised without a physical tag.
Before the count
Freeze the register. Export the active rows, the disposed rows and the capitalised additions for the period.
Define the counting unit: a laptop, a monitor, a chair, a machine. Decide whether components (a monitor arm, a dock) are separate assets or part of the parent.
Print the count sheets from the frozen register, not from memory. Each sheet should carry the asset code, description, expected location and custodian.
During the count
Scan or mark every asset. Record the location, the custodian and the condition. If the tag is missing, record the serial number and a photo.
Do not stop to fix the register during the count. Note the exception and keep moving. Fixing rows mid-count creates a moving target.
Count by location, not by department, and reconcile to the custodian later. People move; rooms are easier to verify.
Exceptions
Separate the exceptions into categories: found, missing, damaged, unlabelled and located elsewhere. Each category needs an owner and a closing action.
A missing asset is not automatically a write-off. Check the repair bench, the store room and the last known custodian before concluding.
An unlabelled asset is a tagging failure. A found-elsewhere asset is a transfer failure. The audit should produce a fix for the process, not only a list.
Depreciation and evidence
Finance needs the cost, purchase date, method and accumulated depreciation for each asset. The audit supports the existence and condition, not the valuation policy.
Keep the evidence: count sheets, photos, signatures, exception notes and the final reconciliation. An auditor may ask for the trail months later.
After the audit
Update the register, close the exceptions and assign a date for the next count. If the same categories fail again, the process is the problem.
A quarterly cycle count of high-value assets is usually more useful than one annual marathon.
A count sheet and reconciliation
A count sheet needs the asset code, description, expected location, custodian, condition and a field for the scan or manual confirmation. Leave space for a note and a photo reference.
Sign every sheet. The person who counted and the person who reviewed should both be identifiable. An unsigned sheet is difficult to defend.
Reconcile in three passes: found as expected, found elsewhere, and not found. The not-found list should go back to the custodian before it becomes a write-off.
Record the reconciliation date and the reviewer. The next audit starts from that baseline, not from the original register.
Tagging materials
QR labels are cheap and work with a phone camera. They suit furniture, IT equipment and assets that a person can walk up to.
RFID tags cost more and need a reader, but they speed up a count in a dense store room or a server rack. Use them where the count is frequent or the assets are hard to reach.
Match the label to the surface. A paper label on a hot machine or a curved tool will fail. The register should record the tag type and the date it was applied.
FAQ
How often should assets be audited?
A full count annually and a quarterly sample of high-value or mobile assets is a practical balance.
What if an asset has no tag?
Record the serial number, photograph it and tag it after the count. Do not invent a code that conflicts with the register.
Does the audit replace a valuation?
No. It confirms existence, location and condition. Depreciation and valuation remain finance decisions.
For the system side, see asset management software development and asset management software cost. For the finance connection, see ERP software development.
