A buyer's guide to utility billing and customer information systems
The CIS is the utility's cash register and its customer front door at once. Here are the real replacement drivers, the metering integration that decides fit, and how the vendor field is structured.
A utility billing system — the customer information system, or CIS — sits at an unusual intersection: it is simultaneously the revenue engine that has to bill every account correctly every cycle and the customer-facing front door residents judge the utility by. That dual role is why replacing it is so fraught. A billing error is not an annoyance the way a slow permit portal is; it shows up on a resident's bill and in the utility's cash position. This guide is the way we would frame a CIS replacement for a municipal water, sewer, stormwater, or electric utility.
As in every category, the buyer's readiness matters more than the logo. But the CIS has one dominant technical determinant of fit that deserves to be surfaced before any demo: how cleanly the system ingests and reconciles meter data.
Know your real replacement drivers
Utilities rarely replace a CIS because they want to. The genuine drivers cluster: a legacy system that cannot handle the rate structures the utility now needs (tiered, seasonal, or conservation-oriented pricing); an AMI or smart-meter rollout the old billing system cannot keep up with; an end-of-support or staffing-risk situation where the people who understand the current system are retiring; or a customer-experience gap where residents expect self-service, e-billing, and autopay the incumbent cannot deliver. Write down which of these is actually forcing the project, because it changes what you should weight.
Be honest about rate complexity specifically. A small municipal water utility with a simple tiered rate has very different needs from an electric utility with time-of-use pricing and net metering. Buying enterprise rating depth you will never configure is as costly a mismatch here as it is in permitting or ERP.
Metering and AMI integration is the fit decision
The single most important integration in a CIS evaluation is the one to your metering infrastructure and meter data management. Make every vendor show, against your actual meter mix and AMI head-end, how reads flow in, how exceptions and estimates are handled, and how a re-read or a disputed consumption value is reconciled. This is where CIS implementations quietly go wrong: the billing engine is fine, but the meter-to-bill pipeline leaks, and the utility ends up with estimated bills and a customer-service backlog.
Treat integration to the financial system of record as the second gate. The CIS posts cash and receivables into the general ledger, and a clean interface to the ERP is not optional. Confirm it is real and reconciled, not a nightly file drop someone babysits.
How the vendor field is structured
At the enterprise end, Oracle Utilities' Customer Care and Billing is built for large, complex water and electric utilities with intricate rate structures, high meter volumes, and demanding integration — genuine depth at scale, but heavy, integrator-led, and generally more system than a small municipal utility needs. In the established mid-market, Harris Computer (a Constellation Software company) owns several distinct CIS brands — Advanced Utility Systems' CIS Infinity, Cayenta, NorthStar, and SmartWorks — that collectively span small utilities up to larger, more complex ones; the draw is long-term ownership stability, and the catch is that these are different products with different heritages, so pin down exactly which brand you are evaluating and reference-check that specific product rather than the parent.
Many smaller local governments do not buy a standalone CIS at all — they get utility billing as a module of an integrated local-government suite. BS&A Software earns unusually strong satisfaction marks for integrated finance, assessing, tax, and utility billing among Midwest municipalities; Edmunds GovTech covers general ledger, payroll, tax, and utility billing with a deep Mid-Atlantic and Northeast base; and Tyler's Munis ERP includes utility billing within its broader municipal finance suite. For a small water utility that is really a city department, that integrated path is often the better answer than a specialist CIS. Finally, note that payments are increasingly a separate layer: Invoice Cloud is a bill-presentment and payments specialist that layers onto an existing CIS to raise e-billing, autopay, and online-payment adoption — a complement to the billing system of record, not a replacement for it, and worth scrutinizing on its integration and its convenience-fee model.
Evaluation criteria and failure modes
Weight the evaluation toward the things that actually determine success: meter-data integration and exception handling, rate-structure fit, GL integration, customer self-service and payments, and — as always — implementation and data-migration risk. Customer and account history conversion is the CIS equivalent of chart-of-accounts conversion in ERP: it is where timelines slip, and a vendor who treats it as your problem rather than a scoped deliverable is telling you something.
The most common failure mode is a go-live that produces a wave of estimated or wrong bills because the metering pipeline was under-tested, followed by a customer-service crisis. Insist on a parallel-billing period where the new system bills alongside the old one and the results are reconciled before cutover. It is the single most protective thing a utility can put in the contract.