Audit Procedures for Fixed Assets: Assertions, Tests, Evidence & Sample Workpapers

Introduction

If your fixed asset audit still sounds like “go check whether the assets are there,” this guide will help. It turns a vague instruction into a practical playbook, covering substantive audit procedures for fixed assets and showing that, in the verification of a fixed asset, the auditor checks existence, accuracy, and supporting evidence so finance teams can follow clear steps, gather stronger proof, and produce cleaner workpapers.

Audit procedures for fixed assets are the tests an auditor performs to obtain sufficient appropriate evidence that fixed assets and related disclosures are recorded correctly. Before diving into individual assertions, it helps to understand the broader fixed asset audit process, methods, and compliance requirements that shape why these procedures exist—because, in practice, each assertion (existence, completeness, rights, valuation, and presentation) must be translated into procedures, evidence requests, exception follow-up, and a review-ready conclusion.

In this guide, you’ll learn:

• What audit procedures for fixed assets actually need to prove, and how assertions like existence, completeness, and valuation connect directly to the tests you perform.
• How to translate each assertion into practical procedures, while linking them clearly to evidence, so your workpapers hold up under review.
• How to execute fixed asset audit procedures step by step, including sampling, physical verification, and reconciling fixed assets to the general ledger where it matters most.
• What strong audit evidence looks like in practice, and how combining physical checks with documents and system data creates more reliable conclusions.
• Finally, how to handle exceptions, edge cases, and real-world gaps, so your audit file reflects judgment, not just checklist completion.

What audit procedures for fixed assets are meant to prove?

Audit procedures for fixed assets are meant to prove whether the fixed asset balance and related disclosures are free of material misstatement. Therefore, a good procedure file does more than confirm that an asset is sitting on the floor. It also tests whether the asset is recorded completely, belongs to the company, is valued correctly, and is presented properly in the financial statements.

That distinction matters because an asset can exist physically and still be wrong in the books. A machine may be present but capitalized at the wrong amount. A laptop may be tagged but assigned to the wrong location. A retired asset may still be depreciating. A project may still sit in CWIP even though the asset has already been placed in service. Strong audit procedures connect the physical asset, the accounting treatment, and the reviewer’s conclusion.

Which fixed asset assertions should drive your test plan?

The best fixed asset audit plan starts with assertions, not with a generic checklist. Each assertion points to different risks, different procedures, and different evidence.

The AssetCues assertion-to-procedure-to-evidence matrix

What documents and data should you pull before testing?

Before fieldwork starts, pull the data that lets you test both the accounting population and the physical population. Otherwise, teams waste time on site and still return with weak evidence.

At a minimum, request the following:

• The latest FAR with asset IDs, descriptions, classes, dates in service, locations, custodians, status, and accumulated depreciation.
• The general ledger rollforward for additions, transfers, depreciation, impairments, and disposals.
• Additions and disposals listings for the period under audit.
• Depreciation reports and the capitalization policy.
• CWIP listing with project age, owner, expected commissioning date, and current status.
• Lease schedules and right-of-use support, if relevant to the scope.
• Transfer logs, movement records, and prior discrepancy logs.
• Site lists, cost-center maps, custodian lists, and known high-risk populations, such as laptops, handheld devices, tools, and mobile equipment.
• Prior audit findings and management action trackers.
• Any write-off memos, scrap approvals, insurance claims, or theft reports relevant to missing assets.

Minimum evidence request list by transaction type

How should you choose fixed asset samples?

Fixed asset samples should reflect risk, not just round numbers. Therefore, build your sample around where misstatement is most likely or most damaging.

A practical enterprise approach is to combine:

• 100% testing for individual material assets or sensitive items.
• Targeted testing for high-risk classes, such as portable IT and field equipment.
• Judgmental or statistical sampling for large homogeneous populations.

How do you perform audit procedures for fixed assets step by step?

Audit procedures for fixed assets work best when the team follows a disciplined sequence.

1. Define the objective, scope, and assertions.
   

   Identify which balances, locations, asset classes, and risks are in scope. Then decide whether the priority is existence, completeness, valuation, disposal accuracy, or a combination.

2. Build a clean testing population.
   

   Pull the FAR, GL rollforward, additions, disposals, CWIP, and lease schedules. Standardize IDs, asset classes, and location naming before you sample.

3. Assess risk and choose the sample logic.
   

   Separate individually material items from high-volume populations. Prioritize portable assets, recent additions, old CWIP, remote sites, and prior exceptions.

4. Understand or test the key controls where they help.
   

   Walk through approvals for additions, transfers, and disposals. Check whether tag assignment, capitalization review, and periodic verification controls are actually operated.

5. Perform record-to-asset and asset-to-record testing.
   

   Trace selected items from the FAR to the floor for existence. Then trace selected physical items back to the FAR for completeness.

6. Test the accounting around the asset.
   

   Vouch additions, recalculate depreciation, review useful lives, inspect lease treatment where relevant, and test disposal entries and CWIP transfers.

7. Investigate exceptions immediately.
   

   When an item is missing or mismatched, do not stop at the management explanation. Review transfer logs, prior counts, disposal support, replacement records, and subsequent events.

8. Write a conclusion that a reviewer can follow quickly.
   

   The workpaper should show the objective, population, sample basis, procedures performed, evidence obtained, exceptions noted, follow-up performed, and conclusion.

What substantive audit procedures for fixed assets usually look like

Substantive audit procedures for fixed assets should respond to the specific assertion at risk. As a result, the procedure mix changes by scenario.

• Existence procedures

Use existence procedures when the risk is that recorded assets do not physically exist or no longer remain under company control.

• • Common procedures:

    • Select items from the FAR and inspect them physically.
    • Match asset ID, description, serial number, location, and condition.
    • Review whether the item appears in use, idle, under repair, or replaced.
    • Corroborate with photo, geolocation, and custodian evidence where appropriate.
    • Investigate any mismatch between the register and the floor.

• Completeness procedures

Utilize completeness procedures when the risk is that real assets are missing from the records.

• • Common procedures:

    • Walk a site, room, warehouse, or production zone and trace selected assets back to the FAR.
    • Review receiving records, capex approvals, and commissioning notes for recent additions.
    • Inspect untagged or temporarily tagged items and determine whether they should be capitalized.
    • Review whether completed projects remain in CWIP even though the asset is already in service.

• Rights and obligations procedures

Use rights procedures when ownership or control is unclear.

• • Common procedures:

    • Inspect vendor invoices, contracts, title documents, or acceptance certificates.
    • Review lease agreements for right-of-use assets.
    • Check whether third-party, customer-owned, or rental equipment is clearly segregated from owned assets.
    • Validate intercompany transfers and internal ownership changes.

• Valuation and allocation procedures

Apply valuation procedures when the asset exists, but the accounting could still be wrong.

• • Common procedures:

    • Vouch cost to source documents.
    • Recalculate depreciation using policy, useful life, residual value, and in-service date.
    • Review useful-life changes, impairments, and idle asset status.
    • Assess whether repairs were expensed correctly or incorrectly capitalized.
    • Review CWIP aging to determine whether capitalization was delayed.

• Presentation and disclosure procedures

Use presentation procedures when the issue is classification or financial statement disclosure.

• • Common procedures:

    • Tie fixed asset classes to disclosure notes.
    • Review whether lease assets, owned assets, and disposals are classified consistently.
    • Confirm that gains or losses on disposal were recorded in the right period.
    • Review whether major restrictions, impairments, or reclassification matters were disclosed as required.

What makes fixed asset audit evidence persuasive?

Fixed asset audit evidence is persuasive when it is relevant to the assertion, reliable in source, timely, and strong enough in combination to support a conclusion. Therefore, the best evidence usually comes from a combination of physical, documentary, and system-based support rather than from a single screenshot or oral explanation.

A simple evidence hierarchy for field teams

For high-risk assets, aim for this combination:

1. Physical sighting.
2. Tag or serial match.
3. Photo or geotagged field record.
4. Source document support.
5. FAR and GL tie-out.
6. Exception follow-up if anything contradicts the first five.

In verification of a fixed asset, what does the auditor check?

In verification of a fixed asset, the auditor checks whether the physical item matches the record and whether the record still makes sense in the real world. That means the auditor checks more than “is it there?” The auditor also checks identity, location, condition, status, ownership clues, and whether anything suggests the accounting should change.

On the floor, the auditor usually checks:

1. Asset identity
   Does the description match the register? Do the tag number, serial number, or equipment ID agree with the record?
2. Exact location
   Is the asset actually in the site, room, line, department, or branch shown in the FAR?
3. Custody or user
   Is the asset with the right team, department, or employee? If not, is there a transfer trail?
4. Condition and usability
   Is the asset operational, idle, damaged, obsolete, or under repair? Does the condition suggest impairment or retirement?
5. Ownership clues
   Does the asset carry company labels, lease markings, customer labels, or service-vendor tags that change the rights analysis?
6. Movement or replacement clues
   Has the asset been replaced, cannibalized, relocated, or split into parts? Is an older asset still on the books after replacement?
7. Evidence capture quality
   Did the field team record the result clearly with date, user, photo, note, and location so a reviewer can rely on it later?

What the floor check does not prove on its own

A physical verification alone does not prove:

• Correct capitalization amount
• Appropriate useful life and depreciation
• Proper derecognition of the replaced asset

That is why strong fixed asset procedures combine fieldwork with document testing and recalculation.

Tests of controls vs substantive procedures for fixed assets

Tests of controls and substantive procedures serve different jobs. Good audit files show that distinction clearly.

A practical way to decide on emphasis is simple:

• If the control environment is weak, expand substantive testing.
• And if the control environment is strong and supported by evidence, use that to target substantive work more efficiently.

What if the auditor cannot observe every site or date?

When the auditor cannot observe every site or the exact count date, the response should be thoughtful, not mechanical. The goal is still to obtain sufficient appropriate evidence through alternative procedures.

1. Roll-back or roll-forward testing
   

   Test assets at a later or earlier date, then reconcile movements between the observation date and the balance-sheet date.

2. Targeted remote evidence
   

   Use supervised video walk-throughs, geotagged photos, mobile verification logs, and follow-up questions for lower-risk or remote sites.

3. Site rotation with risk weighting
   

   Visit the sites with the highest value, highest movement, or worst prior exception history, then use alternative evidence for lower-risk locations.

4. Subsequent event review
   

   Inspect transfer logs, disposal records, repair records, insurance claims, and later-period counts for evidence about the asset’s status at period end.

5. Third-party corroboration where relevant
   

   For leased, warehoused, or managed assets, obtain additional support from the counterparty or operator when appropriate.

6. Expanded exception testing
   

   Increase the sample in categories where alternate procedures are weaker or where contradictions appear.

Special procedures for CWIP, leased assets, impairments, and disposals

Some fixed asset areas deserve separate treatment because the risks are different.

CWIP

CWIP testing should focus on aging, project status, and the trigger for transfer to an in-service asset. Review whether old projects are still active, whether the asset is already operational, and whether borrowing costs, commissioning costs, and direct costs were handled consistently with policy.

Leased assets and leasehold improvements

Leased assets need clean separation between:

• Right-of-use assets
• Owned fixed assets
• Leasehold improvements
• Service or rental items that should not be in the owned asset register

Test the lease agreement, the right-of-use schedule, and the depreciation basis. Then confirm the asset on site matches the lease population where that is relevant to the scope.

Impairment indicators

Impairment testing often begins with physical clues. Idle assets, damaged assets, obsolete devices, and replaced machinery may signal that carrying value needs review. Therefore, field teams should note condition and usage, not just existence.

Disposals

Disposals deserve extra skepticism because a missing asset does not automatically mean theft or error. The asset may have been transferred, scrapped, sold, cannibalized for parts, or replaced. Review approval, disposal support, sale or scrap records, and the derecognition entry. Then confirm that depreciation stopped when it should have stopped.

Sample workpaper wording and evidence examples

A good fixed asset workpaper should let a reviewer answer four questions quickly:

• What was the objective?
• What population and sample were used?
• What evidence was obtained?
• What conclusion was reached?

1: Existence test for distributed laptops

• • Objective
    To test the existence, location, and custody of selected laptops assigned to employees across three offices.
  • Population
    1,284 active laptops in the FAR as of 31 March 2026.
  • Sample basis
    Judgmental sample of 40 laptops selected using value, portability, remote-user risk, and prior exception history.
  • Procedures performed
    Compared FAR details to mobile verification logs. Inspected and sampled laptops physically or through supervised remote verification. Matched asset tag, serial number, assigned user, and current location. Investigated mismatches through transfer records and service-desk tickets.
  • Evidence obtained
    Mobile verification records, timestamped photos, serial-number screenshots, employee acknowledgement logs, and transfer approvals.
  • Exceptions
    Three laptops were not found at the listed location. Two were supported by approved transfer records not yet updated in the FAR. One laptop had no current user confirmation and no disposal support.
  • Conclusion
    Except for one unresolved laptop pending additional investigation, sampled items supported the existence assertion. Register update control over employee transfers requires improvement.

2: Addition vouching for plant machinery

• • Objective
    To test whether selected machinery additions were owned, capitalized in the correct period, and recorded at the correct cost.
  • Population
    26 plant machinery additions during the year.
  • Sample basis
    All additions above the planning threshold plus 5 additional judgmental items near period end.
  • Procedures performed
    Vouched each sample to PO, vendor invoice, GRN, capitalization memo, approval, and in-service evidence. Recalculated capitalized amount and agreed date in service to commissioning support. Verified tag assignment and location where available.
  • Evidence obtained
    Purchase documents, receiving records, capitalization approvals, site commissioning notes, and FAR postings.
  • Exceptions
    One machine was capitalized before commissioning. One invoice included freight and installation support, which was appropriately capitalized. No ownership exceptions noted.
  • Conclusion
    Most sampled additions were recorded appropriately. One period-cutoff exception requires adjustment or a documented rationale.

3: Disposal follow-up for a missing production asset

• • Objective
    To determine whether a recorded missing production asset represented a misstatement, a transfer, or a disposal that had not been recorded properly.
  • Population
    18 assets flagged as missing during physical verification.
  • Sample basis
    Focused testing on all missing assets above the materiality threshold and all assets replaced during the year.
  • Procedures performed
    Reviewed prior-year count result, maintenance logs, transfer history, replacement records, scrap approval, sale proceeds, if any, and GL derecognition entry. Interviewed the site engineer and the finance owner. Inspected replacement asset where relevant.
  • Evidence obtained
    Prior count sheet, maintenance ticket, scrap note, approval email, replacement CAPEX record, and fixed asset disposal journal.
  • Exceptions
    Two assets had been physically scrapped six months earlier, but remained in the FAR and depreciation run.
  • Conclusion
    The missing items represent unrecorded disposals rather than theft. Finance should process derecognition and assess the impact on depreciation expense and net block.

Common exceptions and what they usually mean

Country-specific notes for the USA, India, and the UK

→ USA

For issuer audits, fixed asset procedures should align tightly to the evidence, documentation, risk-response, and sampling logic used under PCAOB standards. In practice, that means the workpaper should clearly tie the procedure to the assertion, show why the sample was chosen, and document enough evidence for reviewer re-performance. Private-company audit teams usually follow AU-C standards instead, but the operational logic remains similar: evaluate evidence quality, respond to assessed risks, and document conclusions clearly.

→ India

In India, fixed asset procedures should not stop at a physical verification checklist. The file should connect the FAR, capitalization support, depreciation logic, and disposal evidence to the audit conclusion. Teams should also maintain strong PPE register support, because statutory audits and CARO-style reporting expectations often depend on whether the entity can show proper records, periodic verification, and how discrepancies were handled.

→ United Kingdom

In the UK, the procedure file should show clear evidence, logic, thoughtful sampling, and accurate class and lease treatment. That matters even more in 2026 because UK reporting teams are working within the FRS 102 change cycle while still needing clean support for PPE recognition, depreciation, and derecognition decisions. Where lease-related assets are in scope, keep right-of-use assets separate from owned assets and test them accordingly.

How software improves evidence capture without replacing auditor judgment

Software improves fixed asset procedures when it strengthens evidence capture, exception handling, and traceability. Software does not replace the auditor’s judgment about risk, materiality, contradiction, or conclusion.

A strong workflow usually helps in five places:

1. Importing the asset population cleanly
   The team starts with a prepared register rather than a broken spreadsheet.
2. Assigning fieldwork clearly
   Auditors can be assigned by site, asset class, or department.
3. Capturing better field evidence
   Mobile verification, photos, geolocation, and live updates improve the quality of existing evidence.
4. Resolving mismatches faster
   Supervisors can review discrepancies, request re-verification, and close evidence gaps while the count is still active.
5. Syncing back to finance systems
   Verified results can feed reconciliation and register updates instead of living in disconnected field files.

That is the real value: not “automation for its own sake,” but better evidence, cleaner audit trails, and less time wasted on rework.

Key takeaways

• Audit procedures for fixed assets should follow assertions, not a generic checklist.
• Physical verification is essential, but physical verification alone does not prove valuation, ownership, or derecognition.
• Strong workpapers link objective, population, sample logic, procedures, evidence, exceptions, and conclusion in one place.
• High-risk areas usually include portable assets, recent additions, old CWIP, recent disposals, and multi-location populations.
• Software helps when it improves evidence quality and traceability, not when it hides weak judgment behind automation.

Conclusion

In summary, effective audit procedures for fixed assets go beyond simple physical checks by linking each assertion to clear tests, reliable evidence, and well-documented conclusions. When teams combine physical verification with document review and accounting validation, they gain a more complete and defensible view of asset accuracy. Organizations that conduct regular fixed asset audits through structured workflows find that exceptions are easier to resolve, audit cycles become more predictable, and financial records reflect ground reality rather than outdated register entries.

Frequently asked questions

Q1: What documents support a fixed asset addition?

Ans: A strong fixed asset addition file usually includes the PO, vendor invoice, GRN, capitalization memo, approval, date-in-service support, and tag assignment or register entry. Together, those documents support ownership, cost, cutoff, and classification.

Q2: How should auditors deal with missing assets?

Ans: Auditors should investigate missing assets through transfer records, disposal support, replacement history, prior counts, and subsequent events. A missing asset can indicate theft, but it can also indicate record lag, weak disposal controls, or simple location errors.

Q3: Can software replace auditor judgment in fixed asset testing?

Ans: No. Software can improve evidence capture, visibility, and workflow discipline, but the auditor still decides which assertions matter, which contradictions are significant, and whether the evidence supports the conclusion.

Author

CA Sunny Shah

Linkedin

Chartered Accountant | 20 Years of Expertise in Automating Fixed Asset Tracking & Management | Driving Digital Transformation in Finance