Why loose meter slips cost real money
The totaliser on a dispenser only ever counts up. That single property is what makes the reading trustworthy and what makes a missing slip unrecoverable: if nobody wrote the closing figure at 10pm, the number that should have been there is gone, and the next morning's opening reading silently absorbs the whole gap.
On paper the failure is quiet. A nozzle whose closing reading was never written still shows a plausible opening reading tomorrow, and the litres that fell into the gap simply never appear in any total. Nothing is out of balance, because the record that would have been out of balance was never made. By month-end the pump has sold more litres than its own register says it did, and the only symptom is a stock variance nobody can attribute.
The fix is not more diligence. It is making the reading the thing the day is built from, so a shift cannot be closed with a nozzle unaccounted for.
The arithmetic that has to hold
Closing reading minus opening reading equals litres dispensed on that nozzle. Sum those across every nozzle drawing on a tank, and the result must equal the tank's book movement for the day. When it does not, you have either a reading error or a stock event — and knowing which one is the whole point.
How meter readings work in PumpDesk
Each nozzle in PumpDesk belongs to a tank, and each tank holds one fuel type. That chain is what makes a reading mean something beyond itself: the litres are attributable to a nozzle, to the tank behind it and to the fuel type in that tank, which is what the fuel-wise report and the stock register are both built on.
You enter the opening reading at the start of the shift and the closing reading at the end. PumpDesk computes the difference, refuses a closing reading below the opening one, and shows the resulting litres immediately rather than at month-end when a typo is no longer correctable from memory.
- Readings are captured per nozzle, per shift — not per day, so a three-shift pump keeps three attributable blocks instead of one anonymous total.
- Litres sold are computed, never typed. Nobody can enter a figure that disagrees with its own readings.
- A reading that would run the meter backwards is rejected at entry, when the operator is still standing at the dispenser.
- Litres flow into fuel sales by type, so petrol, diesel and any branded grade you have configured stay separated all the way to the report.
A worked example
Take a two-tank pump with four nozzles across the morning shift. The readings go in as they are taken; the litres column is the software's, not the operator's.
Litres draw the tank down, and are valued at that day's rate
Litres sold reduce the stock in the tank behind that nozzle, so a dip is compared against a book figure that accounts for what was dispensed. They are also valued at the fuel's rate for that date, which is what makes expected revenue a figure the product derives rather than one you supply. Two things it still does not do: correct volume for density or temperature, and account for pump-test litres drawn and returned.
| Nozzle | Fuel | Tank | Opening | Closing | Litres sold |
|---|---|---|---|---|---|
| N1 | Petrol | T1 | 184320.40 | 185002.10 | 681.70 |
| N2 | Petrol | T1 | 201884.00 | 202451.55 | 567.55 |
| N3 | Diesel | T2 | 312006.25 | 313118.90 | 1112.65 |
| N4 | Diesel | T2 | 298450.10 | 298902.75 | 452.65 |
Morning shift, one day. Litres sold is computed from the two readings beside it, and drawn from the tank named alongside.
What this catches that a notebook does not
A register records. Reconciliation compares. The difference shows up on days when two records that should agree do not, and only one of them can be right.
- A closing reading typed one digit short — caught at entry, because the resulting litres would be negative.
- A nozzle nobody read — visible as a nozzle with no closing reading when the shift is closed, rather than as an unexplained variance six weeks later.
- A nozzle whose litres look wrong against its neighbours on the same tank — the signal that separates a metering problem from a stock problem.
- A shift closed with a nozzle still unread — visible at the checkpoint rather than absorbed into tomorrow's opening figure.
Frequently asked questions
Can I record readings per shift rather than per day?
Yes, and it is the intended way to use it. Readings belong to a shift, so a pump running three shifts keeps three separate blocks of litres, each attributable to the people who were on. A single daily reading is possible but it discards the attribution that makes a cash shortfall solvable.
What if an operator enters the wrong reading?
A closing reading below its opening reading is rejected at entry. For an error that is wrong but still arithmetically valid, a manager can correct the reading — operators can enter readings but not edit them, which is the point of the split — and the litres and the tank movement recompute from the corrected figure rather than needing separate fixes.
Does it handle nozzles that share a tank?
Yes — that is the normal case. Several nozzles draw on one tank, and each reading draws stock from the tank behind it. The tank's total movement for the day is the sum of every nozzle hanging off it, which is exactly the figure you compare against the dip.
What about meter resets and dispenser replacement?
A new dispenser starts its totaliser from a new number. Record the final reading on the old nozzle and the opening reading on its replacement; the litres on each are computed within their own reading pair, so the changeover does not produce a phantom sale or a phantom loss.