Asset register package
The financial register, the technical register and the crosswalk between them, generated together as one Excel workbook. The two registers share the asset tag, and every column states the requirement behind it.
The seamThe two registers that describe the same asset for different purposes, and the traceability between them.
What the package holds
Three sheets, generated together in one Excel workbook: a financial fixed asset register, a technical maintenance register, and a crosswalk between them. The financial and technical registers begin with the asset tag. The crosswalk carries the technical and financial tags that join their rows. Every column names what requires it: a clause, a formula, or this publication.
There are two registers because they answer to different people. The financial register exists so the accounts can be produced and defended, and holds cost, useful life, depreciation and carrying amount at the level finance stands behind. The technical register exists so the asset can be operated and maintained, and holds location, criticality, condition and the date it was first energised. They describe the same assets at different levels of detail, and neither can stand in for the other.
The crosswalk records which maintainable items sit inside which financial line, how each is treated in the accounts, and where the two registers disagree, for example a planned replacement interval that differs from the useful life.
The shared asset tag is what makes the two registers traceable to each other. Traceability is a property of the pair, not of either register alone. Generating the registers together puts the same tag at the start of every row in both, from the first one.
The download is one workbook holding the three sheets, an example row if you want one, and a sources tab listing what requires each column. A single register can be downloaded on its own, and the column list for any register prints from this page. The package is a starting structure to adapt to the entity’s own asset classes and owners; a Saudi government entity uses the Ministry of Finance’s own forms instead, as the first choice below explains.
It changes the answer completely. A government entity records its assets on the ministry's own forms; everybody else has to choose.
No template is mandated, so these three are ours: two registers sharing one key, and the crosswalk between them.
The register sheets contain the header row, the example row if you asked for it, and nothing else: no banner, no notes, nothing anybody has to delete before a filter or a formula works. The mark and the reasoning are on the sources tab, in the file properties and in the printed page header and footer, none of which touches a cell. The header row is frozen, the columns are widened to fit, the column names repeat on every printed page and so does the asset tag. Numbers arrive as numbers, so a cost column sums without being converted first. The workbook is assembled in this browser without a third-party library.
Financial fixed asset register
2026-10-01. projects-advisors.com/tools/registers
One of the three sheets of the asset register package, whose two registers share the asset tag.
Financial fixed asset register. So the accounts can be produced and defended: cost, life, depreciation and carrying amount at the level finance must stand behind. Kept by the financial controller.
| Column | What it holds, and what requires it |
|---|---|
| Asset tagRequired | The shared key. The same string identifies this thing in the technical register, which is what makes the two traceable.This publication. One key shared by both registers is what lets each record be found in the other. ISO 55001:2024 treats data and information in Clause 7.6; the shared key is not attributed to it. ISO/TS 55010 is ISO’s guidance on aligning financial and non-financial functions. What this proposal rests on, and what would show it wrong. |
| DescriptionRequired | What the thing is, in words an engineer would also use. |
| Component of | The tag of the asset this is a component of. Blank where this row is the asset itself. This column is what turns a flat list into the component structure paragraph 41 requires.IPSAS 45, paragraph 41: each part of an item with a cost or value significant in relation to the total shall be depreciated separately. Paragraph 43 requires the remainder to be depreciated too. |
| Asset classRequired | The class the accounts group and disclose this under. |
| Cost or valueRequired | The amount carried. Record the basis in the next column rather than leaving it to be inferred. |
| Basis of the amountRequired | Whether this figure was traced to source records or apportioned from a package total, and if apportioned, on what. A cost that was apportioned is an estimate, and it is the basis of a charge that runs for decades.This publication. IPSAS 45 requires the amount; nothing requires you to record how you arrived at it. On a project that captured cost by contract rather than by asset, that provenance is the difference between a defensible register and an undefendable one, and it is unrecoverable a year later. What this proposal rests on, and what would show it wrong. |
| Date available for useRequired | When depreciation begins. Not the certificate date unless the certificate actually evidences capability.IPSAS 45, application guidance AG27: depreciation begins when the asset is available for use, meaning in the location and condition necessary for it to be capable of operating in the manner intended by management. |
| Evidence of capability | What establishes that the asset was capable of operating as management intended on that date. Usually the commissioning record; frequently, in practice, a taking-over certificate written for another purpose entirely.This publication. AG27 sets a capability test and says nothing about evidencing it, so the column exists to make the judgement visible rather than assumed. An auditor asking why this date was chosen is asking for this cell. What this proposal rests on, and what would show it wrong. |
| Useful life, yearsRequired | The period over which the asset is expected to be available for use by this entity. An estimate about the entity, not a property of the equipment.IPSAS 45, paragraph 8 for the definition and paragraph 47 for allocating the depreciable amount over it. |
| Basis of the life | Where the figure came from: a published dataset, a manufacturer, a policy table, or a judgement. A round number with no basis recorded is the commonest finding in a converted register.ASHRAE Service Life and Maintenance Cost Database for observed lives by equipment type, reported with range and standard deviation. |
| Residual value | Reviewed annually alongside the useful life.IPSAS 45, paragraph 48: the residual value and the useful life shall be reviewed at least at each annual reporting date. |
| Depreciation methodRequired | Reflecting the pattern in which the benefits are consumed.IPSAS 45, paragraph 57, with paragraph 58 requiring the method to be reviewed at least at each annual reporting date. |
| Accumulated depreciationRequired | The running total of the charge since the asset became available for use. Computed, not recorded: the depreciable amount divided over the useful life, accumulated to the reporting date.IPSAS 45, paragraph 47: the depreciable amount of an asset shall be allocated on a systematic basis over its useful life, with the charge recognised each period under paragraph 45. Net book value cannot be stated without this figure, which is what makes a derived column mandatory rather than optional. |
| Net book valueRequired | Cost or value, less accumulated depreciation, less any impairment. The figure that appears on the balance sheet and the one a renewal case is argued against.IPSAS 45, paragraph 47 for the allocation and paragraph 59 for impairment, which reduces this figure independently of depreciation. Called carrying amount in the standard and net book value in most systems; the header uses the term a controller will recognise on their own screen, and this note records that they are the same thing. |
| Life last reviewedRequired | The date the useful life and residual value were last actually examined, not the date the register was last edited. This is the column that makes paragraph 48 auditable, and the column whose absence explains why so many registers still carry the lives set at conversion.IPSAS 45, paragraph 48, and paragraph 49: where maintenance policies exacerbate wear, the useful life should be reassessed. |
Computed from
- ISO 55001:2024, asset management system requirements (2024 edition; read 2026-09-26)https://www.iso.org/standard/83054.html
- IPSAS 45, property, plant and equipment (2023, effective 1 January 2025; read 2026-09-01)https://www.ipsasb.org/publications/ipsas-45-property-plant-and-equipment
- IPSAS 33, first-time adoption of accrual basis IPSAS (2015, as amended; read 2026-08-20)https://www.ipsasb.org/publications/ipsas-33-first-time-adoption-accrual-basis-ipsas-standards
- ASHRAE Service Life and Maintenance Cost Database (live database; read 2026-09-26)https://costdatabase.ashrae.org/service_life.asp