Billing & metering operations · Electric & gas utilities (municipal/co-op)
Catch the bad read before the bill goes out.
An AMI meter flatlines and the read posts as zero, so a commercial account gets a $4 bill. Three months later the true-up triggers a PUC complaint.
The reality
Utility billing is an exception problem.
Every billing cycle runs thousands of meter reads through the CIS, and a small fraction throw exceptions — zero consumption, high/low usage outside tolerance, negative reads, estimated reads on a stuck register. Each one has to be investigated, estimated correctly per the tariff, or routed for a re-read before the bill prints. Miss it and you bill wrong, then fight the dispute.
The operator owns the exception queue end to end: it validates AMI and AMR reads, flags the ones outside tolerance, applies the correct estimation method or orders a field re-read, releases the corrected bill, and then resolves customer disputes — pulling the usage history and meter event log to explain or correct the charge.
How the operator runs billing & metering operations
Cycle 12 · Exception queue
validating- High-usage outlier confirmed against history
- Zero read — re-read ordered
- Estimating stuck register per tariff
01Clear the exception queue
Validates each read against usage history, flags zeros and outliers, and orders a re-read or applies the tariff estimate.
Account 88-4471 · Rate GS-2
billing- Corrected read posted to CIS
- Rate schedule + fuel rider applied
- Bill released into cycle run
02Release the bill
Applies the correct rate schedule and riders, recalculates the corrected charge, and releases the bill into the run.
Dispute DSP-2210 · High bill
resolving- Usage history + event log pulled
- Root cause: seasonal, not meter fault
- Explanation sent — closing
03Resolve the dispute
Pulls the meter event log and usage history, explains or corrects the charge, and documents the resolution.
The outcome
−55% of billing-ops work off the team
Accurate bills out on time, disputes closed fast.
- Read exceptions caught before the bill prints, not after the call
- Estimates applied by the tariff method, so true-ups stop surprising customers
- Disputes resolved with the meter event log in hand, not guesswork
Common questions
Billing & metering operations
- What does the Billing & metering operations operator do?
- The operator owns the exception queue end to end: it validates AMI and AMR reads, flags the ones outside tolerance, applies the correct estimation method or orders a field re-read, releases the corrected bill, and then resolves customer disputes — pulling the usage history and meter event log to explain or correct the charge.
- What impact does the Billing & metering operations operator have?
- −55% of billing-ops work off the team. Accurate bills out on time, disputes closed fast.
- How does the Billing & metering operations operator work?
- Validates each read against usage history, flags zeros and outliers, and orders a re-read or applies the tariff estimate. Applies the correct rate schedule and riders, recalculates the corrected charge, and releases the bill into the run. Pulls the meter event log and usage history, explains or corrects the charge, and documents the resolution.
More operators in Electric & gas utilities (municipal/co-op)
See the full catalogue →