Metering validation helps you catch erroneous or incomplete meter data before it creates billing delays or customer questions.
Instead of discovering data issues only when preparing invoices or final settlements, they come to light earlier. You review and correct them in your metering issue workflow, before they turn into costly manual investigations. This is particularly useful when working with many meter types, different reading frequencies, and a mix of manual and automatic readings.
Enabling metering validation
You enable metering validation via Configuration ➡️ Meter ➡️ Preferences ➡️ Metering validation.
Metering validation is not turned on by default.
You can enable or disable each validation separately.
Start with the validations that matter most for your billing process.
⚠️ Don't see metering validation in your preferences? Contact your CSM.
Why this matters
By validating meter data earlier, you can:
reduce the chance of incorrect invoices;
identify missing or faulty readings more quickly;
spend less time on manual investigations during billing preparation;
keep your meter data more complete and reliable.
What you can validate
You can enable the following validations separately:
Validation | What it detects |
Consumption out of bounds | Manually entered meter readings that are abnormally high or low compared to expected consumption (e.g. a typo). Configurable: margin above and below the expectation (both start at 35%). Currently works for manual readings only. |
Uncontracted consumption | Consumption at a service location during a period when that utility was not supplied. |
Zero consumption | Meters that report no or near-zero consumption for an extended period, even though usage is expected. Takes seasonality into account (e.g. no heat consumption in summer). Configurable: window (starts at 21 days) and minimum number of days with zero consumption (starts at 14 days). |
Missing meter reset | A resetting meter that should have received a reset reading, but never did. |
Incorrect meter reset value | A reset reading exists, but the recorded value is not zero. |
Measurement frequency too low | Hourly or daily channels that stop sending new data within the expected interval. Configurable: interval in days (starts at 14 days). |
Overlapping consumption | Delta consumptions that overlap with an existing consumption period on the same channel. |
Consumption gap | Missing periods between consecutive delta consumption periods. |
Negative consumption | Measurements that result in negative consumption (e.g. a cumulative reading lower than the previous one, or a negative delta value). |
Example – Consumption out of bounds: expected consumption is 100 kWh and both margins are 35%. Allowed range: 65–135 kWh.
Higher than 135 or lower than 65 → issue;
anything in between → no issue.
Use a lower percentage to catch smaller mistakes sooner, a higher percentage if you get too many issues.
⚠️ "Consumption out of bounds" currently works for manually entered readings only, not for readings received automatically from meters. All other validations also check scheduled meter data and imported consumption periods.
Working with metering issues
When a validation detects a problem, Zero Friction automatically creates a metering issue. You review and handle these via the metering issues list or via the "Issues" tab on a meter. For each issue, you choose: resolve, ignore, or mute.
➡️ Resolve
Use resolve when you want to fix the underlying problem and close the issue. Depending on the validation type, that can mean:
correcting a reading (e.g. after a typo or an incorrect reset value);
filling in a missing consumption period for a consumption gap;
correcting or removing an overlapping period;
adjusting the reading frequency of a channel if data is coming in too infrequently;
accepting the current data and marking the issue as resolved, without changing the measurement.
For many validation types, you can resolve multiple issues in bulk, but only issues of the same validation type at a time. Some types (such as consumption gap and overlapping consumption) must be handled one by one.
➡️ Ignore
Use ignore when the measurement should not be used further, but you do not need to correct or replace it right now. Ignoring:
closes the issue with status “ignored”;
does not change the measurement value;
means the measurement is not used for further processing;
keeps the issue findable under the “all” filter.
You can ignore a single issue or several issues at once.
➡️ Mute
Use mute when a meter keeps generating the same type of issue and you want to temporarily reduce the noise. From an issue, choose "ignore and create a muting rule"; you can also create a muting rule from the meter list. A muting rule applies to:
a specific meter;
one or more issue types;
a chosen period: day, week or month.
During the muting period, open issues of those types are ignored and new issues are created as "muted" rather than open. Reading values are not affected by muting. You manage and cancel muting rules on the meter detail page.
Situation | Action |
The data is incorrect and you can correct it. | Resolve |
The data should not be used, but you are not correcting it right now. | Ignore |
The same type of issue keeps coming back on a meter and you want temporary relief. | Mute |
Problem | Solution |
Metering validation is not visible in preferences. | Contact your CSM: the feature may not be enabled for your organisation. |
Too many alerts for "Consumption out of bounds". | Increase the margin above and/or below the expectation (starts at 35%). |
Too many alerts for "Zero consumption". | Increase the window or the minimum number of expected days if short quiet periods are normal for your meters. |
The same issue keeps appearing on one meter. | Create a muting rule for that meter and the relevant issue types. |
Automatically received measurements are not flagged by “Consumption out of bounds”. | This is expected: that validation currently works for manual readings only. |
Do these validations block all incoming data?
No. The goal is to surface suspicious or missing data early so you can review it. Issues do not block all meter activity.
Do I need to enable every validation at once?
No. You can enable validations separately and start with the checks that matter most for your billing process.
Do these checks only apply to manual readings?
No. Only "Consumption out of bounds" focuses exclusively on manual readings. The other validations also check scheduled meter data and imported consumption periods.
Can I resolve issues in bulk?
Yes, for many validation types, but only issues of the same validation type at a time. Some types (such as consumption gap and overlapping consumption) must be handled one by one.
Why are some validations more useful for certain meter types?
Because not every validation applies to every kind of channel or reading pattern. Some are meant for cumulative meters, some for delta consumptions, and some for channels with expected reporting intervals.
What is the main benefit?
You find meter data issues earlier, resolve them with less manual effort, and reduce the risk of billing delays or invoices based on incorrect consumption.