How to Track Salik Usage by Vehicle and Driver (UAE Fleet Guide 2026)

A monthly Salik statement tells a fleet manager one number: the total toll spend across the entire fleet account for the month. What it does not tell them is which of the 40 vehicles was responsible for AED 890 in toll charges last Tuesday, or whether the driver of Van-014 used the Sheikh Zayed Road toll gate at 11:30 PM when the vehicle was not scheduled to be on the road. For any fleet where toll spend matters and with dynamic pricing introduced in January 2025 raising peak-hour crossings to AED 6, it matters for virtually every commercial fleet in Dubai a combined account statement is the starting point for questions that only per-vehicle, per-driver tracking can answer.

This guide explains exactly how UAE fleet managers track Salik toll usage at the individual vehicle and driver level what data sources are required, how they are combined to attribute each crossing to the right vehicle and driver, what the resulting reports look like and what they reveal, how to set up the four-step tracking process in a fleet management platform, and how to use the per-vehicle, per-driver data for accountability, budgeting, and cost control.

Why Vehicle- and Driver-Level Tracking Matters

Identifying High-Cost Vehicles and Routes

Salik toll spend is not distributed evenly across a fleet. A vehicle assigned to a route that crosses Sheikh Zayed Road four times per day generates significantly more toll spend than a vehicle operating entirely within a toll-free corridor. Within the same route, a vehicle that makes those four crossings during peak hours (AED 6 per crossing = AED 24 per day) costs the fleet 50 percent more than an identical vehicle on the same route that times its crossings in off-peak windows (AED 4 per crossing = AED 16 per day). Without per-vehicle crossing data, the fleet manager sees a combined monthly bill but cannot identify which vehicles are generating disproportionate spend or whether scheduling changes could shift crossings to lower-rate periods.

Per-vehicle tracking makes this analysis possible. A report showing that Van-014 generated 62 crossings at an average charge of AED 4.80 per crossing last month while Sedan-022 generated 88 crossings at AED 4.68 average gives the fleet manager the specific data to ask: why does Sedan-022 cross 42 percent more times than Van-014? Is it a genuinely busier route, or is there a routing inefficiency that a schedule change could address? Is the average charge close to peak rates, suggesting that crossings are concentrated in morning and evening peak periods?

Holding Drivers Accountable for Unauthorized Crossings

When a crossing occurs on a vehicle that is not scheduled to be operating at that time, or on a route that does not match the vehicle’s assigned job, or at a toll gate that has no legitimate operational explanation for the route assigned that crossing is a cost the fleet has not authorised. Without driver-level attribution, identifying who was responsible for an after-hours crossing on a specific vehicle requires a time-consuming manual investigation: checking the vehicle log, contacting the supervisor, and potentially interviewing multiple drivers. With driver ID integrated into the fleet platform, the crossing is attributed automatically to the driver logged into that vehicle at that time making accountability immediate and the investigation unnecessary in most cases.

Driver accountability for toll usage also creates a behaviour change effect beyond the specific incidents it catches. Drivers who know that their Salik crossings are tracked to their individual ID are significantly less likely to use company vehicles for personal travel through toll gates both because the crossing will be visible and because the potential for personal journeys to be caught makes the risk not worth taking. This deterrent effect operates continuously once drivers are aware that per-driver tracking is active.

What Data You Need to Track Salik by Vehicle

Salik Account Statement Gate, Time, and Charge

The Salik account statement is the primary data source for toll tracking: it records every crossing on the fleet’s registered Salik tags with three key data fields per crossing the gate identifier (which of the 10 active Salik gates was crossed), the timestamp (date and time of crossing to the second), and the charge applied (AED 6 peak, AED 4 off-peak, or free for crossings between 1:00 AM and 6:00 AM). The statement is available from the Salik portal as a downloadable CSV export or, for fleets using a fleet management platform with Salik API integration, as a real-time data feed that populates the platform’s toll monitoring module automatically.

The gate identifier field is the geographic anchor of the crossing record: each of the 10 active Salik gates corresponds to a specific physical location on Dubai’s road network. Matching the gate identifier to GPS coordinates enables the fleet management platform to plot each crossing on the vehicle’s GPS trip map confirming that the vehicle was at the correct location at the time the crossing was recorded, or identifying discrepancies that suggest data quality issues or tag misassignment.

GPS Trip History Per Vehicle

The GPS trip history for each fleet vehicle is the matching data source that converts the Salik account statement from a flat list of crossings into vehicle-attributed records. The matching logic is straightforward: for each crossing in the Salik statement, the fleet management platform identifies which vehicle’s GPS record places it at or within range of the corresponding Salik gate at the time of the crossing. Because GPS tracking records vehicle position every 30 to 60 seconds, the gate approach and departure pattern is visible in the GPS data alongside the crossing timestamp confirming the vehicle identity with high confidence.

For fleets where multiple vehicles may approach the same Salik gate within a similar time window common on major arterial routes like Sheikh Zayed Road during peak periods the GPS matching uses both the timestamp and the approaching trajectory to resolve the vehicle identity. A vehicle in the left lane approaching Al Garhoud gate at 8:14:32 AM has a distinct GPS trajectory from a vehicle in the right lane at 8:14:45 AM; both can be attributed separately even when the crossing timestamps are close.

What Data You Need to Track Salik by Driver

Driver ID iButton, RFID, or Mobile App Login

Attributing Salik crossings to individual drivers requires a driver identification mechanism that records which driver was operating each vehicle at the time of each crossing. Three technology approaches are standard in UAE fleet deployments. iButton identification uses a small electronic key that the driver touches to a reader on the vehicle dashboard at the start of their shift the key’s unique ID is recorded in the fleet platform and associated with all GPS events and Salik crossings from that vehicle for the duration of the driver’s session. RFID key fob identification operates on the same principle using a passive proximity fob rather than a contact-based iButton. Mobile app login identification requires the driver to log in through the fleet management platform’s driver app at shift start providing a software-based identification record that does not require additional hardware beyond the driver’s company phone.

Each approach has operational advantages that suit different fleet types: iButton is most reliable for large fleets with disciplined handover procedures where drivers reliably touch in and touch out; RFID is faster for high-turnover fleet environments; mobile app login is most appropriate for fleets where driver smartphones are already an operational tool. All three produce the same outcome: a driver ID record linked to every GPS event and every Salik crossing during the driver’s session, enabling per-driver toll attribution.

Shift and Assignment Records

Driver ID data is most valuable when combined with the planned shift and vehicle assignment record the data that describes which driver was supposed to be operating which vehicle, on which route, during which hours. Comparing the actual driver ID record (who was actually operating the vehicle based on their iButton or RFID identification) against the planned assignment record (who was supposed to be operating the vehicle) identifies assignment deviations: a vehicle operated by an unassigned driver, a vehicle operated outside scheduled hours with no driver ID recorded, or a vehicle whose driver ID shows a different driver from the scheduled assignment without a documented handover.

For Salik cost management specifically, the shift record comparison identifies the crossings that occurred when no authorised driver was assigned to the vehicle the clearest indicator of unauthorised vehicle use. A crossing at 10:45 PM on a vehicle whose last scheduled shift ended at 6:00 PM, with no driver ID recorded for the vehicle after 6:00 PM, is an unauthorised crossing that neither the Salik statement nor the GPS record alone would flag without the shift record comparison.

Sample Per-Vehicle Salik Usage Report

The following table illustrates the per-vehicle Salik report format that a fleet management platform generates from the combined Salik statement and GPS trip matching:

Key insights from this sample report: Sedan-022 has 88 crossings but 52 at peak rate (AED 6) the highest peak proportion in the fleet, contributing disproportionately to total cost. Sedan-009 shows a strong scheduling pattern with all 44 crossings in off-peak windows the model route for toll cost management. Bus-003’s single off-route crossing warrants investigation against the route assignment for the flagged date.

How to Set Up Vehicle and Driver-Level Salik Tracking

The four-step setup process moves from data connection to automated reporting applicable whether deploying a dedicated Salik monitoring module or configuring an existing fleet management platform to add Salik attribution.

Step 1 Sync Salik Account Data with Your Fleet Platform

The starting point is connecting the fleet’s Salik account data to the fleet management platform. Two connection methods are available: manual CSV import (exporting the monthly or weekly crossing statement from the Salik portal and importing it into the fleet platform’s toll module) or API integration (where the fleet management platform connects directly to the Salik data API and pulls crossing records automatically at configured intervals). API integration is operationally superior it eliminates the manual export-import cycle, enables real-time crossing visibility as it occurs rather than monthly reconciliation, and removes the data re-entry risk that manual CSV import creates. VZone International’s platform uses API integration as the standard Salik connection method.

During setup, each Salik tag registered on the fleet account must be mapped to the corresponding vehicle in the fleet management platform creating the tag-to-vehicle association that enables automatic crossing attribution. For fleets where tags are permanently fitted to vehicles (the standard configuration), this mapping is a one-time setup task. For fleets where tags are transferred between vehicles (less common but present in rental and mixed-fleet operations), the tag-to-vehicle mapping must include a time dimension that tracks tag reassignment events.

Step 2 Match Crossings to GPS Trip Logs by Vehicle

Once the Salik account data is connected, the platform matches each crossing to the vehicle GPS record using the timestamp and gate location. The matching algorithm compares each crossing timestamp against the GPS position records for all fleet vehicles at that time identifying which vehicle was at the corresponding Salik gate location within the expected crossing time window (typically plus or minus 60 seconds of the recorded crossing time). The match is confirmed when the GPS record shows the vehicle approaching the gate from the expected direction, crossing through the gate zone, and departing on the expected exit trajectory.

High-confidence matches where the GPS record places one vehicle clearly at the gate at the crossing time with no other fleet vehicle within 500 metres are attributed automatically. Low-confidence matches where two vehicles are in proximity to the same gate at similar times are flagged for manual review. In practice, the automated matching confidence rate for standard fleet operations is above 97 percent; the 2 to 3 percent requiring manual review are typically multi-vehicle close-approach scenarios on busy routes that a 30-second timestamp review resolves in seconds.

Step 3 Link Trips to the Assigned Driver

With crossings attributed to vehicles, the driver attribution step links each vehicle trip (and its associated crossings) to the driver ID record active for that vehicle at that time. The platform checks the driver ID log iButton touch-in events, RFID proximity records, or mobile app login sessions and identifies the driver session that was active during each crossing. For crossings that occur within an active driver session (driver has logged in and not yet logged out), the attribution is automatic. For crossings that occur outside any active driver session (no driver has logged in since the previous session ended), the crossing is flagged as unattributed indicating the vehicle was used without a driver login, which itself is a fleet policy flag.

The output of the driver attribution step is a per-driver crossing record: every crossing in the month attributed to the driver who was operating the vehicle at that time. This record feeds the per-driver Salik usage report showing each driver’s monthly crossing count, total toll cost, crossing time pattern (peak vs off-peak), and any flagged crossings outside scheduled hours or off expected route.

Step 4 Build Recurring Vehicle and Driver Reports

The final setup step is configuring the automated reporting cycle that delivers per-vehicle and per-driver Salik reports to the relevant stakeholders at the defined frequency. Standard configuration for most UAE fleet operations includes: weekly vehicle-level crossing summary to the fleet manager (showing total crossings, cost, and flagged events for each vehicle in the past 7 days); monthly vehicle-level full report to finance (showing the per-vehicle breakdown that feeds Salik cost allocation); monthly driver-level report to the safety and operations manager (showing per-driver crossing counts, cost, and flag events for coaching or investigation); and real-time alerts to the fleet manager or operations supervisor when a crossing occurs outside scheduled hours, outside expected route, or above a configured per-vehicle daily threshold.

Automated reports eliminate the weekly manual data extraction exercise that fleet managers without platform integration perform typically 2 to 4 hours per week across a medium-sized fleet. The reports arrive in the relevant stakeholder’s inbox at the configured time without any manual trigger, formatted for immediate review rather than requiring additional processing before they are usable.

Using Per-Vehicle and Per-Driver Data for Accountability and Cost Control

Spotting Patterns After-Hours, Off-Route, and Repeated Crossings

The highest-value output from per-vehicle, per-driver Salik tracking is not the monthly cost summary it is the pattern detection that identifies systematic waste or misuse that individual crossing reviews miss. A single after-hours crossing on Van-014 might be a legitimate emergency trip. Five after-hours crossings on Van-014 across the same three-week period, all within 2 hours of the same driver’s standard shift end, is a pattern that requires investigation. A fleet management platform that generates automated pattern alerts flagging vehicles or drivers with recurring crossing anomalies rather than requiring the fleet manager to review all individual crossing records converts the raw data into the management intelligence that actually drives action.

Route deviation detection is the second high-value pattern: a vehicle that consistently generates Salik crossings at Al Barsha gate when its assigned route should not take it through that area is using a route that either needs route correction (if the deviation is legitimate and efficient) or driver investigation (if the deviation represents personal travel or route negligence). GPS route history alongside the Salik crossing record makes this analysis immediate the map overlay shows the vehicle’s actual path alongside its assigned route, with toll gate crossings marked at their locations.

Setting Per-Vehicle Toll Budgets and Monitoring Compliance

Per-vehicle Salik budgets monthly AED ceilings for each vehicle based on its route and operational profile are the cost management tool that converts per-vehicle tracking data into spending control. A vehicle assigned to a route that historically generates 50 crossings per month at approximately AED 4.50 average should have a budget of approximately AED 230 per month. When the vehicle’s crossing count or cost approaches the budget ceiling during the month, an alert fires to the fleet manager enabling investigation before the budget is exceeded rather than discovering the overage in the monthly reconciliation.

Budget compliance rates across the fleet give the operations director a single-line view of toll cost management performance: a fleet where 38 of 40 vehicles are within budget every month is a well-managed fleet; a fleet where 12 vehicles consistently exceed their budgets by more than 20 percent has a systematic route or behaviour issue that the per-vehicle data can diagnose.

Dynamic Pricing and the Value of Crossing Time Data

Since January 31, 2025, Salik operates on dynamic pricing AED 6 for crossings during peak hours (7:00 AM to 9:00 AM and 5:00 PM to 8:00 PM on weekdays), AED 4 for off-peak crossings, and free for crossings between 1:00 AM and 6:00 AM. For a vehicle making 60 crossings per month, the difference between all crossings at peak rate (AED 360) and all crossings at off-peak rate (AED 240) is AED 120 per vehicle per month AED 1,440 per vehicle per year. Across a 40-vehicle fleet, optimising crossing times from peak to off-peak across just 30 percent of crossings represents AED 17,280 per year in pure toll cost saving without any change to the number of crossings made.

Per-vehicle crossing time reports showing the peak, off-peak, and free breakdown for each vehicle are the input for this optimisation. Vehicles whose routes allow schedule flexibility (early morning or evening deliveries that can be shifted slightly) benefit from route scheduling analysis that targets off-peak crossing windows. Vehicles on fixed-time delivery commitments cannot easily shift their crossing times, but knowing the unavoidable cost provides the finance team with accurate toll cost projection rather than estimates based on the pre-dynamic-pricing flat rate.

Conclusion: A Combined Statement Is Where Cost Visibility Ends Per-Vehicle Tracking Is Where Control Begins

The monthly Salik combined statement is the last point at which toll costs are manageable only at the fleet aggregate level. Every management action below that aggregate identifying which vehicles are generating excess spend, holding individual drivers accountable for unauthorized crossings, optimising schedules to shift crossings from peak to off-peak rates, setting per-vehicle budgets, and detecting the systematic patterns of misuse that a combined statement makes invisible requires per-vehicle, per-driver crossing data.

The technology to produce that data exists and is operational: Salik API integration pulls crossing records in real time; GPS trip matching attributes each crossing to the correct vehicle automatically; driver ID assignment links each trip and crossing to a named individual; and automated report generation delivers the per-vehicle and per-driver summaries that the fleet manager, safety team, and finance department each need in the format they need it, at the frequency they need it, without requiring manual data compilation from any of them.

VZone International’s fleet management platform implements all four steps Salik API connection, GPS crossing attribution, driver ID integration, and automated per-vehicle and per-driver reporting as a standard configuration for UAE fleet clients. The per-vehicle Salik breakdown that transforms the combined statement from a budget line into a management tool is accessible from the same Wialon dashboard that provides GPS tracking, driver safety scores, fuel monitoring, and compliance data for every other aspect of UAE fleet operations.

Frequently Asked Questions