Receipt missing
Ask the driver for the receipt or an explanation; retain the response and reviewer decision.
Close when evidence is accepted or the exception is documented.Keep each fuel purchase with its vehicle, driver, odometer reading, and receipt. Calculate cost and valid fuel-use measures, then review unusual entries with the driver.
Use Jodoo to record purchases and review receipts, mileage and exceptions. Connect a fuel-card or telematics provider when you need automatic transaction or vehicle data.
Start with Jodoo’s Free plan for up to five users. No credit card required.
“Fuel management system” can mean different things. Use the source of the problem to decide what belongs in your first setup.
Mobile purchase log with receipt review and vehicle history.
Link purchases to the vehicle, calculate cost, and keep corrections and reviewer decisions together.
Fuel-card provider with merchant, fuel, time and spending controls.
Review imported transactions and record the explanation for exceptions. Card authorization remains with the provider.
Pump controller, driver identification and tank-monitoring hardware.
Track deliveries, approvals and discrepancies alongside hardware records. Jodoo does not operate the pump.
Telematics and suitable sensors with reliable time-stamped vehicle data.
Assign investigations and track their outcome. A manually entered odometer cannot prove idling or theft.
Example: a full-to-full fill of 50 litres at $1.60 per litre costs $80. If the vehicle travelled 400 km, consumption is 12.5 L/100 km (8 km/L). These are example inputs, not a fleet benchmark.
Record the purchase cost; wait for a complete full-to-full interval before interpreting efficiency.
Fuel purchased is not necessarily fuel consumed over that distance.
Check typing errors, units or a replaced meter before accepting the interval.
A negative distance is a data problem, not an efficiency result.
Compare load, route, idle time, season and maintenance history before deciding what changed.
Do not compare a loaded site truck with a lightly used passenger car.
A useful fuel metric can be traced back to the vehicle, date, odometer, receipt, and business explanation.
Quantity, unit price, total, date, supplier, vehicle, and cost center if used.
Review spend by period and vehicle; open unusual entries before treating them as a trend.
Current and prior odometer readings in a consistent unit.
Detect gaps and impossible sequences; do not calculate from an unverified reading.
Fuel quantity and distance for the same operating interval.
Compare a vehicle with its own recent pattern and operating context, not one universal threshold.
Attachment state, readability, entry reference, response, and review status.
Assign missing receipts to a reviewer and keep them visible until corrected or accepted with an explanation.
Policy result, exception type, reason, driver response, decision, and closure.
Find recurring data or operating problems—not merely count exceptions.
Different problems need different evidence and owners. One generic “flagged” status is not enough.
Ask the driver for the receipt or an explanation; retain the response and reviewer decision.
Close when evidence is accepted or the exception is documented.Compare location, supplier, fuel type, and operating need before approving or escalating.
Do not treat a remote-site premium as fraud by default.Return the entry for correction while preserving the original value and decision history.
Exclude invalid readings from efficiency comparisons until corrected.Check data quality, route or load context, tyre pressure, idling, and possible vehicle condition.
Create a vehicle check when the evidence supports it.Add a supplier, adjust a receipt rule, or give site managers their own review view while keeping purchase history together.
Mobile fuel and odometer entries, receipts, corrections, policy choices, review, approval, and audit history.
Fuel-card transaction feeds, tank level sensors, pump authorization, or automated engine data.
Exception queues, owner and due-date workflows, vehicle-linked cost views, and adaptable rules.
Real-time idling, live location, route-level fuel optimization, theft detection, or OEM diagnostics.
Receive or send data through available APIs and integrations, then manage the human exception process.
Keep the hardware or card provider as the authoritative transaction and telemetry source.
Reliable analysis starts with consistent units, validated odometer data, and transparent exception decisions.
Track vehicle, driver, date, fuel type, quantity, unit price, total cost, supplier, odometer, distance, receipt, policy result, exception reason, reviewer, decision, and closure.
Yes, when quantity and valid distance data are available. Define the unit and formula clearly, and prevent incorrect odometer sequences from silently changing the result.
This app starts with entered fuel purchases. To bring in card transactions, check whether your provider offers an API or export, then configure the import, vehicle matching and exception review. A card feed is not included in the sample app.
Compare a vehicle with its own recent pattern and relevant operating context. Route material changes for review instead of relying on one threshold for every vehicle and duty cycle.
Yes. The mobile form captures the vehicle, driver, odometer, quantity, cost, supplier, and receipt in the same entry.
Yes. A trained administrator can change controlled choices, thresholds, review routes, responsibilities, views, and dashboards as the fleet policy evolves.
Open the populated app to see how the driver response, manager decision, correction, and vehicle-level dashboard remain connected.