When a utility bills a facility for the electricity it consumed, one device decides the number on the invoice, and both parties have to trust it completely. That device is the revenue meter: the certified, sealed, high-accuracy meter that measures energy for billing. It is the electrical equivalent of a custody-transfer flow meter, the point where ownership of a commodity, in this case energy, formally changes hands and money follows the measurement. This guide explains what makes a meter revenue grade rather than merely a monitor, why higher-power services need current and voltage transformers, how sealing protects the billing measurement, and how a SCADA system can read the meter without disturbing that protection.
Revenue Meter in one line: A revenue meter is the billing-grade electric meter a utility uses to measure the energy a customer consumes, built to a certified accuracy class and physically sealed so the measurement it produces is trusted as the basis for the bill. It is the electrical counterpart of a custody-transfer flow meter, marking the point where energy is bought and sold, and at larger services it works through current and voltage transformers that scale down the line values it measures. Its accuracy class, typically far tighter than a monitoring meter, and its tamper-evident seal are what let both the utility and the customer rely on its registers for money.
The essential distinction is one of accuracy and trust. A revenue meter is held to a certified, high-accuracy class because its numbers determine payments, so a small error would translate directly into money gained or lost over time. Monitoring-grade meters, by contrast, exist to give operators a working picture of loads and consumption around a site and can tolerate looser accuracy, because nothing rides on them beyond situational awareness. The same physical quantity, energy, is being measured in both cases, but the standard the device is built and verified to is what separates a meter you bill from a meter you merely watch.
Accuracy classes make this concrete. Revenue metering is specified to tight classes such as the 0.2S and 0.5S designations, where the number reflects the permitted percentage error and the S indicates sustained accuracy across a wide range of load, including the low currents where cheaper meters drift. A monitoring meter might sit at a looser class that is perfectly adequate for load studies but would be unacceptable for billing. Choosing the class is therefore not a detail but the defining decision, because it sets whether the meter's output can stand as the agreed basis for a financial transaction.
This mirrors exactly the world of flow measurement, where a custody-transfer meter is built and proven to a far tighter standard than a meter used only to keep an eye on a process. In both domains the meter that money depends on is treated as a special class of instrument: certified, verified, and protected, because an error is not just a measurement problem but a commercial one. Understanding a revenue meter as the electrical custody-transfer device is the clearest way to grasp why it is engineered and handled so differently from an ordinary monitoring meter.
At small services a meter can measure the line directly, but larger electrical services carry currents and voltages far too high to feed into a meter, so the measurement is scaled down first. Current transformers reduce the line current to a small, standard value the meter can read, and at higher-voltage services voltage or potential transformers scale down the voltage similarly. The meter then measures these reduced signals and multiplies by known ratios to report the real line values. Because the whole measurement depends on those ratios and on the transformers being sound, the CT and PT inputs are part of what has to be correct and protected for the billing to be right.
Sealing is how the integrity of the metering installation is preserved. A revenue meter and its associated wiring and terminals are physically sealed so that the measuring chain cannot be altered without breaking a tamper-evident seal, which would be plainly visible on inspection. The seal does not make the meter more accurate; it makes any interference with the meter detectable, so that the number the meter reports can be trusted to reflect genuine consumption rather than a tampered or mis-wired configuration. Breaking a seal is a controlled act reserved for the utility or an authorised party, precisely because the seal is the guarantee that the billing measurement is untouched.
Tamper considerations extend beyond the seal itself. Revenue metering installations are arranged so that attempts to bypass the meter, reverse connections, or otherwise defeat the measurement are difficult and evident, and modern meters often log events that would indicate interference. All of this exists for the same reason as the accuracy class and the seal: the meter is the trusted arbiter of a payment, and its trustworthiness rests on the whole installation being verifiably intact. The physical protections are as much a part of a revenue meter as its electronics.
A facility usually wants its own view of the energy the revenue meter is measuring, both to cross-check the utility's bill and to allocate energy cost across processes or departments. The key is that this can be done without disturbing the billing measurement at all. Revenue meters commonly expose their registers over industrial protocols such as Modbus or DNP3, and a SCADA system reads those registers as data, pulling the accumulated energy and other quantities the meter reports. Reading data over a communications port is entirely separate from the sealed measuring chain, so the meter continues to bill exactly as before while the plant gains visibility into its own consumption.
This separation is what makes SCADA integration safe. The seal protects the measurement and wiring; the communications interface simply publishes the results. A cloud SCADA platform such as Merobix can therefore bring a revenue meter's energy registers into the same environment as the rest of a facility's instrumentation, without any authorised person ever needing to break a seal or touch the metrology. The plant obtains an independent, continuously updated record of what the certified meter is registering, alongside its flows, pressures, and equipment status, all in one place.
For oil and gas and other industrial operations, that combined view is genuinely useful. Energy is often a major cost, and being able to cross-check the meter's totals against the utility invoice, watch consumption in near real time, and attribute energy to specific equipment or processes turns the revenue meter from a device that only the utility reads into a source of operational insight for the facility too. Because the SCADA read is non-intrusive, the operation gets all of that while the meter remains the untouched, sealed, trusted basis of the bill, which is exactly the balance a revenue meter is meant to strike.
A revenue meter is built and certified to a tight accuracy class and physically sealed because its measurement determines the electricity bill, so both utility and customer must trust it. A monitoring meter exists only to give operators a working picture of loads and can use looser accuracy because nothing financial depends on it. Both measure energy, but only the revenue meter is engineered, verified, and protected to serve as the basis for payment.
At larger electrical services the line currents and voltages are far too high to feed directly into a meter. Current transformers scale the current down to a small standard value, and voltage or potential transformers scale the voltage down at higher-voltage services. The meter measures these reduced signals and multiplies by known ratios to report the true line values. Because the billing depends on those ratios, the transformers are part of the protected metering installation.
Yes. Revenue meters commonly publish their registers over protocols such as Modbus or DNP3, and reading that data is entirely separate from the sealed measuring chain. A SCADA system pulls the energy registers as data for cross-check and cost allocation while the meter continues to bill exactly as before. No seal is broken and the metrology is untouched, so the billing measurement remains fully protected and trusted.
This page references the protocol specifications 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.