Your Asset Register Is Not a Depreciation Ledger
The asset register and the depreciation schedule are two different documents doing two different jobs, and conflating them is the most common mistake in Kenyan fixed-asset practice. Here is exactly which one this module is, and what that means for your year-end.
Two questions get asked about the same laptop. The operations manager asks where it is and who has it. The accountant asks what it is worth on the balance sheet at 31 December. These sound like two views of one record and they are not — they need different fields, they are maintained by different people on different rhythms, and they go wrong in completely different ways. An organisation that assumes one document answers both ends up with a custody register that cannot support a balance sheet, or a depreciation schedule that has no idea the asset was stolen in March.
This module is emphatically the first document. We would rather be precise about that than let it be discovered during an audit, so this article is mostly a boundary drawn carefully.
What the register actually holds
Per asset: a code and barcode, name, description, type and category, serial number, model and manufacturer, purchase date, purchase cost and currency, ownership type, warranty expiry, condition, status and risk level, the current custodian, department, location and warehouse, when it last moved, when it was last verified and by whom, and — when it leaves — a retirement date, the person who retired it and a reason.
That is a genuinely complete custody and lifecycle record. Read the list again with an accountant's eyes, though, and notice what is not on it: no depreciation method, no useful life, no residual value, no accumulated depreciation and no net book value. Those five fields are the depreciation schedule, and they are not here. Purchase cost is the only financial figure the register carries.
The dashboard figure, and what it is not
The assets dashboard does show a value trend over time, and it would be easy to mistake it for a depreciation schedule. It is not one, and the difference is worth stating exactly because the number is real and reasonable while meaning something narrower than it looks.
It is an indicative portfolio estimate applied uniformly: every asset with both a purchase date and a purchase cost is written down on a flat straight-line basis of twenty per cent a year from its purchase date, floored at zero, with retired assets dropping out from their retirement date onward. That is a defensible way to draw a downward-sloping line for a dashboard. It is not a depreciation calculation for accounts, for three specific reasons.
Three assets, one flat rate
The three reasons in one place. First, one rate for every asset class means short-life equipment is overvalued and long-life assets are undervalued, and the errors do not cancel — they depend entirely on your asset mix. Second, there is no residual value, so everything trends to zero. Third, and most easily overlooked: an asset with a blank purchase date or a blank cost is skipped, so a partially completed register produces a trend line that is too low for reasons unrelated to depreciation. Useful as a shape. Not a number to put in accounts.
Where depreciation therefore lives
In your accounting workpapers, prepared per asset class, and posted to the ledger as a journal. The chart of accounts includes an accumulated depreciation account ready to receive it — what does not exist is anything that computes the charge and posts it automatically from the asset register. That link is the missing piece, and it is a link, not a small field.
The practical consequence is that the register is your source of the inputs rather than the producer of the output, and that is a genuinely useful role. It tells you what exists, what it cost, when it was bought, what class it belongs to, and — critically — what has been retired. See straight-line versus reducing balance for the methods themselves.
The two documents, side by side
| The asset register (here) | The depreciation schedule (your workpapers) | |
|---|---|---|
| Answers | Where is it, who has it, what condition is it in, when was it last seen | What is it worth on the balance sheet, what is this period's charge |
| Maintained by | Operations, admin, whoever issues and receives equipment | Finance, monthly or annually |
| Updated when | An asset moves, is verified, is repaired, is retired — continuously | At each period close, and when an asset is added or disposed of |
| Key fields | Custodian, location, condition, status, last verified, movement history | Cost, class, method, useful life, residual value, accumulated depreciation, NBV |
| Fails when | Nobody records a transfer, so the register describes last year's arrangement | An asset is disposed of and nobody tells finance, so it depreciates for years after it is gone |
| What it needs from the other | Nothing, in practice — custody is independent of book value | Additions, disposals and retirements. This is the whole dependency, and it runs one way |
The bottom-right cell is the entire integration you need to operate manually, and it is smaller than it sounds. Finance does not need the movement history or the custodian. Finance needs to know what was added and what left, which the register records precisely — with a retirement date, a reason and the person who did it.
What AWRA OpsHub does today
- Purchase date, purchase cost and currency per asset — the inputs a schedule needs.
- Category and asset type per asset, which is how you group into depreciation classes.
- Ownership type, so owned and leased assets are distinguishable rather than mixed.
- Retirement with a date, a reason and a named person, plus a status — disposal handled properly.
- An indicative portfolio value trend on the dashboard at a flat 20% a year, excluding retired assets from their retirement date.
- Assets and asset movements as reporting datasets, so additions and disposals in a period are extractable for finance.
- An accumulated depreciation account in the chart of accounts, ready to receive your journals.
What it does not do
- No depreciation method per asset. No straight-line, no reducing balance, no per-class default.
- No useful life or residual value fields. The two inputs every method needs, absent.
- No accumulated depreciation and no net book value. Nothing accumulates a charge or holds a carrying amount.
- No automatic posting to the ledger. The depreciation account exists; nothing writes to it from assets.
- No revaluation, impairment or capital work-in-progress handling.
- No separate tax depreciation basis, which in Kenya diverges from the accounting basis via wear-and-tear allowances.
- No depreciation start date distinct from purchase date, so an asset commissioned months after purchase has no way to say so.
- The dashboard trend is a flat-rate estimate that skips assets with a blank purchase date or cost — not a schedule, and not a balance-sheet figure.
We are being deliberately blunt because the failure mode is expensive and quiet. An operations team looks at a downward-sloping value chart, concludes depreciation is handled, and stops maintaining the workpaper. Nine months later the auditor asks for the fixed asset schedule and there is a custody register, a dashboard estimate, and no reconciliation between either of them and the balance sheet. Keep the workpaper.
Running the two together
-
Fill in purchase date and purchase cost on every asset, without exception
These are the fields finance depends on, and a blank one is invisible — it does not error and it silently drops the asset out of the dashboard trend. If a historic cost genuinely cannot be established, record your best estimate with a note in the asset's own notes field rather than leaving it empty.
-
Use category consistently as your depreciation class
Motor vehicles, computer equipment, furniture and fittings, plant and machinery, buildings. Agree the list with whoever prepares your accounts before anybody starts typing, because retrospectively re-categorising three hundred assets is a day of work nobody has.
-
Keep the depreciation schedule where it belongs, per class
A workpaper or your accounting system, with cost, class, method, life, residual value, accumulated depreciation and carrying amount. It is the balance sheet support and no chart replaces it.
-
Export additions and disposals for the period at each close
Both are reportable datasets, so this is a filter on purchase date and a filter on retirement date. Two exports, and it is the entire operations-to-finance handover.
-
Make disposal notification a step in the retirement process
The most expensive fixed-asset error in practice is an asset that was sold or scrapped and continued depreciating for years, overstating both assets and the loss on eventual disposal. The register records the retirement properly; somebody still has to tell finance.
-
Reconcile the count annually, not the value
Compare the number of active assets per category in the register against the lines in the schedule. Values will differ legitimately — the register holds cost, the schedule holds carrying amount. Counts should not differ, and a mismatch is exactly where the unrecorded disposal or the uncapitalised purchase is hiding.
Two registers, one physical count
The annual verification count serves both documents and most organisations only credit it to one. Walking round with the register confirms custody, condition and existence — and existence is precisely what the auditor tests the fixed asset schedule for. Do the count once, record it against the register where the last-verified date and verifier are captured per asset, and give finance the exceptions list. One afternoon covering two obligations is the best value in this whole area, and it is also how missing assets get found while somebody still remembers what happened to them.
Our take
Treat this as a custody register that feeds your depreciation schedule, not as one that replaces it. It holds purchase date, cost, currency, category and a properly recorded retirement — which are exactly the inputs a schedule needs — and it holds no method, no useful life, no residual value, no accumulated depreciation and no book value, so nothing computes a charge or posts to the ledger. The dashboard value trend is an indicative flat 20% a year that ignores asset class and skips any asset with a blank purchase date or cost; it is useful for seeing a portfolio age and it is not a balance-sheet number. So: fill in purchase date and cost on everything, use category as your depreciation class and agree the list with your accountant first, keep the schedule in your workpapers, export additions and disposals at each close, and reconcile counts rather than values once a year.
A register your accountant can actually use
Purchase date, cost, currency and category per asset, ownership type, retirement with date, reason and named person, and assets and movements as reportable datasets — so additions and disposals reach finance as two filters rather than an archaeology project.
See plans & pricingFrequently asked questions
Does the asset register calculate depreciation?
No. There is no depreciation method, useful life, residual value, accumulated depreciation or net book value per asset, and nothing posts a charge to the ledger. The register holds purchase cost, purchase date, currency and category — the inputs a depreciation schedule needs — while the schedule itself belongs in your accounting workpapers.
What is the value trend on the assets dashboard then?
An indicative portfolio estimate. Every asset with both a purchase date and a purchase cost is written down on a flat straight-line basis of twenty per cent a year, floored at zero, with retired assets dropping out from their retirement date. It is a reasonable way to show a portfolio ageing and it is not a balance-sheet figure, because it applies one rate to every asset class, allows no residual value, and skips any asset with a blank purchase date or cost.
Why does one flat rate matter if it is only indicative?
Because the error depends on your asset mix and does not cancel out. At twenty per cent a year, a three-year-old laptop that should be near nil still shows two fifths of its cost, while a building or racking with a fifteen-year life is written down four times too fast. Whether the total is high or low depends entirely on what you own, which is why it cannot be used as an adjustment factor either.
What do we actually have to do at year end?
Maintain a depreciation schedule outside the register with cost, class, method, useful life, residual value, accumulated depreciation and carrying amount per asset, and post the charge as a journal — the accumulated depreciation account already exists in the chart of accounts. From the register you need two exports at each close: additions filtered on purchase date, and disposals filtered on retirement date.
What is the most common mistake here?
An asset that was sold or scrapped and kept depreciating because nobody told finance. It overstates fixed assets for years and then produces a large unexplained loss on disposal. The register captures retirement properly — with a date, a reason and a named person — so the fix is to make notifying finance an explicit step in your retirement process rather than an assumption.
Is tax depreciation handled separately?
No — there is no second basis. In Kenya the accounting charge and the wear-and-tear allowances used for tax diverge, so most businesses maintain two columns in their workpaper. Neither lives in the register, which means the register is neutral on the question rather than helpful with it. Keep both in the schedule.
