Fuel fraud in fleets does not show up as one monstrous fill-up that gets noticed right away. It shows up as a sustained pattern of small deviations that, added up over the year, represent between 3% and 12% of total fuel spend. In a mid-sized fleet, that means tens of thousands of dollars a year leaking out without anyone knowing where.
The good news is that fraud has recognizable signatures. The seven patterns listed below recur in LATAM fleets so often that any reasonably serious control system should detect them. The bad news is that most fleets control none of the seven and only discover fraud when an external auditor points it out.
It is the most obvious sign and the most underestimated. If the vehicle model has an 80-liter tank and the fill-up records 95, someone logged more liters than could physically fit. It may be a typo, or it may be a repeated scheme to inflate reimbursement.
Detection requires having tank capacity loaded in the Model Master and validating every fill-up against that figure. It is the simplest rule to implement and the one that surprises most when it is switched on for the first time in fleets that had never measured it.
If, according to the system, a vehicle covers 200 km and consumes 50 liters, the implied fuel efficiency is 4 km/liter. If the expected fuel efficiency for that model is 12 km/liter, there is a threefold deviation.
There are three possible causes: a real mechanical problem, an error in the recorded odometer, or a false fill-up (more liters were reported than were actually pumped). If subsequent fill-ups return to normal efficiency without any mechanical intervention, the third cause is the most likely.
Split fueling is the classic pattern of organized fraud and one of the hardest invalid fill-ups to spot. The driver arrives at the station, pumps 15 liters, gets a receipt for 15 liters, then pumps another 10 liters charged as a second transaction. When the tickets add up, they total 25 physical liters, but the vehicle only received 18 (the remaining 7 end up in jerry cans or are sold on the side).
Detection requires looking at the sequence: two or more fill-ups at the same station, on the same day, less than 30 minutes apart, adding up to a reasonable amount for the tank. It is invisible if you only look at the monthly total; it is obvious if you look at the sequence.
If GPS shows the vehicle operating all day in zone X, a fill-up at a station in zone Y is suspicious. The driver may have detoured to fuel a personal vehicle, or someone else’s, using the corporate card.
Detection requires integration between the fuel system and the vehicle’s GPS. Without that integration, this sign is invisible.
A fill-up recorded at 11:30 p.m. for a driver whose shift ends at 6:00 p.m. is suspicious. There are three possible situations: the driver is using the card off duty, someone else has the card, or the driver’s recorded schedule is wrong.
On its own the sign does not prove fraud but, combined with others (such as out-of-zone location or frequency), it builds a solid case.
If vehicle ABC-123 is assigned to driver Juan and a fill-up appears on María’s card, it needs to be investigated. It may be a legitimate operational swap (temporary reassignment) or misuse of the card.
Detection requires cross-referencing the fuel system with the vehicle-to-driver assignment system. If your system does not have that information integrated, the sign slips through.
If a fuel card assigned to a vehicle that runs 200 km a day is generating 3 fill-ups a week (when it should generate 1 every 7-10 days), there is an abnormal pattern. The vehicle may be operating more than planned, it may have a mechanical problem that increases consumption, or the card may be used to fuel other, unauthorized vehicles.
The sign is detected by looking at each card’s usage frequency and comparing it against expected usage (calculated from kilometers driven and expected fuel efficiency).
A single isolated sign rarely proves fraud. What builds the case is the combination. The most common pattern indicating organized fraud has 3 to 5 of these signs present simultaneously on the same vehicle or driver:
When three or more of these signs appear on the same vehicle within 30 days, the case is solid enough to escalate to HR and move forward under the company’s internal policy.
Detecting fraud without a clear policy on what to do is half a solution. The policy has to define:
Without a policy, fraud detection ends up as a spreadsheet the fleet manager keeps without knowing what to do with it. With a policy, every detected case triggers a clear workflow.
A documented case from a fleet of 40 medium-duty trucks shows how the 7 signs combine in practice. The full detection and resolution process took 47 days and resulted in the dismissal for cause of a driver with 5 years of seniority.
Week 1. The system flagged three fill-ups for the vehicle assigned to driver X as REVIEW for exceeded capacity (sign 1): the recorded liters exceeded the model’s tank. The initial investigation attributed the problem to data-entry errors by the provider, and the audit lead accepted the explanation.
Weeks 2 and 3. The same vehicle’s implied fuel efficiency came in consistently low (sign 2): actual efficiency between 30% and 40% below the model’s expected figure. The manager opened a mechanical inspection ticket that found no technical anomalies to justify the deviation. Evidence began to pile up.
Week 4. The Fuel module’s weekly pattern report identified that 4 of the vehicle’s last 6 fill-ups had been made at the same station, with less than 25 minutes between the first and second of each pair (sign 3: split fueling). The pattern repeated on Thursdays, the day the driver finished his weekly shift.
Week 5. Cross-check with the vehicle’s GPS (sign 4): on two of the four flagged dates, the vehicle was parked at the station for 35-40 minutes, a time inconsistent with a normal fill-up.
Weeks 6 and 7. The station’s footage was requested from the provider (a contractual procedure under the corporate card program). The images confirmed that the driver pumped a first amount into the vehicle and, after getting the ticket, transferred additional fuel into jerry cans in the vehicle’s trunk.
Resolution. A formal conversation with the driver, presentation of the documented evidence (3 system signs + footage), and application of the company’s internal policy, which provided for dismissal for cause for fraud in the use of corporate assets. Partial recovery via payroll deduction from the last period: approximately USD 1,200 out of an estimated USD 4,500 in fraud accumulated over 6 months.
The case would not have been detected with any of the 3 signs on its own. The combination turned them into documented, defensible evidence.
VEC Fleet implements detection of the 7 fraud signs natively in the Fuel module:
Each sign triggers an automatic flag on the fill-up. Accumulated flags on the same vehicle or driver generate a consolidated review case for audit.
Are you looking at the right signs to detect fuel fraud?
With VEC Fleet, every fill-up is recorded with liters, amount, odometer, location and GPS coordinates. That traceability is the foundation of any case you later need to stand behind.
Without automatic controls, between 3% and 12% of total spend. With well-implemented controls, it drops to 0.5%-1.5% within 90-180 days. The exact figure depends on the country, the organizational culture and the previous level of auditing.
It depends on internal policy and severity. An isolated case of misunderstanding (fueling a colleague’s vehicle with no ill intent) can be resolved with a conversation. A sustained pattern of organized fraud usually justifies dismissal for cause, especially if the documentation is solid.
A conversation based on data, not accusations: the fill-ups for vehicle X show a pattern that differs from the rest, and we want to understand what is happening. If the driver’s answer is reasonable and verifiable, the system is adjusted. If not, it is escalated with documented evidence.
Signs 1, 2, 3 and 7 work without telematics (using only fuel card and mileage data). Signs 4, 5 and 6 improve a lot with integrated telematics, but they can also be partially detected through manual cross-checks against the assignment system.
Ideally, a collaboration between the fleet manager (detects), internal audit (validates) and HR (acts). The policy needs to be signed off by senior management to carry real disciplinary weight. Without that sign-off, the fleet manager is left alone when it is time to escalate.