What Is a Fixed Asset Register? (And What Belongs in One)
A fixed asset register is the authoritative list of everything durable an organization owns — what belongs in it, the fields that make it useful, and the difference between a register that lives and a schedule that lies.
A fixed asset register is the complete, itemized record of an organization's durable property — vehicles, equipment, machinery, computers, furniture, buildings — with each asset's identity, value, location, condition, and custodian. It serves two masters at once: the accountant, who needs values and depreciation for the financial statements, and the operation, which needs to know where things are, who holds them, and when they need service. Most registers serve the first master and abandon the second — which is how organizations end up with an audited number for assets nobody can find.
What belongs in the register
- Everything above your capitalization threshold — the value floor (set in policy) above which purchases are assets rather than expenses.
- Attractive items regardless of value — phones, laptops, cameras, tools: things that walk. Track them even when they fall below the threshold; use a lighter "controlled items" class if the accountant objects.
- Donated and grant-funded assets — with the funder recorded and any conditions noted; see donor-funded registers for why the funding tag matters.
- Leased and custody items, flagged — things you hold but don't own (leased equipment, repossessed collateral, a partner's machine) belong on the register with their ownership status explicit, precisely so they are never absorbed by accident.
The fields that make it useful
| Field | Which master it serves | Why it matters |
|---|---|---|
| Asset tag & serial number | Both | Without unique identity, physical verification is impossible |
| Description, category, purchase ref | Both | Links the asset to the transaction that created it |
| Cost, date, depreciation method & life | Accountant | The financial statement inputs |
| Location & custodian (a named person) | Operation | Accountability attaches to people, not departments |
| Condition & last verification date | Operation | A register is only as true as its last physical check |
| Service schedule & maintenance history | Operation | Preventive maintenance and replace-vs-repair decisions |
| Funding source / ownership status | Both | Donor reporting, lease boundaries, disposal rights |
| Disposal record | Both | Assets must leave the register as formally as they entered |
The register vs the depreciation schedule
The depreciation schedule your accountant maintains is a financial summary derived from the register — not a substitute for it. The schedule says what values exist; the register proves the things exist. When an auditor samples five assets and asks to see them, the schedule cannot answer. The register, verified and current, answers in minutes.
The disciplines that keep it alive
- Assets enter from purchases automatically — created from the received PO, inheriting cost, supplier, and funding source, so the register grows from transactions rather than memory.
- Custody is personal: issued to named people against signature, with exit clearance before final dues.
- Movements are transactions: transfers between locations approved and recorded — the register tracks reality only if changing reality requires touching the register.
- Verification on a rhythm: rolling physical checks (quarterly for portable/high-value, annually for the rest), with variances explained and written off consciously, not silently.
- Disposals are formal: approval, method, proceeds, and removal — the ghost assets that haunt registers are disposals nobody recorded.
Run this way, the register stops being an audit chore and becomes an operating tool: maintenance schedules hang off it, replacement planning reads from it, and insurance claims are supported by it. The pattern is identical whether the assets are a SACCO's branches and fleet, a school's labs and buses, or a company's plant — a system with custody, movements, and verification built in simply makes the disciplines the default.
Turn the schedule into a living register
Assets created from purchases, custodians by name, movements on the record, and verification by phone — reconciling to your accounts.
See asset registers in AWRAFrequently asked questions
What capitalization threshold should we use?
Policy varies by size — the principle is that the threshold is written, approved, and applied consistently. Whatever the floor, keep a lighter tracking class for attractive sub-threshold items; the laptop that walked cost less than the threshold and more than the audit finding.
How often should physical verification happen?
A rolling rhythm beats a annual marathon: portable and high-value items quarterly or twice-yearly, everything else annually, with someone other than the record-keeper verifying. The register field that matters most is "last verified" — a register with two-year-old verification dates is a hypothesis.
How do we deal with assets we find that aren't on the register?
Add them at fair estimate with a note — "found asset" entries are normal in a first cleanup. The reverse case (registered assets that cannot be found) gets investigated, then written off with approval. Both flows must be conscious and logged; silent additions and deletions are how registers rot.
Spreadsheet or system for the register?
A spreadsheet can hold the fields; what it cannot do is enforce the disciplines — assets created from purchases, movements requiring approval, custody signatures, verification workflows. Registers fail on discipline, not data structure, which is the case for keeping the register where the transactions live. The full argument is in [AWRA vs spreadsheets](/blog/awra-vs-spreadsheets).
