By midday, the counting team has visited the same equipment room twice, but several asset records still show unresolved differences. Seven checks before, during, and after physical verification can help prevent this rework by giving staff a consistent way to identify assets, record results, and distinguish genuine exceptions from counting errors.
Why these checks matter
Common signs to watch for
Audit delays often start before anyone reaches the floor: different register versions circulate, room access is unconfirmed, and staff disagree on what evidence is sufficient. During fieldwork, these gaps lead to duplicate scans, handwritten identifiers, and repeated requests for the same documents.
A physical fixed asset count tests more than quantity. Teams need to establish whether recorded assets exist, whether relevant assets found on site appear in the records, and whether location and condition details are accurate.
What happens without consistent checks
Without consistent checks, a printer recorded in the wrong room can take as much time to investigate as an asset that cannot be found anywhere. Meanwhile, an unrecorded machine may go unnoticed if staff only work through the register.
The goal is not to achieve zero exceptions at any cost. It is to prevent avoidable discrepancies and make genuine findings clear enough for a reviewer to assess.
Seven checks for your fixed asset audit checklist
1. Confirm the scope and reconcile the starting register
Before issuing count sheets, define the sites, asset classes, and reporting date covered by the exercise. Decide how to handle leased equipment, third-party property, assets under construction, and items held off site, rather than leaving those decisions to field staff.
Keep a dated register extract and reconcile its relevant financial totals to the general ledger, documenting any differences. This gives the team a controlled starting list; a physical count alone does not validate asset values.
2. Set a movement cutoff and plan site coverage
Set a count window and record receipts, transfers, and removals around that period. If operations cannot pause, maintain a movement log with asset identifiers, timestamps, origin, destination, and supporting references.
Assign each room or zone to a count team and confirm access in advance. Include locked storage, repair areas, spare-equipment cupboards, and remote locations so coverage does not depend on which doors happen to be open.
3. Verify identity beyond the description
Match the asset tag to the register and confirm identity using a serial number or another reliable distinguishing feature. Descriptions such as office chair or production motor cannot reliably distinguish similar items.
When a tag is missing or unreadable, record the available identifiers and flag the item for validation. Do not assign an existing asset number simply because the model and location seem to match.
4. Test in both directions
Trace selected register entries to physical assets to test existence. Then select physical assets independently and trace them back to the register to test completeness within the agreed scope.
For example, a Jakarta office team might verify listed meeting-room screens, then inspect the room for additional equipment missing from its count sheet. Record the direction of each test and explain any sampling approach, rather than suggesting that every asset was checked.
5. Record condition, location, and actual use
Confirm the observed location and custodian, then record whether the asset is operating, idle, damaged, or unavailable for inspection. Agree on condition categories in advance so teams describe similar findings consistently.
An idle machine is not automatically impaired, and a fully depreciated asset is not automatically ready for disposal. Field observations should prompt the appropriate finance or technical review, not an accounting conclusion without supporting evidence.
6. Make each result independently reviewable
Record the asset identifier, test date, counter, observed details, result, and evidence reference together. Where photographs are permitted, capture useful identifying details without exposing unnecessary personal or sensitive information.
Distinguish direct inspection from alternative evidence for assets at repair vendors or remote sites. Do not describe a custodian statement as physical inspection; higher-risk cases may require stronger supporting evidence.
7. Reconcile differences and control closure
Compare results with the controlled register and movement log before proposing corrections. Separate identity mismatches, location errors, unrecorded items, and assets not located, as each requires different evidence.
Keep the original finding, supporting documents, approved correction, and reviewer decision. Unresolved cases should remain visible in the final audit summary, rather than disappearing when someone updates the working file.
A brief example from the field
A Surabaya warehouse count finds a compressor in a different bay from the one shown in the register. Its serial number matches, and a dated movement record explains the change, so the team records a location correction instead of reporting one missing compressor and one unexplained addition.
How to apply the checks without extra complexity
Quick checklist
Use one shared count template with a small set of required fields. Keep supporting documents in a controlled folder and link each result to its evidence, rather than copying documents into multiple spreadsheets.
- Before counting: approve the scope, register version, site coverage, and movement controls.
- During counting: verify identity, test in both directions, and record observations.
- Before reporting: reconcile differences, review evidence, and document unresolved limitations.
Keep field decisions simple
Give counters clear result options, such as verified, discrepancy, and not inspected, and require a reason for the last two. This helps prevent staff from marking unavailable assets as verified just to complete a sheet.
Once a difference is validated, a structured investigation can prevent repeated searches; use exception follow-up for potentially missing assets when an item remains unlocated after identity and movement checks.
Mistakes to avoid
Common mistakes
Do not overwrite the starting register during fieldwork, count the same movable asset in two zones, or accept a signature as proof of inspection. These shortcuts weaken the link between the original asset list and the final conclusion.
Do not treat a successful tag scan as complete verification, either. A scan captures an identifier, but staff still need to confirm that it belongs to the asset they are examining.
How to handle conflicting evidence
When evidence conflicts, preserve both records and request a targeted recheck. For example, if two assets carry the same tag, verify their serial numbers rather than immediately assuming that one register entry should be deleted.
What to confirm before sign-off
A well-supported audit file shows what was covered, how assets were verified, which differences were resolved, and what remains uncertain. Before sign-off, the reviewer should be able to trace a result from the starting register through field evidence to its final treatment without relying on the counter’s memory.
As a practical next step, compare your current count template with these seven checks in the fixed asset audit checklist.
Explore asset verification resources at Fisetra.