How a Verification Is Planned and Run
A fixed asset verification runs in five stages, and each one depends on the one before it. A weak plan cannot be rescued by a careful walk, and a careful walk is wasted if nobody reconciles it.
- Plan Cut-off date, sites, classes and the frozen register extract.
- Sample Which lines are visited, weighted by value.
- Verify The floor work, register to floor and floor to register.
- Reconcile What was seen against the frozen extract, line by line.
- Report Outcome, residue and its accounting effect.
Effort is driven by three things and only three: the number of locations, the number of register lines, and whether identification already exists on the assets. A tagged estate at one site moves quickly; an untagged estate spread over several sites with a stale register is slow, because finding out which machine is which, not counting, becomes the bottleneck. Knowing which of the three dominates tells you where to spend the planning time.
Planning: Scope, Cycle and Coverage
Planning settles three things, and settling them in writing is what separates a programme from an annual scramble.
- Full count or rotation. A modest estate at one or two locations can be covered completely each cycle, and generally should be: the saving from sampling is small and the assurance from completeness is large. A large estate across many sites is covered on rotation, with the cycle defined so that every class and every location is reached within a stated period, not whenever it is convenient.
- Sites and classes in scope, with exclusions recorded. Assets below a value threshold, sites about to close and classes verified through another process can all be legitimate exclusions. They have to be visible in the plan, with their reasons, rather than discovered as gaps afterwards.
- Cut-off and freeze. The register extract is frozen at the cut-off date before anybody travels, because a verification against a moving register cannot be reconciled. Where assets will move during the fieldwork, the treatment is agreed in advance: either movement is paused, or every movement is logged and reconciled at the boundary.
Two practical items complete the plan. Custodians are told when their area will be visited so that locked rooms, off-site equipment and keys are dealt with before the team arrives. Count sheets are prepared from the frozen extract, carrying the register's own data for each selected line, with blank rows for assets found that the register does not list.
Sampling: How Much Is Enough
Selection is weighted by value, because asset registers are almost always skewed: a small number of lines carry most of the money, and a sample drawn evenly across lines spends most of its effort on items that matter least. A sample built the way the three cards below describe can reach most of the carrying value while visiting a modest share of the lines, which is the whole reason it is used.
Layer one
Every line above a value thresholdExamined completely, not sampled. These are the lines where a single exception could be material on its own.
Layer two
The rest, divided into value bandsEach band is represented, so the conclusion covers the whole register and not only its expensive end. Every line in a band has a chance of being picked.
Layer three
Additions by judgementLines with known risk: assets recently moved, sites with a history of exceptions, classes that walk away easily such as laptops and portable tools.
Population size matters less than people expect. Past a certain size, the number of items needed to support a conclusion grows only slowly as the register grows, so a register of twenty thousand lines does not need ten times the sample of one with two thousand. Effort scales with how concentrated the value is and how many sites there are, not with the line count. Where an auditor tests a sample, SA 530 requires every sampling unit to have a chance of selection and any misstatement found to be projected to the whole population, which is why a sample chosen only from convenient locations proves little.
Full coverage is the only defensible answer in three cases: a small population where sampling saves little, a balance that is already disputed, and any register where a single line could be material on its own.
Verification on the Floor
The floor work runs in both directions, and a verification that runs only one is incomplete by design.
- Register to floor. Take a line and look for the asset. This is the direction that finds assets which no longer exist. It is the instinctive approach, because the register is the document in hand, and on its own it never finds anything unrecorded.
Finds the missing - Floor to register. Take an asset that is physically present and trace it back to its line. This is the direction that finds equipment nobody capitalised.
Finds the unrecorded - Condition and use, recorded at the same time. On a defined scale rather than in free text, because these observations cannot be made later from a desk, and whether an asset is actually running matters as much as whether it is intact.
Observed once, on site - Off-site assets by a rule agreed beforehand. Equipment at a repairer, out on hire, at an exhibition or with an employee is verified from documents, and recorded as its own category so the reader can see how much of the conclusion rests on paper rather than sight.
Documents, shown separately
The individual checks made at each asset, from tag legibility to custodian, are listed in the fixed asset verification checklist. What the method adds is discipline about the sheets: every sheet issued is accounted for at the end of the day, findings are written on the sheet at the asset rather than from memory, and photographs show a visible identifier wherever a finding may be questioned.
Reconciliation and Evidence
Reconciliation is where a verification either becomes useful or stops short. It is worked in a fixed order.
- Build two exception lists. Every register line not matched to an asset, and every asset not matched to a register line, held separately because they have opposite accounting effects. Netting them into one figure hides both.
- Work each exception individually. Most resolve. An asset recorded at one site is found at another because it was moved and never transferred. A line that looks unmatched is matched once a duplicate description is unpicked. An asset with no line turns out to be capitalised under a different description.
- Support each resolution with a document. A transfer note, an invoice, a disposal record: the reconciliation should stand up without the person who did it having to explain it.
- Report the residue on its own. What remains is the set of items nobody can account for in either direction. It is valued at carrying amount, reported as its own figure rather than absorbed into an adjustment, and management's written representation is obtained on it.
A residue reported honestly is a finding; a residue quietly netted off is a misstatement. The evidence file behind the reconciliation, meaning count sheets, photographs, the exception lists and the documents that resolved them, is what a reviewer reads. SA 500 requires audit evidence to be sufficient and appropriate and treats evidence obtained directly by the auditor as generally more reliable than evidence obtained indirectly, which is why sight of the asset carries more weight than a custodian's confirmation that it exists. How the result is then written up is covered in the fixed asset verification report format guide.
The method on one page
Every stage above, shortened to what has to exist when it is finished.
Before the walk
- Cut-off date fixed; register extract frozen
- Sites, classes and cycle written down
- Exclusions named with reasons
- Value-weighted sample selected
- Custodians told; count sheets prepared
On the floor
- Register to floor and floor to register
- Condition and use on a defined scale
- Off-site assets verified from documents
- Every sheet accounted for each day
After the walk
- Two exception lists, never netted
- Each exception resolved with a document
- Residue valued and reported on its own
- Management representation on the residue
Doing It Yourself, and When Not To
An internal team can credibly do a great deal of this. It can walk the estate, confirm existence, correct locations and custodians, find unreadable tags and build the exception lists, and doing so before an external verification is almost always worth it. What an internal team cannot supply is independence.
- Where independence is usually needed. A lender assessing its security, a statutory auditor gathering evidence on a material balance, or an insurer settling a claim will generally want the count done by someone with no interest in its outcome. A self-count does not become independent because it was thorough.
Someone outside relies on it - Where the register is too far gone for a self-count. Descriptions duplicated so badly that lines cannot be matched to units; a register that does not tie to the ledger; several years since the last verification; or an earlier internal count whose result management did not accept.
A rebuild, not a check
In either case the register is no longer being checked but reconstructed, and the practical route is to verify what exists, build a corrected register from that, and keep the old register as history rather than as the baseline. That is the point at which an asset verification by an external team resolves in one exercise what internal attempts have not.
