How to do a physical fixed asset verification: a step-by-step guide for Kenyan organizations

A physical verification is the count that makes a fixed asset register true. Somebody walks the premises, checks each asset against the register, and settles every difference. Done well, it takes days and ends with a report that auditors accept. Done badly, it takes weeks, produces a list nobody trusts, and has to be repeated.

This guide is the process we would follow for a county department, an NGO with field offices or a company with several sites. It works with paper, with Excel, or with software, and it is the same in each case: decide what you are counting, make sure it can be identified, count it once, and reconcile.

Why organizations verify

The reasons are practical.

• Audit. Auditors want to see that the assets in the financial statements exist. A register that has never been matched to the floor is an assertion, not evidence.
• Accrual accounting. Public bodies reporting under IPSAS accrual need a complete, verified register before depreciation means anything.
• Tax. Capital allowances depend on assets you can show physically. A tagged, verified register is the starting point for your adviser.
• Donors. Grant agreements often require an asset register and a physical check at project close.
• Control. Verification is how losses, misuse and unrecorded transfers come to light.

Before you count

Most of the effort is here. A count on a messy register only reproduces the mess.

1. Set the scope and the purpose

Write down what you are verifying: the whole organization, a region, a department, or a category such as ICT equipment. Say why. A count for year-end accounts and a count for a donor close-out need different outputs.

Agree who owns the exercise, who approves corrections, and how teams get into restricted areas. Keep the scope small enough to finish. A completed count of one department is worth more than an abandoned count of everything.

2. Clean the register you have

Before anyone walks anywhere, deal with what you can fix at a desk:

• Remove duplicates, and find assets recorded twice under different names.
• Make location names consistent. “Finance office”, “Finance Off.” and “2nd floor finance” should be one place.
• Fill in what is missing: serial numbers, categories, who is accountable.
• Mark what you already know is gone: disposed, sold, scrapped. Do not make the team look for them.

If you are moving to software, this is the moment to import the register, because every error you catch in the spreadsheet is one the count does not have to explain.

3. Make every asset identifiable

An asset can only be verified if you can say which one it is. A serial number inside a casing is not a practical identifier. A durable tag with a unique number, as a barcode or QR code, is.

Tag before you count, or tag as you count and record the number at that moment. Choose tags to suit the asset: aluminium for furniture, machinery and vehicles; polyester labels for indoor IT; tamper-evident labels for portable, high-theft items. Unique numbers should come from one source, never from several people improvising.

4. Plan the teams, the route and the dates

Plan by place, not by asset. Divide the premises into areas that one team can finish in a session, and give each area a name that matches your location list. Decide:

• how many teams, and who is in each. Two people work well: one scans, one records condition and photos;
• the dates, avoiding month-end and when key staff are away;
• what each team carries: a phone or scanner, a printed area list as a fallback, spare tags, a marker;
• who counts what, so that no area is counted twice or left out.

Brief the teams. Show them what a good record looks like and what to do with an asset that has no tag, no number or a number that is not on the list.

During the count

Scan, do not tick

Ticking a list invites the wrong asset to be ticked, and it turns reconciliation into a manual matching exercise. Scanning each tag produces a record of exactly what was found, where and when.

For each asset record, at minimum:

What	Why
The asset identifier	Proves which asset it is
The place you found it	Settles “wrong location”
Its condition	Feeds disposals and replacement planning
Who holds it, if a person	Settles custodian questions
A photo, for anything unusual	Evidence you can show later

Treat the three awkward cases the same way every time

1. Found, but not on the register. Record it with a photo and a note. Do not invent a number on the spot.
2. On the register, but it has no tag. Tag it, record the number, and note which register line it matches.
3. A tag, but no asset to go with it. A tag on a different asset from the one the register says is a finding in itself. Record both.

Count each place completely before moving on, and finish an area before leaving it. Gaps are what turn into “missing assets” later.

Reconcile

Reconciliation compares what you found with what you expected. Every asset falls into one of a few outcomes:

Outcome	Meaning	Usual action
Matched	Found where the register says	Mark as verified
Not found	On the register, not scanned	Investigate
Wrong location	Found, but somewhere else	Move the record, or the asset
Not on the register	Found, but never recorded	Register it, with its evidence
Scanned twice	The same asset counted again	Count once
Wrong custodian or status	Found, but the record is out of date	Update the record

If you are counting in software, this happens as you scan. On paper, it is the part that takes the longest, which is why a clean register and consistent location names matter so much.

Investigate, then correct

Resist the urge to write off at once. For every asset that was not found:

• check whether it was transferred, loaned or sent for repair, and look for the paperwork;
• ask the last known custodian;
• look in the places assets collect: stores, a manager’s office, a repair shop;
• set a deadline, and record what you did.

When the trail is cold, write off through your normal disposal approval, with a reason and evidence. For assets that were found but wrong on the register, correct the record and keep a note of what was changed and why. Make corrections in bulk where you can, so they are consistent and logged.

Report and sign off

The report your auditors want is short, and it traces back to evidence:

1. Scope, dates, who counted.
2. Totals: expected, found, not found, found elsewhere, not on the register.
3. The list of exceptions, with what was done about each.
4. Adjustments made to the register, with approvals.
5. Sign-off by the person accountable.

Freeze the result. A report that can still be edited a month later does not give the comfort it should. In VexCloud AMS a finalized audit is locked, and its result carries a hash that can be recomputed to show nothing has changed.

Keep it true afterwards

A verification is a snapshot. Without habits it is stale again within a year.

• Tag every new purchase on receipt, before it is issued.
• Record transfers when they happen, with a reference.
• Put a date on each verified asset, and a date it is next due.
• Decide who owns the register, and give them the time to do it.

Common mistakes

• Counting without a clean list. You will spend the exercise arguing about names.
• Counting from memory. “Everything in the store is there” is not a count.
• Letting the owner of the assets count them. Verification is stronger when someone independent does it.
• Making corrections without evidence. Every change should be explainable to an auditor.
• Doing it once. Annual, with a plan to keep the register true between counts.

If you want help with the physical part, Vexar Solutions tags and counts assets on site and can hand the register over ready to load. VexCloud AMS then handles the scanning, reconciliation and reporting described above, so the next verification starts from a register that is already true.