Meter validation rules: when a low or high read needs a human

November 16, 2026 · 4 min read

On this page
A high read and a low read don’t deserve the same look. e-automate already keeps the two apart: a read that runs high against the average trips a usage-over-average warning, and a read that goes backward from the last one on file (or matches it exactly) trips a warning of its own. That much you already know if you’ve been running contract billing through e-automate for a while.
What’s less obvious is how you decide, once something’s flagged, whether it actually needs a person or can just clear on its own. The percentage on the warning is only one part of that decision.
The same fork shows up outside e-automate
The two-directions problem isn’t specific to e-automate, or to copiers. Xerox patented a way to catch it back in 2012: a system that uses historical meter reads to predict an anticipated value for a reading, then flags an actual reading as suspect when it runs far enough above or far enough below that expectation, treating an overage and a shortfall as two different conditions to check. In one version of the method, a read counts as suspect if its rate exceeds the threshold value by 25% or more. A read that comes in unusually light can be flagged too, on the same kind of comparison, run the other way. Once something is flagged, the patent describes what can happen next: a user may be alerted on screen and shown details such as the print device, its location and the date of the reading, and may then decide whether the flagged value should update the model going forward.
That’s not a pattern an AI vendor invented to sound careful. The patent places a human decision after the automated flag too, and it was filed in 2009.
Setting the threshold is a real tradeoff
Tighter thresholds pull in more good reads for review, because the same buffer that catches a real problem also catches ordinary fluctuation. NIST’s own engineering statistics handbook makes that tradeoff explicit for statistical process-control charts, and the logic carries over even though a copier meter is a different kind of measurement. A standard 3-sigma control limit produces a false alarm about once every 371 points checked, on average. Add the WECO sensitizing rules on top of that limit, and the false alarm rate rises to about once every 91.75 points. The handbook leaves the tradeoff to the user: it says the user has to decide whether that price is worth paying.
You’re making the same call when you set a meter threshold, just without the sigma notation. Set it tight, and more good reads get pulled in for a second look. Set it loose, and fewer flagged reads get one before they post.
Sorting a flagged read into three buckets
Here’s how we’d sort a flagged variance, once it’s flagged, rather than treat every warning the same way.
- A read that fails before you even get to a threshold should go to a person, no matter how wide the buffer’s set. A meter running backward, a reading identical to the last one, a device with no usage history yet to compare against: these aren’t variance problems, they’re data problems.
- A read that’s off by a small amount, one you’d wave through by hand anyway, doesn’t need someone pulled off the desk to confirm it.
- A read that’s off by an amount that will show up on a customer’s invoice, or that suggests something changed about the device and not just the number, goes to a person. That’s the band your threshold actually controls, so it’s worth setting on purpose.
What a person decides about a flagged read matters too. Xerox’s patent treats it as feedback: the reviewer decides whether the flagged value should update the predictive model going forward.
That feedback loop matters as much as the flag itself. In our conversations with dealers who validate meters by hand, one recurring question sits right alongside it: will it post a bad read? Auralis handles meter-read entry, and routes anything above your own threshold to your team before it posts.
Book a 30-minute walkthrough on your own meter reads: auralis.ai/demo/
Sources
- Xerox Corp, U.S. Patent 8,249,913 B2, Systems and methods for detecting suspect meter reads in a print environment, filed Sep 22, 2009, published Aug 21, 2012.
- NIST/SEMATECH e-Handbook of Statistical Methods, What are Control Charts?.
- ECI, e-automate online help (v250), Billing Contracts.
- Auralis product information and conversations with dealers (internal).
For e-automate dealers
See Auralis on your own service desk
A 30-minute walkthrough on your workflow — meter reads, dispatch, supplies and escalation.
Book a demo
Head of Branding & Partnerships
Related posts

Email is not a workflow: getting billing and contracts out of shared inboxes
Billing and contract questions that live in a shared inbox are hard to track. Why email works badly as a workflow for a copier dealer, and how to move that work into e-automate.

Toner orders: from phone call to sales order without re-keying
A toner order that starts as a phone call often gets keyed twice. How to get it from the call to an e-automate sales order once, with the supply items linked to the right equipment.

Missing meters: flag them the day they go missing
e-automate warns about a reading that looks wrong, but not about a device that stops reporting. How to catch missing meters the day they go missing, before they reach the billing queue.