How a 42-location portfolio across seven states switched utility bill management providers without losing a single bill, account, or vendor handoff.
This case study is a composite drawn from real engagements with multi-location operators. Numbers, sequences, and outcomes reflect actual work.
01 · The portfolio
The example below reflects a 42-location portfolio across seven states, with utility accounts spread across electric, gas, water, and related vendors. The exact industry does not matter as much as the operating reality: dozens of locations, hundreds of utility accounts, multiple vendors, multiple billing channels, and too many places for something important to get missed.
On paper, every utility account was being handled by an established bill management provider. The contract had been in place for years. Bills were being processed. Payments were being scheduled. Reports were being generated. By every visible measure, the system appeared to be working.
In practice, the operations team was still getting calls from location managers every few weeks. A late fee here. A disconnect notice taped to a back door there. A new location that had been open for two months and somehow had no electric bill on file.
The provider always had an explanation. The utility had changed account numbers after a system migration. The bill had bounced because the mailing address on file was still tied to the previous owner. The portal credentials had stopped working and nobody had noticed.
Each explanation was technically true. None of them changed the fact that the team was running its own utility bill operation on top of the one it was already paying someone else to run.
This is what brought them to us.
02 · The decision to switch
The decision to switch is rarely about the new provider. Most teams in this situation are not shopping for a better dashboard. They are shopping for a way out.
The conversation is not usually, "we need more automation" or "we need better reporting." It is, "we can't keep getting surprised."
And switching providers, for most teams, is its own source of risk. Account histories get lost. Bills go missing in the cutover window because the outgoing provider stops collecting and the incoming one has not started. Vendors keep sending invoices to the old payment processor for months. Some accounts never make it across at all, and nobody finds out until a disconnect notice arrives.
"If a transition introduces more risk than the status quo, the rational decision is to stay with the broken status quo."
That is why so many teams stay too long with providers they no longer trust.
The first thing we tell prospects is that this calculation only holds if the transition is unmanaged.
With the right oversight, the cutover can become the safest part of the relationship, not the most dangerous one.
03 · The inventory
Before anything moves, we build a complete account inventory. If a portfolio is currently with an incumbent provider, we work with the customer to pull an export from the outgoing system and format it for ingestion into MeterID. If a portfolio is internally managed, we assemble the inventory from whatever exists: spreadsheets, bill PDFs, vendor lists, accounting records, store manager emails, and prior payment records.
We do the formatting work. The customer does not need to clean data for us. They need to confirm what is real and flag what is missing.
This sounds procedural. It is actually the most important thing that happens in the entire engagement.
The inventory becomes the baseline we track against for the rest of the relationship. Every account we expect to see. Every bill that should arrive. Every vendor that should send something. Every delivery method that needs to keep working. It all gets anchored here.
If an account is missing from the inventory on day one, it can stay missing forever. If it is captured, we can tell you the day a bill stops arriving.
What the day-one inventory exposed
None of this was uncovered by anything clever. It was uncovered by counting.
How this works
We track accounts using entity-level ownership details, not just utility account numbers. Account numbers change — utilities re-issue them after system migrations, mergers, rate-class moves, and ownership transfers. When that happens, the history sitting under the old number can get orphaned, and the new number can show up looking like a brand-new account.
MeterID ties account history to the underlying service relationship, ownership record, and portfolio context, so accounts remain continuous even when utility-side identifiers change. The portfolio included two locations that had changed hands in the prior eighteen months; both showed up in the inventory as continuous accounts, with history preserved instead of fragmented.
04 · The cutover
Once the inventory is built, we set a cutover date. This is the moment the outgoing provider's responsibility ends and ours begins.
We assume the outgoing provider may be uncooperative. We do not rely on them for handoff, forwarding, or warning us about anything they are about to stop doing.
The cutover date is the boundary. Everything before it is theirs. Everything after it is ours. And we manage the seam ourselves.
For each account in the inventory, we record the expected bill delivery method. Some accounts come by paper mail to a specific address. Some come by email to a specific inbox. Some come by portal download with a specific set of credentials. Some come through a utility data feed.
We capture this for every account, because the delivery method is often the first thing that breaks when a transition is mishandled.
We also record the expected billing cycle and historical due date pattern for each account. Most utility accounts bill on a predictable rhythm. The ones that do not — irregular meter reads, estimated bills, off-cycle true-ups — get flagged so we know not to expect them on a standard monthly calendar.
By the cutover date, we know what should arrive, how it should arrive, where it should arrive, and roughly when.
The transition becomes a tracking exercise against a known list, not a hope that nothing falls through.
42
Locations
7
States
118
Accounts
11
Vendors
3
Delivery methods
05 · The first 60 days
Here is what the timeline looked like.
Day 0
Cutover
Inventory baseline locked.
42 locations, 118 active utility accounts, 11 commodity vendors, three delivery methods in active use.
Day 1–14
Inflow
Bills begin arriving through every channel we expected, plus a few we did not.
Each bill cataloged against the inventory. Monthly accounts check in on schedule; bi-monthly and quarterly accounts parked with expected arrival windows noted.
Day 18
Flag
Expected Ohio water bill does not arrive.Almost lost
30-day cycle; previous bill landed 33 days ago. We flag it and pull it from the utility portal the same afternoon. Total customer involvement: zero.
Day 26
Flag
An invoice remained routed to the prior remittance address.Almost lost
Cycle tracking surfaces the gap; we correct the remittance with the vendor and pull the missing invoice.
Day 34
Flag
Two utility portals reject the credentials on file.Almost lost
Both resolved within a day. One was a stale password. One had been re-issued to a different email address that nobody had updated.
Day 41
Flag
A bill arrives for an account that is not in the inventory.Almost lost
The customer confirms a recently opened location that their operations team had stood up without notifying anyone. We add the account, set up delivery method tracking, and roll it into the standing process.
Day 60
Complete
Every account in the original inventory has produced at least one bill.
Bi-monthly and quarterly accounts are confirmed with their next expected arrival noted.
0
Late fees
0
Disconnect notices
0
Accounts lost
Nothing about the above is dramatic. That is the point.
The drama would have been what happened if the work was not happening quietly in the background.
06 · The counterfactual
When we look back at the first sixty days, four issues came close to slipping through the cracks. Each one would have been a different kind of failure in a less disciplined transition.
Day 18 · Ohio water
The bill that didn't arrive.
We flagged the missing 30-day cycle and pulled the bill from the utility portal the same afternoon.
Without uswould have arrived late — possibly with a service interruption notice attached — because nobody on the customer's side was watching that account's billing cycle.
Day 26 · Gas remittance
Invoice still routed to the prior remittance address.
Cycle tracking surfaced the gap. We corrected remittance with the vendor directly and pulled the missing invoice.
Without uswould have sat unpaid at the prior remittance address, eventually triggering a late fee or disconnect notice on a location where the operations team had no visibility into the lapse.
Day 34 · Portal credentials
Two portal credentials no longer worked.
Resolved both inside a day — one stale password, one re-issued to a different email that nobody had updated.
Without uswould have been discovered the next time someone needed to download a bill manually — in the previous arrangement, that could have been weeks or months later.
Day 41 · Untracked location
A bill arrived for a location nobody had told us about.
The customer confirmed the new site; we added the account to the inventory and rolled it into the standing process.
Without uswould have continued operating outside the utility bill management process until someone noticed a charge, a missing accrual, or a past-due notice.
None of these were dramatic individually. Collectively, they were the reason the customer left their previous provider.
A quiet transition is the only kind worth doing
That is what MeterID is built to do. MeterID gives operations and finance teams a live control layer over utility accounts, expected bills, delivery methods, due dates, exceptions, and payments — so provider transitions become manageable instead of invisible.
If you are in the middle of a provider transition, planning an acquisition, opening new locations, or unsure whether every utility account is being tracked, ask yourself one question.
"Could you tell me, right now, which of your utility accounts has not produced a bill this cycle?"
Not whether bills have been paid. Not whether your provider says everything is fine.
Whether you, sitting in front of your own data today, could name the accounts that are missing.
If the answer takes more than a minute, that is the gap. We built MeterID to close it.