From Asset Register to 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.
The asset module is emphatically the first document. The second lives beside it in accounting, as a depreciation profile per asset — and keeping the two distinct, with the right one doing each job, is the point of this article.
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 belong on a depreciation profile in accounting rather than on the register record. Purchase cost is the only financial figure the register itself carries.
The dashboard figure, and what it is
The assets dashboard shows a value too — today's net book value and a trend by day, week, month or year — and it is read from the depreciation postings rather than estimated.
For every asset with a depreciation profile, the dashboard shows cost less the depreciation the monthly run has charged, plus any opening accumulated depreciation. For every asset without one, it shows cost — counted and labelled, with a link to set the profile up, not written down at a rate we invented. Disposed and retired assets are left out. The figure that matters most on that panel is therefore not the total but the count of assets carried at cost.
Three assets, one without a profile
The two profiled assets are at exactly what the depreciation run has posted, so they agree with the ledger. The racking sits at cost because nobody gave it a profile, and the dashboard says so rather than guessing. An asset with a blank cost adds nothing to book value at all, which is the other gap to look for.
Where depreciation lives
In accounting, as a depreciation profile against each asset: its cost, a salvage value, the date it came into service (which need not be its purchase date), the method — straight line or reducing balance — and a useful life or an annual rate. A monthly run posts the charge, debiting depreciation expense and crediting accumulated depreciation, catches up any month that was skipped, never takes book value below salvage, and stops once the asset is retired or disposed of; a month-end reminder prompts the run. Recording a disposal against the profile posts the proceeds and the gain or loss. An asset brought in part-way through its life takes its depreciation charged to date as an opening figure.
The practical consequence is that the register is your source of the inputs and the profile is the producer of the output. The register 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 (the profile in accounting) | |
|---|---|---|
| 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, through a monthly depreciation run |
| 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 | A new asset never gets a profile, so it sits on the register at cost and is never depreciated |
| What it needs from the other | Nothing, in practice — custody is independent of book value | Additions, and the retirements that stop the charge. Retiring an asset in the register stops its depreciation on its own; a new asset still needs its profile set up |
The bottom-right cell is the entire integration, and most of it happens without anybody passing a list across. A retirement in the register ends the monthly charge by itself. What still needs a person is the other direction: every asset added to the register needs a depreciation profile, and an addition with no profile is the error to look for at each close.
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.
- Net book value on the assets dashboard, read from the depreciation postings, today and as a trend — with assets that have no profile carried at cost and counted, and disposed or retired assets excluded.
- 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, posted to by the depreciation run.
- A depreciation profile per asset: straight line or reducing balance, a useful life or annual rate, a salvage value and an in-service date distinct from purchase date.
- Accumulated depreciation and a net book value held against the asset, with an opening figure for an asset brought in part-way through its life.
- Posting to the ledger by a monthly run that catches up skipped months, never goes below salvage, stops at retirement or disposal, and is prompted by a month-end reminder.
- Disposal accounting — proceeds recorded against the profile, with the gain or loss posted.
More we can add to your workspace
- A per-class default method and life, so a new asset’s depreciation profile fills itself in from its category.
- A revaluation, impairment or capital work-in-progress handling.
- A separate tax depreciation basis, which in Kenya diverges from the accounting basis via wear-and-tear allowances.
We are being deliberately blunt because the failure mode is expensive and quiet. An asset with no depreciation profile sits on the dashboard at cost, and an operations team that reads the total without the count beside it concludes depreciation is handled. Nine months later the auditor asks for the fixed asset schedule and half the register was never charged. The figures that count are the ones the depreciation run posts — give every asset a profile, and read the carried-at-cost count at every close.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsRunning 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 an asset with no cost adds nothing to book value. 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.
-
Give every asset a depreciation profile, the day it is added
Cost, salvage, in-service date, method and life, agreed per class with whoever prepares your accounts. The monthly run then posts the charge, and accumulated depreciation and carrying amount are held for you rather than in a workpaper.
-
Check additions against profiles at each close
Additions are a reportable dataset, so this is a filter on purchase date set against the list of depreciation profiles. An asset on the first list and not the second is the one error the system cannot catch for you.
-
Record the disposal, not only the retirement
Retiring an asset in the register stops its monthly charge. Recording the disposal against its profile is what takes it off the books and posts the gain or loss — the step that keeps a scrapped asset from sitting at book value for years.
-
Reconcile the count annually, not the value
Compare the number of active assets per category in the register against the depreciation profiles in accounting. Values will differ legitimately — the register holds cost, the profile 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 the register and the depreciation profile as two documents that feed each other, not as one record. The register holds purchase date, cost, currency, category and a properly recorded retirement — exactly the inputs a schedule needs. The profile in accounting holds the method, life, salvage, accumulated depreciation and book value, and posts the monthly charge to the ledger. The dashboard shows booked net book value, with undepreciated assets at cost — so the quickest health check is how many assets it says have no profile. So: fill in purchase date and cost on everything, use category as your depreciation class, give every new asset a profile, record disposals against it, and keep the tax basis in your workpaper.
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 — and a depreciation profile per asset that posts its own monthly charge.
See how asset tracking worksFrequently asked questions
Does the asset register calculate depreciation?
The register itself does not, by design — it holds purchase cost, purchase date, currency and category, the inputs a schedule needs. Depreciation is calculated in accounting, on a profile per asset with its method, useful life, salvage value and in-service date, and a monthly run posts the charge to the ledger and keeps accumulated depreciation and net book value against the asset.
What does the assets dashboard show?
Net book value as posted, today and as a trend by day, week, month or year. For each asset with a depreciation profile it is cost less the depreciation the monthly run has charged, so it agrees with the ledger. An asset with no profile is carried at cost and counted, with a link to set it up, and disposed or retired assets are left out.
Why does the count of assets carried at cost matter?
Because each one is over-stated by however much depreciation it should have had, and the error depends on your asset mix. A three-year-old laptop with no profile still shows its full cost; racking with a fifteen-year life is over-stated by a fifth after three years. The dashboard counts them for exactly that reason. Drive the count to zero before the figure goes into a board pack.
What do we actually have to do at year end?
Run depreciation up to the year-end month, which posts any months still outstanding. Check that every asset added during the year has a profile — additions filtered on purchase date against the profile list — and that every asset that left has its disposal recorded. Keep the tax basis in your workpaper beside it.
What is the most common mistake here?
An asset that was added and never given a depreciation profile, so it sits at cost and is never charged — or one that was scrapped and retired with no disposal recorded, so it stays on the books. Retiring an asset stops its charge on its own; the habit to build is setting up a profile for every addition and recording every disposal.
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. The accounting charge is posted from the depreciation profile; keep the tax column in your workpaper beside it.
