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

Audit procedures for fixed assets connect assertions like existence, completeness, and valuation to clear tests, evidence, and conclusions. When aligned with a structured physical asset verification process, they produce audit-ready records, reduce exceptions, and strengthen financial accuracy.
Audit-Procedures-for-Fixed-Assets-Assertions-Tests-Evidence-Sample-Workpapers
In this article
    Our Products
    icon-1

    Asset Verification Software

    Automate your physical asset verification with our mobile technology.

    Icon-4

    Asset Tracking Software

    Monitor asset movement, ownership, and status with real-time visibility.

    icon-3

    Fixed Asset Management Software

    Ensure better control over assets throughout their lifecycle.

    Share our Blog

    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 tests auditors perform to obtain sufficient appropriate evidence that fixed assets and related disclosures are recorded correctly. Before examining individual assertions, understand the broader fixed asset audit process, methods, and compliance requirements that guide these procedures. In practice, auditors translate each assertion—existence, completeness, rights, valuation, and presentation—into specific procedures, evidence requests, exception follow-ups, and review-ready conclusions.

    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 checks whether the company has recorded the asset completely, owns or controls it, values it correctly, and presents it 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.

    Assertion Practical question Typical procedures Strongest evidence Common failure mode
    Existence Is the recorded asset real and on hand? FAR-to-floor testing, physical inspection, tag and serial-number match, custodian confirmation Physical sighting tied to tag or serial, dated field evidence, photo, and geolocation, where appropriate Ghost assets, moved assets, replaced assets still on books
    Completeness Are all material assets recorded? Floor-to-file testing, site walk, additions tie-out, CWIP review Asset found in use, plus receiving or capitalization support Unrecorded additions, assets parked in CWIP, and untagged items
    Rights and obligations Does the company own or control the asset? Review invoices, title, lease agreements, acceptance records, and intercompany support Invoice, contract, title, lease agreement, handover record Leased or customer-owned items misclassified as owned assets
    Valuation and allocation Is the cost recorded and depreciated correctly? Vouch additions, recalculate depreciation, review useful life, and assess impairment indicators Original invoice, capitalization memo, policy, recalculation, impairment analysis Wrong useful life, wrong in-service date, duplicate capitalization, stale CWIP
    Presentation and disclosure Is the asset classified and disclosed correctly? Note tie-out, class review, lease, and disposal disclosure checks Financial statement note support and movement schedules Wrong asset class, incomplete disclosure, disposal gains/losses misstated
    Practical Rule
    A physical sighting is powerful evidence for existence, but a physical sighting alone does not prove ownership, correct capitalization, useful life, impairment status, or derecognition.

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

    Assertion Typical risk Core procedures Best evidence combination What does contradicting evidence usually mean
    Existence Ghost assets or moved assets remain in the books Select FAR samples, inspect physically, match description, tag, serial number, and location Physical sighting + tag/serial match + dated field note + photo/geolocation The asset may have moved, been disposed of, been replaced, or never existed as recorded
    Completeness Real assets exist, but were never recorded or capitalized Walk the site, trace assets back to FAR, review GRNs, project handovers, and recent additions Asset in use + receiving support + capitalization evidence + new tag or temporary ID Additional controls may be weak, or handover from project to finance may be delayed
    Rights and obligations Third-party, rented, or customer-owned assets are misclassified Review ownership support, lease contracts, service contracts, and intercompany records Invoice/title/contract + site labeling + lease register where relevant The balance may require reclassification, lease treatment, or scope exclusion
    Valuation and allocation Cost basis, useful life, or depreciation is wrong Vouch additions, recalculate depreciation, test useful-life changes, review impairment triggers Invoice + capitalization memo + depreciation recalculation + policy support The balance may be misstated even though the asset exists physically
    Presentation and disclosure The note disclosures or class mapping are incomplete Tie the FAR classes to financial statement notes, test transfers, and disposals Note support + movement schedule + reviewed disclosure checklist The financial statements may need revised note wording or a class presentation

    What does verification of assets in auditing involve?

    Verification of assets in auditing is the process by which an auditor confirms that the assets on the balance sheet exist, belong to the entity, are in usable condition, and are carried at an appropriate value with proper disclosure. It is broader than a physical count: verification covers existence, ownership, possession, condition, and valuation together, which is exactly what the assertion tables above operationalise.

    The objective of verification of assets is fourfold:

    • Existence — Confirm each recorded asset is real and on hand, not a ghost entry.
    • Rights — Confirm the entity owns or controls the asset, through invoice, title, or lease support.
    • Condition — Confirm the asset is in service and usable, and flag idle, damaged, or obsolete items for valuation review.
    • Valuation and disclosure — Confirm cost, depreciation, and classification are supported and presented correctly.

    Verification and valuation of assets: linked, but not the same

    Verification and valuation of assets are companion exercises, and strong audit files treat them as one chain of evidence. Asset verification answers “is the recorded asset real, owned, and in service?”; valuation answers “is the amount it is carried at correct?”. A machine can pass verification on the shop floor and still fail valuation because its useful life is wrong, its impairment indicators were ignored, or its capitalized cost includes items that should have been expensed. That is why every existence test in this guide is paired with a valuation test.

    Teams use several names for this work. An asset verification audit focuses on the existence-and-condition slice of the procedures on this page; a fixed asset verification audit extends the same discipline across the full register. Whatever the label, the asset verification audit procedures are the same: select from the register, inspect physically, match identity, corroborate ownership and value, and document a conclusion a reviewer can follow.

    In India, this work sits inside the statutory framework: SA 501 addresses the auditor’s evidence over the existence and condition of tangible assets, and CARO 2020 requires the auditor to report whether management has physically verified fixed assets at reasonable intervals and how material discrepancies were dealt with in the books.

    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.

    What-documents-and-data-should-you-pull-before-testing

     

    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

    Area Request first Why it matters
    Additions PO, invoice, GRN, capitalization memo, tag assignment, in-service date support Confirms cost, ownership, and capitalization timing
    Transfers Transfer request, approval, location update, custodian sign-off Confirms that the moved assets were not treated as missing
    Depreciation Policy, useful life master, depreciation run, override logs Confirms valuation and allocation
    Disposals Approval, disposal note, sale or scrap record, accounting entry Confirms derecognition and gain/loss treatment
    CWIP Project register, capex approvals, stage completion notes, commissioning memo Confirms whether an item still belongs in CWIP
    Leases Lease agreement, lease register, right-of-use schedule Confirms classification and depreciation base

    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.

    Risk driver Why it matters Sample priority
    High-value assets A single misstatement can be material Always include individually significant items
    Portable assets Loss, misuse, and movement risk are higher Sample heavily, especially laptops, tablets, tools, and test devices
    Recent additions Cutoff, capitalization date, and ownership errors are common Sample current-period additions and near-period-end additions
    Old CWIP Projects often remain parked too long Sample aging CWIP with no recent movement
    Recent disposals Derecognition failures are common Sample disposals and replaced assets
    Multi-location sites Movement and record-lag risk are higher Sample remote sites and low-visibility locations
    Prior exceptions Errors often repeat Include prior-year exception categories in the new sample

    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.

    How do you turn these procedures into a fixed asset audit work program?

    A fixed asset audit program is the operating document that converts the fixed asset audit procedures above into assigned, trackable work: which areas to cover, which risks matter, which evidence to retain, who prepares and reviews each step, and how exceptions get closed. The distinction is simple — procedures are the tests; the work program is the framework that organises them, and the workpapers are the supporting documentation behind each line.

    The 12-section fixed assets audit work program

    Step Objective Core test focus Expected evidence
    1. Planning and scoping Define the review clearly Confirm entities, locations, asset classes, systems, and exclusions Scope memo, location list, prior-year issues, policy references
    2. Register integrity Confirm the population is usable Tie the fixed asset register to the general ledger and sub-schedules FAR export, GL tie-out, reconciliation notes
    3. Additions and capitalization Prevent unsupported capitalization Review material additions and capitalization triggers PO, invoice, approval, in-service date, tag creation
    4. Tagging and custody Strengthen identity and accountability Confirm tag assignment, custodian data, and location fields Tag register, assignment record, custody trail
    5. Transfers and movement Prevent stale location records Test transfer approvals and updates between sites or users Transfer forms, system logs, and receive acknowledgement
    6. Physical verification — immovable assets Confirm the existence of stable assets Verify site-level presence of plant, equipment, and fixtures Site sheets, photos, scan logs, observer notes
    7. Physical verification — portable assets Address higher movement risk Test laptops, tools, scanners, and shared devices separately User assignment, geotag, scan log, offboarding record
    8. Depreciation and useful-life review Reduce valuation drift Review useful lives, residual values, and fully depreciated assets still in use Depreciation schedule, management review evidence
    9. CWIP and capitalization timing Prevent aged project leakage Review aging, stalled projects, and capitalization triggers CWIP schedule, project status report, commissioning evidence
    10. Lease / ROU assets if material Keep asset population complete Check lease-related assets where relevant Lease schedule, commencement details, site status
    11. Disposals and write-offs Prevent ghost assets and book overstatement Test approvals, removals from the register, and accounting entries Disposal request, sale/scrap proof, journal entry, wipe certificate where relevant
    12. Exception closure and reporting Finish the file properly Assign action owners, due dates, and re-verification steps Exception log, management response, re-check evidence

    Every strong fixed asset audit program follows the same chain: objective → risk → procedure → evidence → owner → result → follow-up. A program line that stops at a checkbox is not usable after fieldwork — add status, exception severity, due date, and re-verification fields so the file still works when the review ends.

    Internal audit, external audit support, and finance audit-prep teams can share this architecture, but each should tailor the emphasis: control objectives and root cause for internal audit, assertions and workpaper cross-references for external audit support, and document owners and readiness status for finance.

    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.

    Evidence type What it proves best Strength Common weakness Best practice
    Physical inspection Existence, location, condition High for existence Does not prove ownership or valuation by itself Pair it with tag/serial match and supporting records
    Original invoice or contract Ownership, cost, date, rights High May not prove current existence Tie it to the FAR and the physical result
    System report from ERP/FAR Population completeness, depreciation, and history Moderate to high Depends on control quality and data accuracy Use with approvals, reconciliations, and exception testing
    Photo with geolocation and timestamp Existence, location, condition Moderate to high Can be incomplete if the tag or serial is not visible Capture the tag, the asset image, and exact location together
    Management explanation Context and follow-up direction Low on its own Not sufficient as standalone evidence Use only to guide additional procedures
    Written representation Closing support on matters not otherwise proven Low on its own Does not replace substantive evidence Use to support, not substitute, other evidence

    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.

    The audit-ready evidence stack: six layers of fixed asset confidence

    A practical way to organise all of this evidence is to think in layers rather than in documents. The audit-ready evidence stack builds fixed asset confidence from the register up to the final report — each layer answers a different risk, and a scan on its own only ever answers one of them.

    Layer Core question Typical evidence
    1. Register integrity Is the master record complete and usable? Asset ID, class, description, cost, date-in-service, location, custodian, status
    2. Identity proof Can each asset be uniquely identified? Barcode, RFID tag, serial number, equipment number, plate number
    3. Physical proof Can the team prove existence, location, and condition? Scan record, photo, timestamp, geo-tag, field note, custodian confirmation
    4. Accounting proof Does finance reflect reality? FAR-to-GL reconciliation, capitalization support, useful life data, and disposal entries
    5. Control proof Were lifecycle events authorized and logged? Approvals, transfer forms, disposal approvals, movement logs, exception workflow
    6. Reporting proof Can management act on the findings? Coverage summary, exception report, financial impact, remediation tracker, sign-off

    The stack separates physical evidence from accounting and control evidence, which is exactly the distinction reviewers look for. A complete file shows register integrity, identity proof, physical proof, accounting proof, control proof, and reporting proof together — and directs each exception to the layer where it actually belongs.

    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.

    In-verification-of-a-fixed-asset-what-does-the-auditor-check

     

    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.

    Area Test of controls Substantive procedure
    Additions Check whether additions require approval and finance review before capitalization Vouch selected additions to PO, invoice, GRN, capitalization memo, and in-service date
    Transfers Check whether transfers require approval and register updates Inspect the moved assets physically and verify the current location against the records
    Depreciation Check whether useful lives and policy tables are maintained through controlled workflow Recalculate depreciation on sampled assets
    Disposals Check whether the disposal workflow requires approval and an accounting update Test sampled disposals to approval, sale/scrap support, and derecognition entry
    Periodic verification Check whether counts occur at the required frequency and discrepancies are reviewed Inspect sampled assets and investigate exceptions directly

    A practical way to decide on emphasis is simple:

    • If the control environment is weak, expand substantive testing.
    • 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.

    Key Point
    Alternate procedures must still respond to the relevant assertion. A later photo may support existence. It will not automatically resolve valuation or rights.

    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. Check whether old projects remain active, whether the asset is already operational, and whether the organization has accounted for borrowing, commissioning, and direct costs consistently with its 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

    Exception What it usually means Immediate follow-up
    Asset not found at the listed location Transfer lag, disposal gap, poor tagging, or ghost asset Review movement logs, prior counts, custodian evidence, and disposal support
    Asset found, but tag missing or wrong Weak tagging discipline or duplicate records Capture serial number, assign corrective action, test for duplicates
    Asset exists, but the description does not match Poor register hygiene or asset replacement without cleanup Review replacement history and record-maintenance workflow
    Asset in use but still in CWIP Delayed capitalization Review commissioning evidence and transfer timing
    Asset capitalized but not yet in service Early capitalization Review the cutoff and policy application
    Leased item treated as owned asset Rights/classification issue Review the lease contract and fixed asset class mapping
    Disposed asset still depreciating Derecognition failure Test disposal approval, accounting entry, and depreciation stop date
    Damaged or idle asset still at full carrying value Potential impairment issue Escalate for valuation review and management assessment

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

    → 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. 

    → South Africa

    In South Africa, audit procedures for asset management in the public sector run against a distinct framework: GRAP governs how municipalities and public entities recognise and measure assets, and the MFMA places responsibility for maintaining a credible asset register and safeguarding assets on the accounting officer.

    Auditor-General audits routinely test the existence, condition, and completeness of movable and immovable assets against that register — so the assertion-to-procedure-to-evidence discipline on this page applies directly, with the GRAP-compliant asset register and dated verification evidence as the anchor documents. Private-sector teams reporting under IFRS follow the same assertion logic as the rest of this guide.

    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. The same approach carries over to technology assets, where an IT asset audit confirms that laptops, servers, and network hardware exist, sit where they should, and reconcile to the systems that govern them.

    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.

    Q4: What should we verify in the audit of an asset?

    Ans: Verify five things: confirm the asset exists and can be physically identified; establish that the entity owns or controls it; check that its location, custodian, and status match the register; assess whether its condition supports its carrying value; and ensure the entity records and discloses its cost, depreciation, and classification correctly. A physical sighting alone covers only the first.

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

    Share our Blog

    Our Products
    icon-1

    Asset Verification Software

    Automate your physical asset verification with our mobile technology.

    Icon-4

    Asset Tracking Software

    Monitor asset movement, ownership, and status with real-time visibility.

    icon-3

    Fixed Asset Management Software

    Ensure better control over assets throughout its lifecycle.

    Subscribe to our Newsletter
    Subscribe and get the latest updates and news about best practices in Fixed Assets Management.

    Contact Us

    Share your details & we’ll connect you with right team.

    Download Template

    To receive this Fixed Asset Audit Work Program Template, please enter your business email ID.