Sometimes a measurement error is only discovered after the volumes have already been reported, settled, and moved on. A prior period adjustment, or PPA, is the formal restatement of a measured volume for a period that has already closed, made when something is found to have made the original figure wrong. This page explains what triggers a PPA, the industry rules that limit how far back one can reach, how the correction is documented and re-flowed through allocation, and how SCADA and EFM history make a retroactive correction defensible rather than suspect.
Prior Period Adjustment (PPA) in one line: A prior period adjustment (PPA) in gas measurement is a restatement of a volume for a period that has already been reported and closed, made when an error such as a bad meter factor, a wrong orifice plate, an incorrect gas analysis, or clock drift is later discovered. The corrected volume is documented with its cause and re-flowed through allocation, and industry and contract rules bound how far back adjustments may be made.
A PPA is prompted by discovering that a past volume was measured wrong for a reason that has a definite cause and, usually, a definite timeframe. Common triggers are physical and configuration errors: a meter factor that was wrong or out of date, an orifice plate of the incorrect bore size installed against what the flow computer was told, an inaccurate gas analysis feeding the calculation, or clock drift that misaligned data with the intervals it should have been booked to. Each of these makes the reported volume systematically off during the affected period.
What distinguishes a PPA-worthy error from ordinary measurement noise is that it is identifiable, has a knowable effect, and spans a definable period. A wrong orifice plate bore, for example, biases every volume computed while it was in place by a calculable amount, so once the error and its date range are known, the correct volume for that period can be recomputed. This is different from routine uncertainty, which VEE handles interval by interval; a PPA restates an already-closed period wholesale because a specific fault has been found.
The discovery itself often comes from later scrutiny: a meter proving that reveals the factor was off, an inspection that finds the wrong plate, a lab result that corrects a gas analysis, or an audit that catches a timing error. Because these are found after the fact, the volumes they affect have usually already been reported and settled, which is exactly why a formal adjustment mechanism is needed rather than simply editing live data.
How far back a PPA may reach is not unlimited; it is bounded by contract terms and industry and regulatory rules that set look-back windows for adjustments. These limits exist so that settlements reach finality within a reasonable time and parties are not exposed indefinitely to retroactive changes. The applicable window depends on the contracts and jurisdiction involved, so part of processing a PPA is confirming the correction falls within the period that adjustments are still permitted for, rather than one that has closed for good.
Documentation is what makes a PPA legitimate rather than a suspicious after-the-fact change. A proper PPA records the cause of the error, the period it affected, the original reported volume, the corrected volume, the basis for the recalculation, and the supporting evidence such as the proving result or inspection finding. Because a PPA changes a number that money already moved on, this paper trail is essential: it lets a counterparty and an auditor see precisely why the volume changed and satisfy themselves the restatement is correct.
Once the corrected volume is established, it has to be re-flowed downstream. Gas volumes usually pass through allocation, which apportions measured quantities among wells, owners, or contracts, so a changed measured volume means allocation for the affected period must be rerun with the new figure. The adjustment then propagates into restated statements and settlements for the parties involved. A PPA is therefore not just a corrected number but a controlled process of recomputing, re-allocating, and re-reporting a closed period.
A PPA can only be done confidently if the historical data needed to recompute the period still exists, which is where retained SCADA and EFM history is decisive. Recomputing a corrected volume requires the original interval data, the configuration and event logs showing what the flow computer was set to, and the record of the erroneous parameter, and if any of that has been overwritten or lost, the restatement rests on guesswork. A cloud platform such as Merobix that has collected and preserved the raw quantity records, configuration logs, and event history for each meter is what supplies the evidence a PPA is built on.
The audit trail also pins down the period the error affected. Event logs that timestamp when a constant changed, when a plate or meter was serviced, or when a configuration was edited let an analyst determine exactly which intervals carried the fault, so the adjustment covers the right span and no more. Without that timeline the analyst would have to estimate when the error began and ended, which weakens the correction; with it, the affected period is a matter of record rather than of argument.
The combined effect is that retained history turns a retroactive correction from something that looks like tampering into a documented, reproducible restatement. The operator can show the original data, the specific fault and when it applied, the recomputed volume, and the re-run allocation, all grounded in preserved records rather than reconstruction. For a measurement team, a SCADA and EFM system that reliably retains this history is what makes prior period adjustments both possible to perform accurately and defensible to a counterparty or auditor after the fact.
A PPA is caused by discovering, after a period has closed, that a volume was measured wrong for a specific reason such as a bad or out-of-date meter factor, an incorrect orifice plate bore, an inaccurate gas analysis, or clock drift. Each of these biases the reported volume by a knowable amount over a definable period, so once the fault and its dates are known the correct volume can be recomputed and the closed period restated.
The look-back window for a PPA is bounded by the governing contracts and by industry and regulatory rules, which exist so that settlements reach finality within a reasonable time. The exact limit depends on the agreements and jurisdiction involved, so confirming that the affected period still falls within the allowed adjustment window is part of processing a PPA. Beyond that window a period is generally closed to further adjustment.
Recomputing a corrected volume needs the original interval data, the flow computer's configuration and event logs, and the record of the erroneous parameter, all for a period that has already passed. A SCADA and EFM system that has collected and retained this history supplies exactly that evidence, and its timestamped event log pins down which intervals the error affected. Preserved history is what makes the restatement accurate and defensible rather than a guess.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.