Tank-farm inventory reconciliation: separate stock, movement and corrections

Topics: terminal inventory reconciliation; tank farm stock reconciliation; petroleum terminal inventory; product movement records.

The terminal report shows 1,120 approved quantity units. The ERP shows 1,150. Both reports were generated this morning, and each passes its own internal arithmetic. The thirty-unit difference is sent to finance as a possible stock adjustment.

The first question is whether the reports describe the same population and cutoff. Tank-farm inventory reconciliation should explain the difference through source movements and authorised corrections before anyone changes stock. Matching two totals without their boundaries can manufacture a loss or gain that does not exist.

Agree the boundary in plain language

Record the location population, product or item scope, ownership basis, approved unit and quantity basis, business period, timezone and posting cutoff. State whether the report includes stock owned by others, goods in transit, held stock or movements awaiting commercial posting.

The qualified measurement and operations owners establish the source quantities and applicable methods. This article uses already-approved values; it does not prescribe gauging, conversion, custody-transfer equations or tolerances.

A terminal operational stock view and a financial inventory view can legitimately differ in scope. The reconciliation should identify those differences explicitly. For example, physical custody does not by itself establish ownership. The commercial and finance owners decide the relevant treatment under the actual agreements and accounting policies.

1. 01Align the report boundary

   Confirm product, ownership, basis, locations and cutoffs.

   Owner: Terminal accounting

2. 02Trace movement differences

   Link each timing item, transfer and correction to its source.

   Owner: Accounting + source owners

Is the remaining difference explained?

Yes · supported path

Retain the supported bridge

Close timing items once included in the ERP extract; retain their history.

No / unresolved · exception path

Open the right investigation

Separate physical-stock differences from missing postings or scope mismatches.

Owner: Measurement, operations or finance owner

Reconcile again after the source or authorised correction is available.

Agreement between ledgers is not confirmation of physical stock.

Original diagram: NextEdge Labs.

Build a movement bridge

Illustrative example. Opening stock is 1,000 units on one approved basis. Receipts total 300 and dispatches total 180. The terminal's movement ledger therefore has a calculated closing figure of 1,000 + 300 − 180 = 1,120. This is a book balance, not an independent physical observation.

One dispatch of 30 units occurred before the terminal cutoff but was posted after the ERP extraction. The ERP contains only 150 units of dispatches and therefore shows 1,000 + 300 − 150 = 1,150.

The thirty-unit bridge explains a timing difference. It is not a recommendation to post a thirty-unit loss. Confirm the original dispatch and its eventual ERP posting, then close the timing exception with both references. If the ERP posting never arrives, the same case becomes an unresolved interface or business-process issue.

On the next run, remove D-88 from the outstanding bridge once its posting is included in the ERP extract. Retaining both the posting and the old bridge would subtract the same dispatch twice. Keep the closed bridge item in the audit history, with the cutoff at which it ceased to be outstanding.

Agreement between the two ledgers still does not establish physical stock. Suppose a separately approved physical-stock record, aligned to the same scope, time and basis, shows 1,118 units. The difference from the reconciled book balance is 1,120 − 1,118 = 2 units. Record that as a separate investigation for the responsible measurement and accounting owners. The arithmetic alone cannot establish a physical loss, its cause or the appropriate accounting treatment.

Now imagine the original dispatch appears twice after a retry. The second entry requires investigation and the supported correction process. Deleting the bridge because the totals happen to match another report would conceal the duplicate.

1. ERP at extraction1,150

   Only 150 dispatch units are included.

2. Timing bridge D-88−30

   Dispatch before terminal cutoff, absent from ERP extract.

3. Comparable book balance1,120

   Matches the terminal movement ledger.

4. Separate physical record1,118

   Same scope, time and approved basis in the example.

5. Investigation difference2

   1,120 − 1,118; not automatically a loss or adjustment.

Illustrative quantities. Remove D-88 from the open bridge once its posting is included, or it will be counted twice.

Original visual: NextEdge Labs.

Transfers need two sides and one relationship

An internal transfer can create a dispatch from one location and a receipt at another. Retain the common transfer identity, sending record, receiving record and the state of any in-transit quantity. Compare each side at the agreed cutoff.

Do not count an internal transfer as external consumption in a consolidated view. Equally, do not remove both sides if the reports cover different location populations. The reconciliation scope determines the treatment.

A delayed receiving record should remain an owned exception. Its age and custody evidence matter more than a generic “transfer variance” label. Where the approved quantities differ between the two records, the measurement and commercial owners determine the reason and treatment; the software should not invent an adjustment to force agreement.

Separate correction types before assigning work

A useful queue distinguishes missing movement, duplicate movement, period mismatch, ownership mismatch, unit or basis conflict, approved measurement correction and unexplained difference. Each case carries source references and a decision owner.

Terminal accounting owns the comparison and close record. The source-system owner investigates delivery failures. Qualified measurement or operations authorities validate the quantity basis. Finance approves accounting corrections. Contract owners resolve relevant ownership or entitlement questions.

For every correction, preserve the original value, revised approved value, reason, reviewer, effective period and posting reference. A general provenance model such as W3C PROV can inform the data relationships, while the terminal defines the actual business decisions. W3C PROV overview

Avoid turning the dashboard into a measurement system

A reconciliation layer can read approved movement and stock records, align their identifiers and expose differences. It should display the source cutoff and freshness. If a feed is unavailable, show the last confirmed position instead of silently presenting a current-looking number.

Rules can check arithmetic, duplicate keys and missing references. When those checks leave an unexplained quantity, retain the difference and its investigation owner. Filling the gap with an estimated adjustment would make the dashboard appear settled before the underlying issue is understood.

For a small number of movements, a controlled bridge worksheet may be enough if it preserves source references, cutoffs and approvals. A recurring reconciliation service becomes useful when volume or repeated extracts make manual tracking unreliable. Compare both against the same late-posting and duplicate-transfer cases; automation should reduce handling effort without turning an unresolved difference into an automatic adjustment.

What a useful review should demonstrate

Select a closing report and trace every bridge item to a movement or authorised correction. Confirm that closed timing exceptions have a final posting reference. Show outstanding cases by category, age and owner, including differences that cannot yet be explained.

Measure unmatched movement count, aged unresolved quantity differences and adjustments lacking source or authority. Keep units and product groups separate where quantities cannot meaningfully be added. An aggregate “variance percentage” across incompatible bases creates false precision.

Summary and next actions

A sound terminal reconciliation explains why the reports differ before proposing a stock change. Shared cutoffs, explicit scope and traceable movements often resolve the apparent discrepancy; the remaining cases can then reach the correct authority with useful evidence.

1. Align one pair of terminal and ERP reports on scope, approved basis and cutoff.
2. Build a movement-level bridge, separating timing items from corrections.
3. Assign each unresolved case to its source, measurement, commercial or finance owner.
4. Test late postings, duplicate transfers and revised approved quantities before automating the close.

A terminal-reconciliation assessment can start with a pair of anonymised reports, their cutoffs and the movement references behind one timing difference. The output should separate missing data, scope differences and questions that need the measurement or finance owner.