Reconcile petrol station inventory by comparing opening stock, recorded receipts, dispensing and the closing tank reading over the same period. Preserve the original readings and investigate the difference before changing book stock. The useful software test is whether it keeps deliveries, sales and measurement evidence distinct when those events overlap.
Start with one tank, one product and one clearly defined reconciliation window. Identify the source of each figure and who checks it. A complete-looking total can conceal a missing delivery reference, inconsistent reporting time or a quantity that has been counted twice. Those are questions for the evidence trail before they are questions for an adjustment entry.
The examples below use Veeder-Root’s TLS-450PLUS and Business Inventory Reconciliation, or BIR, documentation for wet-stock functions. ERPNext provides a separate example of book-stock adjustment. The original worksheet connects the questions you should ask without assuming that these products are integrated at a particular station.
Which readings and transactions must belong together?
Veeder-Root describes BIR as tracking fuel entering and leaving underground storage tanks. BIR’s product description includes collecting metered sales from electronic and mechanical dispensers. Use the BIR feature description to identify the inputs the proposed configuration will receive, then request a demonstration of those inputs for your test scenario.
The BIR page describes delivery and reconciliation reports on a shift-by-shift basis. Agree what defines the shift in your own evaluation, including its opening and closing times. Ask how the proposed report associates dispenser transactions, delivery events and tank inventory with that period. Keep any missing or delayed inputs visible beside the result.
For each figure, record its product, tank reference, unit, timestamp and measurement basis. Ask the responsible equipment specialist to explain which values are comparable in the proposed configuration. A quantity copied from a delivery record should retain its original meaning; it should not silently become a closing tank measurement simply because both are displayed as volume.
Veeder-Root warns that an inaccurate tank chart can produce inaccurate variances. Ask what tank-chart information the proposed setup uses and how its suitability is established. Keep that question with the measurement evidence rather than assuming that a software reconciliation can correct every underlying input problem.
Why does dispensing during a delivery need its own test?
The BIR Adjusted Delivery Report accounts for fuel dispensed during a delivery. That documented function makes an overlapping delivery a useful demonstration case. Ask the demonstrator to identify the report’s delivery quantity, dispensing quantity and resulting inventory movement, using the terminology of the actual configured system.
Distinguish a received amount from a net change in tank stock. In an overlapping period, the worksheet needs an explicit explanation of what each reported quantity includes. This is especially important when a figure already reflects dispensing and the same dispenser activity also appears elsewhere in the reconciliation.
Require the proposed integration to show its mapping. Which field enters the stock records as a receipt? Which figure is retained as evidence? Which transactions become sales or other movements? Review those choices with the people responsible for both forecourt records and book stock before accepting an automated transfer.
Original shift worksheet: explain the difference without erasing it
This hypothetical example uses fictional litre quantities already assumed to share an agreed measurement basis. It demonstrates arithmetic and record ownership only. The values are not a station’s results, a permitted loss or an instruction for physical fuel operations.
| Worksheet line | Fictional quantity | Evidence the reviewer should request |
|---|---|---|
| Opening inventory | 4,000 litres | Identified opening reading and time |
| Received quantity | 2,000 litres | Delivery record with its quantity meaning stated |
| Dispensed during the window | 500 litres | Transactions assigned to the same reporting window |
| Expected closing inventory | 5,500 litres | Opening plus received quantity minus dispensing |
| Recorded closing inventory | 5,480 litres | Identified closing reading on the agreed basis |
| Unexplained difference | Minus 20 litres | Difference retained for investigation and ownership |
The worksheet calculation is 4,000 plus 2,000 minus 500, giving an expected 5,500 litres. The recorded closing figure is 20 litres lower. The arithmetic identifies a difference; it does not identify its cause. Keep the inputs, their sources and the unresolved difference together for review.
Define the window. Write the opening and closing times and the tank/product mapping before filling the table. Ask one reviewer to assemble the evidence and another to check that each item belongs to the same window. Put late or uncertain records on an exception list instead of quietly changing the period to make the totals agree.
Test the overlap. Suppose the fictional dispensing occurs during the delivery. Ask the demonstrator to show the gross receipt and net inventory movement separately. If a net movement of 1,500 litres is used as the receipt and the 500 litres dispensed is subtracted again, the worksheet will answer a different question. Mark the mapping error and correct the interpretation before considering any stock adjustment.
Retain the original difference. Give the minus-20-litre result a review reference, an owner and a next action. Do not label it acceptable merely because it is a small part of the total. The worksheet deliberately supplies no threshold and no diagnosis. Any operating or investigation decision follows the station’s authorised process.
Introduce a missing input. Remove the delivery reference in the test copy while retaining its displayed quantity. Ask a second reviewer whether they can distinguish a supported receipt from an unexplained number. The comparison should reward a visible exception and an assigned owner, rather than a tidy report whose evidence cannot be reconstructed.
How should book-stock reconciliation remain separate?
ERPNext Stock Reconciliation distinguishes opening stock from reconciling book and actual stock. Its stock reconciliation documentation describes an accounting and inventory adjustment mechanism. Use that as a separate stage in the discussion, after the evidence has been examined and the responsible person has decided what the book record should reflect.
ERPNext allows editing the posting date and time for a stock reconciliation. ERPNext’s reconciliation procedure sets an Item Code and Warehouse before fetching current quantity and valuation. In a test copy, ask the demonstrator to show the intended item/location mapping and effective time. Confirm that these match the approved adjustment record rather than merely the time someone happened to open the form.
Keep the unadjusted comparison alongside any proposed adjustment. Ask who can authorise the entry, what supporting reference is retained and how a reviewer can follow the explanation afterwards. A changed book quantity and an explained physical difference are separate outcomes; your evaluation record should make both visible.
What should the software handover preserve?
The TLS-450PLUS product page describes built-in data logging for wet-stock management data transfer. The TLS-450PLUS product page describes predefined or custom user roles for permissions. Use the console documentation to ask what data the proposed setup exports and which user can read, configure or change the relevant information.
The BIR page lists reconciliation alarms and warnings that can be displayed, emailed and printed. Ask the demonstrator to show the selected notification route and its responsible recipient in the test environment. Record how an unresolved warning is handed over between shifts, without treating an alert as proof of a particular cause or regulatory status.
Retain the worksheet, quantity definitions, event mapping and unresolved exceptions with the product configuration. For the wider integration discussion, read POS and inventory reconciliation and business systems. To discuss requirements, get started with one completed shift example and the evidence your proposed system still needs to connect.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.