Fixed Asset Physical Verification: How to Run a Physical Count

Physical verification is what turns a fixed asset register from a set of claims into something you can defend. It's also the task most often pushed to next quarter, because everyone assumes it means a week of stopping work.

It doesn't have to. A well-scoped count, recorded on a phone as it happens and spread across the year, finds the same problems with far less disruption. This guide covers what a physical count is, who expects one, how to run it, and what it has to leave behind.

What fixed asset physical verification is

Fixed asset physical verification — also called a fixed asset physical inventory, physical count or fixed asset audit — is the process of confirming, by direct observation, that the assets recorded in the register exist, are located where the register says, and are in the recorded condition. It is distinct from a stock count: you are verifying individually identified equipment you use, not quantities of goods you sell.

It answers three distinct questions, and it's worth separating them because they fail differently:

There is a fourth question the count answers by accident: is there anything here we don't know about? Found-but-not-recorded items test completeness, and they're how untracked purchases surface.

Who expects a physical count, and how often

The requirement comes from different places depending on who you report to. Very few rules set a frequency; most set an expectation and leave the interval to you.

For US public company audits, PCAOB AS 1105 defines the existence or occurrence assertion — that assets 'exist at a given date' — and describes inspection as examining records or documents 'or physically examining an asset' (PCAOB AS 1105, Audit Evidence). A recent, well-documented management count is the evidence that makes the auditor's own inspection quick.

For equipment bought with US federal money — common at universities, hospitals and research non-profits — the rule is explicit: 'A physical inventory of the property must be conducted, and the results must be reconciled with the property records at least once every two years', and any loss, damage or theft must be investigated (2 CFR 200.313(d)).

In the UK, section 386 of the Companies Act 2006 requires records sufficient to show and explain the company's transactions, including a record of its assets (legislation.gov.uk). It doesn't mandate a count, but a register nobody has checked against reality is hard to describe as adequate.

Grant terms, lender covenants, insurers and public-sector funders can all add their own requirement on top. Read the actual terms; they are often more specific than the law.

Planning the count

1. Define the scope precisely — a site, a class, a department, a cost centre. Write down what is excluded as well as what is included.
2. Extract the expected list from the register as at a stated date, so the comparison has a fixed baseline.
3. Decide the evidence standard. Is sighting the asset enough, or must the tag be scanned and the serial matched? Scanning is stronger and, on a phone, faster.
4. Assign counters who are not the custodians of what they are counting, where you can. Independence matters to whoever reviews the result.
5. Agree how to handle in-transit items — equipment issued to someone, out for repair, or at another site. These are not discrepancies if you can show where they are.
6. Freeze movements, or record them. Either pause issues and returns in the scope during the count, or make sure every movement is recorded in the same system the count uses.

A full pre-count, during-count and post-count list is in the asset audit checklist, and the step-by-step method is in how to do an asset audit.

Running it

Walk the scope and record each item as you go. The critical discipline is recording at the point of checking rather than transcribing afterwards, because transcription is where errors enter and where the timestamp stops being real.

*Each item recorded verified or missing as the count proceeds, with progress and discrepancies visible throughout.*

Record found-but-not-expected items too. Equipment present and not on the register is as much a finding as the reverse.

For equipment held by remote staff, a scan by the holder of their own label — with the location recorded — is weaker than an independent sighting but much stronger than a confirmation email. State in the report which method was used for which items.

The evidence it must leave

• The scope and the baseline date of the expected list.
• The counter's identity, the dates of the count, and a closing note or signature from whoever is responsible.
• A per-item result: verified, not found, or found unexpectedly.
• Notes against individual items where condition or location differed.
• A reconciliation showing how each discrepancy was resolved, and what was adjusted in the register and the ledger.
• An export in a form the requester can file without reformatting.

Handling discrepancies

Don't correct the register during the count. Record what you found, close the count, then reconcile — otherwise the evidence of the discrepancy disappears into the correction, and the audit trail shows a clean count that never happened.

Losses need a decision about the books as well as the register. A capitalised asset that is confirmed lost should come off the books: FRS 102 paragraph 17.28, for example, requires derecognition 'when no future economic benefits are expected from its use or disposal' (FRS 102, FRC), which means removing its cost and accumulated depreciation and recognising the loss. If it was grant-funded, the funder may need to be told — 2 CFR 200.313(d)(3) requires notifying the agency or pass-through entity of any loss that will affect the programme.

Worked example (hypothetical)

A regional office has 412 assets on the register at the baseline date. The count scans 391 of them. Of the 21 not scanned, 9 are on loan to named people and confirmed by the holder, 4 are out for repair with open tickets, 3 turn up in another building, and 5 can't be found. The count also finds 7 items not on the register — monitors bought on a corporate card.

The headline isn't '5 lost'. It's that 8 of 412 records were wrong — 3 in the wrong place, 5 missing — and 7 assets weren't on the register at all — and each of those has a cause you can fix.

Sampling, when a full count isn't realistic

Sometimes the estate is too large or too dispersed to verify completely in any useful timeframe. Sampling is a legitimate answer, provided it's designed rather than improvised.

Whichever you choose, write down the method before you start. A sample described after the fact looks like the parts that were convenient, whether or not it was. And check your rules first: a two-year federal inventory requirement is about the property records as a whole, so a sample alone may not satisfy it.

Tagging gaps found during verification

Every first count finds equipment with no tag, an unreadable tag, or a tag belonging to a record that was retired years ago. Resist fixing these mid-count. Note them, finish the count, then work the list.

• No tag, on the register — match on serial, tag it, note the gap.
• No tag, not on the register — a found asset. Add it with whatever acquisition detail survives.
• Tag unreadable — reprint against the existing record; the history is intact.
• Tag on a retired record — the disposal was never closed. Fix the disposal, not the tag.

What the report should say about what you couldn't check

This is the section people leave out, and it's the one that makes the rest credible.

State plainly what was out of scope, what was inaccessible on the day, and what was accepted on documentary evidence rather than sight. A report claiming complete verification of an estate that includes equipment in twelve vans and three engineers' homes will be read sceptically, and rightly.

How often to count

Where a rule sets the interval — every two years for federal-grant equipment — that is the floor. Where none does, annual coverage of the whole estate is the common expectation of auditors and boards.

Achieving it through rolling cycle counts scoped by location or department is usually better than one annual event: the same coverage, spread across the year, with discrepancies found while they're still recent enough to resolve. High-value or high-risk classes can justify a shorter cycle. Set that by consequence rather than by value alone — a cheap item whose absence stops a job may matter more than an expensive one in a cupboard.

Software helps mainly by removing transcription. In Stackroom, for example, a count is scoped, each item is scanned as verified or marked missing with a note, and the count closes with a note and an exportable result — but a well-run paper count with the same discipline is still a valid count.

If you report in India

Under CARO 2020, clause 3(i)(b), the statutory auditor reports whether property, plant and equipment have been physically verified by management at reasonable intervals, whether material discrepancies were found, and whether they were properly dealt with in the books (ICAI study material on CARO 2020). What counts as reasonable is left to the auditor's judgement, having regard to the size of the company and the nature of the assets (Taxmann), so a documented programme that covers the estate over a stated cycle is the usual answer. Everything else in this guide applies unchanged.

For the register the count is checked against, see what is a fixed asset register; for how this fits a wider audit programme, see audits and compliance.

Sources

• AS 1105: Audit Evidence — Public Company Accounting Oversight Board
• 2 CFR 200.313, Equipment — eCFR, current
• Companies Act 2006, section 386 — legislation.gov.uk
• FRS 102, Section 17 Property, Plant and Equipment — Financial Reporting Council, September 2024
• CARO 2020 study material — Institute of Chartered Accountants of India, 2022
• Property, plant and equipment under CARO — Taxmann