Fleet running costs in Malta, down to the kilometre
Included with Yipii Mobility, the add-on that extends your IoT account. One subscription covers everything in the app, so no feature here is sold on its own. What Yipii Mobility includes
Every euro that leaves, tied to a vehicle
Fuel is the biggest line you can actually do something about. The rest of the spend lives next to it so the totals mean something.
Fuel logs
Type, volume, cost, odometer, vendor and reference on every fill. Yipii divides cost by volume, so the price per litre is worked out for you.
Fills the tracker spots
When fuel-level data shows a rapid increase, Yipii writes the log itself: volume, date and time, odometer, and the trip it happened on.
Cost per kilometre
Per asset, built from fuel logs and distance covered. This is the number that settles whether the old van still earns its keep.
Expenses with approval
Eleven categories, a receipt on each claim, and an approval step the submitter cannot wave through on their own.
Fleet fuel management starts at the pump
A fuel log belongs to one asset and records what went in: fuel type, volume, fill date, cost, odometer, vendor and reference number. Price per unit is not something anyone types. Yipii divides cost by volume and fills it in, which is why the figure is consistent across a fleet where five people log fills five different ways. Seven fuel types are on the list: diesel, petrol, electric, hybrid, LPG, CNG and other.
- Fuel type, volume, date, cost, odometer, vendor and reference
- Price per unit calculated from cost divided by volume
- Litres or gallons, set once for the whole account
- Receipt attached as JPG, PNG, PDF, WebP or HEIC, up to 10 MB
Fills that log themselves, then wait for the price
Where a vehicle reports its own fuel level, the tracking server watches that reading and treats a rapid increase as a fill, working the volume out from the size of the jump. The log is written for you and marked as coming from the tracker rather than from a person. What it cannot know is what you paid, so it arrives carrying a 'Needs completion' indicator until somebody adds the cost.
- Volume, date and time, odometer reading and the trip it belongs to
- Fuel type as well, when the OBD data carries it
- Cost, vendor, reference and the personal-use flag stay manual
- Driver-reported fills sit beside detected ones, so the two reconcile
Fleet running costs per kilometre, ranked by vehicle
Cost per kilometre is calculated per asset, and it lives with the fuel logs rather than in the general expenses view, because it is fuel and distance that produce it. Next to it sits a km/l ranking across the fleet and consumption broken down by driver, which is the comparison that matters when two people share a van and one of them returns it empty every Friday.
- Cost per kilometre by asset, from logged spend and distance covered
- Fleet ranked by km/l, or mpg if that is your unit
- Consumption by driver, comparable across the same vehicle
- Average fuel price over time, which is the diesel bill in one line
Eleven categories, and nobody approves their own claim
Everything that is not fuel gets filed under one of eleven categories, with a receipt attached and a vehicle behind it. A claim starts as pending. An admin or a fleet manager approves it, or rejects it with a reason so it can be corrected and resubmitted, and the server refuses to let the submitter approve their own. That single rule is what makes the monthly total defensible when someone questions it.
- Fuel, maintenance, insurance, registration, repairs, parts, tolls, parking, fines, cleaning and other
- Pending, approved, or rejected with a reason and a resubmission
- Submitter and approver must be different users, admins included
- Receipts kept private, with links that expire after 15 minutes
What fuel logs will not tell you
There is no fuel-theft alert
Detection looks for fuel going in, not fuel going out. A rapid rise in the level becomes a fuel log, and that is the whole of it. Nothing messages you about a drop, a siphoning event or a tank that emptied overnight.
The workable substitute is comparison: detected fills against driver-reported ones, and a vehicle that slides down the km/l ranking in the reports.
An automatic entry has no price on it
The tracker knows how much went in, never what it cost. Until someone adds the cost, the entry stays flagged as needing completion and your cost per kilometre is reading low. Somebody still has to do the ten seconds of typing.
Automatic entries also depend on the vehicle reporting a fuel level in the first place. An asset that sends no fuel-level data produces no detected fills, and every log on it is typed in by hand.
Frequently asked
Every fill becomes a fuel log against one vehicle, either typed in by whoever filled up or written automatically when the tracker sees the fuel level jump. Each log carries the fuel type, volume, cost, odometer reading, vendor and reference number, and Yipii works out the price per litre from cost divided by volume. Once the logs are in, fleet running costs come out as cost per kilometre by asset, consumption by driver, and an average fuel price you can watch over the months.
No. We would rather say that plainly than let you find out after signing. What the tracker detects is a rapid increase in fuel level, which is a top-up, and it turns that into a fuel log. There is no siphoning alert and no drop detection behind it. If fuel is going missing, the practical route today is to compare the fills your drivers report against the fills the tracker recorded, and to watch the km/l ranking for a vehicle that suddenly falls down it.
Yes, and it sits with the fuel logs rather than in the general expenses view. Cost per kilometre is calculated per asset from the logged fuel spend and the distance the vehicle covered, so it only reflects reality once the automatic entries have their cost filled in. Alongside it you get a km/l ranking across the fleet, consumption broken down by driver, and the average fuel price over time.
An admin or a fleet manager, and never the person who submitted it. The server itself enforces that the submitter and the approver are different users, so an admin cannot approve their own claim even though the role would otherwise allow it. A claim moves from pending to approved, or to rejected with a reason attached, after which it can be corrected and resubmitted. Every approval and rejection is stamped with the time and the user who did it.
JPG, PNG, PDF, WebP or HEIC, up to 10 MB per file, which covers a photo taken on any phone at the pump. Files sit in a private store rather than on a public URL, and the links used to open them expire after 15 minutes, so a receipt shared by accident stops working quickly.
Also included in Yipii Mobility
Nothing here is bought separately. Taking Mobility gets you all of it, and each part makes the cost figures on this page more accurate.
Field by field, including what a detected fill contains and how the approval states move, it is written out in the fuel logs guide and the expenses guide in the Yipii Mobility docs.