Reconcile fuel issues without treating every variance as theft

In this fictional example, opening stock is 1,000 litres, deliveries are 500 litres and recorded issues are 1,200 litres. With no other movements in the example, expected closing stock is 300 litres. A physical count of 280 litres leaves a 20-litre shortfall to investigate.

The balance is 1,000 plus 500 minus 1,200 minus 280 equals 20. It is a tank reconciliation, not a calculation of machine fuel efficiency. The issue total could be perfectly recorded while the count is wrong, or the count could be sound while a movement is missing. Preserve both the expected and observed figures while checking the evidence.

Add transfers, returns and adjustments only when they actually occurred and have supporting records. A balancing entry called normal loss would make the arithmetic agree without explaining the event. Any authorised adjustment needs its own reason, evidence, approver and effect on the relevant reporting period.

Record tank identity, fuel type, quantity, unit, event time, posting time and source reference. A delivery completed before the count but posted afterward can create an apparent shortage or surplus, depending on the report's basis. Make the cut-off rule explicit and retain late entries as identifiable corrections.

For each delivery, link the purchase or supply reference, delivery evidence and the site's quantity verification. For each issue, record the issuing point, recipient machine or approved destination and the person responsible for the transaction. A generic issue-to-site label makes later investigation much harder.

ERPNext's Stock Entry documentation illustrates recording material movements and transfers. A fuel register can use the same traceable-movement principle, but its tank, meter and receiving-machine controls need to be designed for the site's actual operation. A stock transaction alone does not verify the measured litres.

The responsible stores and plant team should establish the approved counting and measurement method, instrument identity and relevant calibration or maintenance evidence. Keep the method consistent enough that opening and closing figures can be compared. Record a changed instrument or counting method as part of the reconciliation context.

A damaged gauge, meter reset, duplicate reading or missing transaction needs review before the difference is attributed to physical loss. If the reading is uncertain, label the estimate and its limitation. Do not replace an uncertain observation with a precise-looking value copied from the expected balance.

Where measurement conditions require technical correction or specialist assessment, have the qualified owner define the method. Software should preserve that approved method and its version. This guide does not supply a universal tolerance, conversion factor or acceptable-loss percentage.

Suppose an excavator receives fuel near the end of the shift. Most of that issue may remain in its tank at the reporting cut-off. Dividing the issued litres by that day's engine hours would therefore misrepresent consumption. Machine-level reconciliation needs an agreed opening and closing basis, relevant issues or returns and reliable operating context.

Keep machine identity stable across sites. A local nickname or reused registration field can attach fuel to the wrong asset. When a hired machine replaces another, retain both identities and their effective assignment dates rather than moving the old machine's history onto the replacement.

Engine hours also need interpretation. A reset or replacement meter can make the apparent interval negative or unusually large. Record the event, supporting maintenance evidence and the approved treatment. Do not silently repair the reading by choosing the value that produces a plausible consumption rate.

A controlled tank-and-issue register may be adequate when transaction volumes are modest and measurements are dependable. Digital dispensing or telemetry can reduce copying and provide more frequent observations. It still needs correct asset mapping, reliable timestamps and a way to handle missing or inconsistent data.

Evaluate options using a late delivery entry, a meter reset, a duplicate issue and a machine transfer. Ask the system to show the original events and the proposed explanation. A smooth consumption chart is not enough if the underlying exceptions are hidden. The equipment-maintenance evaluation applies a similar evidence check before assignment.

For machine comparisons, use similar work and conditions. Load, work type, waiting, travel and maintenance condition can affect the interpretation. The plant manager should identify which differences matter before comparing rates. Avoid an automatic ranking of operators from incomplete fuel and hour records.

Stores verifies tank counts and movements. The plant team checks machine identities, meter history and operating context. Finance or the delegated authority reviews any proposed adjustment. If the evidence raises a concern requiring a formal investigation, the organisation's authorised process determines how that is handled.

Keep reported concerns separate from established findings. Restrict access to sensitive investigation material and provide a route to correct inaccurate associations. The fuel dashboard should show an unresolved 20-litre difference with an owner, not a theft label attached to a worker.

Track repeated unexplained balances and issues lacking a valid machine reference. Those measures can reveal weaknesses in the recording process even when no physical loss is established. Review the effectiveness of corrections so the same missing-reference problem does not recur each month.

A useful reconciliation lets another reviewer reconstruct stock movements, the physical observation and the explanation of any difference. It also shows which machine-level questions remain separate. That is the basis for a proportionate operating decision.

1. Rebuild one tank balance using a defined cut-off and the original movement records.
2. Verify the measurement method, instrument history and late or duplicated entries.
3. Trace questionable issues to the correct machines and operating periods.
4. Record the authorised correction or investigation outcome without treating the initial variance as proof of misconduct.