By Sharon Watkins, Founder and CEO, RadiusPoint
A utility meter inventory is the UEM parallel to a telecom service ID file because both are the authoritative list of every billable identifier an organization pays for, and both are the level where a real audit actually happens. In Telecom Expense Management (TEM), an auditor works from the service ID, the unique number tied to a single line, circuit, or trunk. In Utility Expense Management (UEM), the equivalent unit is the meter. Audit the meters and you’re doing expense management. Pay the account totals and you’re only doing bill pay.
Here’s the thesis in one line: UEM audits at the meter level the way TEM audits at the service ID level, and without a meter inventory of record, utility bill pay is payment, not expense management. That gap has a price. When a site closes or a unit goes vacant and its meter never leaves your inventory, the invoice keeps arriving and finance keeps paying it. At RadiusPoint we run UEM on ExpenseLogic right beside TEM, on one platform, so the same discipline that catches a ghost phone line also catches a meter that should have gone dark months ago.
Key takeaways
- A utility meter is the UEM equivalent of a telecom service ID, the smallest unit a real audit can work from.
- Bill pay without a meter inventory is payment only. Meter-level auditing is what turns it into expense management.
- A meter inventory of record needs six fields at minimum: meter ID, commodity, site, tariff class, status, and cost centre.
- Closed and vacant sites are where a missing meter costs the most, because nobody’s watching an invoice for a location nobody visits.
UEM versus paying the utility bill
Utility Expense Management is the practice of validating utility charges at the meter level, and it’s a fundamentally different job from paying the utility bill. Bill pay is a three-step loop: receive the invoice, code it, remit the payment. It answers one question, whether the bill got paid on time. UEM answers a harder set. Is this meter on the correct tariff class? Does the consumption make sense for this site? Did a charge cross a threshold that signals an error? Is the cost landing in the right cost centre?
Those questions map to three kinds of audit that only exist once you work at the meter level: a contract and tariff rate audit, a consumption-based audit, and a threshold-based audit. None of them are possible from an account total, because a total hides the meter that’s wrong behind the meters that are right. It’s the same reason a telecom invoice total tells you nothing useful until you break it down by service ID. A program that stops at bill pay is paying accurately and auditing nothing. Knowing when a managed expense program earns its keep starts with recognizing that the audit, not the payment, is where the money is.
Why the meter is the service ID of utilities
The meter is the service ID of utilities because it’s the one identifier that ties a physical point of consumption to a rate, an account, and a cost centre, which is exactly what a telecom service ID does for a line or circuit. Every discipline TEM applies to a service ID has a clean counterpart in UEM at the meter. The unit of consumption changes from minutes and data to kilowatt-hours, therms, CCF, and gallons, but the structure is identical: an identifier, a rate applied to it, a volume measured against it, and a cost centre it belongs to.
| Dimension | Telecom (TEM) | Utility (UEM) |
|---|---|---|
| Core identifier | Service ID (line, circuit, or trunk) | Meter ID (meter number) |
| What it identifies | A single billable telecom service | A single physical point of consumption |
| Account grouping | Billing account number (BAN) | Utility account number |
| Unit of consumption | Minutes, data, ports, circuits | kWh, therms, CCF, gallons |
| Rate structure | Tariff, rate plan, USOC | Tariff class, rate schedule |
| What the audit checks | Contract rate versus billed, zero-use lines, cramming | Tariff class fit, consumption anomalies, threshold breaches |
| Change events | Moves, adds, changes, disconnects (MACD) | Service start, transfer, close, vacancy |
| Cost allocation key | Cost centre by service ID | Cost centre by meter ID |
| Failure mode when missing | Ghost line keeps billing | Meter at a dead site keeps billing |
The tariff class row is where a lot of recoverable money hides. A meter left on the wrong rate schedule after a site’s usage profile changed can overbill for years without ever triggering a late payment. That’s a meter-level finding, and it’s the utility version of a telecom line stuck on an outdated contract rate. RadiusPoint treats it exactly that way through utility rate reclassification, which is only possible when every meter carries its tariff class in the inventory. You cannot reclassify what you have never recorded.
Building a meter inventory of record
Building a meter inventory of record means creating one authoritative list of every meter, reconciled against actual invoices, so no billable point of consumption exists off the books. The build follows the same path as a telecom inventory. You extract every identifier from the invoices, cross-check it against a physical site list, and resolve the two into a single source of truth. In telecom that source is the service ID file. In utilities it’s the meter inventory. The onboarding work that produces a clean TEM data foundation is the direct model for how a meter inventory gets stood up.
At minimum, every meter record in ExpenseLogic captures these six fields.
| Field | What it records | Why the audit needs it |
|---|---|---|
| Meter ID | The unique meter or account number the utility bills | The primary key every charge and audit ties back to |
| Commodity | Electricity, gas, water, sewer, or waste | Sets which consumption logic and units apply |
| Site | The physical location the meter serves | Links the meter to a real, verifiable building |
| Tariff class | The rate schedule the meter is billed on | Enables the rate and reclassification audit |
| Status | Active, closed, or vacant | Flags meters that should no longer be billing |
| Cost centre | The department or entity the cost belongs to | Drives accurate allocation and chargeback |
Closed and vacant sites where meter inventory pays off
Closed and vacant sites are where a meter inventory pays for itself, because a meter that stays active after a location goes dark keeps billing every month with nobody left to review the invoice. This is the utility twin of the ex-employee wireless line no one disconnects. The location is empty, the service is still on, and the charge flows straight through bill pay because it looks exactly like every legitimate invoice. The status field in the inventory is the only thing that catches it, which is why a meter inventory without a status column simply cannot do this work.
Property management feels this most sharply during tenant transitions. A tenant moves out, never transfers the account, and the utility keeps billing the property owner for a unit generating zero revenue. Recovering those charges is the core of vacant utility cost recovery, and it only works when you can prove which meters map to which vacant units. One multi-location RadiusPoint client recovered about $1,500 a month, roughly $18,000 a year, from utilities that were still billing at locations the company had already closed. That money was recoverable for one reason: the meters were in the inventory, flagged by status, and audited against the site list. Without the inventory, those invoices would still be quietly paid.
One ExpenseLogic estate for TEM and UEM keys
Running TEM and UEM on one ExpenseLogic estate means telecom service IDs and utility meters live in the same system of record, audited by the same team against the same rules. Most vendors split these into separate products, which forces you to maintain two inventories, two audit workflows, and two exception queues that never talk to each other. On ExpenseLogic, the service ID file and the meter inventory are two expressions of one idea, a complete list of every billable identifier, each carrying its rate, its status, and its cost centre.
The verdict
The verdict is simple. If you can’t produce a current list of your meters with their commodity, tariff class, status, and cost centre, you don’t have Utility Expense Management, you have utility bill pay. The meter is the service ID of the utility world, the meter inventory is your service ID file, and the audit that recovers real money can only happen at that level. Build the inventory of record first. Everything else in UEM, from rate reclassification to vacant cost recovery, depends on it.
Frequently asked questions
Does UEM mean Unified Endpoint Management here?
No. In this article UEM means Utility Expense Management, the practice of auditing electricity, gas, water, sewer, and waste charges at the meter level. Unified Endpoint Management is a separate discipline in device and IT security that happens to share the acronym. When RadiusPoint says UEM, it always means the utility spend side of ExpenseLogic.
What is a meter inventory of record?
A meter inventory of record is one authoritative, invoice-reconciled list of every utility meter an organization pays for, with each meter carrying its meter ID, commodity, site, tariff class, status, and cost centre. It’s the utility equivalent of a telecom service ID file.
How does a utility meter compare to a telecom service ID?
A utility meter is the direct counterpart of a telecom service ID, since both are the smallest billable unit and the level at which a genuine audit takes place. A service ID ties a rate and a cost centre to a single line or circuit. A meter ties a tariff class and a cost centre to a single point of consumption.
Why do closed or vacant sites cost so much in utilities?
Closed or vacant sites cost so much because their meters often stay active and keep billing long after anyone stops reviewing the invoice. The charge looks legitimate, so bill pay processes it without question. Only a meter inventory with a status field catches it, which is what makes vacant cost recovery possible
Can TEM and UEM run on the same platform?
Yes. RadiusPoint runs both Telecom Expense Management and Utility Expense Management on ExpenseLogic, so service IDs and meters share one system of record, one audit workflow, and one exceptions queue.