ERP for utilities: five vendors compared

No single ERP vendor covers the four things that decide a utility program. Of the five that show up on utility shortlists, only SAP and Oracle own a utility customer information system for meter-to-cash. IFS leads on asset management but has no billing engine. Infor sold its asset management product to Hexagon in 2021, and Microsoft Dynamics 365 reaches billing only through partners.

ERP Research puts total cost of ownership from $150,000 for a small cooperative on Dynamics 365 to more than $5 million for an investor-owned utility on SAP S/4HANA, with go-lives from 8 to 36 months. Your size, and when your next rate case lands, decide which of those numbers is yours.

Four things decide a utility ERP program, and no vendor leads all four

A utility ERP selection is scored on four areas that a manufacturer or a bank never thinks about. The first is enterprise asset management and work management, because poles, pipes, substations, and treatment plants are the balance sheet. The second is meter-to-cash, the customer information system (CIS) that reads meters, bills, and collects. The third is regulatory reporting, which in the United States means the FERC Uniform System of Accounts. The fourth is field service, the crews and storm response that the other three feed.

Each vendor is strong in one or two of these and relies on a partner, a companion product, or configuration work for the rest. Capability cells come from a vendor page or ERP Research's guide; the last column is our judgment.

The Dynamics 365 price comes from ERP Research's vendor guide, which estimates IFS at about $100 per user per month; IFS does not publish list prices.

Asset management is where IFS and Oracle lead, and where Infor needs a check

The asset register is usually the largest data object in a utility, and the EAM module decides whether the ERP program can carry the capital program. IFS positions IFS Cloud as "the only true end-to-end asset lifecycle management solution" and sells asset investment planning for utilities.

Oracle's Work and Asset Cloud Service was built for utilities rather than adapted from manufacturing, with condition ratings, repair-versus-replace decisions, and prebuilt integrations to ERP, GIS, and construction systems. SAP's asset management sits inside S/4HANA and shares the ledger, which matters most when a construction work order has to capitalize cleanly into plant accounts.

Infor needs the most careful reading. Infor sold its global EAM business, including the Infor EAM product and about 500 employees, to Hexagon in July 2021, yet its utilities page still describes asset management and claims 22 percent longer asset life. Ask for the product name, the publisher, and the support contract for the asset module on the order form before you score Infor on asset management.

Dynamics 365 has no utility EAM. Dynamics 365 Field Service carries work orders and asset records, and partners or GIS tools carry network asset management. That works for a cooperative with 50,000 meters. It does not for an investor-owned utility with a million customers and a transmission system, and ERP Research does not place Dynamics 365 in that segment.

Whichever vendor you pick, budget a line item for data cleanup. Legacy asset records, some still on paper, often need heavy work before migration (ERP Research).

Only SAP and Oracle own a billing engine, so the other three need a partner or a second program

The CIS usually costs more and carries more risk than the ERP, in our judgment, so who owns the billing engine matters more than any feature list. SAP S/4HANA Utilities, the product most utility people still call IS-U, covers meter-to-cash, device management, and market communication.

Oracle Utilities Customer Cloud Service and its on-premise twin, Customer to Meter, put metering, customer care, and billing in one platform with a shared database. Oracle claims an accelerated package delivers a CIS "in months, not years."

Dynamics 365 reaches billing through partners such as Itineris, whose UMAX product runs on Dynamics 365 Finance at Regional Water Authority in Connecticut, serving about 432,000 people. Microsoft reports it largely eliminated about 14,000 erroneous bills a year. MECOMS 365 from Ferranti is the other common route. Either way the partner is your billing vendor, and the contract should say so.

Infor sells meter-to-cash billing inside CloudSuite Public Sector and claims a 60 percent cut in billing processing time, a vendor figure aimed at municipal scale. IFS does not sell a CIS, so an IFS program is a two-vendor architecture by design.

The order of billing and ERP is the largest scheduling decision in a utility program, larger than the vendor choice, because the two systems share the same finance and customer teams, test windows, and ledger. In programs we have advised, a tier 1 ERP program needs 36 months from decision to go-live, and a CIS replacement needs a window of similar length.

Consider a 400,000-customer investor-owned electric utility replacing a 20-year-old CIS and an SAP ECC-based ERP. Suppose the ERP program is quoted at $25 million over 36 months and the CIS at $45 million over 30 months. Billing first puts the new CIS live in month 30 against the old general ledger and the ERP live around month 66, and pays for the CIS-to-ledger interface twice, once to ECC and once to the new system.

Running both at once compresses the calendar to about 36 months but doubles the change load on the same teams and puts two cutovers in one test year. It raises the odds of joining the 31 percent of implementations that a survey reported by ERP Today found ran longer than expected.

ERP first means the ledger and the FERC chart of accounts are stable before the CIS posts to them, at the price of carrying the old billing system until about month 66, three years longer than billing first. The rule we recommend is ERP first unless the old CIS is the system that is failing, and never two cutovers within six months of each other.

FERC accounting is configuration work, and it has to be right before go-live

None of the five vendors ships a FERC module. Regulatory accounting is a chart of accounts design problem, and in our judgment it is the part of a utility program most often rebuilt after go-live. The FERC Uniform System of Accounts uses three-digit accounts that sort cost into demand, energy, and customer components for cost of service and rate design.

PowerPlan, a regulatory accounting software firm that reports working with more than 90 utilities, points out that a corporate chart of accounts string runs 15 to 20 or more digits, so the three-digit USOA account has to be reserved inside it or carried in a subledger.

Who has to comply is broader than many CIOs assume. Major electric utilities file FERC Form 1 each April once they exceed thresholds such as 1 million MWh of sales for three consecutive years. Publicly owned utilities and cooperatives are exempt, but the American Public Power Association says most municipal systems use the USOA anyway because bond covenants and state law depend on it, and cooperatives file the analogous RUS Forms 7 and 12.

FERC account configuration needs utility-specialist expertise, and reclassifying after go-live is costly (ERP Research). The design phase is 10 to 20 percent of implementation hours (ERP Research cost breakdown), and the regulatory accountant belongs there, not in testing.

Among the five vendors, ERP Research rates IFS weaker on FERC accounting and says Dynamics 365 needs add-ons for it. It calls SAP the incumbent standard for regulated utilities, and our reading of that installed base is that SI staff who have configured a FERC chart of accounts in SAP are easier to find.

One accounting rule affects the program budget directly. Major costs can be deferred to FERC account 182.3, Other Regulatory Assets, when it is probable that a regulator will include them in rates later (ASC 980 for FASB filers, GASB 62 for public power). That lets an ERP program's cost wait for the next rate case instead of hitting the income statement in the year it is spent.

Field service is the one area all five can claim, so test it on a storm day

Every vendor in the table has a field service product, and ERP Today reports that IFS added Resolve for Utilities in February 2026 for crew callout, mutual aid, and extreme weather response.

Infor describes mobile inspections, crew scheduling, and GIS-integrated tools. Dynamics 365 Field Service is Microsoft's native product and the strongest module in its utility story.

The differences show up in two places. The first is whether field service shares the asset register with EAM or syncs to it, because a crew closing a work order against a stale asset record recreates the data cleanup you just paid for. The second is whether the product handles storm callout, mutual aid, contractor crews, and offline work. Demo a storm day with 300 crews, not a planned meter exchange.

Utility size changes the shortlist more than vendor features do

The US utility market is three markets. Investor-owned utilities file FERC Form 1, run rate cases, and buy at tier 1 scale. Just over 2,000 community-owned utilities serve about 15 percent of electric customers, and 1,400 of them serve communities of 10,000 people or fewer (APPA).

NRECA counts 830 distribution cooperatives and 60 generation and transmission cooperatives serving an estimated 42 million people, or 13.6 percent of the nation's electric customers.

Cost bands and timelines are ERP Research's published figures for utilities, with no stated method. Treat them as a sanity check, not a budget, and plan at the top of each band. CIS integration and the FERC chart of accounts work are costs a non-utility program in the same band does not carry.

Three things change across the segments. The first is the CIS decision: an investor-owned utility almost always has a CIS program of its own, while a small cooperative often buys billing and accounting from a cooperative-specific vendor such as NISC iVUE and leaves it alone. The second is governance: a municipal utility is often an enterprise fund inside a city, so the ERP is the city's ERP, which is why Infor's public sector suite and GASB reporting show up there. The third is funding: rates for investor-owned utilities, rate studies and bonds for municipals, member rates and RUS financing for cooperatives.

Rate case exposure sets the timing and shape of the program

For an investor-owned utility, the ERP program is recovered through a rate case, and the rules of that recovery shape the program more than any vendor feature. Capital spending enters rate base and earns the authorized return. Operating expense is recovered at cost, if the commission allows it, and earns nothing. On-premise software has usually been capitalized, while a cloud subscription has usually been booked as operating expense.

In Utility Dive's coverage of the NARUC resolution, consultant Jill Feblowitz estimated a typical SaaS charge at about $1 per customer per month, and said a provider would need to roughly halve that to offset what the utility gives up by not rate-basing the system.

Regulators know this creates a bias toward the older architecture. NARUC passed a non-binding resolution in November 2016 urging state commissions to treat cloud and on-premise software alike for earning a return, and the Illinois Commerce Commission approved a first-notice proposed rule on June 1, 2018, to put prepaid cloud computing on par with on-site IT investment. Most other states still decide case by case.

Before you sign a RISE with SAP, Oracle Fusion, IFS Cloud, Infor CloudSuite, or Dynamics 365 subscription, get regulatory counsel's view in writing on how that fee will be treated in your jurisdiction, and whether a prepaid or multi-year structure changes the answer.

Timing is the second exposure. A general rate case in Indiana typically takes 10 to 12 months from filing to order, and a utility cannot file another until 15 months after the last one. June 2025 alone saw 17 initial rate increase requests totaling $3.846 billion, according to S&P Global. A program that goes live after the test year closes waits for the next case, which can mean two and a half to three and a half years of carrying cost before recovery begins. That is why the FERC 182.3 deferral matters, and why CFOs push to land go-live inside a test year.

The third exposure is scope. A rate case is costly and infrequent, so CFOs either bundle ERP, CIS, and EAM into one filing, which pushes toward one large scope, or phase them to match the filing cycle. The mistake is letting the SI's preferred phasing decide a question that belongs to the rate case calendar.

Take the same 400,000-customer utility. Suppose its last rate order came in March 2026 and its state uses a historical test year. It plans to file in June 2028 on a calendar 2027 test year and expects an order between April and June 2029 on a 10 to 12 month schedule. An ERP go-live in October 2027 lands inside the test year: the capitalized build enters plant in service, the first subscription payments show up in test year expense, and the filing carries both.

Slip go-live to February 2028 and the same spending falls outside the test year. The utility then either absorbs the cost or defers it to FERC 182.3 and asks the commission to approve the deferral. Under a 15-month refiling bar, the next filing comes no earlier than September 2029, with an order in mid-2030; a utility on its usual cadence files in 2030 for an order in 2031. Recovery on a $25 million program then begins two and a half to three and a half years after go-live, with carrying cost at the authorized return the whole time. Set the go-live date from the test year backward, not from the SI's resource plan forward.

Municipal utilities and cooperatives do not run rate cases in this sense, but a municipal rate study, a bond covenant, or a cooperative board setting member rates against RUS loan terms plays the same role. The question before selection is the same in all three segments: who pays for this, when, and does the deployment model change the answer.

Where each vendor wins

SAP S/4HANA wins at the large investor-owned utility that wants ERP and billing from one vendor, already runs SAP ECC and IS-U, and can find an SI bench that has configured FERC ledgers in SAP before. The risk is scope. ERP Today warns that the clean core promise "only works if industry depth does not get pushed back into side systems," and a utility has more industry depth than most.

Oracle wins at the regulated utility that wants finance, CIS, EAM, and field service from one vendor and will run Oracle Fusion for the ledger. Its named customers (Exelon, El Paso Electric, American Electric Power, Southern Company, Evergy) are the right size for the claim. The risk, in ERP Today's words, is making that breadth feel integrated alongside legacy operational systems.

IFS Cloud wins at the asset-heavy distribution, water, or generation utility where maintenance and field work are the business and billing is simple or already handled. ERP Research gives it the lowest cost band of its three leaders, $200,000 to $1 million or more, and a 6 to 14 month go-live band. The risk is the two-vendor billing architecture and the weaker FERC story, both designed around from day one.

Infor CloudSuite wins at the municipal utility inside a city government, where finance, HR, and the utility share one public sector ERP and GASB reporting matters more than FERC Form 1. Infor names El Dorado Irrigation District, serving 130,000 people, and the City of Corpus Christi. The risk is asset management after the Hexagon sale.

Dynamics 365 wins at the cooperative or municipal already on Microsoft, with a partner CIS such as UMAX or MECOMS 365 and Dynamics 365 Field Service for crews. Regional Water Authority is the reference case. The risk is that FERC, NERC CIP, and network asset management all come from add-ons, so the architecture has more seams than the license price suggests.

At investor-owned scale the mixed case, one vendor's ERP with the other's CIS, is as common as a single-vendor pairing, because the two are rarely replaced in the same decade. In every segment the billing engine is the more expensive and riskier system, so the ERP shortlist is built around whatever the CIS decision has already fixed.