Fleet & Fuel Control in Kenya: Reconcile Fuel Like Cash
Fuel is the most stolen commodity in Kenyan business and the easiest to reconcile — cost per vehicle, fuel-to-distance discipline, and the route math that decides which vans deserve to exist. A method, not a module: read the honesty block before evaluating.
Ask what the fleet costs and most Kenyan businesses can quote the fuel bill. Ask what vehicle KBZ 402C cost last month — fuel, repairs, tyres, insurance, financing — per kilometer, and the room goes quiet. That silence is expensive: fleets are typically the second or third largest operating cost, and they are managed with less precision than the stationery. The fix is not GPS gadgets first; it is accounting first — every shilling landing on a specific vehicle, every liter reconciled to distance.
Cost per vehicle: the foundational habit
- Every fleet expense posts against a vehicle, not a general "transport" account: fuel, service, parts, tyres, insurance, inspection, financing.
- Every vehicle logs distance — odometer at fueling is the minimum; trip logs are better.
- The monthly output is one line per vehicle: kilometers, total cost, cost per km, and fuel efficiency — trended against its own history.
- A vehicle file holds the service schedule and every repair, so replace-versus-repair is a data decision. Keep it yourself: the asset register gives you the vehicle, its custodian and its movements, but no service interval and no repair log.
Fuel: reconcile it like cash
Fuel is cash that burns — and it leaks the same three ways: siphoning, phantom fueling (receipts for liters never pumped), and private mileage. All three die under one reconciliation:
| Check | The math | What it catches |
|---|---|---|
| Consumption vs distance | Liters ÷ km against the vehicle's known baseline | Siphoning and phantom liters — consumption "worsens" without mechanical cause |
| Fueling vs route | Fuel events against the day's assigned route and trip log | Private mileage and weekend safaris |
| Receipts vs card/account statements | Station receipts against fuel card or account billing | Phantom receipts and split billing |
| Tank capacity sanity | No fill exceeds the tank | The oldest trick still works surprisingly often |
Baselines beat gadgets
Fuel monitoring hardware has its place, but most fleets recover 80% of the leak with arithmetic alone: establish each vehicle's consumption baseline over a clean month, then investigate deviations beyond ~10%. Drivers know within a week that the math is being done — and the math being done is most of the control.
Service on schedule, not on breakdown
- Service intervals (km or months) tracked per vehicle with lead-time reminders — the same preventive logic as any critical equipment. This lives on your own calendar or wall chart; nothing here schedules a service or warns you one is due.
- A vehicle file per unit: every repair, part, and cost — three gearbox visits in a year is a pattern, not bad luck. Also yours to keep, since a repair cannot be recorded against an asset.
- Downtime recorded: a van off the road is a route unserved; the downtime cost usually dwarfs the repair invoice. Record it alongside the service schedule — it is not derivable from the asset history.
- Tyres tracked as their own line — in high-mileage fleets they quietly rival fuel, and they walk.
The route math
Once cost per vehicle per day exists, the strategic question opens: does each route earn its van? Route revenue (from van sales and deliveries) minus stock consumed minus the vehicle's daily cost = route contribution. Kenyan distributors who run this math for the first time almost always find one route that has been subsidized for years and one that deserves a second vehicle. The field operations stack exists to make that sentence computable.
What AWRA OpsHub does today
- Vehicles as assets in the asset register, with a named custodian, movement history, purchase cost and retirement.
- Fuel purchases as expenses or stock, coded to a category and a project. Not a department — an expense carries none — so a standing project per vehicle or per route is the convention that actually reports.
- Budgets per department and period for a fuel or transport envelope.
More we can add to your workspace
- A vehicle, trip, route, odometer and fuel entity — the records this whole article would hang on.
- A fuel-to-distance reconciliation. Consumption per kilometre is not something the system can compute, because it holds neither distance nor a fuel log.
- Service scheduling: a service interval, a next-service date, meter or hours tracking and a reminder — which together make "service on schedule" answerable.
- A maintenance visit,. A service or repair cannot be recorded against a vehicle at all. Sent-to-maintenance and returned-from-maintenance exist as movement types but nothing creates them, so the only representation is editing the asset's status to "maintenance" — which overwrites the previous value and leaves no dated trail. Time out of service is therefore not recoverable.
- A route contribution or cost-per-vehicle report. Cost per vehicle can only be approximated by coding expenses to a project or department per vehicle.
This is the least well-covered article in the field-operations cluster and it deserves a straight answer: if fleet and fuel control is your primary requirement, we are not the right system, and a dedicated fleet package will serve you better. The workable partial pattern is to make each vehicle an asset with a custodian and a project code, and read cost per vehicle off project spend — useful, but a long way from what this article describes.
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 needsKnow what KBZ 402C actually costs
Vehicles as custodied assets, movement history between depots, and fuel coded to a project or budget envelope — the parts of fleet cost we do hold.
See fleet control in AWRAFrequently asked questions
Fuel cards or cash — which is easier to control?
Cards (or station accounts) — they produce a statement to reconcile against, which cash never does. But cards without the consumption-vs-distance math just produce tidier theft records. The reconciliation is the control; the payment method only sets how good the paper trail is.
Do we need GPS trackers on every vehicle?
Start with the arithmetic — odometer discipline, fuel reconciliation, route logs — which costs nothing and catches most leakage. Add trackers where the math flags persistent anomalies, for high-value cargo, or where route verification matters commercially. Hardware amplifies discipline; it does not replace it.
How do we handle drivers who fuel from their own pocket on emergencies?
A documented reimbursement flow: receipt, odometer photo, route context, approved against the vehicle — the same [field advance discipline](/blog/field-advances-mobile-money) as any other field money. What kills control is the informal "sort it later" pool where reimbursements and floats blur.
What is a reasonable private-use policy for company vehicles?
Whatever the board writes down and the logs can verify: defined personal-use allowances (taxed correctly as a benefit where applicable), trip logs that make the split visible, and fuel apportioned accordingly. The unworkable policy is the unwritten one — it converts every weekend trip into a governance argument.
