FMIS Guides · Fixed asset accounting

Fixed Asset Management Policy and Procedures: A Guide for Finance Teams

Create, review and maintain financial rules and working procedures for your fixed assets.

Practical guidance for financial controllers, finance managers and fixed asset accountants, with sample policy clauses, worked procedures and an editable template.

By John de Robeck · Updated: October 28, 2026 · About 19 minutes to read

Financial policies for tangible fixed assets. Apply the reporting framework and local requirements relevant to your organisation.

Browse fixed asset resources for related guidance. For the wider lifecycle, read the Fixed Asset Management Guide.

Explore FMIS Fixed Asset Accounting
Fixed asset management policy and procedures guide cover showing policy documents, an asset register, equipment and a building.

Understand the requirementsPolicies, procedures and accounting decisions.

Create or improve your policyA practical drafting and implementation process.

Review an existing policyOwnership, updates and evidence that it works.

On this page

What are fixed asset policies and procedures?

An organisation’s fixed asset management policy and procedures set out how it makes, records and reviews decisions about its fixed assets. The policy establishes the requirements and authority. Supporting procedures explain who carries out each task, when it happens and what evidence is retained.

For finance teams, these documents connect accounting judgements with everyday transactions. They should explain how an acquisition reaches the fixed asset register, who approves changes and how the reported balances are checked. A useful document is specific enough to guide a colleague who did not design the process.

Understand the difference between a policy, a procedure and a control

Scroll sideways to view the full table.

One disposal requirement, three connected elements
Element Purpose Example
Policy Establishes the rule and authority. Disposals require authorisation under the approved delegation schedule and notification to finance.
Procedure Explains the steps and handovers. The custodian submits the asset reference and proposed disposal; an authorised person approves it; finance assesses and records the accounting.
Control Prevents or detects an error and provides evidence. A reviewer matches the disposal record, approval, proceeds and register update, and signs off exceptions.

An organisation’s fixed asset policy document can contain accounting policies, financial controls and administrative requirements. They are related, but changing a procedure is not automatically a change in accounting policy. That distinction matters when a document is revised.

Set a clear boundary

This guide focuses on financial policies for tangible fixed assets, or property, plant and equipment. Define how the document connects with procurement, operational custody, lease accounting, intangible assets and inventory policies. Keep physical control requirements for low-value equipment visible even where those items are expensed.

For the broader financial lifecycle, including accounting explanations and calculations, see the Fixed Asset Management Guide. Here, the emphasis is on turning those decisions into clear, maintained working documents.

What should your fixed asset management policy and procedures cover?

Your fixed asset management policy and procedures should define the scope, accounting basis, responsibilities, decision rules, record requirements and review arrangements. Each requirement should have a supporting process and an identifiable owner.

Scroll sideways to view the full table.

Core content for a finance-led fixed asset policy
Policy area Decision to document Supporting evidence or procedure
Purpose and scope Entities, reporting bases, asset classes and exclusions. Scope statement and links to related policies.
Authority Who owns, approves and applies the requirements. Responsibility matrix and delegation schedule.
Recognition and cost Recognition criteria, thresholds, grouping and cost assessment. Capitalisation checklist and approval record.
Depreciation and valuation Methods, estimates, measurement basis and review requirements. Approved class schedule and review evidence.
Register governance Required fields, authoritative records and change access. Data definitions and change procedure.
Verification and reconciliation Coverage, frequency, review and exception resolution. Verification plan and reconciliation procedure.
Transfers and disposals Authority, notifications and accounting responsibilities. Transfer and disposal records.
Evidence and retention Documents retained, location, access and retention basis. Evidence schedule and records-retention policy.
Maintenance of the policy Review cycle, triggers, approval and communication. Document history and change log.

The policy does not need to reproduce every system instruction. Keep stable rules in the policy, detailed steps in procedures and frequently changing information in controlled schedules. Link them clearly, with an owner for each document.

How do you create or review a fixed asset policy?

Start with the decisions and transactions the organisation needs to control. Review how work is actually completed before drafting the requirements. An existing document can often be improved through targeted changes rather than a complete rewrite.

  1. 1. Establish the reporting and operational scope

    List the entities, accounting frameworks, asset classes, locations and teams covered. Identify local requirements, funding conditions and specialist policies. State which requirements apply throughout a group and where an approved local schedule is needed.

  2. 2. Gather the current evidence

    Collect the policy, procedures, delegation schedule, register fields, ledger mappings and relevant audit findings. Ask the people completing the work to show a recent addition, adjustment and disposal. Document differences between the written process and actual practice.

  3. 3. Identify decisions and gaps

    Record unclear thresholds, inconsistent classifications, missing approvals and unresolved reconciliations. Prioritise gaps by the risk of financial misstatement, loss or delayed reporting. Assign an owner and a proposed action rather than collecting observations without follow-up.

  4. 4. Draft requirements and supporting procedures

    Use role titles, defined records and clear deadlines. Replace wording such as ‘promptly’ with a deadline suited to the close timetable. A procedure should explain what happens if information is incomplete or a transaction falls outside the normal process.

  5. 5. Test representative transactions

    Walk through a straightforward purchase, a mixed-cost invoice, a completed project, an estimate change and a disposal. Check that a colleague can identify the decision, approver, required evidence and final record. Amend impractical requirements before approval.

  6. 6. Approve, communicate and follow up

    Obtain approval under the organisation’s governance arrangements. Publish the current version, withdraw superseded instructions and explain changes to affected teams. Review the first reporting cycle after implementation for questions, missed handovers and exceptions.

Reviewing an existing policy?

Start with changes since the last approval and recurring problems. An unchanged cover date does not show whether a policy still fits the business; a new version number does not demonstrate that the controls operate.

Which accounting decisions must the policy document?

The policy should identify the accounting decisions that affect recognition, measurement and reporting, and the people authorised to make them. Describe the required assessment and evidence without treating a convenient system default as an accounting conclusion.

Identify the applicable reporting framework

Specify the framework, reporting period and applicable version of the requirements. IFRS reporters should refer to IAS 16 for property, plant and equipment; UK and Irish entities applying FRS 102 should refer to the relevant sections and amendments. US GAAP reporters should use the applicable FASB Codification requirements, including Topic 360 where relevant. These bases are not interchangeable. [1] [2] [5]

For public bodies, charities and funded organisations, record additional reporting directions or restrictions that apply. A general group policy should not conceal a local requirement, and a local exception should not silently change the group reporting basis.

Recognition, thresholds and asset classes

Document the recognition assessment, approved classes, treatment of groups and components, and the basis for any capitalisation threshold. Explain who considers materiality and unusual purchases. A threshold should support consistent decisions, rather than replace consideration of the relevant accounting requirements.

Keep separate schedules for capitalisation thresholds, purchase-approval limits and physical-control requirements. They answer different questions. A purchase below the capitalisation threshold can still require approval and custody records.

Capital expenditure, repairs and subsequent costs

Specify who reviews mixed invoices, replacements and improvements, and how the conclusion is supported. Require enough information about the work to assess it, rather than accepting a supplier’s description as the accounting decision. Consider whether an existing component also needs removal from the records.

Under IAS 16, directly attributable preparation costs and day-to-day servicing have different treatment; qualifying replacements also require consideration of the replaced part. Use these principles to design the assessment, with detailed calculations in the parent guide. [1]

Assets under construction and available-for-use dates

Assign responsibility for reviewing incomplete balances, confirming completion and notifying finance. Require completion or commissioning evidence and an approved assessment of the relevant date. Include staged completion, abandoned work and late supplier invoices in the procedure.

Under IAS 16, depreciation begins when the asset is available for use. The policy should therefore explain how finance obtains that information, rather than relying only on invoice or payment dates. [1]

Depreciation methods, useful lives and residual values

Maintain an approved class schedule and a process for supported exceptions. Record who proposes estimates, who approves them and how changes reach the relevant books and future calculations. Identify the review required by the reporting framework.

IAS 16 requires review of useful lives, residual values and the depreciation method at least at each financial year-end. FRS 102 uses indicators of significant changes to trigger review of estimates and methods. A regular internal review timetable can support the process while preserving this distinction. [1] [2]

Impairment, revaluation and derecognition

Set a route for operational teams to report damage, obsolescence, changed use or closure plans. Assign the accounting assessment to finance and involve specialists where necessary. Separate an impairment assessment from any revaluation process. IAS 36 distinguishes indicator-based assessments for many assets from the annual tests required for specified assets. [3]

Document the approval and evidence required when an asset leaves the accounts. Under IAS 16, derecognition occurs on disposal or when future benefits are no longer expected from use or disposal. A fully depreciated asset is not automatically a disposal. [1]

Separate books, entities and tax records

State which book supports each reporting purpose and who maintains its rules. Distinguish transfers within an entity from transfers between legal entities. Where tax treatment differs, identify the separate tax record and reconciliation responsibility rather than assuming accounting depreciation determines tax relief.

Who should own, approve and operate the policy?

A named finance role should own the policy, with approval at the level required by the organisation’s governance. Day-to-day procedures need separate task owners, reviewers and operational contacts.

Scroll sideways to view the full table.

Illustrative responsibilities to adapt to your organisation
Role Typical responsibility
Finance director or equivalent Sponsors the policy and approves significant matters within delegated authority.
Financial controller or policy owner Maintains requirements, resolves interpretation questions and oversees reviews.
Fixed asset accountant or finance preparer Assesses transactions, maintains financial records and prepares reconciliations.
Finance reviewer Challenges significant decisions, approves relevant entries and reviews exceptions.
Budget holder and procurement Provide authorised purchase information and identify expenditure needing assessment.
Custodian, project lead or operational team Confirm receipt, readiness, custody, movements, condition and proposed disposal.
System administrator Maintains authorised access and configuration through the change process.

Use a delegation schedule to specify transaction types and approval limits. State who acts when the usual approver is absent. Avoid giving someone unrestricted ability to request, approve, record and review the same transaction.

Make smaller-team arrangements explicit

Where duties cannot be fully separated, document an alternative review by an appropriately authorised person. For example, a finance lead can review the register change report against source evidence and journal records. Explain the population reviewed, timing, evidence and escalation of concerns.

Internal or external audit can challenge the design and operation of controls. Management remains responsible for approving and operating its policy.

What procedures should support the policy?

Supporting procedures should cover the financial events and period-end tasks needed to apply the policy. Give each procedure a clear trigger, owner, sequence, approval, evidence requirement and exception route.

Scroll sideways to view the full table.

Procedures and their expected outputs
Procedure Expected output
Acquisition and capitalisation Approved assessment, complete register record and connected accounting entry.
Changes and transfers Authorised change with effective date and consideration of entity and book implications.
Depreciation and close Reviewed processing results, approved journals and explained exceptions.
Register-to-ledger reconciliation Agreed balances, investigated differences and reviewer sign-off.
Estimate and valuation reviews Supported conclusions, approved changes and updated calculations where needed.
Verification Coverage and findings connected to investigated exceptions and approved updates.
Disposal, loss and write-off Approved event, accounting assessment, updated records and retained history.

Worked procedure: reconcile the register to the ledger

The following is an illustrative monthly procedure. Adapt its frequency and deadlines to the organisation’s reporting timetable and risk assessment.

  1. Define the population. The preparer confirms the entity, accounting book, period, currency and included asset classes. Save the report parameters.
  2. Obtain consistent records. Export the register balances and relevant ledger accounts for the same cut-off. Confirm processing status and sign conventions.
  3. Compare the balances separately. Reconcile cost, accumulated depreciation and impairment, with other relevant movements. Do not rely only on matching net book value.
  4. Investigate differences. Check late additions, direct journals, duplicate postings, mapping errors and unprocessed disposals. Give each difference an explanation, owner and target resolution date.
  5. Approve corrections. Obtain the required approval before posting adjustments. Confirm that a correction has reached all affected records.
  6. Review and close. The reviewer checks the reconciliation and significant items. Retain the signed evidence and carry unresolved differences into the exception log.

Required evidence: report extracts and parameters, account mapping, reconciliation, supporting explanations, approved corrections and review sign-off. Specify where these records are stored and who can retrieve them.

Worked procedure: process an asset disposal

  1. The custodian identifies the asset, proposed method, reason and expected event date.
  2. Finance checks the record and any funding, ownership or other restrictions, then routes the request under the delegation schedule.
  3. The authorised approver records the decision before the proposed action, except where an emergency procedure applies.
  4. The responsible team confirms the actual event and supplies the relevant sale, collection, recycling or other evidence. Refer data-bearing equipment to the information-security disposal process.
  5. Finance determines the accounting date and treatment, records proceeds and removes the appropriate balances. A missing item is investigated before its accounting treatment is decided.
  6. A reviewer checks the disposal evidence and accounting. Update custody records and preserve the historical asset record.

Approval is one step in the process. The control is incomplete if an approved disposal never reaches the register or the accounting entry is unsupported.

How do you keep fixed asset policies and procedures current?

Give the policy a review owner, a scheduled review date and defined triggers for earlier reassessment. Maintain a change record that explains the decision, approval, effective date and action required by affected teams.

Use a scheduled review and event-driven updates

An annual policy review is a practical starting point for many organisations, rather than a universal accounting requirement. Review earlier when standards, reporting arrangements, asset populations or business processes change.

Useful triggers include an acquisition, a new entity or country, new funding conditions, an ERP or asset-system migration, new asset classes, revised delegations, staff changes and recurring reconciliation or audit findings. Check whether the policy, procedure, system configuration and training all need amendment.

Classify the change before changing the accounting

Scroll sideways to view the full table.

Different changes need different assessments
Change Example Finance response
Administrative procedure A new approval form or document location. Update instructions, access and communication; check whether any control changes.
Accounting estimate New information changes an asset’s expected remaining use. Assess and support revised estimates and their effect under the applicable framework.
Accounting policy A proposed change in measurement basis. Assess whether permitted, transition requirements and disclosures before implementation.
Error correction A material transaction was recorded incorrectly. Determine the correction and reporting implications rather than treating it as a new estimate.

Under IAS 8, estimate changes arising from new information are generally recognised prospectively. Accounting policy changes and errors have different requirements, including relevant transition provisions and materiality considerations. Document the assessment before changing historic records. [4]

Control versions, exceptions and communication

Record the document owner, approver, version, effective date, next review date and linked schedules. Archive superseded versions with their effective periods, and make the current version easy to find. Retain the evidence behind material judgements under the organisation’s retention requirements.

Log exceptions with a reason, authorisation, scope, expiry or review date and any alternative control. An approved process exception cannot override the applicable accounting requirements. Review repeated exceptions as a possible sign that the policy or process needs attention.

Explain changes to the people who request purchases, confirm project completion and report disposals, as well as finance. Review implementation after the next relevant reporting cycle.

How can you check whether the policy works in practice?

Check both the written requirements and evidence from real transactions. A current policy document is useful only when people can follow it and reviewers can establish what happened.

  • Scope: can colleagues identify which entities, assets and reporting bases are covered?
  • Decisions: are unusual capitalisation and estimate decisions supported and approved?
  • Responsibilities: does each handover have a task owner and deadline?
  • Records: can a register change be traced to its source information and authority?
  • Reconciliation: are differences investigated, assigned and resolved?
  • Disposals: do operational notifications reach the financial records?
  • Exceptions: are temporary arrangements reviewed rather than becoming undocumented habits?
  • Maintenance: do procedures and configuration reflect the current approved requirements?

Turn findings into specific actions

Choose a manageable set of recent transactions across different teams or asset classes. Record the requirement tested, evidence examined, finding, owner and completion date. This is a management review of policy implementation; it does not replace an external auditor’s work.

Warning signs include inconsistent treatment of similar purchases, unexplained journals to asset accounts, unresolved differences carried forward, missing completion dates and approvals held only in personal inboxes. Investigate the cause before adding another form or instruction.

Keep this review distinct from a detailed physical asset count. The question here is whether financial requirements and controls operate, including the follow-up of verification findings.

Fixed asset policy template and sample wording

A fixed asset policy template provides a starting structure. It needs local accounting decisions, responsibilities and approvals before adoption. Use the editable companion to record those decisions and connect the policy with its supporting procedures.

Download the editable policy template

The template includes scope and document control, an accounting decisions schedule, a responsibility table, a procedure record, an exception log and a review checklist. Complete the decision fields and remove instructions that do not apply. Keep this webpage available alongside the template for explanation.

Sample provision: capitalisation decisions

Finance will assess expenditure against the applicable accounting requirements and the approved capitalisation schedule. The assessment will identify the relevant asset or component, eligible costs, entity and reporting book. Matters outside the schedule will be referred to the policy owner for a documented decision before the financial record is finalised.

Complete locally: reporting framework; thresholds and their materiality basis; grouped purchases; component treatment; reviewer; approval authority; supporting documents; and the procedure for incomplete information. The sample deliberately does not set a monetary threshold.

Sample provision: reconciliations

The designated preparer will reconcile the fixed asset register to the relevant ledger accounts at the frequency stated in the close timetable. Differences will be explained and assigned for resolution. The designated reviewer will record the review and approval of corrections, with unresolved matters retained in the exception log.

Complete locally: entities and books; frequency; cut-off; preparer and reviewer; deadline; escalation criteria; evidence location; and closure requirements.

Sample provision: disposals and write-offs

Asset disposals and write-offs will follow the approved delegation schedule. The responsible team will notify finance of the event and provide the required evidence. Finance will assess the accounting treatment, update the relevant records and retain the authorisation and transaction history.

Complete locally: transaction types; approval limits; restrictions; notification deadlines; emergency and loss procedures; proceeds handling; data-security handover; and required review evidence.

How can software support fixed asset policies and procedures?

Fixed asset accounting software can help finance apply agreed rules consistently, maintain financial records and examine movements. Its configuration, access and outputs should reflect the approved policy and the checks performed around it.

FMIS Fixed Asset Accounting supports multiple entities, accounting books and currencies, with depreciation and reconciliation reporting. These capabilities can support different reporting requirements within one financial asset process. The finance team remains responsible for selecting appropriate inputs, approving judgements and reviewing results.

When assessing a system, test a representative addition, estimate change, reconciliation and disposal. Check what evidence is available, who can change key data and how exceptions are handled. Include migration and configuration changes in the policy implementation plan.

Explore FMIS Fixed Asset Accounting

Common questions about fixed asset policies

Yes, a group can establish common governance and processes, with controlled schedules for local requirements. Identify the reporting basis for each entity and book, differences requiring approval and the relationship with group reporting. A single document should make those differences visible.

Some expensed items still need custody or tracking records because they are portable, sensitive or important to operations. Define the physical-control requirement separately from the accounting threshold. Record which team maintains the information and how losses or disposals are reported.

A template needs adaptation to the organisation’s framework, assets, responsibilities, systems and approval arrangements. Test it with actual transactions and obtain the required approval. Sample wording alone does not establish that the accounting decisions or controls are appropriate.

Software supports processing and records, while procedures explain responsibilities, evidence, reviews and exceptions. Document how the system is configured and used within the approved process, including the work that happens outside it.

Related fixed asset guidance

Use the Fixed Asset Management Guide for the wider financial lifecycle and accounting examples. Browse the fixed asset resources hub for related guidance and resources.

Sources and further reading

The practical procedures and sample clauses are drafting aids. Apply the accounting standards, reporting directions and local requirements relevant to the entity and period. Organisational examples do not set universal thresholds, approval limits or useful lives.

  1. IFRS Foundation: IAS 16, Property, Plant and Equipment. Recognition, measurement, depreciation and derecognition; in particular paragraphs 12-13, 51, 55, 61 and 67.
  2. Financial Reporting Council: FRS 102. Check the edition and amendments applicable to the reporting period; Sections 10, 17 and 27 cover relevant policy, PPE and impairment matters.
  3. IFRS Foundation: IAS 36, Impairment of Assets. Relevant indicators and assessment requirements.
  4. IFRS Foundation: IAS 8. Accounting policies, changes in estimates and errors; use the version applicable to the reporting period.
  5. FASB Accounting Standards Codification. Starting point for applicable US GAAP, including Topic 360 where relevant.
  6. Harvard Financial Policy Office: Financial Management of Property, Plant and Equipment. An example of structuring an institutional policy and supporting procedures, not a rule for other organisations.