In this guide
The Columns a Fixed Asset Register Needs
A workable register needs eleven columns and no more: tag number, description, class, location, custodian, date of capitalisation, original cost, useful life, depreciation to date, written down value and status. Those eleven let somebody stand in front of an asset and confirm what the books say about it, which is the only test that matters. Identification, location and custodian make physical verification possible, because without them a difference cannot be assigned to anyone or anywhere. Cost, life, depreciation and written down value make the accounting testable. Status distinguishes an asset that is in use from one that is idle, disposed or awaiting write-off, and it is the column most registers are missing. Everything else people add is decoration: supplier name, invoice number, colour, warranty text and free-text remarks all belong in a purchase record, not in a register somebody has to reconcile line by line at the end of a count.
Identification and Description
Three fields identify an asset, and each does a different job. The asset code is the primary key and it is the number physically on the tag, which sounds obvious and is routinely got wrong: registers that hold an internal code in one column and the printed tag number in another have created two identifiers for one asset and guaranteed that they will diverge. One number, in one column, matching what is on the label. The description is the field that lets a person standing in front of the asset confirm they have the right line, and it has to be written for that purpose rather than for accounting convenience. Descriptions like plant and machinery, repeated across forty lines, make matching impossible; a description naming what the thing is and something distinguishing about it makes it straightforward. Make, model and serial number are the third element and they are the corroboration. Where they exist they should be captured, because they are the only attributes an asset carries independently of anything the business attached to it, and they are what allows a line to be matched to a machine when the tag has been lost, painted over or transferred.
Location, Custodian and Movement
Location has to be recorded at the level somebody can actually walk to. Site alone is useless on a large campus, and room-level detail is unmaintainable in a warehouse, so the granularity is chosen per class of asset rather than uniformly: site, building and floor for office equipment; site and department for plant. The test is whether a counter given the register line can find the asset without asking anybody. The custodian field names the person or role answerable for the asset, and it should carry the date it last changed. A custodian field without a date is a field nobody can audit, because there is no way to tell whether it describes the current position or one from four years ago. Naming a role rather than an individual survives staff turnover better and is usually the more useful choice. Movement history is the field most registers omit and the one that makes reconciliation possible. Where each location change is retained rather than overwritten, an asset that cannot be found at its recorded location can be traced through where it has been, and a pattern of unrecorded movement becomes visible as a control finding rather than a series of unexplained exceptions.
Cost, Depreciation and Book Value
The accounting columns are where a register connects to the financial statements, and they need to be complete enough to recompute rather than merely to report. Capitalisation date and cost come first, and the date matters as much as the amount because it is what determines the depreciation charged to date. Cost means the amount at which the asset was brought into the books, including the expenditure directly attributable to bringing it to its location and working condition, so a register holding only the invoice value will not reconcile to the ledger. Method, rate and accumulated depreciation follow. Holding the method and the rate against each line, rather than applying them by class in a separate schedule, is what allows any individual line's charge to be checked without reconstructing the whole calculation. Written down value is then derived rather than stored, since a stored value can drift from its own inputs. Componentisation belongs in the same block. Where parts of one asset have significantly different useful lives and each is significant in cost, they are recorded as separate lines carrying their own dates and rates, because replacing a component in a register that never split it capitalises the same part twice.
Fields the Auditor Will Ask For
Three fields beyond the standard register columns get asked for at every verification, and registers that lack them force the same work to be reconstructed each time. The first is the verification date and result against each line: when the asset was last physically seen, by whom, and what was found. Without it, a register cannot show that verification happened at reasonable intervals, which is precisely what has to be demonstrated. The second is a condition and impairment flag. An asset recorded as present but noted as damaged, idle or awaiting disposal is carrying a value that assumes none of those things, and the flag is what triggers the impairment question rather than leaving it to be discovered. The third is the disposal reference and the approval behind it. When an asset leaves the register, the line should not simply vanish; it should carry the authorisation, the date and the reference of whatever document evidenced the disposal. A register from which lines disappear without trace cannot be reconciled backwards, and a reconciliation that cannot run backwards cannot support the closing figure it produces.
Using the Template Without Breaking It
One row per asset, without exception, is the rule that keeps a spreadsheet register usable. The moment two assets share a row, or one asset spans two, every count, filter and reconciliation performed afterwards returns a number that is quietly wrong. Merged cells are the specific mechanism by which this happens, and they should not appear anywhere in the sheet. A merged cell breaks sorting, breaks filtering, and silently drops rows from any total computed over the range, so a register that looks tidy on screen produces different answers depending on how it is queried. The same applies to blank rows inserted as visual separators and to totals placed inside the data range. A spreadsheet has outgrown the estate when the file is slow to open, when more than one person needs to edit it at once, when nobody can say which copy is current, or when the history of an asset can no longer be reconstructed because rows were overwritten. At that point the answer is a system rather than a better template, and how we tag and track assets sets out what the transition involves.
