Salik and Darb disputes are the most-ignored revenue recovery channel in UAE rent-a-car operations. Most operators believe a posted toll is final. It isn't. Eight specific dispute scenarios are winnable within the regulator's 30-day window ÔÇö if you know the evidence pattern each one demands. This is the scenario-by-scenario playbook for getting unrecognised, duplicate, or wrongly-attributed Salik and Darb charges removed from your account, with the documentation each scenario needs and the realistic success rate per category.
Scenario 1 ÔÇö Customer denies passing the gantry
Your renter calls saying "I never went to that bridge / road." The pass appears in your account. Win conditions:
- Telematics log showing the vehicle was elsewhere at the timestamp.
- Customer screenshot of their location-tracker at the moment.
- Photographic evidence (parking-lot CCTV, hotel-room photo with timestamp).
Success rate: ~55% if telematics shows the vehicle was demonstrably elsewhere. If telematics confirms the pass, the customer is wrong ÔÇö politely close the dispute.
Scenario 2 ÔÇö Tag scanned twice within 60 seconds
A vehicle physically passes one gantry but is charged twice. Common at Al Garhoud, Al Maktoum, or any high-volume crossing during peak hours when antennae double-read.
- Submit dispute citing impossible physics ÔÇö a single car can't pass the same gantry twice in 60 seconds.
- Attach screenshot showing both charges from your statement.
Success rate: 80-90%. This is RTA's most-common admitted technical error.
Scenario 3 ÔÇö Tag scanned but vehicle was in garage
Charge timestamps when the car was demonstrably stationary. Causes: defective tag broadcasting at idle, or RFID interference from a vehicle passing nearby with a near-duplicate tag.
- Workshop entry/exit log timestamps.
- Service ticket from workshop covering the period.
- CCTV from your lot or workshop.
Success rate: 75-85% with workshop documentation.
Scenario 4 ÔÇö Customer paid but you got the bill
Some customers carry their own Salik tag (UAE residents). A scenario can arise where the resident customer's tag is active in your car alongside your tag ÔÇö but RTA bills your tag account. Or the rental contract was supposed to include Salik passthrough but the customer claims they were promised "no Salik charges."
- Signed rental contract clause on Salik passthrough.
- WhatsApp / email trail showing the customer was informed.
- Photographic evidence of the tag arrangement at handover.
Win the dispute by billing the customer per contract ÔÇö not by disputing the Salik charge itself (the charge is valid; the question is who pays).
Scenario 5 ÔÇö Tag damaged mid-rental
The tag falls off, gets removed, or breaks. The car then passes gantries without a tag ÔÇö generating "violation" fines (~AED 100/pass) instead of normal toll charges.
- Photographic evidence of tag damage / loss.
- Replacement tag receipt with date.
- Customer acknowledgement at return (if known about pre-return).
Dispute the violation fines as "tag malfunction" ÔÇö RTA typically converts the violation to standard tolls. Success rate: 70%.
Scenario 6 ÔÇö Post-rental gantry pass
Customer ends rental at 2 PM. A toll appears at 6 PM on the same day ÔÇö meaning the customer kept the car after the contract ended. Common when customers "extend" without notifying.
- Contract end time vs toll timestamp.
- Vehicle return-photo timestamp.
- WhatsApp / call log showing un-communicated overrun.
This is a contract-violation billback, not a Salik dispute ÔÇö but the documentation matters for chargeback defence.
Scenario 7 ÔÇö Long-haul transfer between customers
A car returns from one customer's rental, gets driven to your second branch by a staff member, then gets rented again. The transfer-drive tolls accumulate on YOUR account. Not customer-billable.
- Internal transfer log with driver name, time, route.
- Mark these as "operator-absorbed Salik" in your accounting ÔÇö don't try to bill back.
Reconciliation matters but no dispute is filed.
Scenario 8 ÔÇö Replacement / loaner vehicle edge case
Your customer's car had a breakdown. You swap them into a replacement. The original car comes back via tow. Toll charges from BOTH vehicles appear during the transition window. Some are customer-billable; others are operator-side.
- Detailed swap timestamp + log.
- Tow-recovery paperwork showing original car's transit.
- Customer-rental-on-replacement contract.
Allocate carefully. Customer pays only for tolls under THEIR active possession.
The escalation path
- Day 1-7 after charge: Submit dispute via the RTA Salik portal. Free of charge.
- Day 14-21: If no response, follow up via phone or in-person at RTA Customer Happiness Centre.
- Day 21-30: Escalate to RTA Director's office if the matter is material (AED 1,000+).
- Beyond 30 days: Dispute window closes. Tolls become final.
The data discipline that wins disputes
Operators with high dispute success rates share three habits:
- Telematics on every car ÔÇö independent location/time data.
- Rental ERP that auto-matches Salik passes to active contracts on import.
- Workshop ticket system with timestamps.
Without these, even legitimate disputes get rejected for "insufficient evidence."
The financial impact
For a 20-car fleet, typical UAE rental experience:
- Total Salik passes per year: ~9,000-12,000.
- Disputable scenarios (across all 8 categories): 3-5% of passes.
- Estimated value: AED 12,000-25,000/year in recoverable disputes.
Operators who file disputes systematically recover most of this. Operators who treat tolls as "the cost of doing business" lose it permanently.
FAQs from operators handling Salik disputes
Can I dispute a Darb (Abu Dhabi) charge with the same process?
Yes ÔÇö Darb has a parallel dispute portal under the Department of Transport. Similar 30-day window, similar evidence requirements. Success rates are slightly lower (~10-15% lower than Salik) because Darb is a newer system with less mature dispute mediation.
What if the dispute is rejected?
You can re-file with new evidence once. After that the charge is final. Operators who keep filing without new evidence get flagged and lose dispute-portal access entirely.
How do we communicate Salik billbacks to customers during dispute?
Charge the customer per contract regardless. If the dispute succeeds AFTER you've billed the customer, refund the customer the disputed amount. This protects cashflow during the 30-day dispute window.
Should we file disputes in-house or use a third-party service?
In-house for 5+ cars. Third-party services charge 25-40% of recovered amount ÔÇö economical only if your in-house team can't keep up with volume. Most ERP platforms now include dispute-filing helpers.
What's the time investment per dispute?
10-20 minutes for clear scenarios (2, 3, 5). 30-60 minutes for ambiguous ones (1, 4, 8). Scenarios 6 and 7 are not disputes ÔÇö they're billing reconciliation, faster but still 10-15 minutes each.
What documentation does the RTA Salik portal accept?
PDF or image attachments up to 5MB each. Multiple attachments allowed per dispute. Common acceptable evidence: telematics reports (in PDF), workshop service tickets, CCTV stills, customer screenshots, rental contracts. Word documents and Excel files are NOT accepted ÔÇö convert to PDF before upload. Submit in English; the portal supports Arabic but English is faster for review.
How does Darb (Abu Dhabi) compare procedurally to Salik?
The Darb dispute portal is similar but with two key differences: (a) dispute window is 21 days vs Salik's 30; (b) Darb's review team is smaller, so processing takes 18-30 days vs Salik's 7-21 days. Plan Darb disputes earlier in the dispute window to avoid window-closure issues.
Can we automate dispute filing via an ERP integration?
Partially. Some UAE rental ERPs detect dispute-candidate Salik passes automatically (duplicates, workshop-window passes, etc.) and pre-fill the dispute form. Final submission still requires human review and click. Full end-to-end automation is not yet available because RTA portal lacks an open API for third-party submission.
What's the relationship between Salik recovery rate and customer pre-authorisation?
Higher pre-authorisation amount on the card at booking enables more aggressive post-rental billback. With AED 1,500 pre-auth: you can confidently charge up to that limit for post-rental fines/Salik. With AED 500 pre-auth: each fine notification requires re-authorisation. The simpler practice ÔÇö bigger pre-auth ÔÇö protects recovery rate.
Stop running your UAE rental on goodwill and Excel
Every operational pain in this article maps to a feature in PRO-VIA Portal ÔÇö UAE's purpose-built rental ERP. FTA-compliant invoicing, Salik & fines reconciliation, digital handover, owner statements, multi-branch reporting, telematics integration. Built in Dubai for UAE rental operators.
Plans from AED 290/month. Start your portal in 10 minutes ÔåÆ ┬À compare plans
Frequently asked questions
What if I want to take a rental to Oman or Saudi?
Cross-border travel requires a written NOC from the rental operator, an insurance endorsement extending cover to the destination country, and validation that the customer's licence allows driving there. Most operators charge AED 100–300 for the extension paperwork and condition it on a higher deposit.
How long do I need to retain rental contracts?
Civil rentals: minimum 7 years for VAT/CT audit purposes. Damage / dispute related: longer if any legal interest persists. PDPL allows retention of customer PII as long as a legal-or-contractual basis exists, but you must define the policy and follow it consistently.
What's the riskiest compliance corner most operators miss?
Mulkiya transfer on used-car purchases — pending fines from the previous owner attach to the vehicle and become yours unless cleared at transfer. RTA inspection requirements vary by emirate and routinely delay renewal. Build a tracker that flags both.
How does UAE VAT 5% apply to rentals?
Standard 5% applies to the rental fee itself. Salik recharges, fines and damage waivers have specific treatments under FTA guidance — most operators get this wrong by treating Salik as zero-rated. Cross-border rentals and short-term insurance have nuanced rules worth checking with your accountant.