No shipper delivers gas into a pipeline in exactly the amount it takes out, so every transportation contract has to answer a practical question: how far off is allowed before it becomes a problem? The answer is the imbalance tolerance - a defined band around zero within which a shipper's nominated and delivered quantities can differ without triggering penalties or cashout. This guide explains what the tolerance threshold is, how it is expressed and sized, and why staying inside it is the whole point of daily balancing.
Imbalance Tolerance in one line: An imbalance tolerance is the contractual band, usually stated as a percentage, within which a shipper's scheduled versus actual delivered gas quantities may differ before a pipeline applies penalties or forces a cashout. Imbalances that stay inside the tolerance are typically carried forward or trued up in kind without charge, while imbalances that breach it move into penalty or cashout treatment.
An imbalance tolerance is a threshold, not a document or a settlement. It defines the boundary between an imbalance the pipeline will treat leniently and one it will penalize. Inside the band, a shipper's difference between scheduled and delivered gas is considered normal operational drift - the pipeline expects it, absorbs it, and usually lets the shipper carry it forward or resolve it in kind. Outside the band, the same difference stops being routine and becomes something the tariff acts on. The tolerance is the line that separates those two worlds.
The band is almost always expressed as a percentage rather than a fixed volume, most commonly as a percentage of the scheduled or nominated quantity. Stating it as a percentage lets the same rule apply to a small shipper and a large one, because the allowed absolute imbalance scales with how much gas each is actually moving. A shipper nominating a large daily quantity is granted a proportionally larger cushion than one nominating a small quantity, which keeps the tolerance fair across very different volumes on the same pipeline.
It helps to keep the tolerance conceptually separate from the mechanisms that engage once it is breached. The tolerance itself only says how much drift is permitted; it does not describe how an out-of-band position is resolved. Whether a breach leads to a cashout at an index price, a penalty charge, a forced makeup, or a required trade is a matter of the surrounding tariff terms. The tolerance is simply the trigger point, and understanding it as a threshold - distinct from the statement that reports the position and the settlement that resolves it - is what makes the rest of the balancing picture legible.
How wide a tolerance a shipper gets depends on the pipeline's tariff and often on the type of service. A tolerance can be applied on a daily basis, a monthly basis, or both, and the daily and monthly bands are frequently different sizes, because short-term swings are more forgivable than a persistent monthly drift. A shipper may be allowed to run relatively far off schedule on any single day as long as the position averages back toward zero over the month, which is why reading a tolerance means knowing which period it governs.
Many pipelines also tier the tolerance rather than using a single hard line. Instead of one band that is either met or breached, the tariff may define graduated zones: a small imbalance sits comfortably inside and is trued up in kind, a moderate one is allowed but priced at or near an index, and a large one falls into a punitive zone with pricing set deliberately against the shipper. The effect is a schedule of increasing consequence, so the further past the innermost tolerance a shipper drifts, the more expensive each additional unit of imbalance becomes.
The size of a tolerance is not arbitrary; it reflects how much operational slack the pipeline can absorb without jeopardizing system integrity. A pipeline with ample storage and flexibility can afford to grant wider bands, while a tightly balanced system with little cushion must keep tolerances narrow to protect line pressure and deliverability. From the shipper's side, the practical takeaway is that the tolerance is a managed budget of allowable error, and the narrower it is, the more precisely daily flow has to track the nomination to stay inside it.
A tolerance is only useful to a shipper who can tell, during the month, where its position sits relative to the band. Because an imbalance accumulates day by day while the formal statement arrives only after the period closes, the shipper that waits for the statement finds out too late to steer. The information that actually matters is the running difference between each day's confirmed schedule and each day's metered flow, compared continuously against the tolerance threshold so the shipper knows how much of the band it has left.
Cloud SCADA makes that comparison a live readout rather than a month-end reconstruction. When daily metered volumes flow into the same view as the confirmed nominations, the running imbalance can be plotted against the tolerance band directly, so an approaching breach is visible while there is still time to act - trimming an over-delivering point, adjusting the next nomination cycle, or arranging a trade with a counterparty holding the opposite position. The tolerance stops being an abstract number in a tariff and becomes a live boundary the shipper is actively managing toward.
A platform such as Merobix supports this by centralizing metered volumes from scattered delivery and receipt points into one browser-based dashboard, where the running position and its tolerance can be watched together in near real time. Instead of being surprised by a penalty for a breach it never saw coming, a shipper monitoring its balance against the tolerance can keep the position comfortably inside the band and treat the eventual statement as a confirmation rather than a verdict. That is the practical value of real-time measurement to the tolerance concept: it turns a contractual limit into something you can steer away from.
They are closely related but not identical. The imbalance tolerance is the band within which drift is permitted without consequence, while the cashout threshold is the point at which an unresolved imbalance is converted to cash under the tariff. In many pipelines the outer edge of the tolerance effectively is the point where cashout or penalty pricing begins, but the tolerance describes what is allowed, whereas cashout describes how a breach is settled.
Expressing the tolerance as a percentage of the scheduled quantity lets one rule apply fairly across shippers of very different sizes. A large shipper moving a big daily volume is naturally going to have larger absolute swings than a small one, so a percentage band scales the allowed imbalance to each shipper's activity. A fixed volume would be far too tight for large shippers and far too loose for small ones on the same pipeline.
Once the imbalance runs past the tolerance band, the pipeline's tariff takes over, and the specific consequence depends on those terms. Common outcomes include penalty pricing on the out-of-band volume, a forced cashout at a defined index price, a requirement to make up the position through adjusted future flow, or pressure to trade the imbalance with another shipper. In tiered structures, the further past tolerance the position drifts, the harsher the pricing tends to become.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.