What is smart metering? Continuous measurement and how it maps to usage billing
Written by Arnon Shimoni
✓ Expert
Last updated on:
Smart metering is the practice of measuring consumption continuously and automatically, then feeding those readings straight into billing. The term comes from utilities, where smart meters replaced monthly manual readings with interval data sent over the network. In software it means the same thing applied to product usage: instrument the thing customers consume, collect it in near real time, and bill from the reading rather than from an estimate.
Field | Detail |
|---|---|
What it is | Continuous automated measurement of consumption, fed directly into billing |
Origin | Utilities (electricity, gas, water), now standard language in telecom and software |
Software equivalent | Usage metering, the term most SaaS and AI companies use |
Core requirement | Accurate readings, deduplication, late-event handling, an auditable trail |
Why it matters | Estimated consumption becomes disputed invoices and revenue leakage |
What makes a meter smart
Three properties separate a smart meter from a counter.
It reads continuously. A traditional meter is read once a period by a person. A smart meter emits readings at an interval short enough that nobody has to interpolate. In software, that means events land as they happen rather than being reconstructed from logs at month end.
It reports on its own. No truck rolls, no manual export. The meter pushes to the system that prices it. In a software stack this is the difference between a metering pipeline and a monthly data pull that someone has to remember to run.
It supports two-way visibility. The customer can see the same readings the vendor bills from. Utilities learned early that disputed bills are expensive, and the fix is showing consumption before the invoice arrives, not after.
Smart metering versus usage metering
They describe the same mechanism in different industries. If you work in energy, telecom, or industrial IoT, smart metering is the native term. If you work in SaaS or AI, usage metering is what your buyers and your engineers will say. The concepts map cleanly onto each other, and the hard parts are identical: getting readings you can defend, handling events that arrive late or twice, and keeping a record an auditor can follow.
The one real difference is unit stability. A kilowatt hour does not change definition. A software meter does, because product teams ship new features, rename events, and change what counts as a billable action. That instability is why software metering needs versioned meter definitions in a way utility metering never did.
What smart metering has to handle
Deduplication. Retries and at-least-once delivery mean the same event can arrive more than once. Billing the duplicate is a refund conversation.
Late arrival. An event generated at 23:58 on the last day of the period may land after the invoice run. The meter needs a defined lateness window and a rule for what happens outside it.
Aggregation windows. Per second, per hour, per day, per period. The window determines what the customer sees and how overage charges get calculated.
Meter versioning. When the definition of a billable unit changes, historical periods still need to reprice correctly under the old definition.
Auditability. Every line on the invoice traces back to raw readings. Without that, disputes get settled with credits instead of evidence.
Where it shows up in software pricing
Any model that charges for consumption depends on it. Usage-based pricing bills the reading directly. Hybrid models use it for the variable component sitting on top of a platform fee. Credit pricing uses it to decrement a wallet. Minimum commits and volume commitments use it to measure drawdown against a contracted floor.
In each case the meter is load bearing. If the reading is wrong, the price is wrong, and no amount of pricing sophistication upstream fixes it.
Where Solvimon fits
Solvimon meters product events in real time and prices them in the same system, so the reading and the invoice line are never reconstructed from two different sources. Meters are versioned, late events are handled inside a defined window, and every charge traces back to the raw events behind it.
Frequently Asked Questions
What is smart metering?
Smart metering is continuous automated measurement of consumption that feeds directly into billing, replacing periodic manual readings and estimates. It originated in utilities and now describes the same mechanism in telecom and software.
Is smart metering the same as usage metering?
Practically, yes. Smart metering is the utility and telecom term, usage metering is the SaaS and AI term. Both mean measuring consumption accurately and billing from the measurement.
Why does deduplication matter in metering?
Event pipelines usually guarantee at-least-once delivery, which means duplicates are normal rather than exceptional. Billing a duplicate produces an overcharge, a dispute, and a credit, so the meter has to deduplicate before pricing.
What happens when usage events arrive late?
The meter needs a defined lateness window. Events inside the window are folded into the correct period, and events outside it follow an explicit rule, usually landing in the next period with an adjustment note rather than silently changing a closed invoice.
Do customers need to see meter readings?
Showing consumption before the invoice arrives is the cheapest way to prevent disputes. Utilities learned this decades ago, and it is why usage visibility in-product has become standard for consumption-priced software.
Related
Usage metering. The SaaS term for the same practice, with the full operational detail.
Metering. Turning raw product events into billable usage.
Usage-based pricing. The model that bills directly from the meter.
Usage metering pitfalls and how to avoid them. The failure modes that show up in production.
Ready for billing v2?
Solvimon is monetization infrastructure for companies that have outgrown billing v1. One system, entire lifecycle, built by the team that did this at Adyen.
