How to Choose Utility CIS and Billing Software: A Selection Guide

Choosing utility CIS and billing software comes down to fit, not feature count. SAP, Oracle, and Cayenta can all run meter-to-cash for a utility. The right choice depends on your size, your rate complexity, the systems you already run, and who will actually implement it. The fastest way to make that decision defensible is a weighted RFP scorecard that every vendor is measured against, using your own tariffs and bills rather than a vendor demo script.

This guide gives you that scorecard, a set of weights you can adapt, fit notes on how each vendor typically positions, the questions to put in your RFP, and the red flags that should slow a selection down. Vendor facts are sourced and dated as of September 2026.

Who this guide is for

This is written for the team running a CIS and billing replacement: the customer service, billing, finance, and IT leads, plus whoever owns procurement. It applies to:

• Investor-owned utilities with large customer bases, complex tariffs, and regulatory reporting to a state commission.
• Municipal and public power utilities, often multi-service (electric, water, wastewater, refuse) and tied to city finance and budgeting processes.
• Electric cooperatives that need member billing, capital credits, and a lean IT team.
• Water and wastewater districts with tiered and seasonal rates and growing AMI programs.

The criteria are the same for all of them. The weights are what change.

The evaluation criteria

Eight criteria cover the decisions that make or break a CIS program. For each one, the question is what the vendor can prove with your data, not what the brochure says.

1. Billing complexity and rate engine. Can the system bill your hardest tariffs as configured, not custom coded? Test time-of-use, tiered, seasonal, demand, net metering, budget billing, and any bundled multi-service bill you issue today.
2. Meter-to-cash and AMI/MDM integration. How do interval reads get from the head-end system through validation, estimation, and editing (VEE) into billing? Is meter data management part of the same platform, a sibling product from the same vendor, or a third-party integration?
3. Customer self-service. Portal, mobile, payments, start-stop-transfer, outage and usage information, and increasingly AI agents that answer account questions.
4. Deployment model and cloud path. SaaS, single-tenant hosted, private cloud, or on-premises, and what the upgrade model looks like five years after go-live.
5. Implementation timeline and partner ecosystem. Who does the work, how many of their people have delivered this product at a utility like yours, and what a realistic plan looks like.
6. Total cost of ownership drivers. Subscription or license, implementation services, integrations, internal staff backfill, testing, hosting, and ongoing support over the full term.
7. Regulatory and reporting fit. Commission reporting, disconnection and payment arrangement rules, low-income programs, and, for public power, fund accounting and budget reporting.
8. Data migration. How much history converts, how many mock conversions are planned, and how bills from the new system are reconciled against the old one before cutover.

A weighting you can adapt

Weights should be agreed by the steering group before any vendor presents. A baseline that works for most utilities, out of 100 points:

A large investor-owned utility in a competitive retail market might move points into billing and regulatory fit. A multi-service municipal utility might add a criterion for integrated financials and work management and fund it from self-service. What matters is that the weights are written down first, so the scores cannot be tuned afterward to fit a favorite.

The RFP scorecard template

Score each criterion from 1 to 5, multiply by its weight, and total the result. Define the scale in the RFP so every evaluator scores the same way:

• 5: Demonstrated with your data in a scripted demo or sandbox, and confirmed by a reference.
• 4: Demonstrated with your data, with minor configuration gaps.
• 3: Demonstrated with sample data, or delivered through a standard integration.
• 2: Possible only with custom development or a third-party product not in the bid.
• 1: Not supported, or the vendor could not show it.

Keep the evidence column. It turns the scorecard from an opinion poll into an audit trail your board, council, or commission can follow.

How each vendor typically positions

These are fit notes, not scores. Your scorecard should produce the scores.

SAP: S/4HANA Utilities (and IS-U on ECC)

SAP’s utilities functionality runs inside the ERP itself. SAP’s own training material describes S/4HANA Utilities as covering the chain from metering and consumption determination to invoice creation and customer payment, with components for meter reading, device management, energy data management, billing, contract accounting (the receivables subledger usually called FI-CA), and customer engagement. That tight coupling to SAP finance and logistics is the main reason SAP-estate utilities start here. For the full module map, see our SAP IS-U guide.

Timing is the other driver. SAP committed in February 2020 to mainstream maintenance for SAP Business Suite 7 core applications until the end of 2027, with optional extended maintenance until the end of 2030. In August 2025 SAP added a time-bound SAP ERP, private edition, transition option covering 2031 to 2033, aimed at its largest and most complex ERP customers, with conditions that include moving to SAP ERP, private edition on SAP HANA before the end of 2030 and a minimum system size of 2 TB. A utility on IS-U today is therefore choosing a platform on a clock, whichever vendor it picks.

On the cloud path, SAP’s newer utility capabilities point to its private cloud: the Utilities Customer Self-Service Agent in SAP’s Q4 2025 Business AI release highlights draws on contracts, tariffs, and consumption data through its integration with SAP S/4HANA Cloud Private Edition. SAP also documents S/4HANA Utilities under its on-premise edition, which the utility or its hosting partner installs and runs.

Oracle: Customer Cloud Service and Customer Care and Billing

Oracle offers its utility customer platform in two deployment forms. Its CIS product page describes Oracle Utilities Customer Cloud Service as the SaaS option and Oracle Utilities Customer to Meter as the on-premises option, both combining meter data management, customer care, and billing on a shared database. Oracle also highlights point-and-click rate configuration with no coding required, self-service for start-stop-transfer and payments, and updates delivered in small releases throughout the year. The same page says its accelerated implementation package delivers the CIS “in months, not years,” which is a vendor claim to test against references.

Oracle also documents Customer Care and Billing Cloud Service as a billing system for utilities of all sizes that supports one to many service types, with releases listed as 25.4, 25.10, 26.4, and 26.10 as of September 2026. That twice-yearly cadence is good news for staying current and a real workload for regression testing, so price it in.

For utilities with AMI underway but a CIS replacement further out, Oracle’s 2020 Customer Cloud Service data sheet describes starting with its meter solution cloud service and adding the full customer platform later. For a deeper product-by-product comparison with SAP, read our Oracle vs SAP for utilities comparison.

Cayenta: CIS plus integrated utility ERP

Cayenta, a division of N. Harris Computer Corporation, was founded in 1983 as Solutions for Government to serve local governments and utilities, and that public-sector heritage still shows in its product line. Its solutions page lists a customer information system with a flexible rates engine alongside mobile workforce management, a customer engagement portal, meter data management, an outage management system, and work, financial, and human capital management designed for utilities and municipalities. It also includes Cayla, an AI layer with a customer service agent and an in-app assistant.

Deployment is either CayentaCloud, which the same page describes as single-tenant SaaS in dedicated environments backed by SOC 2 certification, or on-premises. On implementation, Cayenta’s services page says its own team drives the program from planning through go-live, which is a different model from a systems integrator bid. For a full assessment of where it fits, see our Cayenta CIS review.

Fit at a glance

AI is moving fast across all three. Our SAP vs Oracle vs Cayenta AI comparison covers what each has shipped, but treat AI as a tiebreaker in the self-service score rather than a reason to pick a platform.

RFP questions to ask each vendor

Ask every vendor the same core questions, then add the vendor-specific ones.

Questions for all three:

• Recalculate these ten bills from our current tariff book live in the demo. Which rates required configuration, and which required code?
• Who, by name, will lead our implementation, and which comparable utility projects have they delivered on this exact product?
• What is included in the subscription or license, and what is priced separately (MDM, portal, mobile, analytics, AI features, test environments)?
• How many mock data conversions are in the plan, and who owns bill reconciliation?
• Can we speak with two reference utilities of our size and service mix, chosen by us from your list?

For SAP:

• Which deployment are you proposing, S/4HANA Cloud Private Edition or on-premises, and what does that mean for upgrades?
• If we run IS-U on ECC today, which path do you recommend relative to the 2027 and 2030 maintenance dates, and does the 2031 to 2033 transition option apply to us?
• Which systems integrator is bidding, and how is responsibility split between SAP and that partner?

For Oracle:

• Are you proposing Customer Cloud Service or Customer to Meter, and why?
• With releases twice a year, what regression testing do we own, and what tooling is included?
• If our financials are not Oracle, what integrations are prebuilt and what must be built?

For Cayenta:

• In CayentaCloud, what does Cayenta manage and what stays with our staff? Can we review the SOC 2 report?
• Which modules in your proposal are native to the platform and which are integrated products?
• How is your implementation team staffed for a project of our size, and what do you need from us?

Red flags

Slow the process down if you see any of these:

• The vendor will not run your bills. A demo built on the vendor’s sample tariffs tells you nothing about your rate book.
• “Configuration” that turns out to be code. Ask for a written list of every custom object in the proposal.
• An unnamed implementation team. A bid that lists roles but not people can change after signature.
• Pricing without scope. A per-customer price with no stated modules, integrations, or environments is not comparable.
• No conversion plan. If the vendor cannot say how many mock conversions are planned, data migration has not been thought through.
• Only hand-picked references. Ask for the full reference list and choose your own calls.
• A vague upgrade story. You should know how the system stays current five years after go-live.

A step-by-step selection process

1. Document the current state. Your rate book, bill types, integrations, and the pain points you want solved. Pull your hardest bills now; they become the demo scripts.
2. Set weights before you talk to vendors. Agree the scorecard with the steering group and record it.
3. Run an RFI to build a shortlist. Two or three vendors is enough for a serious evaluation.
4. Issue the RFP with scripted scenarios. Include your tariffs, sample meter data, and the questions above.
5. Hold scripted demos and a sandbox trial. Score in the room, against the evidence column.
6. Check references you chose. Ask what the vendor underestimated and what the utility would do differently.
7. Build a ten-year cost model. Put every bid on the same template so the totals compare.
8. Negotiate the statement of work, not just the price. Lock the team, the conversion plan, and acceptance criteria into the contract.

Data migration deserves its own plan from day one. Our guide to utility CIS modernization and migration covers what real moves off legacy platforms look like.

Sources and disclosure

Vendor facts on this page come from the vendors’ own material, checked in September 2026: SAP’s S/4HANA Utilities training content and SAP News Center announcements, Oracle’s CIS product page and product documentation, and Cayenta’s solutions and about pages. None of these vendors publishes list pricing, so this guide gives no prices.

Disclosure: UtilitiesLabs is backed by AvanSaber, which operates a SAP utilities consulting practice. That is a commercial relationship that could bias us toward SAP. We manage it by naming it, citing vendor sources for product claims, and holding SAP, Oracle, and Cayenta to the same scorecard. See our editorial policy.