Fleet fuel control: the 5 pillars you can't skip

Pillar 1: Expected fuel efficiency by model, not by fleet

The first pillar is knowing how much fuel each vehicle should use. That figure is not the same for the whole fleet: it depends on the model, the year, the type of use (urban, highway, mixed) and the typical load.

Expected fuel efficiency is loaded as master data per vehicle model and expressed in km/liter or liters/100 km. It serves one purpose, but a critical one: providing a benchmark against which to compare every actual fueling. Without expected fuel efficiency, there is no way to know whether a vehicle is consuming more than normal or whether a fueling is out of proportion.

A mid-sized fleet usually has 5-10 different models. Setting up the expected fuel efficiency of each one takes less than a day and saves managers months of guesswork.

Pillar 2: Automatic detection of invalid fuelings

An invalid fueling is one that, for some reason, does not fit the logic of the vehicle or the moment. The most common ones are:

• Liters exceed tank capacity. If the model has an 80-liter tank and the fueling recorded 95, there is an error or fraud.
• Implied fuel efficiency out of range. If the vehicle traveled 200 km and used 50 liters between the last fueling and this one (4 km/liter against an expected 12), something does not add up: either the odometer was not recorded correctly, the fueling is fake, or there is a mechanical problem.
• Price out of range. If the price per liter is 30% above the historical average, it is worth reviewing.
• Location inconsistent with the vehicle’s GPS. If the card was used at a station the vehicle never came close to, the fueling is suspicious.

Invalid fueling control has to be automatic. If it depends on someone reviewing it manually, most of them will slip through. Every fueling should go through the four validations and be flagged as NORMAL or REVIEW without intervention.

Pillar 3: Integration with the fuel card provider

Most LATAM fleets operate with fuel cards (YPF, Repsol, OXXO, Petrobras, Galp, depending on the country). Without integration, fueling data lives in a monthly PDF or in a provider portal that someone has to download and reconcile by hand.

Native integration changes this: each fueling shows up in the system right away (or nearly so), with all the provider’s raw data (liters, amount, time, station, driver identified by PIN). That allows the pillar 2 validations to run automatically and makes accounting reconciliation instant.

Without integration, fuel control will always be 30 days behind.

Pillar 4: Actionable reports, not just descriptive ones

The fourth pillar is the analysis layer. Having the data is useless if you don’t look at it. The minimum reports every fleet management operation needs:

• Fuel efficiency by vehicle vs. expected fuel efficiency. Identifies the ones consuming more than normal.
• Driver efficiency ranking. Same vehicle model, similar route: if one driver consumes 15% more than another, there is something to correct.
• Fuel cost per kilometer. A universal metric to compare bases, cost centers and models.
• Invalid fuelings by month and by vehicle. If one vehicle concentrates flagged fuelings, there is a pattern.
• Price deviation by station. Detect whether a station systematically charges above average.

These reports need to be on the fleet manager’s dashboard and sent automatically by email to the relevant stakeholders. If the only way to see them is to log into the system and build them by hand, nobody will look at them.

Pillar 5: A fuel policy that is enforced, not just written

The fifth pillar is not technological, it is organizational. The company needs a fuel policy that defines:

• Who can fuel (which drivers, which vehicles, at what times).
• Where fueling is allowed (network of accepted stations, authorized exceptions).
• The maximum fueling limit per event.
• What happens when an invalid fueling is detected (process, deadlines, escalation).
• Who pays when fraud is proven (company, driver, payroll deduction).

The policy has to be signed by every driver and enforced consistently. A policy that exists as a PDF but that nobody enforces controls nothing. A policy built into the management system (where the system itself blocks or alerts on non-permitted situations) is the one that actually reduces cost.

What happens when the 5 pillars work together

Fleets that implement the 5 pillars in an integrated way (not as isolated controls) see consistent results within 90-180 days:

• An 8-18% reduction in total fuel cost, without changing routes or scaling back operations.
• A 40-60% drop in suspicious fuelings, because the system detects them as they happen and drivers know every fueling is traceable.
• Less administrative time spent managing fuel, from 8-12 hours a week to less than 1 hour.
• More predictable operating costs for financial reporting and planning.

The result does not depend on a single pillar: it depends on all five working together. Skipping one lowers the ROI of the rest.

Reference case: a consumer goods distributor in 6 months

A consumer goods distributor with a fleet of 60 vans and medium-duty trucks started the fiscal year with no automatic fuel control. Fuelings were recorded in the fleet manager’s Excel file and reconciled against the card provider’s monthly statement. Monthly fuel spend was around USD 78,000, and the team’s general feeling was that it was high, but that’s just how the operation is.

The 5 pillars were implemented in waves. Month 1: loading expected fuel efficiency for the fleet’s 8 models and setting up the integration with the card provider. Month 2: activating the 4 automatic invalid-fueling validations and a review inbox assigned to the fleet manager. Month 3: building the 5 native reports and setting up automatic email delivery to the CFO and the operations director. Month 4: drafting and signing the internal fuel policy, with defined escalations.

The first results appeared in month 2: invalid fuelings detected in the first month accounted for 9% of all fuelings (a high number that confirmed the problem was real). Investigating those fuelings revealed two cases of organized top-off fraud and a driver who was fueling his personal vehicle with the corporate card. All three cases ended in dismissal with documented cause.

By month 6, monthly fuel spend had dropped to USD 65,500, a 16% reduction from the starting point. Broken down by cause: 6% from invalid fuelings avoided, 5% from better driving habits after the driver ranking was introduced, 3% from renegotiating with the card provider based on the price deviation by station report, and 2% from detecting mechanical problems that were affecting the fuel consumption of specific units.

Projected annualized savings were USD 150,000, against a total implementation investment (system + team time) of under USD 20,000 in the first year. Full ROI was reached in less than 2 months.

How VEC Fleet applies the 5 pillars

VEC Fleet’s Fuel module implements the 5 pillars natively:

• Expected fuel efficiency by model, configurable from the Model Master.
• Automatic detection of invalid fuelings with the four validations (capacity, fuel efficiency, price, location) and NORMAL/REVIEW flagging as fuelings come in.
• Native integrations with the main LATAM card providers, with automatic fueling sync.
• Native reports on fuel efficiency by vehicle, driver ranking, cost per kilometer, invalid fuelings and price deviations, available on the dashboard and exportable.
• Fuel policy enforced in the system: per-fueling limits, network of authorized stations, automatic escalations when an out-of-policy event is detected.

Want to stop finding out about fuel deviations a month late?

With VEC Fleet you can validate every fueling automatically, see the cost per kilometer of each unit and centralize spending on a single platform.

Book a demo →