Every time a custody meter is proven, the event has to be documented in a way that stands up to audit and contract disputes. That document is the meter proving report. This guide breaks down what a proving report contains, why it is a contractual and audit deliverable rather than a routine log entry, and how a cloud SCADA can auto-generate a tamper-evident version of it.
A Meter Proving Report in one line: A meter proving report is the formal record of a single proving event. It documents the as-found and as-left meter factors, each run's results and repeatability, the temperature and pressure corrections, the prover base volume and equipment used, and witness sign-offs, serving as the auditable evidence that a custody meter is measuring correctly.
A complete proving report captures both the inputs and the outcome of the proving. On the inputs side it identifies the meter and its tag, the prover used and its certified base volume, the fluid, and the operating conditions - flow rate, temperature, and pressure at both the meter and the prover. It lists the correction factors applied for temperature and pressure on the metal and on the liquid, since these turn raw indicated volume into a corrected reference. It also records the calculated meter factor for each individual run.
On the outcome side, the report shows the as-found factor - what the meter was reading with before this proving - and the as-left factor that will be applied going forward, so the change is explicit. It presents the accepted set of consecutive runs and the repeatability spread across them, demonstrating the run set met the acceptance criterion. Finally it carries identifying and accountability information: date and time, the operator, and witness signatures or electronic approvals from the parties to the custody transfer. Together these make the report a self-contained proof of the proving.
In custody transfer, the meter factor from a proving directly changes how much product each party is credited with, which means money. The proving report is the evidence that the factor now in use was established correctly, on a specified date, under known conditions, and agreed by both sides. That is why witness signatures matter and why the report is retained: in a measurement dispute or a regulatory audit, the report is what proves the number was not arbitrary. It ties the applied meter factor to a traceable prover and a documented procedure.
Because of this contractual weight, proving reports are prepared to the format and content expected by the governing standards, such as the relevant API MPMS chapters, and they are kept for the retention period required by contract and regulation. Auditors reconstruct measurement history by walking backward through a chain of proving reports, checking that each meter was proven on schedule, that each run set met repeatability, and that the as-left factor of one proving matches the as-found factor at the next. A gap or an unexplained factor jump in that chain is exactly what an audit looks for.
Manually transcribing run sheets into a report invites transcription error and, worse, leaves room for a number to be changed after the fact. A cloud SCADA platform can assemble the proving report directly from the data the flow computer produced during the run: the paired counts, per-run factors, corrections, and the pass or fail against repeatability, all captured with server time stamps as the proving happened. Because the underlying run data is recorded immutably, the generated report reflects what actually occurred rather than what was later typed.
Merobix reads the proving results as tags from the flow computer or proving controller and stores them alongside the meter's history, so it can produce a consistent, complete report every time and flag anything missing, such as a run set that never reached repeatability. Tamper-evidence comes from the fact that the source records carry immutable time stamps and user attribution; a later edit is visible as a new entry rather than a silent overwrite. An operator or counterparty can retrieve any past proving report from a browser, which shortens audits and removes the scramble to find paper certificates.
The as-found factor is what the meter was operating with before this proving started, and the as-left factor is the value that will be applied afterward. Showing both makes the change explicit and lets an auditor see whether the meter had drifted. The as-left factor of one proving should match the as-found factor recorded at the next proving.
In custody transfer the meter factor changes how much product each party is credited with, so the parties witness and sign the proving to agree the number was established fairly and correctly. The signatures make the report a mutually accepted contractual record rather than one side's internal note. In a dispute or audit, that sign-off is the evidence the factor was not set arbitrarily.
Retention is set by contract and by regulatory requirements, and it is typically measured in years so historical measurement can be reconstructed during audits. The reports are kept because auditors trace measurement history by walking backward through the chain of provings. A cloud system helps by retaining every report and its underlying run data automatically for the required period.
This page references the standards, specifications, and official documentation published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.