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 | Maintenance trips recorded as movements and repair invoices coded to the asset — a convention, not a feature |
The maintenance boundary, precisely
This is where asset software claims get loose, so here is the line drawn exactly. An asset register records that something went to maintenance and came back. A maintenance management system plans, schedules and costs the work. They are different products and the gap between them is wider than most vendors admit.
Register or maintenance system?
What an asset register holds
Custody and history — where the asset has been and who had it.
- Sent to maintenance and returned from maintenance, as recorded movements.
- 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 maintenance system holds
Planning and cost — what work is due and what it consumed.
- Service intervals per asset, by time or usage.
- Meter and engine-hours readings.
- Work orders with labour and parts booked against them.
- Preventive maintenance scheduling and due-for-service alerts.
- Cost per asset rolled up automatically.
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. There is no preventive-maintenance scheduler, no meter or hours tracking and no work orders in our product, and if planned maintenance is core to your operation the right answer is a maintenance system alongside this one. A vendor describing a movement log as maintenance management is describing 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.
- Warranty expiry as a date, and a maintenance status affecting availability reporting.
- Offline capture so verification and movements happen at remote sites without a connection, syncing without duplicating.
- Depreciation methods and an asset register report set, for the accounting requirement.
What it does not do
- No preventive-maintenance scheduler. No service interval per asset, no due-for-service reminder by time or usage.
- No meter or hours tracking. Engine hours, kilometres and print counts are not fields the register maintains.
- No work orders. A maintenance trip is a movement, not a job card with labour and spares booked against it.
- No automatic cost roll-up per asset. Repair invoices live in purchasing and expenses; tying spend to a specific asset is a coding convention you enforce.
- No RFID or GPS tracking hardware. Optional GPS is captured from the device at the moment of a transaction; nothing is tracked continuously.
- No statutory fixed-asset ledger output. Depreciation is calculated and reported; the statutory treatment stays with your accountants.
The cost roll-up gap is worth solving with a convention rather than waiting for a feature: 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 is not built for your market today can still be built for you
Anything described above as not built is a statement about what ships in the standard product today — not a limit on what AWRA OpsHub can do in your market. Kenya's eTIMS integration and its maintained payroll engine exist 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 or a link to a system you already run 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.
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 buy a maintenance system separately if planned maintenance is core, because a movement history is not a work order however it is labelled.
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?
No. There is no meter or engine-hours field, no service interval per asset and no due-for-service alert by time or usage. Maintenance appears as recorded movements — sent to maintenance, returned from maintenance — alongside assignments, transfers and verifications, with a maintenance status so availability reporting is honest, and warranty expiry held as a date. If planned maintenance with intervals and work orders is core to your operation, buy a maintenance system for that and connect the two; we would rather do that than mislabel a movement log.
Can assets be verified at a remote site with no connectivity?
Yes, and it is usually the difference between verification happening and not happening. Verifications, movements and condition updates are captured on a phone or tablet 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?
By convention rather than by feature, and we would rather say so. Repair invoices and expenses live in purchasing and expenses, and there is no automatic roll-up of spend against a specific asset. Put the asset code in the reference on every repair invoice and expense, consistently, and the total becomes retrievable from a report. It takes a few seconds per invoice and it is what makes the repair-or-replace conversation possible 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.
