Last reviewed: July 2026.
A fixed asset database is the operational record behind property, plant and equipment balances. It should show what the entity owns or controls, where each asset is located, its accounting history and who is responsible for it.
The database becomes reliable only when additions, changes, depreciation, impairments and disposals are controlled and reconciled to the general ledger.
Define the purpose and scope
The register should cover material property, plant and equipment and any lower-value items the entity chooses to control operationally. Accounting and safeguarding thresholds may differ.
Define whether leased assets, assets under construction, spare parts, components and fully depreciated assets remain in the database and how they are identified.
Core asset fields
| Field group | Examples |
|---|---|
| Identity | Asset ID, description, serial number, barcode |
| Ownership and location | Entity, site, department, custodian |
| Accounting | Cost, in-service date, class, useful life, method, residual value |
| Movement | Transfers, improvements, impairment, revaluation, disposal |
| Evidence | Invoice, purchase order, approval, photograph, title document |
Mandatory fields should reflect reporting and operational needs. Free-text descriptions alone are rarely enough for effective verification.
Additions process
New assets should originate from approved capital expenditure, procurement or project records. Finance verifies that the item meets the recognition policy and determines cost, component structure and in-service date.
The asset ID should be created once. Duplicate detection using invoice, serial number and purchase order reduces double capitalisation.
Assets under construction
Projects not yet available for use are normally tracked separately and are not depreciated as operating assets. Costs should be reviewed for capital eligibility and impairment indicators.
Completion requires a documented handover, transfer to the correct asset class and a confirmed available-for-use date.
Component accounting
Significant parts with different useful lives may require separate records. The database should connect components to the parent asset while preserving separate cost and depreciation schedules.
When a component is replaced, the old component’s carrying amount should be identified and derecognised rather than leaving both old and new components in the register.
Location and custodian controls
Transfers between sites or departments should use authorised movement records. Custodian confirmations and barcode scans can support periodic verification.
Assets found in a different location are not automatically accounting disposals, but unexplained movement can indicate weak safeguarding or inaccurate records.
Depreciation master data
Asset class, useful life, residual value, method and depreciation start date drive automated charges. Changes to these fields should be restricted and logged.
Exception reports should identify zero-life assets, negative residual values, depreciation beyond cost, fully depreciated assets still in use and assets available for use but not depreciating.
Impairment and revaluation
The database should record impairment tests, losses, reversals where permitted and revaluation dates. Supporting valuation reports and approvals should be linked or referenced.
Future depreciation must use the revised carrying amount. Changes should reconcile across the asset database, general ledger and disclosure schedules.
Repairs, improvements and subsequent expenditure
Repairs maintain existing service potential and are generally expensed, while qualifying improvements or replacements may be capitalised. The database should link capital additions to the affected asset.
Policy rules and review are needed because invoice descriptions such as repair or upgrade do not determine accounting treatment.
Disposals and retirements
Disposal workflow should capture authorisation, date, proceeds, buyer, removal from service and evidence of sale, scrapping or loss. Both cost and accumulated depreciation must be removed.
Assets should not disappear from the database merely because a user deletes a row. Disposal status, journals and audit history should remain available.
Physical verification
Periodic counts test existence, location, condition and use. Select samples from register to floor and from floor to register so both existence and completeness are tested.
Count differences should be investigated and approved before adjustment. The process can identify idle assets, impairment indicators and unrecorded transfers.
General ledger reconciliation
| Reconciliation layer | Control |
|---|---|
| Opening balance | Agree register to prior-year closing ledger |
| Additions | Agree to capital invoices and ledger postings |
| Depreciation | Agree monthly charge and accumulated depreciation |
| Disposals | Agree cost, accumulated depreciation, proceeds and gain or loss |
| Closing balance | Agree by asset class to financial statements |
Reconciling only the net book value can hide offsetting errors. Compare gross cost and accumulated depreciation separately.
Access, audit trail and cybersecurity
Role-based access should separate asset creation, approval, depreciation processing and disposal. Privileged changes require monitoring.
Maintain backups, change logs and tested recovery procedures. Interfaces from procurement, projects and the general ledger should use control totals and rejection reports.
Management reporting and useful analytics
Useful reports include capital expenditure against budget, asset age, fully depreciated assets in use, idle assets, missing tags, overdue verification and disposal proceeds.
Analytics should support decisions without replacing evidence. A dashboard is only as reliable as the master data and reconciliations beneath it.
Related Accounting Support guides
- Fixed Asset Register: Fields, Controls and Reconciliation
- Fixed Asset Register and General Ledger Reconciliation
- IAS 16 Property, Plant and Equipment Disclosures Checklist
Official sources
- IFRS Foundation: IAS 16 Property, Plant and Equipment
- U.S. GAO: 2025 Green Book—Standards for Internal Control
Key takeaway
A controlled fixed asset database links physical assets, approved evidence and accounting records. Protect master data, preserve change history and reconcile cost and accumulated depreciation by asset class every period.