Unbilled Salik trips — toll passages incurred during customer rentals that the operator failed to bill back to the customer — represent one of the most common margin-leakage patterns at UAE rental operators, costing AED 4,500 to AED 28,000 per fleet per year in absorbed toll cost that should have been recovered through customer billing. The leakage occurs because the salik notification system has timing delays, the customer-billing process has gaps, and operators without structured processes default to absorbing the unbilled tolls rather than chasing post-rental customers for small amounts. The systematic checklist that prevents the leakage is knowable and the implementation is straightforward.
The Salik (Dubai's toll system) and Darb (Abu Dhabi's toll system) operate through automatic transponder readers that charge the vehicle's registered account at each passage. The standard charge per passage is AED 4 for Salik and AED 4 for Darb. A typical rental vehicle accumulates 4 to 20 toll passages per rental, depending on customer driving pattern and route choice. The aggregated toll cost per rental ranges AED 16 to AED 80 for typical rentals, AED 100 to AED 400 for high-mileage corporate or tourist rentals.
The notification timing reality
Salik passages do not appear in the operator's account in real time. The typical notification timeline: the passage occurs, Salik's central system processes within hours, the operator's account is debited within 24 to 72 hours, the operator's accounting system surfaces the charge within the next reporting cycle (typically next-day if integrated, end-of-week or end-of-month if manual). The cumulative delay between passage and operator-visibility ranges from 1 to 14 days.
The customer-billing implication: many rentals are completed and the customer has departed before the salik charges become visible. The customer's pre-authorisation may have been released, the payment method may not be available for additional charges, the customer may not respond to post-rental billing requests for small amounts.
Mistake one: failure to anticipate salik in the pre-auth structure
Operators whose pre-auth amount is set without consideration of expected salik exposure routinely face the unbilled-salik problem because the pre-auth is captured at return based on visible charges, leaving no buffer for subsequent salik notifications. The fix is pre-auth structure that includes a salik allowance for routes likely to incur toll charges.
The discipline: per-rental pre-auth includes a salik allowance based on rental duration and destination (Dubai-area rentals AED 50 to AED 200, multi-day Dubai rentals AED 150 to AED 400, Abu Dhabi to Dubai cross-emirate rentals AED 100 to AED 250). The allowance is held against the pre-auth until salik notifications resolve.
Mistake two: pre-auth released before salik notifications resolve
Operators who release the entire pre-auth at rental return without holding the salik allowance frequently find themselves billing the customer post-release. The fix is to hold the salik allowance for a defined window post-return (typically 7 to 14 days, aligned with the salik notification delay), with the salik-specific portion released only after the notification window closes or the actual salik charges are captured.
The customer-experience trade-off: the customer sees a smaller residual hold for 7 to 14 days rather than full pre-auth release. Clear communication at return about the structured hold timing reduces the customer-experience friction.
Mistake three: no post-rental customer-billing process for unbilled salik
When salik notifications arrive after the pre-auth has fully released, the operator needs a structured process to bill the customer through alternative channels: email invoice with payment link, charge against stored card on file (if the customer agreed to recurring charges), follow-up communication with payment options.
The operators who skip this process default to absorbing the unbilled salik. The economic impact at typical volumes is meaningful enough to justify the process investment. The customer-experience consideration: be reasonable on small amounts (under AED 20) where the collection effort exceeds the recovery, aggressive on larger amounts where the cost-recovery justifies the effort.
Mistake four: salik charges not reconciled against rental records
The salik account aggregates charges across all vehicles in the fleet. Without per-vehicle and per-rental allocation, the operator cannot identify which charges belong to which customer rental. The fix is salik-to-rental reconciliation: salik passage timestamps matched to rental records (which customer had the vehicle at that time), with each charge allocated to a specific rental.
The reconciliation can be manual (time-consuming for large fleets), spreadsheet-based (workable for mid-scale fleets), or ERP-integrated (the standard for mature operators). The reconciliation quality determines whether unbilled-salik patterns can be identified and addressed.
Mistake five: customer disputes accepted without verification
Customers occasionally dispute salik charges, claiming they did not use the toll route. Operators accepting disputes without verification either absorb legitimate charges or refuse legitimate disputes inconsistently. The fix is structured dispute handling: pull the specific salik passage details (date, time, location) and compare against the rental period and the vehicle's GPS location data if available, accept the dispute if the customer's claim is supported by data, decline with documentation if not supported.
The customer-communication discipline
Clear communication about salik handling at rental start reduces disputes and supports post-rental billing acceptance. The communication that works: "Salik tolls are charged to your account based on actual passages during your rental. We hold AED [X] against pre-auth for expected tolls. Final settlement within 14 days after notification from Salik." The transparent framing produces customer acceptance even when post-rental billing occurs.
The communication that fails: silent handling of salik with surprise charges weeks later. The customer's experience is "they charged me again after I returned the vehicle" regardless of policy legitimacy.
The cross-jurisdiction consideration for Abu Dhabi (Darb) and Sharjah
Salik is Dubai's toll system; Darb is Abu Dhabi's; Sharjah does not currently operate a tolling system. Customers driving across emirates may incur both Salik and Darb charges depending on route. The reconciliation discipline should track both systems with appropriate per-system accounting and customer billing.
Checklist: unbilled salik prevention discipline
- Per-rental pre-auth includes salik allowance based on duration and route.
- Salik allowance held for 7 to 14 days post-return until notifications resolve.
- Post-rental customer-billing process for unbilled salik after pre-auth release.
- Salik-to-rental reconciliation matching passages to specific rentals.
- Per-vehicle salik allocation supporting the reconciliation.
- Dispute handling with verification against passage details and rental records.
- Customer communication at rental start explaining salik handling.
- Receipt at rental return showing salik allowance status.
- Cross-jurisdiction tracking for Darb and Salik separately.
- Monthly review of unbilled salik patterns to identify process gaps.
Frequently asked questions
What is the typical salik exposure per rental? AED 16 to AED 80 for typical Dubai-area rentals, AED 100 to AED 400 for high-mileage corporate or tourist rentals. Variance depends substantially on route choice and rental duration.
How long should I hold the salik allowance against pre-auth? 7 to 14 days post-return aligns with typical salik notification delays. Longer holds frustrate customers; shorter holds risk unbilled exposure.
Should I charge a service fee on salik pass-through? Many operators add a modest administrative fee (AED 5 to AED 15 per rental with salik passages) to cover the reconciliation and billing overhead. The fee should be transparent at booking.
What is the right minimum unbilled salik to chase post-rental? AED 20 is a reasonable threshold — amounts below this typically cost more to collect than the recovery. Amounts above this should be pursued through structured billing.
How do I handle the customer who disputes that they used the toll route? Verify against passage details and GPS data if available. Accept the dispute if data supports; decline with documentation if not.
Can I bill salik against a stored card on file? Yes, with the customer's explicit consent at the original transaction. Document the consent clearly.
What is the right discipline for cross-emirate rentals that incur both Salik and Darb? Track each separately with appropriate per-system reconciliation, with consolidated customer billing showing both jurisdictions.
What is the most common unbilled-salik operator mistake? Failing to include salik allowance in the pre-auth structure. The single discipline prevents most of the unbilled-salik exposure.
Operate UAE rentals at the level customers expect in 2026
PRO-VIA Portal — UAE's purpose-built rental ERP. FTA invoicing, Salik & fines reconciliation, owner statements, digital handover, multi-branch reporting. Built in Dubai for operators ready to scale beyond spreadsheets.
Plans from AED 290/month. Start your portal in 10 minutes → · compare plans