Transportation ERP Consultant, UAE

Several fleet businesses inside one company

A UAE transport company often carries several fleet lines that behave like separate businesses. Container trucks shuttle between the ports, inland depots and customer warehouses and are paid per move. Tankers deliver water or fuel and may be paid per load. Buses carry workers between accommodation and sites, or children to schools, on monthly contracts per route. Low-bed trailers move cranes and excavators at short notice and bill per job or per day.

Each line has its own billing logic, its own vehicles and often its own drivers, but they share a workshop, a parts store, a yard and an accounts team. When costs are booked only at company level, the bus contracts can quietly subsidize an underpriced tanker contract, and nobody notices until the renewal is negotiated.

My first step is to describe each line as its own process: how work is ordered, assigned, evidenced and billed. Then I design cost centers by line and vehicle, with clear rules for sharing workshop, yard and supervision costs. This page is about operators with their own vehicles; for forwarders and 3PLs see logistics ERP in the UAE, and for the general fleet model see ERP for transportation.

Tolls, fines and fuel: costs that arrive by plate, not by trip

A UAE fleet's variable costs mostly arrive tied to a toll tag or plate number. Salik in Dubai and Darb in Abu Dhabi charge tolls to the vehicle's account. Traffic fines are issued against the plate. Fuel comes through fleet cards or company accounts at stations. None of these documents mentions the trip, the customer or, often, the driver.

To make them useful, the ERP needs three keys at every moment: which vehicle, which driver and which trip or contract. Telematics and the trip log provide time and location; toll and fine statements provide date, time and plate. I design matching rules that use those keys to allocate each charge, plus exception queues for anything that does not match.

Then the policy decisions follow. Which tolls are recharged to customers under the contract. Which fines are recovered from drivers, with what approval, and how that appears on payroll. How fuel above an expected consumption per route is flagged for review. These rules belong to management, not the software, but the system must be able to apply them consistently month after month, and show the operations manager what was allocated where.

Driver costs, visas and the Wage Protection System

Drivers in UAE fleets are typically employed on company-sponsored visas, and the employer carries a set of costs that never appear on a fuel or trip report: visa and medical fees, health insurance, accommodation, transport to the yard and end-of-service obligations. Because wages go through the Wage Protection System, payroll must be accurate and on time, with deductions agreed and documented.

A transport ERP should build the full cost of a driver, not just the salary. I design the employee record so visa, insurance and accommodation costs are captured against the driver and then spread to the vehicles or contracts they work on. Trip allowances, overtime and recovered fines flow in from approved trip data, so the payroll file and the cost report agree.

Driver documents matter operationally too. License categories, visa expiry, medical fitness and any training required for dangerous goods or passenger transport should sit in the same record as vehicle assignments, so dispatch cannot plan someone who is not currently able to drive that vehicle. Payroll rules and end-of-service calculations should be checked with your HR and legal advisors before they are configured.

Registration renewals, permits and cross-border runs

Every vehicle carries a renewal calendar: registration, insurance, periodic testing, and where relevant permits for dangerous goods, oversized loads or passenger transport. A lapse can stop a vehicle or put its cover at risk, so the vehicle file needs dates, documents and a named person who acts on alerts. I design these as structured records, not attachments, so one report can show what expires in the coming weeks across the whole fleet.

Many UAE fleets also run into Oman, Saudi Arabia and other GCC countries. A cross-border trip brings transit documents, border waiting time, permits and costs paid in other currencies, often by the driver from an advance. The ERP needs a trip record that holds those costs in their original currency, a driver advance settled against receipts when the vehicle returns, and a way to recharge border costs where the contract allows.

For trips that leave the country, confirm the VAT treatment of the transport and any recharged costs with your tax advisor. Domestic and international transport may be treated differently, and the ERP should carry that treatment by service code once it has been agreed.

Picking a platform and working with me remotely

UAE transport companies often run an accounting package with spreadsheets for trips and a separate GPS portal for tracking. Some have a fleet maintenance tool, and few have these connected. The options are to strengthen the accounting layer and keep specialist tools, to adopt an ERP that holds trips, fleet and payroll together, or to choose a transport suite and connect it to finance.

I compare these with scripted scenarios from your business: a monthly bus contract with route changes, a container move with tolls and a fine, a tanker load with fuel above expectation, and a cross-border trip settled from a driver advance. Vendors show those, and your team scores what it sees. The requirements gathering behind those scripts is usually the most valuable part.

All of this runs remotely through video workshops, shared documents and reviews of system exports, at times agreed with your operations team. Fleet owners weighing VAT, e-invoicing plans or a group-wide system will find more in my notes on running ERP projects across the Emirates, with market context on the UAE hub.