A response to ongoing industry discussions about operational complexity and risk in retail energy
A recent vendor article argued that as retail energy markets become more complex, risk arises in the gap between what suppliers sell and what they can reliably deliver. The authors referenced a “real-world utility billing software failure” that generated phantom load charges, resulted in tens of millions in exposure, and offered no clear resolution due to the complexity of the error.
This serves as a valid warning and highlights a critical question every retail energy supplier should consider regarding their back-office infrastructure.
However, the article does not address a more important question: What does it look like when a billing platform manages this complexity effectively?
The issue is not complexity itself but rather using the wrong system to manage it.
The ISO-NE case discussed in the article involved a Local Distribution Company (LDC) back-office system failure, not a retail energy billing failure. This distinction is important. LDC back-office systems are designed to accurately track usage in hourly or fifteen-minute intervals, rate classes, tariff structures, and customer accounts details like meter ID, premise location and such, while retail energy billing systems, especially for large commercial, industrial, and data center loads, use the LDC data to calculate monthly charges. When the LDC’s systems are not providing accurate data to retailers, as was the case in ISO-NE, it is the responsibility of the LDC to find and correct the errors, since they own the meters, wires, and systems collecting the data.
In this case, when the error was caught months later, the ISO mechanism to correct the bad data from the LDC going back multiple months across so many accounts, was limited and penalized the retail energy provider and their clients. This is a failure of the LDC systems, and the ISO market rules, not the retail energy provider billing system.
In similar cases around the country, FERC has intervened to have the ISO rules updated to fix this problem. That is a similar path the retailer is escalating with the ISO to fix this problem.
Now let’s talk about the real challenges when LDCs don’t get their data wrong
A large industrial customer’s monthly invoice isn’t just one bill. It’s a layered structure of interval usage data, ancillary service pass-throughs, block allocations, and market resettlements, each calculated at 15-minute or hourly intervals, across multiple ISOs, governed by market-specific rules that change. A single invoice for a complex commercial account can require processing more than 200,000 unique determinants. Multiply that by tens of thousands of accounts, and you have a system that produces over 60 million ancillary service rates every single month, each of which has to be validated before billing.
That’s not a billing problem and the retailers experiencing it aren’t the ones whose systems failed. This is a problem with the market rules at the State, ISO, and FERC level, which don’t have the controls to catch LDC created data errors on a large scale over large periods of time and mechanisms to correct the errors that are caught months/years later.
On-system configuration is the differentiator, without any requirements for custom coding.
The article frames the risk correctly: billing errors, exception overload, remittance discrepancies, the inability to trace a variance quickly. What it doesn’t address is how the right platform architecture eliminates those risks before they materialize, and why the architectural choice matters more than any individual feature.
The core question isn’t whether a billing system can handle complexity in theory. It’s whether it was designed so that complexity is managed through configuration rather than through custom development. These are fundamentally different operating models.
In a configuration-driven system, new products, new charge codes, new ISO rules, and new ancillary service structures are implemented by operations teams in hours or days, without touching code. In a development-dependent system, every new requirement enters a queue. It gets scoped, estimated, prioritized, built, tested, and deployed. That cycle takes weeks to months. Everything is implemented for the first time, adding risk. During the lengthy development period, the business is carrying exposure.
Every month of custom development is a month of exposure and a risk from new-code production failure. Every workaround is a point of failure. Every manual process is a variance waiting to surface.
The retail suppliers competing most effectively today aren’t the ones with the most sophisticated products. They’re the ones whose back-office infrastructure can execute those products accurately, at scale, without friction — and adapt when the market changes without waiting for a new development cycle with all the related testing and risks.
Reliability isn’t a feature. It’s the table stakes.
Speed and adaptability matter. But they’re only valuable on top of a foundation that doesn’t fail.
Billing accuracy and system availability aren’t differentiators in the way they used to be. They’re the minimum expectation. The question isn’t whether a platform claims high uptime. It’s whether it can demonstrate it across a full set of operational metrics: billing accuracy by count and dollar, invoice timeliness, resettlement processing, enrollment and drop timing, payment posting, and priority request response.
Thirteen tracked SLA metrics. Not one. Not three. Thirteen. And the platform that can show a clean record across all of them demonstrates something qualitatively different from a platform that tracks only the easy ones.
The same logic applies to invoice transparency. In a market where industrial energy managers scrutinize every line item, a complex invoice that arrives without a full backing sheet isn’t just inconvenient. It’s a service desk ticket, a dispute, a relationship cost. Every invoice should be fully auditable by the client without requiring a call to operations.
The article warns that in a market where wholesale volatility and settlement complexity are the baseline, billing precision is a business continuity issue. That’s right. But the answer to that risk isn’t caution. It’s capability.
The infrastructure question every retailer should be asking.
The retailers navigating this market most successfully aren’t choosing between growth and operational control. They’re asking a different question: does our back-office infrastructure give us the freedom to compete aggressively, or is it the thing that slows us down?
That question has a specific answer for the complex C&I and data center segment. Winning that business requires the ability to design and deliver highly customized products — interval-based pricing, block structures, ancillary service pass-throughs configured to each client’s portfolio. It requires billing that can absorb market resettlements without creating operational chaos. And it requires a system that gives the sales team the ability to say yes to client requirements without checking with the development team first.
The gap the industry article describes is real. But it isn’t inevitable. The suppliers who have closed it aren’t the ones who simplified their business to fit their billing system. They’re the ones who found infrastructure that was built for the complexity they were already selling.
The question isn’t whether your business is complex. It’s whether your platform was built to handle it, or whether you’re about to find out it wasn’t.
Learn how purpose-built billing infrastructure supports complex retail energy operations.
Read the case study: Complex Billing Delivered at Scale
By: Rob Roy, Director of Business Development, Retail Energy Sales, Customized Energy Solutions
