TopN AnalyticsAutomating Weekly Vehicle-Leasing Settlement and Garage Maintenance Analytics
A leading pan-India fleet management company leasing vehicles to driver-partners.
Where things stood
A company leasing vehicles to driver-partners needs to reconcile a wide range of weekly charges per vehicle — base rent, platform earnings, and roughly fifteen distinct penalty and adjustment categories (repairs, servicing, RTO fines, accident costs, and more) — into a settlement figure.
It also separately needs to track vehicle maintenance activity (garage visits, spare-parts consumption, turnaround time) and identify vehicles being driven for unaccounted, non-revenue-generating distance.
What we built
MySQL operational data (leasing adjustments, trip data, garage jobcards, GPS data) feeds a PostgreSQL analytics warehouse, with garage analytics built via stored procedures, producing weekly settlement tables and garage-operations marts.
How it works
TopN Analytics built a weekly settlement pipeline that reconciles rent, earnings, and roughly fifteen penalty/adjustment categories per vehicle, alongside a garage-operations analytics layer tracking jobcard-level maintenance detail, city-level throughput, and spare-parts inventory consumption.
A specific, well-defined 'Dead KM' penalty identifies GPS-measured distance that can't be explained by a vehicle's logged revenue trips plus a standard allowance buffer — with penalty thresholds that vary by city and business model, and an exemption for high-trip-volume drivers regardless of dead-km volume, so the penalty targets genuine unauthorized usage rather than penalizing a vehicle's busiest drivers.
What we delivered and learned
The Dead KM penalty logic is deliberately calibrated rather than a blunt flat rule — thresholds differ by city and business model, and drivers who clear a high enough weekly trip count are exempted entirely, so the rule targets likely unauthorized usage rather than penalizing high-activity drivers.
The settlement and garage pipelines are intentionally left on manual trigger rather than a fixed schedule, giving the operations team a review step before financial figures are finalized each week.
What it's built on
Want the full picture?
We're happy to walk through the details, numbers, and trade-offs directly.