How to Audit Fixed Assets: Procedures and Checklists
A structured guide to fixed asset audit procedures — covering planning, fieldwork, reconciliation, and reporting for both internal and external audit teams.
Who It's For
Internal auditors, external audit teams, and finance directors
Review Level
High
Knowledge Layer
How to Audit Fixed Assets: Procedures and Checklists
Clear operational guidance designed to move from understanding into implementation.
Category
Compliance
Section
Audit Readiness
What a fixed asset audit actually covers
A fixed asset audit is not just counting physical items against a register. It covers the entire control environment — existence and completeness testing, valuation accuracy, depreciation correctness, ownership verification, and the adequacy of internal controls around additions, disposals, and transfers.
The scope depends on whether the audit is internal (focused on control improvement) or external (focused on financial statement assertions). Both need evidence, but the emphasis and reporting differ.
Audit planning phase
Effective audit planning reduces fieldwork surprises. The planning phase should establish scope, timing, sampling methodology, and evidence requirements before any fieldwork begins.
- Obtain the complete fixed asset register as at the audit date
- Review prior year audit findings and management responses
- Assess the control environment — who authorises additions, disposals, transfers?
- Design sample selection — risk-based, value-based, or random
- Coordinate physical verification with site access requirements
- Prepare audit checklists covering each assertion (existence, completeness, valuation, rights)
Fieldwork procedures
Fieldwork is where the register meets reality. The auditor selects a sample of assets from the register and physically locates them (existence testing), then selects assets observed in the field and traces them back to the register (completeness testing). Both directions matter.
- Existence: Select items from register, physically locate and inspect
- Completeness: Select items in the field, trace back to register
- Condition: Assess whether physical condition supports carrying value
- Location: Confirm assets are where the register says they are
- Identification: Verify asset tags, serial numbers, and unique identifiers match
Common findings and how to prevent them
The most common audit findings are predictable and preventable: ghost assets that were disposed but never removed, assets without physical identification tags, incorrect useful life estimates never reviewed, transfers between sites not reflected in the register, and supporting documentation for additions that cannot be located.
Prevention comes from embedded process discipline — not from pre-audit scrambles.
FEEDBACK
Was this helpful?
Tell us how this article felt in one click.
Cite this resource
If you found this documentation helpful, link to it in your internal wikis, RFP requirements, or project plans. Copied links include the full structural schema.