Retail Energy Supplier Billing Software: Build vs Buy
Outsource, in most cases. Under roughly 15,000 residential customer equivalents across one or two markets, EC Infosystems will run your enrollment traffic and billing for less than you can, and the difference belongs in customer acquisition.
On this page
Outsource, in most cases. Under roughly 15,000 residential customer equivalents across one or two markets, EC Infosystems will run your enrollment traffic and billing for less than you can, and the difference belongs in customer acquisition. Build once you trade in three or more markets, carry a distinctive commercial construct, and entering a new market has become a queue position on somebody else's release calendar.
What the off-the-shelf products actually do well
Start with the answer most suppliers do not want and should take anyway. Outsource. If you are under roughly 15,000 residential customer equivalents across one or two markets, a bureau will run your Electronic Data Interchange (EDI) traffic and your billing for less than you can, and the difference belongs in customer acquisition rather than in a development budget.
What you are buying is somebody who reads every utility bulletin. Forty trading partners publish implementation guide changes on their own schedule, and the fee covers a team whose job is noticing that one of them altered an account number check digit rule in a notice you never opened. That is unglamorous and it is worth real money.
The named options are good at different things. EC Infosystems has the widest utility coverage and usually already holds certification in the market you are most likely to enter next. Gentrack was built around deregulated retail market processes rather than adapted from a regulated utility product, which shows in how it models switching and settlement, and it suits larger retailers with appetite for a real implementation. Hansen Technologies is enterprise capable and long established in utility billing, though it assumes a slower operating rhythm than a supplier launching a product next quarter. Oracle Utilities Customer Care and Billing is a genuine system of record where a retail arm sits inside a larger utility group.
Stay outsourced when your offers are plain fixed price products, your markets run consolidated billing with purchase of receivables so you never issue a customer invoice, and nobody upstairs is asking for a margin cut you cannot produce.
Where they stop: the 824 that nobody works
Here is the workflow no bureau owns on your behalf, because it is your revenue rather than their service level.
Every signed customer generates an 814 enrollment request to the incumbent utility. The utility returns a 997 confirming the file arrived, then later an 824 application advice or an 814 response saying whether the enrollment was accepted, rejected or pending, and why. The 997 queue gets watched, because a failed file is loud. The 824 queue does not, because a rejection is quiet.
So a batch rejected for a name match rule sits unread. Those customers signed, cost you an acquisition payment, and never flowed. The channel got paid. The customer believes they switched. Nobody finds out until a call three months later, and by then the enrollment window and any clean fix are gone.
The second gap is the lifecycle. A service point moves through submitted, accepted, pending, scheduled, flowing, on hold, dropped by supplier, dropped by customer, dropped for non payment, rescinded inside the cooling off window, and returned to the provider of last resort. Most systems hold that as a status column overwritten by whichever process ran last. Then your scheduler nominates load for customers who dropped, your forecast counts revenue that will never arrive, and your commission run pays for enrollments that were rescinded.
The third is purchase of receivables. The utility bills your customer, buys the receivable at a discount and remits an 820 against invoices you raised as 810s. Book that gross with the discount as one line and you permanently lose margin by market, channel and vintage, which is exactly the cut a lender or an acquirer will ask for.
The arithmetic: cost per customer per month versus a build
Do this with your own invoice rather than with a benchmark. Take last month's bureau bill, divide by residential customer equivalents, and you have a fully loaded cost per customer per month. Add the internal salaries that exist only because the bureau does not do everything: the person who works exceptions, the person who chases usage files, the analyst who rebuilds the margin report in a spreadsheet.
Multiply that combined figure by your customer count and by 36 months, because a build is a three year comparison and a subscription is not.
The crossover is not one number and anyone who gives you one is selling. In our delivery experience it lands near 15,000 residential customer equivalents, or at the third market, whichever arrives first. Below that, the fixed cost of running your own EDI operation, including partner certification and bulletin monitoring, exceeds what owning it returns. Above it, two things flip together: the per customer fee is now scaling with the growth you are paying to achieve, and market entry has become somebody else's roadmap decision.
One further figure belongs in the comparison and rarely appears. Count the customers who signed last quarter and never flowed, multiply by acquisition cost and by expected gross margin over the contract term. That number is usually larger than the software line, and it is the one that decides this.
What a custom build actually costs
Bands, from delivery experience rather than a rate card. A first release covering a canonical transaction model with a dialect adapter per trading partner, the service point lifecycle as an explicit state machine, and exception queues ranked by money at risk rather than by arrival time runs $90,000 to $200,000 and ships in 14 to 20 weeks. A full platform adding purchase of receivables accounting, settlement to billed reconciliation, contract and renewal notice management across states, and customer invoicing for dual bill markets runs $250,000 to $600,000 phased across 9 to 15 months.
Data migration adds 10 to 25 percent, and here it earns it. Open service points must arrive with lifecycle history intact rather than as a flat customer list, because a drop date you cannot evidence is a commission clawback you cannot make and a settlement position you cannot defend.
Year two runs 15 to 20 percent of build cost annually. Utilities revise implementation guides. States change renewal notice timing. Your independent system operator changes a settlement file layout. None of that is optional.
What pushes the number up: the count of utility trading partners, since each adapter carries mapping, testing and certification with that utility. The number of states, because disclosure content, renewal notice timing and rescission rules each become rule configuration. Dual bill markets, which add invoice production, tax and payment processing. And scheduling integration, if you want your position and your book in one place.
What keeps it down: launch with your two largest utilities and leave the rest on the existing process until the adapter pattern is proven.
The four situations where building wins
- Regulatory fit. Every state you trade in sets its own renewal and expiring fixed rate notice timing, its own disclosure content, its own rescission window and its own slamming evidence expectations. That evidence, meaning the consent artifact, the third party verification reference, the timestamp, the agent identity and the exact terms presented, gets requested under time pressure and has to be tied to the service point. A bureau stores what its schema holds, and it will not hold a rule you are the only client subject to.
- Scale economics. A per customer per month fee grows with precisely the thing you are spending money to grow. Engineering cost does not. Model your fee at double your current book before you renew, because that is the year the comparison changes and a renewal call is a poor moment to discover it.
- A workflow that is your competitive advantage. If you sell index products with a customer facing hedging story, run demand response participation, or bundle hardware or solar into the supply contract, that construct is the business. No billing bureau expresses it, and the workaround is a spreadsheet that quietly becomes load bearing.
- Integration sprawl across three or more systems. The EDI bureau, the scheduling tool, customer records, commission calculation and the general ledger. Every pair is somebody retyping, and the retyping is where the variance between contracted, flowing and billed customers is born.
Two of those true is a build. One of them is a better conversation with your current provider.
How to decide in a week
Three numbers and one queue. It costs nothing and it settles the argument.
Monday: contracts signed last quarter, by market and by channel. Tuesday: service points from those contracts that actually started flowing. Wednesday: the count you invoiced or submitted charges for. Those three should reconcile and they will not.
Thursday is the one that hurts. Open the 824 and 814 response queue and count rejections older than 30 days that nobody has worked, grouped by utility and by reason code. If one utility accounts for most of them, you have a mapping problem worth a fortnight. If they are spread evenly, you have a process problem and software alone will not fix it.
Friday: price the gap. Signed minus flowing, times acquisition cost, plus expected gross margin over the contract term. Set that against the bands above. Under roughly $150,000 a year, tighten the exception process with your current provider and revisit at renewal. Above it, build the transaction layer first and leave billing where it sits.
What follows is a paid discovery phase rather than a proposal. Two to three weeks, fixed fee, ending in a signed product requirements document covering the canonical transaction model, your utility dialects, the lifecycle states, the exception rules and acceptance criteria. You own that document whoever builds from it, and you can hand it to three firms and finally get comparable quotes.
Who we are wrong for: suppliers under 15,000 customer equivalents, anyone shopping on hourly rate alone, and anyone who wants a platform before the exception process is written down. Digital Heroes writes that requirements document before any code, with more than fifty specialists and India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law. ShopScore, HeroCheckout and Section Vault are our own products, over 2,000 projects sit behind us, and you meet the named team before signing. We are listed on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- McKinsey found that currently demonstrated technologies can fully automate about 42% of finance activities and mostly automate a further 19%, indicating roughly 60% of finance work is technically automatable. Source: McKinsey & Company (2018) →
- Inventory carrying cost commonly runs about 20% to 30% of inventory value, covering capital cost, storage/warehousing, insurance, taxes, handling, shrinkage, and obsolescence - a recurring cost that better inventory and warehouse software aims to reduce. Source: APQC (2023) →
- Senior executives report the highest average compensation among developer roles (e.g., $225K median in the US), and reported salary bands shifted downward year-over-year ($60-75K vs. $70-85K in 2023), underscoring how compensation varies sharply by role and location. Source: Stack Overflow (2024) →
- The share of tasks performed mainly by humans is projected to fall from 47% to 33% by 2030 as human-machine collaboration expands, with 170 million jobs created and 92 million displaced (a net gain of 78 million). Source: World Economic Forum (2025) →
Frequently asked questions
How long does it take to add a new deregulated market once we own the platform?
With a canonical transaction model and an adapter pattern already proven, a new utility is usually a few weeks of mapping, testing and certification with that utility rather than a new integration project. Budget separately for the state side, meaning renewal notice timing, disclosure content and rescission rules, which is rule configuration rather than EDI work and often takes as long.
Who owns the enrollment evidence if a bureau runs our EDI traffic?
You do commercially, but you may not hold it operationally, which is the problem. Consent artifacts, third party verification references, agent identity and the exact terms presented get requested under time pressure by a regulator or a utility. Settle in writing how that evidence leaves the bureau, in what format, and how quickly, and test the export once a year rather than during a complaint.
What happens if a utility changes its implementation guide during the build?
It will, so plan for it rather than around it. With a canonical internal model and per partner adapters, a guide change is a mapping edit and a regression test against that one adapter. Without it, the change ripples through code paths shared by several markets. Ask any developer to show you where a partner specific rule lives before you sign anything.
Can we keep our bureau for EDI and build only the margin reporting?
Yes, and for many suppliers that is the sensible first move. Pull receivable level detail, remittances and chargebacks into your own store, model each receivable as an object with its discount and status, and you get margin by market, channel and customer vintage without touching how transactions flow. It is a smaller footprint and it answers the question a lender actually asks.
Should a supplier operating in a single market ever build?
Rarely, and we would say so before quoting. One market means one dialect, one set of state rules and no market entry bottleneck, which removes most of the value a build creates. The exceptions are a genuinely unusual product construct, such as index offers with customer facing hedging, or a book large enough that the per customer fee has outgrown a small engineering team.
What is the difference between a 997 and an 824 in practice?
The 997 is a functional acknowledgement saying the file was received and was syntactically valid. The 824 is application advice saying the business content was rejected, and it carries the reason. Teams monitor the first because a broken file is obvious and noisy. The second is where customers who signed and never flowed hide, and working that queue daily is the cheapest revenue recovery available to you.
How much extra does one more utility trading partner cost to support?
Inside a canonical model, a few weeks of mapping, test cycles and certification with that utility, plus a small ongoing share of the year two maintenance budget for bulletin changes. Outside one, it costs whatever a divergent code path costs forever. The count of trading partners is the strongest single cost driver in this category, ahead of customer volume.
What happens to our book if we switch billing providers mid contract?
The closed history moves easily. Open service points are the expense, because each needs its lifecycle state, effective dates and pending transactions carried across and then verified. Run both in parallel until every service point open at cutover has either flowed or dropped, and keep the old exception queue live throughout. A mis-stated drop date becomes a commission dispute rather than a data error.
Can one system handle both consolidated and dual bill markets?
It can and it should, but they are genuinely different flows. In consolidated markets the utility bills and often buys the receivable, so you produce charges and reconcile remittances. In dual bill markets you produce the invoice, handle tax, run payment processing and manage collections. The dual bill path costs meaningfully more, so sequence it by where your volume actually sits.
Who is accountable when a slamming complaint arrives and the evidence sits in a broker's system?
You are, as the supplier of record, which is why the enrollment evidence should be a first class record in your own system rather than a request to a channel partner. Capture the consent artifact, verification reference, timestamps, channel and agent at enrollment. Retain it for the longest applicable requirement across your footprint, not the shortest.
When does it make sense to move off QuickBooks to custom accounting software?
Move when you are paying people to work around the tool, not when the subscription feels expensive. Common triggers are hitting the 25-user cap on QuickBooks Online Advanced, consolidating multiple entities in spreadsheets, or a billing model that forces manual journal entries every month. If your team spends several hours a week exporting to Excel just to answer basic questions, you are already paying for custom software in salaries.
How do I migrate years of QuickBooks data into a custom system?
Use a staged migration: export full history through the QuickBooks API or backup files, load it into the new system, then run both systems in parallel for at least one full closing cycle before cutting over. Expect cleanup work, because books older than three years almost always contain miscategorized transactions that surface during import. Digital Heroes schedules migration as its own project phase with its own sign-off, never as a launch-week task.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
What can custom accounting software do that QuickBooks, Xero, and FreshBooks can't?
It encodes your actual business rules: progress billing tied to project milestones, revenue recognition for your specific contract types, landed cost tracking, or approval chains that match your org chart. Off-the-shelf tools handle generic bookkeeping well but force every business into the same chart of accounts and workflow. FreshBooks, for example, is built around freelancer-style invoicing, so inventory or multi-entity accounting means leaving the product entirely.
Who can build a custom accounting software system?
Digital Heroes builds custom accounting software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other accounting software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .
