Many mid-sized municipal utilities have a patchwork of billing, financial, and other software, including software used by the city. It all may have been adequate at one time but no longer is.
The search for a new utility enterprise resource planning (ERP) platform starts with a list of requirements from every department. Field crews want software that does not slow them down. Finance staff want a system that survives an audit without a last-minute scramble. Customer service wants fewer callbacks from customers with questions about service or bills. The same is largely true for electric cooperatives.
And so, the search for the right system begins. Come up with a list of vendors and start setting up demos. It’s a complex undertaking. An ERP platform touches every department in a utility, from customer service to work orders to the general ledger to human resources. That scope can make the selection process confusing. Vendors can use similar language to describe different functionalities, integrations, support, and long-term cost. The stakes are high, and demos do not always reveal how well a system will fit the needs of your utility. A shortlist built on a massive feature checklist alone won’t get the job done.
The eight questions below are meant to cut through the noise and give utility leaders, municipal and cooperative alike, a consistent way to compare utility ERP solutions before signing a contract that will shape daily operations for years to come. They are written to be asked out loud, in a demo or a follow-up call. The difference between a vendor who answers with specifics and one who falls back on general reassurances is often a sign of what to expect after the contract is signed.
1. Does the platform natively integrate billing, financials, and operations, or require add-on modules?
Almost every ERP vendor will say their system is integrated. The more useful question is whether that integration was built from the ground up or assembled over time through acquisitions and third-party software. A native platform shares one database across billing, financials, work orders, and customer service, so everyone sees the same thing. By contrast, a system requiring multiple add-on modules, often requires nightly reconciliation, custom interfaces, or manual re-entry to keep modules in sync.
Third-party modules are common and can work well. For very specialized, esoteric needs that fall outside the ERP vendors’ core competencies, third-party modules can be necessary, but they may have separate databases, separate login credentials, and separate support requirements. Consequently, the more functionality an ERP vendor can provide within their platform, the better. Ask vendors directly whether each module in their proposal was built by their own company or acquired from another vendor.
For related reading about integrated platforms versus standalone or loosely connected systems see Utility ERP vs. Standalone Software: Why Integrated Platforms Win During Peak Demand.
2. Does the platform scale to fit your utility’s size, and the number of services you bill for?
Utilities come in all sizes, and an ERP platform sized for one may be a poor fit for another. According to federal ownership data on U.S. electric utilities, publicly owned utilities average around 12,100 electric customers each, while cooperatives average closer to 24,500; of course, both categories include utilities much larger, and smaller. A system that works well for a utility with a few thousand accounts may buckle under eighty thousand accounts. An enterprise platform built for a large investor-owned utility may be far more than a small municipal system needs, or can afford to maintain, both in license cost and the IT staff required to keep it running.
Scale is not only about customer count. Many municipal utilities bill for electricity, water, sewer, sometimes broadband, and other services from the same office. Ask vendors directly how their platform handles multi-service billing today, not on their future roadmap, and ask to see it demonstrated with your own service mix rather than a generic sample account. A platform that handles single-service electric billing well is not automatically ready to deal with water, gas, and sewer charges. Does the vendor ‘s system support multiple services assigned to one customer account, or do they have to create multiple accounts for the same customer (one for each service)?
3. How well does the system deal with public reporting and audit requirements?
Municipal utilities operate under a level of public scrutiny that private companies do not. Open records requests, city council presentations, and annual audits all depend on software that can produce clean, defensible reports. Questions from a city council need to be answered without hours of manual work or a staff member rebuilding an old spreadsheet. Cooperatives face similar expectations; member-elected boards expect clear financial reporting and rate justifications too.
In both cases, the underlying need is the same: an ERP platform with reporting tools built for utility governance and accounting, not just generic business reporting. Ask vendors to show how a standard audit report or a rate case exhibit is generated and how long it takes a staff member to produce one. For a closer look at the documentation municipal utilities are expected to produce each budget season, see Rate Case and Budget Season: How Municipal Utilities Use Software to Build Their Annual Rate Justification.
4. What is the true total cost of ownership, not just the license price?
The number on a vendor’s proposal is not always what it ends up being when all is said and done. Implementation fees, data migration, staff training, custom report development, hardware or hosting costs, and ongoing support contracts all add to the total cost of ownership over a given period. Ask for a complete, itemized cost breakdown covering the first three to five years, not just year one, and ask specifically what triggers additional charges after go-live, such as adding a new service type, a new report, an added user seat, and changes needed to support a government mandated change in reporting.
5. How does metering data flow into the system?
Does the vendor’s billing system rely directly on an advanced metering infrastructure (AMI) headend, or do they offer a meter data management system (MDM). Ask vendors to walk through the actual data path: how often meter reads flow into billing, and what happens when a read is missing or flagged as an estimate. Utilities that have already invested in AMI should ask detailed questions about how well a vendor’s platform works with their AMI provider and ask for references. If the vendor provides an MDM option, how tightly it integrates with the AMI, billing, outage and mapping systems is crucial.
6. What does implementation and training involve, and how long does it take?
Utility ERP implementations are rarely quick, and vendors who promise an implementation timeline that sounds too good deserve extra scrutiny rather than extra enthusiasm. A realistic implementation includes data conversion and validation, parallel testing against the old system, staff training across departments, and a cutover plan that accounts for the utility’s billing cycle and seasonal demand patterns. Ask for a project timeline broken into phases and ask what happens if a phase runs long.
Training deserves particular attention. Software that works well in a vendor’s demo can still fail without adequate hands-on training. Ask how training is delivered, whether it happens on-site or remotely, and what ongoing training looks like for new hires after the initial rollout is finished. Utilities preparing for a system change ahead of a high-demand season should also review Advance Your Utility ERP Ahead of Peak Season: What Operations Teams Need in Place, which covers the operational readiness steps that matter most.
7. Is support built specifically for utilities, or is it generic enterprise software support?
Utility operations do not follow a typical business calendar. Storm response, disconnect and reconnect cycles, rate changes, outages and peak summer or winter demand all create support needs that a nine-to-five help desk cannot handle. Ask how the vendor’s support team is structured: are the people answering calls familiar with utility-specific workflows and terminology?
It is also worth asking where support is located, how response times are guaranteed, and what happens during declared emergencies or severe weather events, when a billing or work order system going down has real consequences for both the utility and their customers. Ask for examples of how the vendor supported using their system during a past emergency. Don’t rely only on what their service level agreement promises.
8. How does the vendor keep up with regulatory change and evolving utility technology?
Utility software must keep pace with changes utilities do not control, such as state reporting requirements, evolving cybersecurity expectations, new metering technology, and shifting customer expectations around self-service and digital communication. Ask vendors how often the platform is updated, how those updates are tested before release, and whether utilities have direct input into the product roadmap or simply receive whatever changes the vendor decides to make.
This question also touches on vendor stability. A utility signing a multi-year ERP contract is making a long-term bet on the vendor’s ability to keep developing the platform, maintain compliance, and support the utility through changes on both sides of the relationship. Ask for references from utilities of a similar size and service mix to your own, rather than accepting only the vendor’s largest or most polished reference account. A short conversation with a comparable utility that has lived with the software for a few years can be invaluable.
Bringing It Back to Your Shortlist
No two utilities weigh these eight questions the same way. But working through all these questions with each vendor, and insisting on specific, demonstrated answers rather than general reassurances, is the most reliable way to compare utility ERP solutions before deciding.
It is worth writing the answers to these questions down as you go, side by side across every vendor on the shortlist, rather than relying on memory as demos start running together. A vendor’s answer to question one, on native integration, often predicts how they will answer question five, on metering data, and question six, on implementation timelines, because all three trace back to the same underlying platform architecture. Patterns across the eight questions in this article tend to say more than any single answer does on its own.
At Central Service Association, our team is ready to help.
The information presented in this article is intended for general educational purposes. Utility software environments vary significantly. We recommend consulting with a qualified technology advisor to evaluate solutions appropriate to your organization’s specific operational requirements.