·
·
·
·
·
·
·
·
·
·
··
·
·
·
·
·
·
·
·
Any corporate that outsources employee transportation to a cab vendor and pays distance-based bills is exposed to overbilling — with zero tools to challenge it today.
Large campuses, shift-based rosters, hundreds of daily cab movements
Fixed shift timings, repeated routes, high volume of daily trips
24/7 operations, late-night shifts, employee safety and billing both critical
This isn't about dishonest vendors. It's about a broken system where the vendor controls the distance data and the corporate has no independent source of truth.
A small Ajjas GPS device is fitted in each cab. From that moment, every kilometer is independently recorded by your system — not the vendor's.
A compact Ajjas IoT tracker is installed in each vendor cab. IP67-rated, tamper-resistant, works across India's road conditions. Quick IMEI or QR-code onboarding in CABTRACK — your device, your data.
The moment a cab starts moving, Ajjas records the route, the start and end points, the duration, and the exact distance — updated every 10 seconds. The cab's status is visible live on your CABTRACK dashboard.
When the vendor's monthly invoice arrives, your transport team opens CABTRACK, pulls the verified odometer readings for each cab, and reconciles against the vendor's claimed distances. Discrepancies are flagged instantly — with GPS-backed evidence you can actually use.
Approve what matches. Dispute what doesn't — with a downloadable trip log, timestamps, and route proof. The vendor knows you have independent verification. Overbilling drops simply because it can now be caught.
Your transport team sees this every morning. Flagged trips are ready for dispute. Matched trips are approved instantly.
| Cab / Route | Vendor km | Ajjas km | Difference | Status |
|---|---|---|---|---|
| MH12 AB 4521 · Office → Airport · 8:30 AM | 62 km | 49 km | ↑ +13 km | Flagged |
| MH04 CD 8812 · Airport → Office · 11:15 AM | 51 km | 50 km | +1 km | Approved |
| GJ05 EF 3309 · Shift pickup · Surat · 6:00 AM | 88 km | 61 km | ↑ +27 km | Flagged |
| DL01 GH 7734 · Late shift drop · Delhi · 2:00 AM | 34 km | 33 km | +1 km | Approved |
| MH09 WX 2201 · Employee pickup · Pune · 9:00 AM | 74 km | 52 km | ↑ +22 km | Flagged |
Once Ajjas is in the cab, your transport team gets a full operational view — not just a billing checker.
| Situation | Without Ajjas | With Ajjas CABTRACK |
|---|---|---|
| Billing basis | Vendor's odometer — unverified | GPS odometer — your independent data |
| Disputing an invoice | No evidence. Vendor wins. | Timestamped GPS route log, court-admissible |
| Knowing where a cab is | Call the driver. Hope for honesty. | Live map, 10-second updates |
| Employee safety at night | No visibility after cab leaves | Route deviation alerts + trip completion |
| Adding a new cab | Paperwork, calls, delays | QR scan — live in 60 seconds |
| Monthly vendor reconciliation | Manual cross-check, hours of work | Auto-flagged discrepancy report |
| Driver behaviour accountability | Complaint-based only | Per-driver score, shareable with vendor |
Whether you run 10 cabs or 1,000 — Ajjas gives you the independent intelligence to operate smarter and cut costs.
Measured data about what your vehicles actually did, independent of whoever reports it to you — distance travelled, trip records, driving behaviour and location, all collected by a device under your control. Your team uses that data inside your existing billing and audit process. Ajjas supplies the measurement; it does not generate or approve invoices.
Both, and they are recorded separately. Where a vehicle exposes odometer data through its OBD port, Ajjas reads the actual odometer. Every Ajjas device also computes trip distance from GPS, so there is a reading even on vehicles that do not expose it. Keeping the two figures apart is deliberate — it lets you compare rather than take one number on trust.
Yes — driving behaviour is already captured on every trip, not added as an option. Harsh braking, speeding, harsh cornering and idling are recorded and rolled into a driver score, which can also be viewed by vendor. For employee transport, that gives you a safety record sitting alongside the billing record, with nothing extra to fit.
It gives you a number the vendor did not produce. When a transport vendor bills for a month of trips, your team can set their figure against distance measured by a device on your account, trip by trip. Small variance between any two measurements is normal. A consistent gap in one direction is what is worth raising.
Your company. The devices and the account sit with you, not with the vendor being billed — data supplied by the party you are checking is not independent data. Access follows a hierarchy you define, so an administrator sees everything while a regional or vendor-level manager sees only the vehicles in their scope. Who gets visibility is your decision, not the vendor's.
Yes. Every device is mapped to one vehicle by its registration number, and all your vehicles sit in a single account, so several transport vendors run side by side in one view rather than in separate systems. Access can be grouped by vendor so each set stays separate, and vehicles are added or removed as your contracts change.
In practice, yes — the vehicles belong to them, so it is written into the transport contract or agreed at renewal. The practical objection is smaller than most people expect: the device plugs into the vehicle's OBD port, so there is no workshop visit, no wiring and no vehicle taken off the road. Each device is then mapped to that vehicle's registration number.
An alert. Removing a device notifies the administrator, and alerts can also go to nominated people by SMS or WhatsApp, so a removal becomes a recorded event that somebody has to account for rather than a quiet gap in the record. A driver who unplugs the device before a trip has, in effect, reported himself for doing it.
Ajjas does not sell a swap-station product, but the assets moving through a swapping network are exactly what the platform tracks: vehicles and batteries in circulation, where they are, how much they are being used, and pack condition where the battery management system exposes it. Describe your asset flow and the team will tell you what is workable.