The asset register: the engineering register, the fixed asset register, and how to reconcile them
Most industrial organisations keep two asset registers: the engineering register in the CMMS, built to maintain equipment, and the fixed asset register in finance, built to account for it. What each holds, why they drift apart, and how to build and keep a reconciliation between them.
Key takeaways
- Most industrial organisations keep two asset registers without quite admitting it: the engineering register in the CMMS, which exists to maintain equipment, and the fixed asset register in the finance system, which exists to account for it.
- They answer different questions, so they are structured differently. The engineering register goes down to the maintainable item. The fixed asset register stops at the unit that was capitalised, which is often a whole plant area.
- Neither is wrong. The problems start when nobody can say how a record in one maps to a record in the other, which is when a capital project disposes of equipment that is still being maintained, or depreciation runs on a crusher that was scrapped two years ago.
- The fix is a reconciliation key: a documented, many-to-one mapping from engineering records to finance records, kept current through management of change.
- An asset register is only as good as the process that updates it. Projects, change-outs and disposals are where registers drift, so that is where the controls go.
Ask a maintenance planner and a financial accountant for the asset register and you will get two different lists. The planner opens the CMMS and shows thousands of items, each one a place a work order can land. The accountant opens the finance system and shows a few hundred lines with a cost, a useful life and a book value. Both are called the asset register, and both are right.
The two exist for different reasons. The engineering register is there to maintain the equipment, so it is structured by what the equipment does and where it is. The fixed asset register is there to account for the money, so it is structured by what was bought and when. Trouble starts not because there are two, but because nobody has written down how a record in one maps to a record in the other.
This guide covers what each register is for and what it holds, how the two relate, why they drift apart, how to build and keep a reconciliation between them, and what a good register looks like on either side.
Two registers, two purposes
The differences are structural rather than a matter of quality. Each register is shaped by the question it exists to answer, and forcing one into the shape of the other produces a register that serves neither.
In the CMMS
Engineering asset register
- Crushing plant
- Primary crushing circuit
- Primary crusher
- Lubrication system
- Lube oil pump
Down to the maintainable item
In the finance system
Fixed asset register
- FA-10421 · Primary crushing circuit
- Cost, in-service date
- Useful life, depreciation method
- Accumulated depreciation, book value
- Cost centre, disposal
At the unit that was capitalised
| Engineering asset register | Fixed asset register | |
|---|---|---|
| Exists to | Maintain the equipment and record what happens to it | Account for the investment and its depreciation |
| Lives in | The CMMS or EAM | The finance system or ERP asset module |
| Organised by | Function and location, in a hierarchy | Acquisition, project and cost centre |
| Goes down to | The maintainable item, where work orders land | The unit that was capitalised, often a whole area or package |
| Key attributes | Tag, class, make and model, criticality, strategy, bill of materials | Cost, dates, useful life, depreciation, book value, cost centre |
| Changed by | Master data requests, projects, change-outs | Capitalisation, transfers, impairments, disposals |
| Owned by | Maintenance or asset management | Finance |
| Governed by | ISO 14224 taxonomy, site master data standards | AASB 116 and the accounting policy |
One finance record usually covers many engineering records. That is not a defect. It is the relationship the reconciliation has to carry.
What the engineering register holds, and why the hierarchy matters
The engineering register is the set of records in the CMMS that describe every maintainable item: what it is, where it sits, what it is made of and what is done to it. Its structure is the asset hierarchy, the levels from site down to component that ISO 14224 lays out, and the register is only as useful as that structure allows.
A good register puts each item at a level where its history can be found and compared, carries the attributes that decisions need rather than every field the system offers, and links each record to its bill of materials, its documents and its maintenance strategy. The master data that fills those records is what the schedule, the spares and the analysis all depend on, which is why rebuilding it is a project rather than a tidy-up.
- A functional location hierarchy for where things are and what they do, with equipment records for the physical items that occupy those places, so a motor can be swapped without losing the history of the position.
- An equipment class and type for every record, from a controlled list, so like can be compared with like.
- Criticality on every record, because it drives the strategy, the spares and the response to failure.
- Status that reflects reality: installed, in store, under repair, scrapped. A register full of scrapped items marked active is the most common form of drift.
What the fixed asset register holds
The fixed asset register records property, plant and equipment as the accounting standards define it. In Australia that is AASB 116, which sets how an asset is recognised, measured, depreciated and derecognised. Each record carries the cost of the asset, the dates it was acquired and brought into service, the useful life and depreciation method applied, the accumulated depreciation and book value, and its disposal when it leaves.
The unit of account is the decision that shapes everything else. An accountant capitalises at the level that makes the depreciation sensible and the audit defensible, which is usually larger than a maintainable item. A crushing circuit might be one asset with one useful life, or it might be split into the crusher, the structure and the conveyors because they have different lives. That componentisation decision is where the two registers either line up or do not.
Where a significant part of an asset has a different useful life from the rest, the accounting standard expects it to be depreciated separately. That is the hook for reconciliation: the components finance recognises should correspond to levels in the engineering hierarchy, so a major change-out can be capitalised and the replaced component derecognised without a research project.
Why the two registers drift apart
The registers start out aligned when a plant is built, because the capital project hands over both at once. They drift from the first change afterwards, and the changes that cause the most drift are predictable.
- Capital projects that add, modify or replace equipment and update finance through the project close-out but not the CMMS, or the other way round.
- Major component change-outs, where a new gearbox is installed and maintained but the asset it belongs to keeps depreciating the old one.
- Disposals recorded in the CMMS as a status change and never reaching finance, so depreciation runs on equipment that was scrapped.
- Relocations of mobile and relocatable plant between sites and cost centres, with the two systems updated at different times or not at all.
- Insurance spares held in store, which are in the engineering register as equipment and in finance as inventory, or as nothing at all.
- Acquisitions and mergers that bring in equipment with a finance record and no engineering record, or a tag with no history.
Drift is not caused by the registers. It is caused by the change processes that update one and forget the other.
Building the reconciliation
The reconciliation is a key: a documented, many-to-one mapping from engineering records to finance records, held in both systems. In most CMMS and ERP products the natural carrier is a field on the functional location or equipment record that holds the finance asset number, set at the level the asset was capitalised and inherited by everything below it.
The first pass is a one-off exercise. Extract both registers, agree the level of mapping with finance, match what matches, and work through the orphans on each side. The orphans are the findings: equipment being maintained that finance does not know it owns, and assets being depreciated that engineering cannot find. Each one is a decision, to add, to retire or to write off, and the list of them is usually the business case for the work.
Keeping it current is the harder part and the one that lasts. The rule is that any transaction that creates, moves or removes equipment updates both registers in the same approval: project handover, change-out, transfer and disposal. A periodic reconciliation, quarterly or at year end, then catches what slipped rather than rebuilding from nothing.
- Agree the mapping level with finance before touching data. It is usually the level finance componentises at, which should be a level in the hierarchy.
- Carry the finance asset number in the engineering register, inherited downwards, rather than a list of tags in the finance system, which nobody maintains.
- Write the change-out rule down: which component swaps are capital, which are expense, and what each does to both registers.
- Give the key one owner, with the authority to hold a project close-out or a disposal until both registers are updated.
- Report the orphan count on each side as a measure, and expect it to be near zero after the first year.
What a good register looks like, on either side
The test is the same for both. Can a person who did not build it find a record, trust what it says, and see how it connects to the rest? On the engineering side that means a sound hierarchy, controlled attribute lists and a change process. On the finance side it means a componentisation that reflects how the plant is actually renewed, and dates that match the engineering reality.
Both benefit from the same discipline on data quality. ISO 8000 frames master data quality as a matter of specification and conformance: say what a complete record is, then measure how many records meet it. Applied to either register that turns a vague sense that the data is poor into a count of records missing a class, a criticality, a cost centre or a date, and a plan to fix them.
| Test | Engineering register | Fixed asset register |
|---|---|---|
| Complete | Every maintainable item present, none that were scrapped | Every capitalised asset present, disposals derecognised |
| Structured | Every record at the right level of the hierarchy | Componentised to match useful lives and the hierarchy |
| Described | Class, type, attributes and criticality from controlled lists | Cost, dates, life, method and cost centre complete and consistent |
| Connected | Linked to bill of materials, documents, strategy and history | Linked to the engineering records it covers through the key |
| Controlled | Changes through a master data process with an owner | Changes through capitalisation, transfer and disposal controls |
Common mistakes
- Trying to make one register do both jobs, so finance gets a hierarchy it cannot depreciate and maintenance gets a list it cannot work from.
- Capitalising a plant area as one asset with one life, so every component change-out is expensed and the register never reflects renewal.
- Holding the mapping in a spreadsheet that one person understands.
- Treating the reconciliation as a year-end exercise rather than a rule in the change process.
- Rebuilding the engineering register in a new CMMS without carrying the finance key across.
- Leaving scrapped equipment active in the CMMS because deleting feels risky, until the register is a third fiction.
- No owner for the key, so each side assumes the other is keeping it current.
Reconciling the two registers
Agree the level
Where finance componentises, matched to a level in the engineering hierarchy.
Extract and match
Both registers out, matched on tag, location and description.
Resolve the orphans
Each unmatched record becomes an add, a retirement or a write-off, with an owner.
Load the key
The finance asset number on the engineering records, inherited downwards.
Fix the change processes
Projects, change-outs and disposals update both registers in one approval.
Reconcile on a cycle
Orphans counted each quarter, and the number expected to stay near zero.
Agree the level
Where finance componentises, matched to a level in the engineering hierarchy.
Extract and match
Both registers out, matched on tag, location and description.
Resolve the orphans
Each unmatched record becomes an add, a retirement or a write-off, with an owner.
Load the key
The finance asset number on the engineering records, inherited downwards.
Fix the change processes
Projects, change-outs and disposals update both registers in one approval.
Reconcile on a cycle
Orphans counted each quarter, and the number expected to stay near zero.
Common questions
What is an asset register?
An asset register is a structured list of the assets an organisation owns or is responsible for, with the information needed to manage them. In an industrial business there are usually two: an engineering or maintenance asset register, held in the CMMS, listing every maintainable item with its location, attributes and history, and a fixed asset register, held in the finance system, listing the capitalised assets with their cost, depreciation and book value.
What is the difference between an asset register and a fixed asset register?
The engineering asset register exists to maintain equipment and goes down to the level work orders are raised against, which can be thousands of items in one plant area. The fixed asset register exists to account for the money spent and stops at the unit that was capitalised, which may be the whole area. The first is structured by function and location, the second by purchase and project. A single finance record commonly covers many engineering records.
What should an engineering asset register contain?
For each maintainable item: a unique identifier and tag, its place in the functional location hierarchy, equipment class and type, manufacturer, model and serial number, key technical attributes, criticality, install date and status, the bill of materials, the maintenance strategy that applies, and links to its documents and history. ISO 14224 gives a taxonomy and attribute set for most equipment classes.
What should a fixed asset register contain?
For each capitalised asset: an identifier, description and location, the acquisition date and cost, the capitalisation and in-service dates, useful life and depreciation method, accumulated depreciation and book value, any impairment or revaluation, the cost centre it belongs to, and the disposal date and proceeds when it goes. AASB 116 sets the accounting treatment in Australia.
How do you reconcile the engineering register with the fixed asset register?
Define a key that maps each engineering record to the finance record it belongs to, usually a functional location or equipment at the level the asset was capitalised. Load the key into both systems, reconcile the two lists once to find the orphans on each side, and then keep it current through the change processes: capital projects, major component change-outs and disposals each update both registers in the same transaction.
Who owns the asset register?
The engineering register is owned by maintenance or asset management, with a master data role that controls changes. The fixed asset register is owned by finance. The reconciliation key needs a single owner who sits between them, because when it drifts neither side notices until an audit, an insurance claim or a capital project exposes the gap.
Is an asset register the same as an asset hierarchy?
No. The hierarchy is the structure, the levels from site down to component that organise the register. The register is the content, the records that sit in that structure with their attributes. A register without a sound hierarchy is a flat list that cannot be analysed, and a hierarchy with poor records is a structure with nothing reliable in it.
Key terms
Plain-language definitions from our glossary for the concepts this article leans on.
Standards and further reading
- ISO 14224:2016 Collection and exchange of reliability and maintenance data for equipment (ISO)
- ISO 8000-110:2021 Data quality, master data, exchange of characteristic data (ISO)
- IEC 81346-1:2022 Structuring principles and reference designations (IEC)
- AASB 116 Property, Plant and Equipment (Australian Accounting Standards Board)
- ISO 55001:2024 Asset management system requirements (ISO)
- Data Management Body of Knowledge (DMBOK) (DAMA International)
Related case studies and tools
Related reading
Working through something like this?
See how we approach these initiatives, or tell us what you are dealing with.