Terminal agreements are operationally dense and commercially opaque. A shipper signs for capacity and movement, receives monthly invoices combining base tariff, ancillary services and occasional adjustments, and pays them because the volumes broadly match what was moved. The agreement itself is consulted when a dispute arises or a renewal approaches.
The economics, though, sit in terms that no invoice surfaces. A loss allowance set half a point too generous transfers real value over a long term. A minimum throughput commitment missed by a small margin produces a deficiency payment that could have been avoided months earlier. A tank turn requirement forces a movement at the wrong moment. An ancillary rate schedule escalates on an index nobody is checking.
None of this requires sophisticated analysis. It requires the contracted parameters to exist as fields next to the operational data, so the comparison happens on a cycle instead of during a dispute. This datasheet sets out the parameters worth holding and the reconciliation each one supports.
The parameters worth holding as fields
Five parameter sets cover the terms that determine what a terminal relationship actually costs and constrains.
- Commitment and measurement, the minimum throughput or storage volume, the measurement period, the deficiency rate and any make-up or carry-forward right.
- Loss allowance, the permitted loss percentage, the basis on which it is calculated, the reconciliation cadence and the compensation rate above the allowance.
- Capacity and turn requirements, leased tankage, product segregation requirements, minimum turns per period or maximum dwell, and any capacity reduction rights.
- Ancillary schedule, rates for blending, heating, additive injection, inspection, sampling and nitrogen, with the escalation index and cadence for each.
- Scheduling and demurrage, berth or bay availability commitments, laytime, nomination windows, and the allocation of delay cost between the parties.
Each of these supports a specific monthly or quarterly reconciliation. That is the point of holding them as data: a parameter in a filed agreement enables nothing, while the same parameter in a field next to actual volumes enables a comparison that either confirms the invoice or identifies a recovery. Shippers running several terminals get a second benefit, which is comparability: once the parameters are held consistently, the differences between terminals become visible and the weakest terms become an obvious renegotiation target. Inconsistency between terminals is rarely deliberate; it accumulates because each agreement was negotiated by a different team at a different point in the cycle.
Most shippers check that billed throughput matches moved throughput and stop there. The loss reconciliation, comparing actual product loss against the contracted allowance, is the check that finds money, and it is the one almost nobody performs on a regular cycle.
The reconciliations that find value
Five recurring reconciliations turn contracted parameters into either confirmation or recovery. They are all straightforward once the parameters exist as fields.
- Cumulative commitment tracking. Compare throughput to date against the commitment with a projection to period end, monthly. This is the reconciliation that converts a year-end deficiency charge into a mid-year decision.
- Loss against allowance. Compare measured losses against the contracted allowance each period. Losses persistently below allowance are a renegotiation argument; losses above it are a claim the agreement already provides for.
- Ancillary billing against schedule. Check billed ancillary charges against the contracted schedule and its escalation terms. Drift here is common over long terms and is usually resolved once identified rather than disputed.
- Turn compliance and dwell. Track dwell time against the turn requirement so a forced movement is anticipated rather than demanded. This also identifies capacity that is being paid for and not used.
- Berth performance against commitment. Log actual berthing against the availability commitment. The record is what supports either a renegotiation or a defence against a demurrage claim, and it cannot be reconstructed after the fact.
A five-step implementation path
Step 1, Abstract the active agreements
Extract the five parameter sets for every terminal agreement in use. Portfolios with several terminals commonly find inconsistent loss allowances and commitment structures that nobody chose deliberately, which is itself useful negotiating information.
Step 2, Connect operational volumes
Feed movement and inventory data against each agreement. Monthly aggregates are sufficient to begin; the requirement is that the comparison runs on a schedule rather than being assembled for a meeting.
Step 3, Set up the five reconciliations
Build each comparison as a standing report with a named owner and a review cadence. Reconciliations that exist as a report somebody runs on request tend not to be run.
Step 4, Version the ancillary schedules
Record each schedule with its effective date and escalation basis, and load the escalation dates as obligations. Rate changes applied by notice and never papered are the usual source of drift.
Step 5, Review the portfolio before each renewal
Bring the reconciliation history into renewal negotiations. A shipper that can show two years of losses well inside allowance, or persistent berth unavailability, is negotiating from evidence rather than from position.
See terminal reconciliation working
Walk through commitment tracking, loss reconciliation and ancillary schedule checks on live agreements.
The relationship to volume commitments elsewhere
Terminal deficiency mechanics behave much like the take-or-pay and minimum volume structures found upstream and in transportation, and they fail for the same reason: the commitment is annual, the visibility is monthly at best, and the make-up rights that exist to soften a shortfall go unexercised. The tracking discipline set out in take-or-pay and minimum volume clauses, where value leaks applies without modification, and organizations that run both through the same obligation register can see aggregate commitment exposure across the value chain rather than terminal by terminal. Deficiency mechanics also interact with allocation and force majeure terms in the same way, since a shipper prevented from moving product should not accrue a shortfall for volume the terminal declined to handle, and that suspension has to be recorded when it happens rather than argued at period end. That aggregate view is usually what makes the case for the work, and it is the same register described in obligation management for energy and mining.
Parameters, reconciliations and cadence
The table below maps each contracted parameter to the reconciliation it enables and the frequency at which that check is worth running.
| Parameter | Reconciled against | Cadence | What it prevents or recovers |
|---|---|---|---|
| Minimum throughput commitment | Cumulative volume moved | Monthly, with projection | Avoidable deficiency payment at period end |
| Loss allowance percentage | Measured product loss | Monthly or per cycle | Uncompensated loss above allowance |
| Tank turn or dwell limit | Inventory dwell time | Monthly | Forced movement at unfavourable timing |
| Ancillary rate schedule | Billed ancillary charges | Quarterly | Overbilling from undocumented rate drift |
| Berth availability commitment | Actual berthing performance | Per vessel, reviewed quarterly | Unsupported demurrage claims; weak renewal position |
Terminal agreements reward attention more reliably than most contract categories, because the parameters are numeric, the operational data already exists and the reconciliations are arithmetic rather than judgment. The barrier is that the parameters live in documents and the volumes live in operating systems, and nobody owns the comparison. Assigning that ownership and holding the parameters as fields is the whole intervention. It is worth doing before a renewal rather than after one, because two years of reconciliation history is the strongest position a shipper can bring to a tariff negotiation, and it cannot be created retrospectively. The reconciliations themselves are arithmetic, so once the parameters exist as fields the ongoing cost is a monthly report review rather than an analyst.
For related guidance, see The land manager’s guide to mining royalty obligations, Decommissioning and abandonment obligation tracking and Mine water supply agreement obligations.
