Fuel and tolls, attached to the load that burned them.
Every fleet knows what it spent on diesel last month. Very few can say what a specific Lyon run cost, which is the only number that decides whether to take that job again. The gap between the two is a reconciliation nobody has time to do by hand.
The transactions find their own order.
Fuel card transactions arrive with a card number, a plate, a timestamp and a product. VIGILFleet syncs them hourly, normalises the plate, classifies the product, and attaches the transaction to the order the truck was running at that moment. Diesel, AdBlue and tolls are kept apart, because averaging AdBlue into the diesel price quietly ruins every cost per kilometre downstream.
- Hourly sync, staggered per company, plus a nightly reconciliation
- Diesel, AdBlue and toll products classified separately
- Plates normalised before matching, so formatting differences do not orphan a transaction
- Cost per truck per kilometre and margin per order, updated as the costs land
Two joins, not one.
The plate says which truck. The timestamp says which of that truck's orders. Doing both by hand across a month of transactions is the reconciliation nobody has time for, and it is the only route from a fuel bill to a margin.
Fuel that leaves the tank without a transaction.
The tank level comes from the telematics feed and the purchases come from the card. When the level drops without a matching purchase, that is a question worth asking on the day rather than at the end of the month. The detector raises it against the truck and the time window so it can still be answered.
Then the numbers become a decision.
Once costs sit on orders, per-truck profitability stops being a spreadsheet exercise. Revenue, fuel, tolls, driver cost and margin per vehicle, and cost per kilometre by truck and by month, are just a view of the same data the dispatcher already created by doing the day's work.
- Revenue, fuel, toll and driver cost per truck, per period
- Euro per kilometre by truck, by month
- Monthly and daily fuel snapshots kept so the history does not depend on a provider's retention
- Exports to Excel for the people who will want it in Excel anyway
Questions people actually ask.
- Which fuel cards do you sync?
- AS24 is integrated directly through their partner API, including toll products. Other card providers can be loaded from their statement files. Tell us which card you run and we will be straight with you about what is automatic and what is an import.
- How does a transaction get attached to an order?
- By plate and by time. The transaction's normalised plate identifies the truck, and the timestamp identifies which order that truck was running.
- What counts as a suspicious fuel drop?
- A fall in tank level from the telematics feed that has no fuel card purchase behind it. The alert names the truck and the window so a dispatcher can check the route rather than accept it.
- Do we get cost per kilometre per truck?
- Yes, along with revenue, fuel, tolls, driver cost and margin per truck, over whatever period you choose.
Read next
Find out what last month's Lyon run actually cost.
Book a call, connect your fuel card, and we will show you the answer on your own transactions.