How much does each truck really burn, and how do you avoid counting a fill-up twice?
The fill-up log, two lines matched into a single fill-up, an odometer that never goes back, consumption over thirty and ninety days against the norm, and the card statement import with a preview.
What you get
- Real consumption for each truck against your norm.
- Card statements matched to receipts, and an odometer that never goes back.
- The card statement in one file, with a preview, no typing.
Transcript
Diesel is your first cost line, and almost always the last one anyone starts to measure. Let's be clear: this module can't see the tank. It keeps a log of fill-ups, reads your fuel card statements and works out real consumption between full tanks.
Two lines from the twelfth of August: one from the card statement, the other from the driver's receipt. In an ordinary spreadsheet that's two fill-ups: the liters count twice, and the consumption lies. Here, when the statement was imported, the system matched them by itself: it's one fill-up, and it counts once.
A line from the seventh of August: the odometer is below the current one. The entry is accepted, you can log an old receipt, but the tractor's odometer doesn't move back. And a warning prompts you to double-check the figure: a single odometer typo skews a truck's consumption for months.
Consumption is calculated over thirty and ninety days, and what you read is the deviation from your own norm, truck by truck, with a separate winter norm. With fewer than two reliable points, the system shows a dash, not a zero. A zero in the consumption column would read like an achievement.
You upload the card statement as a file, see a preview, ready lines, duplicates, errors, and only then apply it. The system recognizes the statement's columns by itself, and an applied import can be rolled back with one button.
Real consumption for every truck against your norm, with card and receipt matched and an odometer that never goes backwards.