Asset register
A structured record of the assets an entity owns or controls, carrying the attributes needed to recognise them in the accounts and to operate and maintain them.
The term hides a plurality. A financial fixed asset register exists so the accounts can be produced: cost or value, useful life, depreciation and componentisation, at the level finance must defend. A technical or maintenance register exists so the assets can be operated: location, condition, criticality and maintenance history, at the level engineering must act on. They are usually different systems with different owners, and nothing obliges their contents to reconcile.
Accrual conversion is what forces the question, because IPSAS 33 gives a first-time adopter up to three years during which it need not recognise its assets, and the register assembled in that window becomes the opening balance sheet. What is built once, under a deadline, tends to persist for decades.
ISO 55001:2024 treats data and information in Clause 7.6, which ISO/TC 251’s guidance describes as revised in 2024 to clarify how data and information differ. What answers the split is traceability between the registers, and that is a property of the pair, not of either alone.
The same term, through four lenses
01
Project
the delivery team and the contract
The project does not keep an asset register. It keeps a cost ledger, a document register and, near the end, an equipment schedule assembled for handover.
That schedule is where most registers actually come from, which sets their quality permanently. It is compiled under deadline by people leaving, from procurement records rather than from what was installed, and no clause requires it to carry the attributes either of the eventual registers will need.
Fixed by
FIDIC Conditions of Contract, 2017 edition, Sub-Clause 10.1, which requires as-built records and O&M manuals at taking over. It requires no register and specifies no attributes.
Recorded in
The handover schedules and the document register.
02
Engineering
design, commissioning and the technical record
The technical or maintenance register exists so the assets can be worked on. Its unit is the maintainable item, and its attributes are location, criticality, condition, maintenance history and the plan of work due.
Its test is operational: can a technician be dispatched to the right thing with the right instruction. An entry with a correct value and no location fails that test completely.
Fixed by
ISO 55001:2024, Clause 7.5 on documented information and Clause 7.6 on data and information.
Read the sources
- ISO 55001:2024, asset management system requirements2024 edition; read 2026-09-26.ISO’s product page: the publication details and ISO’s own summary of the standard, not the requirement text. The contents, foreword and introduction cited in this publication are taken from the standard’s preview pages hosted on the ANSI webstore, not from this page.
Recorded in
The maintenance management system.
03
Finance
the accounts and the fixed asset register
The financial fixed asset register exists so the accounts can be produced. Its unit is the recognised asset or the separately depreciated component, and its attributes are cost or value, useful life, accumulated depreciation and carrying amount.
IPSAS 45 paragraph 8 declines to prescribe a unit of measure for recognition and permits individually insignificant items to be aggregated, so this register is deliberately coarser than the technical one in places, and it is not a fault when it is.
Fixed by
IPSAS 45, paragraph 8 on the unit of measure and aggregation, paragraph 41 on depreciating significant parts separately, and paragraph 48 on the annual review of useful lives. IPSAS 33 for the transitional relief a first-time adopter may take.
Read the sources
- IPSAS 45, property, plant and equipment2023, effective 1 January 2025; read 2026-09-01.Free in full, with its Basis for Conclusions in the same document. Replaced IPSAS 17 from 1 January 2025.
- IPSAS 33, first-time adoption of accrual basis IPSAS2015, as amended; read 2026-08-20.
Recorded in
The fixed asset register, and the note to the accounts.
04
Operations
the people who run and maintain it
Operations needs both and is usually given neither in a usable state. The questions it asks cross the two: what is failing, what has it cost, what is it worth, and is it due for renewal.
Where the registers do not reconcile, the operator is the one who discovers it, typically when preparing a renewal case that has to state both a condition and a carrying value for the same physical thing.
Fixed by
ISO 55001:2024, Clause 7.6, data and information, and ISO/TS 55010 on aligning the two functions.
Read the sources
- ISO 55001:2024, asset management system requirements2024 edition; read 2026-09-26.ISO’s product page: the publication details and ISO’s own summary of the standard, not the requirement text. The contents, foreword and introduction cited in this publication are taken from the standard’s preview pages hosted on the ANSI webstore, not from this page.
Recorded in
Whatever reconciliation exists between the two registers, if any.
Where the lenses part
Finance against Engineering
The plurality is not the error, and this is where most commentary goes wrong. Two registers with different units, different owners and different tests are the correct answer to two different questions. What is usually missing is traceability between them: the ability to say which financial line a given maintainable item sits in, and which maintainable items make up a given financial line. Without it, the same pump is a component in one register, part of an aggregated line in another, and absent from a third, with nobody able to say which view is complete.
Project against Operations
The register is populated at the moment of least knowledge and used for decades. IPSAS 33 gives a first-time adopter up to three years before it must recognise its assets, and the register assembled in that window becomes the opening balance sheet. What is built once, under a deadline, by people who will not operate the asset, is what the operator is still working from long after everyone who compiled it has gone.
What has to agree, and how you would know
| The datum | Held by | The test |
|---|---|---|
| Identity: which record refers to which physical thing | Engineering, Finance | Pick one physical item and find it in both registers. Then pick one financial line and list the maintainable items it contains. If either lookup requires a person who remembers the project, the traceability does not exist in the records. |
| Terminology | Engineering, Finance, Operations | Compare the naming and classification used in each register for the same category of plant. Different names for the same class are the first thing that breaks any attempt to join them. |
| Completeness against what was built | Project, Engineering, Finance | Take a system from the as-built records and check that every item in it appears in the technical register and is accounted for, individually or in an aggregated line, in the financial one. Absent from both is the failure mode nobody detects, because a missing asset generates no transaction. |
Sources
IPSAS 33, First-Time Adoption of Accrual Basis IPSASs, transitional relief for the recognition of assets. ISO 55001:2024, Clause 7.6, data and information. IPSAS 45 for what the financial register must be able to support.
Read the sources
- IPSAS 33, first-time adoption of accrual basis IPSAS2015, as amended; read 2026-08-20.
- ISO 55001:2024, asset management system requirements2024 edition; read 2026-09-26.ISO’s product page: the publication details and ISO’s own summary of the standard, not the requirement text. The contents, foreword and introduction cited in this publication are taken from the standard’s preview pages hosted on the ANSI webstore, not from this page.