A fixed asset register is the authoritative record of every asset an organisation owns: what it is, where it is, who holds it, what it cost, and what it is worth now. It exists for financial reporting and assurance, and it is only as useful as its accuracy at the moment somebody asks.
Most organisations have something they call a fixed asset register. Rather fewer have one that would survive somebody checking it.
The gap usually isn't effort. It's that the register was built for one audience and is now being used by three, and nobody noticed the moment that happened.
What a fixed asset register is for
A fixed asset register is the authoritative record of the assets an organisation owns and expects to use over more than one period. It serves three audiences, and confusion between them causes most of the trouble.
|
Audience |
What they need from it |
The question they ask |
|---|---|---|
|
Finance |
Cost, depreciation and book value |
What are these worth, and what is the charge this year? |
|
Assurance |
Existence and condition |
Can you prove these exist and are accounted for? |
|
Operations |
Location, holder, status |
Where is it, who has it, and is it working? |
A register built only for finance is accurate about value and useless for finding anything. A register built only for operations is current about location and unable to support a year-end. A good one serves all three, which mostly means capturing a few more fields at acquisition.
The fields a fixed asset register must carry
|
Field |
Purpose |
Notes |
|---|---|---|
|
Unique asset identifier |
The primary key |
Flat and meaningless — encoding site or category breaks the first time either changes |
|
Description, make, model |
Identifies the thing |
Specific enough to distinguish two similar units |
|
Serial number |
Manufacturer identity |
The field an insurer and the police will ask for |
|
Category |
Grouping and depreciation policy |
Drives the default useful life |
|
Location |
Where it is |
Hierarchical — site, building, room |
|
Custodian / holder |
Who is responsible |
A named person, not a department |
|
Acquisition date and cost |
The basis of everything financial |
Without both, book value cannot be computed |
|
Supplier |
Provenance and warranty route |
Links to the vendor record |
|
Depreciation method, life, rate |
How value declines |
Agreed with finance, set by category |
|
Current book value |
What it is worth now |
Derived, not typed |
|
Condition and status |
Usable, in repair, retired, lost |
Drives whether it can be issued |
|
Disposal date and method |
Closes the record properly |
Missing disposals inflate every subsequent count |
Fixed asset register vs operational asset register
These are often the same system and sometimes shouldn't be.
- A fixed asset register answers ownership and value. It changes slowly, is reconciled periodically, and its audience is finance and audit.
- An operational asset register answers location, custody and condition. It changes constantly and its audience is whoever is trying to find or issue something.
Running them as two systems produces exactly the drift you would expect: finance has assets that were disposed of two years ago, operations has equipment finance has never heard of. One register carrying both sets of fields is almost always better, provided the operational fields can be updated where the work happens.
The capitalisation threshold
Not everything belongs on a fixed asset register. Most organisations set a value threshold below which items are expensed rather than capitalised.
That's a finance decision, and it creates an operational trap: equipment below the threshold isn't on the fixed asset register, so it goes untracked entirely — and low-value, portable, numerous equipment is precisely what disappears.
The answer is to track it operationally even when it isn't capitalised. Tracking isn't the same as capitalising, and conflating them puts the hole in your register exactly where the losses are.
Getting the identifier right, because you only get one go
The most common design mistake in a fixed asset register is encoding meaning into the asset number: a site prefix, a category segment, a year block.
It reads beautifully on day one and breaks the first time an item moves site or a category is renamed — at which point the code says one thing and the record says another, and the code is the thing painted on the asset.
|
Approach |
Example |
What happens later |
|---|---|---|
|
Meaningful code |
LON-IT-2024-0042 |
Wrong the moment it moves to Manchester |
|
Flat sequence |
AST-00042 |
Stays true forever; attributes live in fields |
|
Manufacturer serial as key |
C02X1234JGH5 |
Breaks on replacement boards and unserialised items |
Use a flat sequence and let categories, locations and departments be fields that can change. If you're inheriting meaningful codes from an old system, import them as a secondary reference so search still works, and stop issuing new ones.
The capitalisation threshold trap
Finance sets a value below which items are expensed rather than capitalised. Perfectly sensible accounting, and it creates a operational hole nobody intends.
Below-threshold equipment isn't on the fixed asset register, so in most organisations it isn't tracked at all. And below-threshold equipment is overwhelmingly the portable, numerous, easily-mislaid kind: monitors, docks, chargers, hand tools, adaptors.
Tracking and capitalising are different decisions. Track operationally down to whatever value you'd notice missing; capitalise according to your accounting policy. Conflating them puts the gap in your register precisely where the losses are.
Building one from nothing
If there is no register at all, the temptation is to start with a template and fill it in. Start with the sources instead — you already have most of the data, just not in one place.
- Purchase records. The finance system or the purchase ledger gives you what was bought, when, and for how much. This is your spine.
- Any existing lists. IT's device list, the facilities spreadsheet, the insurance schedule. Each is partial and each contains something the others do not.
- A physical walk. The only way to find what no record contains, and it always finds something.
- Reconcile the three. Items in purchase records but not physically present are either disposed-and-not-closed or missing — and you need to know which.
Expect the first version to be wrong. A register that is 80% right today and improving is worth considerably more than one that is 100% right in six months, because the second one does not exist.
What to do about assets nobody can identify
Every build finds equipment with no serial, no purchase record and no obvious owner. Three options, in order of preference:
- Register it with what you have — description, location, estimated value, and a note that provenance is unknown. Imperfect data beats absence.
- Ask around with a photo before deciding. Somebody usually knows, and it takes a day.
- Dispose of it, if it is genuinely unidentifiable and unused. Carrying unidentifiable assets forever makes every count worse.
What not to do is leave it off because the record would be incomplete. An incomplete record is a record; an omission is a gap that nobody will ever revisit.
Reconciling with finance without a fight
If operations and finance both hold asset records, they will diverge. The question is only whether you find out on a schedule or during an audit.
- Agree the scope of the reconciliation — usually capitalised assets only, since operations tracks more.
- Agree a cadence. Quarterly is plenty for most organisations; annually is too late to remember anything.
- Treat differences as questions, not corrections. A difference usually means a process gap, and silently overwriting one side destroys the evidence of it.
- Close disposals in both. Unclosed disposals are the single largest source of phantom assets, and they inflate every count that follows.
Keeping it accurate
- Capture at acquisition. Every field above is cheap to record once and expensive to reconstruct later.
- Make operational updates frictionless, or location and holder will drift regardless of policy.
- Cycle count rather than relying on an annual reconciliation.
- Close disposals properly. Unclosed disposals are the single largest source of phantom assets.
- Reconcile with finance on a defined cadence, and treat differences as questions rather than corrections.
Key takeaways
- A fixed asset register serves finance, assurance and operations — designing for only one causes most register problems.
- Identity, value, location, custodian, depreciation basis and disposal are the non-negotiable fields.
- Use a flat meaningless identifier; encoding site or category into it breaks when either changes.
- Items below the capitalisation threshold still need operational tracking — that is where losses concentrate.
- Unclosed disposals create phantom assets that inflate every subsequent count.
Frequently asked questions
What is a fixed asset register?
The authoritative record of assets an organisation owns and uses over more than one accounting period, recording each asset's identity, location, custodian, cost, depreciation basis, current book value and eventual disposal.
What fields are required in a fixed asset register?
At minimum: a unique identifier, description, make, model, serial number, category, location, custodian, acquisition date and cost, supplier, depreciation method and life, current book value, condition and status, and disposal details when it leaves.
Is a fixed asset register a legal requirement?
Requirements vary by jurisdiction and entity type, but most organisations that prepare audited accounts need one to support the fixed assets shown in the balance sheet. Grant-funded and public bodies frequently have explicit obligations. Check your own jurisdiction and funder terms.
What is the difference between a fixed asset register and an inventory?
A fixed asset register covers assets you own and use over multiple periods, tracked individually. Inventory covers stock you hold to consume or sell, tracked by quantity. They need different systems because one is about identity and the other about quantity.
Should low-value items be on the fixed asset register?
Not necessarily for capitalisation — most organisations expense below a threshold. But they should still be tracked operationally, because portable low-value equipment is exactly what goes missing, and excluding it puts a hole in the register precisely where the losses are.
Who should maintain the fixed asset register?
One named person accountable for its accuracy, with everyone who handles equipment able to record movements. Splitting it the other way — many people accountable, few able to record — is the arrangement that produces drift.
What is the difference between a fixed asset register and a CMDB?
A fixed asset register records what you own, what it is worth and who holds it. A CMDB records configuration items and the dependencies between them, for the purpose of managing IT services. Different questions, different audiences, and they overlap only on identity.
How do you handle assets at multiple locations?
Hierarchical locations — site, building, room — so an asset sits at whatever depth makes sense and filtering by a parent shows everything beneath it. That is what makes 'what is at the Leeds site' a view rather than a phone round.