The accounts manager at a Kathmandu-based distribution company noticed something in the monthly P&L: fuel costs had grown 38% over 12 months while the fleet had grown by only two vehicles - roughly 15%. The explanation from the fleet supervisor was rising diesel prices and longer routes to new customers. That was partially true. But when they built a per-vehicle fuel consumption report for the first time, the picture changed. Three of their fourteen trucks were consuming 30-40% more fuel per kilometre than the fleet average. The remaining 11 trucks were within an acceptable band. Those three vehicles had been quietly burning excess fuel for months - possibly years - with the cost buried in an aggregate fuel expense line that showed only total spend, never per-vehicle efficiency.
Fuel is typically the largest single operating cost in a fleet, often running at 30-45% of total vehicle operating costs for commercial trucks in Nepal. The gap between efficient management and no management is large: fleets that track fuel per vehicle and compare actual versus expected consumption routinely find savings of 8-15% within the first year - simply from identifying anomalies and addressing them. The anomalies are almost always there. Siphoning, unauthorized vehicle use, inefficient driving behaviour, and undetected mechanical problems all show up as excess consumption before they show up anywhere else.
Fuel tracking software moves fuel from a petty cash entry into a controlled, vehicle-linked expense stream. Each fuel issue is recorded against a specific vehicle, with quantity, cost, odometer at fill-up, and the person who authorized the issue. From those records, the system calculates consumption rate per vehicle (litres per 100 km) and compares it against the expected rate for that vehicle type and route. Variance analysis tells you which vehicles are running efficiently and which need attention.
The Structure of Good Fuel Tracking
Fuel tracking requires three inputs per fill-up: how much fuel was issued, to which vehicle, and at what odometer reading. The odometer reading is the critical link - without it, you can calculate total fuel cost but not consumption rate per kilometre, which is what makes anomalies visible. A vehicle that uses 80 litres in a week looks normal if it covered 800 km. The same 80 litres looks wrong if it covered 400 km.
Fuel can enter the system through two main channels: direct issues from a company fuel tank (common in construction firms with on-site storage) and external refuels where the driver gets a cash advance or fuel card and submits a receipt. Both need to be captured. Company tank issues are typically more controlled - a supervisor or store keeper records the dispensing. External refuels rely on driver compliance and receipt submission, which requires clear policy and enforcement. Some operations require the driver to send a photo of the fuel receipt immediately via mobile before the expense is recorded - this reduces receipt manipulation and delayed submissions.
Route assignments also matter for benchmarking. A truck running on the Kathmandu-Hetauda route via Narayanghat will consume more fuel per kilometre than the same truck running on flat Terai roads between Birgunj and Bhairahawa. Expected consumption benchmarks need to account for route profile - assigning a flat-road benchmark to a hill-route vehicle will show constant false positives in variance analysis.
Fuel tracking without odometer readings produces a cost record, not an efficiency record. The value comes from consumption rate (litres per 100 km) compared to expected benchmarks - and benchmarks must reflect actual route difficulty, not a single fleet-wide average.
Fuel Variance Analysis: How to Read the Numbers
Variance analysis compares actual consumption against expected consumption for each vehicle over a period. Here is a worked example for a distribution company running a mixed fleet between Kathmandu valley and Terai routes:
Nepal's diesel price is controlled and subject to periodic revision by Nepal Oil Corporation (NOC). Fuel cost calculations should use the actual price per litre at the time of each fill-up rather than a fixed monthly average - prices sometimes change mid-month. Petrol pump receipts in Nepal now include quantity and price details; requiring receipt submission with every external refuel is both practical and auditable. NOC pricing changes are published on the NOC website and take effect immediately, so systems should allow price updates without recalculation of historical records.
| Vehicle | Route Type | Expected (L/100km) | Actual (L/100km) | Variance | Action |
|---|---|---|---|---|---|
| Truck BA 1 Kha 4521 | Terai | 18.0 | 18.6 | +3% (normal) | None |
| Truck BA 2 Kha 7833 | Hill | 24.0 | 25.2 | +5% (normal) | None |
| Truck BA 3 Cha 2241 | Terai | 18.0 | 26.1 | +45% (flag) | Investigate |
| Pickup BA 4 Pa 8819 | Valley | 12.0 | 14.3 | +19% (watch) | Monitor next month |
Truck BA 3 Cha 2241 at 45% over expected consumption needs immediate investigation. The causes could be mechanical (fuel injector issue, air filter clog, tyre under-inflation) or procedural (siphoning, unauthorized use). The variance report identifies the problem; the investigation determines the cause. Without per-vehicle tracking, this truck's excess cost would have remained invisible in an aggregate fuel expense line for months.
A variance threshold of 10-15% over expected is worth monitoring. Above 20% triggers investigation. The first step is always to check the mechanical state of the vehicle - excess consumption is often the first symptom of a maintenance issue, not a fuel integrity problem.
Preventing Fuel Fraud and Siphoning
Fuel fraud in fleet operations takes several forms: siphoning from the vehicle tank, filling a smaller quantity than recorded on the receipt, using the company vehicle for unauthorized personal trips, and submitting duplicate or inflated receipts for external refuels. None of these are unique to Nepal, but the cash-based nature of many fuel transactions in Nepal's informal economy makes receipt-based controls less reliable than in markets where fuel cards with transaction data are standard.
The most effective controls are procedural rather than technological: require odometer entry at every fill-up, require receipt photos for all external refuels, reconcile fuel issued against distance covered regularly, and investigate anomalies promptly. Software makes these controls practical by automating the reconciliation and flagging variances without manual calculation. The act of tracking - and the fact that drivers know their fill-ups are being analysed - reduces informal fuel diversion significantly.
For operations with company fuel tanks, a tank dipstick reading at start and end of each day, compared against recorded issues, is the most reliable anti-siphoning control. The discrepancy between dipstick and records shows any unrecorded withdrawals. This manual cross-check takes two minutes a day and is more effective than any software control alone for on-site fuel storage.
Route-based controls add another layer. If a truck assigned to a Kathmandu-Birgunj route submits a fill-up receipt from Pokhara, the route context is clearly inconsistent. Requiring drivers to record departure and arrival points with each trip log creates a geographic consistency check that can be reviewed alongside fuel records. This does not require GPS tracking - a simple trip log with start point, end point, and odometer is sufficient for basic geographic consistency review.
Fuel fraud controls work best in layers: odometer-linked fill-up records, receipt photo requirements, regular variance analysis, and prompt investigation of anomalies. Software automates the variance detection; the organizational response determines whether controls are effective in practice.
Connecting Fuel Costs to Vehicle and Route Reporting
Individual vehicle efficiency is one level of analysis. Fleet managers and finance directors also need to understand fuel cost by route, by vehicle type, and by time period. A distribution company needs to know whether the new Pokhara route is as fuel-efficient as the Terai routes it serves, and whether the three new trucks bought last year are performing better than the five-year-old vehicles they replaced. These questions require fuel data linked to route and vehicle attributes - not just a total fuel expense account in the ledger.
When fuel tracking integrates with the accounting system, the analysis becomes available without exporting data to a spreadsheet. Pivot tables across vehicle class, route, depot, and month show where fuel costs are concentrated and where efficiency gains are achievable. Budget vs. actual comparison by vehicle type helps fleet managers plan fuel budgets for the next fiscal year rather than applying a percentage increase to last year's total.
Cost-per-kilometre analysis by route is particularly useful for pricing decisions in transport businesses. If you know that the Kathmandu-Dharan route costs rū 12.50 per km in fuel (after accounting for vehicle class and load), you can price freight rates with a factual baseline rather than an estimate. Underpriced routes are sometimes only discovered when a full cost allocation shows the route is not covering its direct costs - by which point the relationship with the customer has already been priced incorrectly for months.
Fuel cost per kilometre by route is a pricing input, not just an operations metric. Transport businesses that know their route-level fuel costs can price freight accurately; those that use fleet-wide averages often underprice high-cost routes and cross-subsidize them invisibly from efficient ones.
Frequently Asked Questions
The most reliable approach is to calculate actual average consumption for each vehicle type on each route over the first 2-3 months of tracking, then use that average as the baseline benchmark. Manufacturer specifications are a starting point, but Nepal's road conditions mean actual consumption is typically 15-30% higher than manufacturer figures. Start with your own data, set the benchmark at the average of your best-performing vehicles on that route type, and flag anything more than 15% above that benchmark for review.
For small fleets (3-10 vehicles) without dedicated logistics staff, keep the process simple: drivers submit a fuel log at the end of each week with vehicle number, date, quantity, odometer, and receipt. A single administrator enters this into the system weekly and reviews the variance report. This takes about 30-45 minutes a week for a 10-vehicle fleet and provides enough data to catch significant anomalies. The goal is not real-time tracking but weekly visibility - which is far better than the monthly aggregate that most small fleets manage today.
Yes. GPS tracking adds value but is not required for basic fuel consumption analysis. Odometer-based fuel tracking works without GPS - you need the odometer at each fill-up, not a GPS track of every kilometre. GPS adds the ability to verify that the odometer reading is consistent with the actual distance the vehicle travelled and to detect unauthorized route diversions, but most Nepali fleets get significant value from odometer-based tracking alone. Start with odometer tracking; add GPS when the scale justifies the investment.
Fuel Analytics Built Into Your Fleet and Finance System
MISAC's fuel tracking module records every fill-up against a vehicle, with odometer, quantity, cost, route, and driver. Custom fields let you capture exactly the attributes that matter for your fleet - fuel type, tank number for company fuel storage, route zone, or load type. These fields are not fixed in the system; your administrator adds them through configuration, not code. Field-level access control means drivers record what they need to record and see nothing else, while fleet managers and finance directors have full reporting access.
The reporting layer is where MISAC separates from standalone fleet software. Because fuel costs post directly to the accounting ledger with vehicle and route dimensions, pivot table analysis works across any combination of dimensions without exporting to a spreadsheet. Cost per kilometre by route, consumption variance by driver, monthly trend by vehicle class - all from the same system that produces your P&L. When the finance director asks why fuel cost is up this quarter, the fleet manager can answer with a drilldown report in minutes, not a spreadsheet built overnight.
Businesses we work with have found MISAC's integrated approach particularly useful during Nepal's periodic diesel price changes - the system updates the price point for new fill-ups without recalculating historical records, keeping cost comparisons clean across price change dates. MISAC Intelligence Pvt. Ltd. builds these capabilities as part of the same ERP that handles your accounting, inventory, and HR - one system, one audit trail, no reconciliation between separate tools.
Ready to See MISAC in Action?
Connect with us to see how fuel tracking integrates with fleet management and accounting in MISAC's ERP platform.