A Salik fine almost never happens because a driver deliberately ran a toll gate without paying. It happens because a vehicle changed hands mid-shift, a tag was linked to the wrong plate after a swap, or nobody caught that a balance had run low until three weeks of charges had already stacked up. By the time the fine arrives, the driver who was behind the wheel that day is often not even the one operating that vehicle anymore.
The gap is between the vehicle and the driver, not the toll gate
Salik tracking only works as a deterrent if it is tied to what actually happened on the road: which driver was assigned to which vehicle, on which day. A fleet that tracks toll spend at the vehicle level but assignments at the driver level in a separate system has two records that quietly drift apart, and the fine lands on whoever the paperwork blames, not whoever was driving.
Dedup matters more than detection
Once a fleet grows past a handful of vehicles, the real problem is not missing a toll charge, it is seeing the same expiring-document or low-balance warning five times because nobody marked it read. Alert fatigue is how a genuinely important warning gets ignored the one time it matters.
What we built into FleetManager
Salik costs post against the vehicle and the assigned driver together, and document or balance alerts are deduplicated rather than repeated, so a warning that has already been seen does not bury the one that has not. See how FleetManager tracks it. The fine still happens sometimes. Figuring out afterward exactly who was driving and why does not have to.