Missing meters: flag them the day they go missing

November 13, 2026 · 5 min read

On this page
When you enter a meter reading, e-automate checks whether it’s credible and warns you if it isn’t. A device that stops sending anything doesn’t trigger that warning, because there’s no reading for it to check. If nobody catches it earlier, it can surface later as a missing-meter issue in the billing queue.
Here’s how to catch it closer to the day it happened.
Why a device goes quiet in the first place
ManagedPrint, a print fleet company, lists reassigned IP addresses, restricted SNMP traffic and a stopped data collection agent as three of the reasons printers stop reporting data. A changed IP address can disrupt communication with the monitoring software. A security policy update can restrict SNMP traffic instead. Or the collection agent itself can stop running, and if it does, printers stop reporting data. None of that produces a bad reading. It produces no reading, and the validation warning only ever runs on a reading that shows up.
Start with the request task’s own limits
e-automate’s Meter Reading Request task, run through e-agent, sends requests by email or fax, or builds a phone list for your team. It can be configured to keep sending until a suitable meter comes in, or you can cap it, so it stops sending after a set number of requests. Reaching that limit without a reading is worth checking on its own, before it ever reaches billing.
Each emailed request goes out with a self-authenticating link that stays enabled for 10 days, and the system generates a fresh one every month. After 10 days, the old link no longer works.
The equipment record also carries a Next request date and a reading cycle you can check directly, if you know to go look before the invoice run stalls.
Check the FMAudit date, not just the billing queue
For equipment on FMAudit, e-automate can populate a Last FMAudit custom property with the Last Meters Audit date every time FMAudit updates a meter, once it’s set up through the ESN FMAudit sync API and a custom property configuration. After that it updates on its own, without anyone keying it in.
A device with a Last FMAudit date from three weeks ago (our own rule of thumb, not a number e-automate sets), on a contract that bills monthly, is worth a call before the cycle closes, and worth a check for a network problem or a blocked agent first.
Know what “missing” looks like once it reaches billing
Contract billing moves a contract from the Contracts tab to the Billing queue tab, then to Ready to invoice/propose, and finally to Invoices/Proposals. Contracts ready to bill get a Validated status on the Billing queue tab, and missing cycles, suspect meters and missing meters are among the issues that can keep a contract from getting there. If you’re simply missing meters, you work that tab in meter view mode to enter or query readings that should already be there. That lets you resolve the contract in front of you, using the same request task, FMAudit date and equipment record covered above to figure out why the meter never came in.
What we’d check, in order
- If your process or reporting exposes it, review equipment where the meter reading request task hit its configured request limit without a suitable meter coming back.
- Check the Next request date on equipment nearing the end of its cycle. e-automate can’t issue a validation warning at all when there’s no usage history to check a reading against.
- For FMAudit-connected devices, compare the Last FMAudit date against the reading cycle, not against a vague sense of “recently.”
- When a device goes quiet, check the ordinary causes first: an IP address that changed, a security setting now restricting SNMP traffic, or the collection agent itself, before assuming it’s a meter problem.
- Use the billing queue to resolve missing-meter issues, not as the place you first learn about them.
Dealers we talk to rank meter reads as the job they most want off the desk, and having missing meters flagged the day they go missing is one of the things they ask for. Auralis reads meter emails and attachments from shared inboxes and writes them into e-automate through our ECI partner integration, via the ESN API, so the reads that do come in stop waiting on someone to key them.
How do we connect to your E-Automate? has the detail: which records get written, by what path, and what’s held for a person to approve.
Sources
- ManagedPrint, Why Your Printers Aren’t Reporting Data (And How to Fix It), Mar 19, 2025.
- ECI, e-automate online help (v250), Configuring Meter Reading Requests.
- ECI, e-automate online help (v250), Integrating FMAudit with E-automate.
- ECI, e-automate online help (v250), Billing Contracts.
- ECI, e-automate online help (v250), Additional Info - Meter Volume Checks.
- 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
Brand Manager
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.

Meter validation rules: when a low or high read needs a human
A high read and a low read need different handling. How to set meter validation rules in e-automate so the right reads go to a person, borrowing from control-chart practice.