Asset Management Software for African Organizations
Registers fail for the same reason everywhere on this continent: they record what an organization owns rather than who is holding it. Custody, verification and disposal as the three things that matter — and a precise boundary between an asset register and a maintenance system.
Nearly every organization that says it has no asset register actually has three: a spreadsheet from the year of the last audit, a folder of purchase invoices, and a person who knows where things are. The first two are historical documents. The third is the only one anyone consults, and they are increasingly considering other opportunities.
The reason registers fail is narrower than it looks. Almost all of them record ownership — an item, a cost, a date, a depreciation schedule — and almost none record custody. But every question an organization actually asks about an asset is a custody question.
The questions people actually ask
- Where is the projector? A location question, answerable only if movements are recorded.
- Who has the vehicle this week? A custody question, answerable only if custody is a field rather than an arrangement.
- Did the laptop come back when he left? An offboarding question that arrives too late unless the register knew he had it.
- Do we still have the generator the grant paid for? A funding-source question, answerable only if the source was recorded at receipt.
- When did anyone last physically see it? A verification question, and the one that separates a register from a list.
Notice that a depreciation schedule answers none of them. Depreciation is an accounting requirement and it belongs in the register, but organizations that build the register around depreciation end up with a document that satisfies an auditor once a year and helps nobody in between.
A register that knows what you own and not who is holding it answers the one question nobody asks.
Three things that carry the whole discipline
-
Custody, recorded at the moment of handover
A named person, a location, a date, and where relevant an expected return. Thirty seconds at the counter; an archaeology project six months later. Everything else in this discipline depends on this one habit and no amount of software substitutes for it.
-
Verification on a rhythm
Somebody physically confirms the asset exists, where it is meant to be, in the condition recorded — and that confirmation is stored with a date. Annually is the minimum, and "when the auditor asks" is not a rhythm.
-
Disposal as a governed event
Approved, recorded, with a reason and a destination. The most common asset loss in any organization is not theft — it is an item quietly written off, taken home by someone who felt entitled to it, and never appearing as a disposal at all.
What is genuinely harder on this continent
The principles above are universal. Four conditions make them harder to hold, and they are worth naming so that the design responds to them rather than ignoring them.
| Condition | What breaks | What actually fixes it |
|---|---|---|
| Assets spread across distant sites | Verification never happens, because a physical check means a journey | Verification captured on a phone at the site, offline, with optional GPS on the record — so the check happens when someone is already there |
| Assets held by non-employees | No offboarding process catches the return; contractors demobilise abruptly | Custody recorded against the contract, with expected return dates and an outstanding-custody view someone reviews |
| Donor or grant-funded assets | Funding source derived from a purchase ledger years later, badly | Funding source on the asset from receipt, so project close is a report rather than an investigation |
| Labelling that does not survive the environment | Tags fall off, get painted over, or were never applied | Barcode or QR labels applied at receipt as part of the receiving process, with movements capturable by scan |
| Power and generator dependence | Critical equipment has no service history, so repair-or-replace is a feeling | Preventive schedules that open their own work orders, with downtime and repair cost recorded on the asset |
The maintenance boundary, precisely
This is where asset software claims get loose, so here is the line drawn exactly. Ours plans calendar maintenance and records it: a preventive schedule on the asset opens its own work order when the service falls due, and the work order carries the downtime and the cost. A full maintenance management system goes further, into usage meters and parts drawn from the store, and the gap between the two is wider than most vendors admit.
Register or maintenance system?
What our asset module holds
Custody, history and calendar maintenance — where the asset has been, who had it, and what work is due.
- Preventive schedules on a fixed calendar or from the last service, opening their own work orders.
- Work orders with labour, parts and other cost recorded on completion, and overdue work chased.
- Work orders opened, started and closed on a phone from the workshop floor.
- Sent to maintenance and returned from maintenance, as recorded movements written by the work order.
- A maintenance status on the asset, so availability reporting is honest.
- Damaged, lost and written off as distinct recorded outcomes.
- Warranty expiry as a date on the record.
- Physical verification history with dates.
- Named custody with expected return dates.
What a dedicated maintenance system adds
Usage and consumption — what the machine has done and what the work drew from stock.
- Service intervals by usage as well as time.
- Meter and engine-hours readings.
- Spare parts issued from stock onto the job and valued from inventory.
- Maintenance cost posted into the accounts against the asset.
What crosses the boundary
- The asset identifier, so both systems mean the same machine.
- Parts consumption, which should be issued from stock in one place rather than counted twice.
- Repair purchases and invoices, which live in procurement wherever the maintenance planning lives.
We are on the left, and the right column is work we can add to your workspace. If usage-based servicing and parts drawn from the store are core to your operation, that is the conversation to have before you buy. A vendor describing a movement log as maintenance management is describing half of the left column with the right column's label.
The straight answer
What AWRA OpsHub does today
- A register with named custody — who holds each asset, where, since when, and due back when.
- Movement history covering assignment, transfer, maintenance, return, damage, loss and disposal as distinct recorded outcomes.
- Physical verification records with dates, so "when did anyone last see it" is answerable.
- Funding source held on the asset, which is what makes donor and grant asset accountability workable at project close.
- Barcode and QR labelling, with movements capturable by scan and optional GPS capture on checkout, check-in, transfer and verification.
- Preventive maintenance and work orders — schedules on a fixed calendar or from the last service open their own work orders, overdue work is chased, and each completed work order records labour, parts and other cost and the hours the asset was out of service.
- Warranty expiry as a date, and a maintenance status affecting availability reporting.
- Work orders in the mobile app — opened, started, completed or cancelled from the workshop floor, beside the asset’s own record.
- Offline capture for asset movements and verification at remote sites without a connection. A verification, check-out, check-in, transfer or relocation, or marking an asset damaged or lost, on an asset the phone has already loaded is queued on the device, with its GPS stamp where required, and syncs without duplicating when a signal returns.
- An asset register report set covering what you hold, who has it, where it is, its condition and when it was last verified. Book value lives beside it in accounting: a depreciation profile per asset — straight line or reducing balance, a useful life and a salvage value — a monthly run that posts the charge to the ledger, disposal with its gain or loss, and a fixed asset register that reconciles to the general ledger.
More we can add to your workspace
- Meter and hours readings, and schedules due on usage. Engine hours, kilometres and print counts recorded against the machine, so a service can fall due at 500 hours rather than on a date.
- Spares drawn from stock onto a work order, issued from the store and valued from inventory rather than typed as a cost.
- Maintenance cost posted to the ledger as a repairs expense against the asset.
- Repair invoices and expense claims tied to an asset, so a repair bought through purchasing rolls into the same per-asset total as the work orders.
- An RFID or GPS tracking hardware. Optional GPS is captured from the device at the moment of a transaction; nothing is tracked continuously.
- A statutory fixed-asset ledger output. Depreciation is calculated and reported; the statutory treatment stays with your accountants.
The repair-invoice link is worth solving with a convention rather than waiting for a feature: record the cost on the work order, or put the asset code in the reference on every repair invoice and expense. It takes seconds and it is what makes the repair-or-replace conversation possible at all.
What we can build for your market on top of the standard product
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point for your market, not a limit on what AWRA OpsHub can do there. Kenya's eTIMS integration and its maintained payroll engine are in the product because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If a revenue authority pipeline, a bank or mobile money feed, a statutory return format, a rule specific to how your operation runs, or a link to a system you already have is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
Tax and e-invoicing pipelines
Electronic invoicing against your revenue authority's published interface, with the parts vendors gloss over — retries, a failure queue and a daily report of sales carrying no fiscal reference.
Banks, payments and mobile money
Statement feeds, payment gateways, bulk-payment files and collection accounts wired into the Payments Register so money in and out reconciles without re-keying.
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.
Payroll and statutory returns
Payroll and social security schedules produced in the layout your filing body expects, generated from live payroll records rather than rebuilt each month.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
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. No roadmap slide, and no pretending in a demo that something exists when it does not.
Tell us what you need integratedStarting smaller than feels responsible
Organizations attempting an asset register usually begin by trying to capture everything, which collapses somewhere around the fourth week and the two hundredth chair.
The version that survives is narrower. Start with the assets whose absence would actually be noticed — vehicles, laptops, generators, medical or lab equipment, anything donor-funded — and record custody religiously for those alone. Two hundred assets recorded properly are worth more than four thousand recorded once. The habit then spreads outward from something that visibly worked, which is the only way this discipline has ever taken hold anywhere.
Where to go next
The continental framework is in the best ERP software for African businesses. The foundational disciplines, market-neutral: asset tracking and custody, maintenance records that actually get kept, asset disposal and retirement and the fixed asset register.
By context: donor-funded asset registers, procurement and asset management for South African NPOs, asset registers for Tanzanian institutions and mining and industrial supply in Southern Africa.
Our take
Build the register around custody, not around depreciation. Record who holds each asset at the moment of handover, verify physically on a rhythm rather than when an auditor asks, and treat disposal as a governed event with a reason and a destination. Put funding source on the asset from day one if any of it is grant-funded. Then start with two hundred assets rather than four thousand — and give the machines whose failure stops work a preventive schedule, so the work order opens itself. If usage-metered servicing is core to your operation, settle that before you buy.
See a register built around custody
Named holders, expected return dates, movement and verification history, funding source on the asset, scannable labels, and offline capture so a remote site actually gets verified.
Explore asset trackingFrequently asked questions
What makes an asset register different from a fixed asset schedule?
A fixed asset schedule answers the accountant: what was bought, when, at what cost, depreciated how. An asset register answers everyone else: where is it, who has it, when did anyone last physically confirm it, and what happened to it. Both matter and they live in the same record, but organizations that design around the schedule end up with a document that satisfies an audit once a year and helps nobody in between. Design around custody and the schedule falls out of it.
Do you track engine hours or schedule servicing?
Servicing, yes; engine hours, not yet. A preventive schedule on the asset holds an interval on a fixed calendar or counted from the last service, and a daily job opens the work order when it falls due and chases it once if it slips. A work order that takes the asset out of service records the sent-to-maintenance and returned-from-maintenance movements, so downtime is measured, and labour, parts and other cost are recorded when it closes. Meter readings and schedules that fall due on usage are work we can add to your workspace.
Can assets be verified at a remote site with no connectivity?
Yes, and it is usually the difference between verification happening and not happening. A verification — and any of the other asset actions, from a check-out to marking an asset damaged or lost — on an asset the phone or tablet has already loaded is captured offline and queued locally, syncing when the device reaches a signal, with each operation carrying its own identifier so nothing arrives twice. Optional GPS capture records where the verification physically occurred, and assets can carry barcode or QR labels so the check is a scan rather than a form.
How do we handle assets bought with donor funds?
Put the funding source on the asset at the moment it is received, not derived from a purchase ledger at project close. Everything the donor eventually asks for — which assets their grant paid for, where each one is, who holds it, its condition, its verification history and what happened to it at disposal — then becomes a report rather than an investigation. Retrofitting funding source across three years of assets is the single most common panic in this sector, and it is entirely avoidable at receipt.
Do you support RFID or GPS tracking?
Not as continuous tracking. Assets can carry barcode or QR labels and movements can be captured by scan, and GPS coordinates can optionally be recorded at the moment of a checkout, return, transfer or verification — that is a stamp on a transaction, not a live location feed. There is no RFID gateway support and no tracking hardware. For most organizations the transaction stamp is the useful part anyway, because it evidences that a person was physically where they said they were.
How do we know what a repair actually cost us?
Record it on the work order. Labour, parts and other cost are entered when a work order is completed, and the asset shows its completed maintenance spend and hours out of service over the last twelve months. A repair bought through a purchase order or claimed as an expense is not linked to the asset automatically, so for those put the asset code in the reference, consistently. Between the two, the repair-or-replace conversation happens with numbers instead of impressions.
Where should we start?
With the assets whose absence would actually be noticed — vehicles, laptops, generators, medical and lab equipment, anything grant-funded — and nothing else. Record custody at every handover, label them at receipt, and verify on a set rhythm. Two hundred assets recorded properly are worth more than four thousand recorded once and never touched again, and the habit spreads outward from a subset that visibly worked. Attempting the full estate in month one is the most reliable way to abandon the register in month two.
