Utility Billing and CIS Software: Custom Build vs Oracle, NISC, Harris and Gentrack
Buy the customer information system. Below roughly 80,000 customers, a package such as NISC iVUE, SEDC, Harris or Gentrack will handle customer records, receivables, payments and service orders better and cheaper than anything you commission.
On this page
Buy the customer information system. Below roughly 80,000 customers, a package such as NISC iVUE, SEDC, Harris or Gentrack will handle customer records, receivables, payments and service orders better and cheaper than anything you commission. Build one thing instead: the rating and determinant service that holds your tariffs, versions them by effective date and can re-rate history after a retroactive order.
Where Oracle, SAP, NISC, Harris, SEDC and Gentrack genuinely fit
The council passed a rate ordinance in May, effective 1 July, and your billing supervisor found out in the third week of June when somebody forwarded it to her. That is the shape of this decision, and it is not solved by picking a different product. Still, be fair about what the products do.
Oracle Utilities Customer Care and Billing is deep and it is the right answer for a large investor owned utility with the implementation budget to match. The caution is proportion: implementation and configuration routinely cost a multiple of licence, and mid sized utilities underestimate that ratio badly. SAP S/4HANA Utilities is the same shape of decision, sensible when your organisation already runs SAP and finance integration is the priority, and an enormous amount of platform if it does not.
NISC iVUE is genuinely strong for electric cooperatives and its fit with the wider cooperative ecosystem is a real advantage. Harris Advanced Utility Systems and SEDC both serve the mid market and cooperative space competently and know this domain deeply. Gentrack is capable and strongest where markets are deregulated and water billing is complex. Tyler and Cogsdale sit reasonably for municipals that want billing inside the same house as the general ledger.
Every one of these is a reasonable purchase for the customer, account, receivable and service order machinery. That machinery is roughly 80 percent of a customer information system (CIS), it is commodity, and you should not pay anyone to rebuild it. We say that knowing it removes the largest project on the table.
Where they stop: the tariff nobody outside your building has ever seen
Read any CIS demonstration script and rating gets ten minutes. In reality it is where the money is and where every implementation overruns, and it is the specific workflow no product models for you.
A single residential electric bill can carry a customer charge, an energy charge across seasonal blocks, a time of use split with its own holiday calendar, a power cost adjustment that changes monthly, a net metering credit with carry forward and an annual true up, a low income discount, a franchise fee, a state tax and a municipal tax. The order of operations between the fee and the taxes is set by your ordinance rather than by convention. Get it backwards and every bill in the class is wrong by a small amount, which is worse than being wrong by a large one.
Then the part that quietly breaks systems. A customer moves in on 12 July, mid cycle, into a tiered water rate. The tier boundaries have to prorate, and most rate tables assume a whole billing period. The workaround under time pressure is a flat allocation, which puts several thousand accounts into the wrong tier by a few units, and nobody notices until August when the finance director asks whether the July distribution to the water fund was right. On the commercial side, a demand ratchet billing the higher of current demand or a percentage of the peak in the preceding eleven months forces the system to reach backwards into history every cycle.
Underneath all of it sits re-rating. Commission orders and council ordinances arrive with retroactive effect more often than anyone admits, and rate cases settle months after the rates took effect. If your rating logic cannot be versioned by effective date and replayed across a period that already billed, every retroactive change becomes a manual project with statutory refund interest attached.
The arithmetic: cost per bill against the cost to build
Use your own contract. Packages here price per customer per month, per bill produced, or as an annual fee banded by account count, plus a separate implementation figure. Take the annual total, divide by your accounts, divide again by bills produced per account per year, and you have cost per bill. Then add the number nobody puts beside it: the average cost of a vendor change request for a rate change, and how many you raised last year.
Now the other side. A rating and determinant service sits in the band below. Amortised over five years with support, the midpoint lands near $85,000 a year. Compare that against your change request spend plus the staff weeks lost to manual rebills, not against your licence, because you are not replacing the licence.
The crossover is an account count. Below roughly 80,000 customers, a full custom CIS is almost never right and we will say so before you ask. Between 80,000 and about 250,000 accounts it depends entirely on how local your tariffs are: one commodity on standard rates stays bought, three commodities on one statement under council set ordinances usually does not. Above 250,000 accounts with multi commodity billing the full build becomes defensible, and conversion is then the largest line inside it rather than development.
What a custom build actually costs, including conversion and year two
Across the enterprise systems Digital Heroes has delivered, the bands look like this. The rating and determinant service with tariff versioning, re-rating and a regression suite of real accounts runs $200,000 to $450,000 over 5 to 8 months. A customer self service and usage presentment layer on top of it runs $80,000 to $180,000 over 3 to 5 months. A full custom CIS spanning customer, receivables, payments, service orders, arrears, disconnect workflow and multi commodity billing runs $700,000 to $2,000,000 across 12 to 24 months.
Conversion runs 10 to 25 percent of build cost and in a full CIS it reliably lands at the top. What has to move is not just customers and balances: deposits with interest accrued under state rules, levelised billing plans mid cycle with their accumulated variance, payment arrangements with remaining instalments, service orders in flight, meter history, decades of consumption used for high bill investigations, collection status and lien history. Plan at least three mock conversions, each with a financial reconciliation that ties converted balances to the legacy trial balance to the cent.
Year two and after runs 15 to 20 percent of build cost annually. In utility billing that is rate work, and it is the whole point: your council passes ordinances every year and the system has to follow them without a change request.
Cost drivers specific to this domain: the number of commodities on one statement, because each adds rate structures and its own fund distribution; net metering with export credits, carry forward and annual true up; prepay programmes, which change the entire billing cadence; the age of the legacy extract; and how many of your rules exist only in the billing supervisor's head, which you discover during the first mock conversion.
The four situations where building wins
Regulatory fit. Disconnection is the sharpest case. Medical certification holds, seasonal weather moratoria that vary by state, notice periods with specific delivery requirements, payment arrangements that suppress an account, deposits offsetting arrears and third party notification for vulnerable customers are each a rule with a date and a source. Most legacy systems encode that as a query somebody wrote a decade ago. Getting one wrong is a household without water, not a billing error.
Scale economics. Past 250,000 accounts, or past a change request count that has become a budget line, per account pricing plus vendor services outruns a build.
A workflow that is your advantage. For a municipal utility that is the multi commodity statement itself: electric, water, sewer and refuse on one bill, each with its own fund, its own ordinance and its own proration behaviour. No product will price that combination without a services contract, and it is the thing your council changes most often.
Integration sprawl across three or more systems. Count them: the meter data management system, the head end, the payment processor under PCI DSS 4.0, the interactive voice response line, the general ledger, the collections agency file and the customer portal. Once a bill cycle crosses three, reconciliation becomes somebody's monthly job.
How to decide in a week: the three awkward tariffs test
Take your three most awkward tariffs and time three things. First, how long it took the last rate ordinance to appear correctly on a bill, measured from adoption to the first correct statement. Second, how many accounts were manually rebilled in the last twelve months and how many staff hours that consumed. Third, hand those three tariffs to your incumbent vendor and to one developer, and ask each to describe the calculation including proration on a partial period, the order of fees and taxes, and what happens on a rate class change mid cycle.
The answers sort themselves quickly. If nobody asks about proration or the fee and tax order, they have not billed a utility. If your ordinance to correct bill time is measured in months, the rating engine is where your money should go, and no amount of portal work will compensate.
Then pay for a discovery phase rather than accepting a free proposal. At Digital Heroes that produces a signed product requirements document before any code exists: the tariff model with rule versions, the re-rating path, the determinant interfaces, the conversion plan with reconciliation gates, acceptance criteria and a fixed price. You keep that document whether we build it or your package vendor does, and it is the artefact that makes four quotes comparable.
Who we are wrong for: a utility under 80,000 customers looking to replace a full CIS, and anyone wanting a single vendor to own billing and the general ledger together. We work as India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law, you own the repository from the first commit, and you meet the named engineers before signing. More than fifty specialists, over 2,000 projects, checkable 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.
- Large companies globally have captured, on average, only 31% of the expected revenue lift and 25% of the expected cost savings from their digital and AI transformations - a significant gap between expected and realized value. Source: McKinsey & Company (2023) →
- McKinsey found that tech debt can amount to 20-40% of the value of a company's entire technology estate before depreciation, and CIOs report that 10-20% of the budget for new products is diverted to resolving tech-debt issues. Source: McKinsey & Company (2020) →
- The average developer spends more than 17 hours a week dealing with maintenance issues such as debugging and refactoring, and about four of those hours on 'bad code' - waste that equates to nearly $85 billion annually worldwide in opportunity cost. Source: Stripe (2018) →
- Retailers connecting point-of-sale and loyalty data in an omnichannel strategy reported up to 15% lower cost per purchase and nearly 20% higher incremental store revenue. Source: Deloitte (2024) →
Frequently asked questions
How long does a custom rating and determinant service take to build?
Five to eight months for tariff versioning by effective date, the determinant calculations, a re-rating path that can replay a period which already billed, and a regression suite built from real accounts. The single largest schedule risk is not engineering. It is extracting rules that currently exist only in a billing supervisor's memory and in a binder of ordinances, which needs her time booked in advance.
Who owns the tariff rules if we change developers later?
You should own the repository, the cloud accounts and the rules themselves as readable, exportable data rather than compiled logic. Tariffs are public instruments adopted by your council or approved by your commission, and a utility that cannot move its own rate logic to another firm has bought a decade of change orders. At Digital Heroes the client owns the code from the first commit.
What happens if a commission order applies retroactively?
This is the case that decides your architecture. With versioned rules and a replay path, you add the corrected version with its effective date, re-rate the affected period, and produce a reconciliation showing every account that changed and by how much. Without it, the correction is a manual rebill one account at a time, plus whatever refund interest your state prescribes for the delay.
Can we keep our current CIS and build only the rating layer?
Yes, and for most utilities that is the recommendation. The rating service holds the tariffs and computes determinants, then writes billing line items back into the package so statements still print from it and the general ledger never notices. Your customer records, receivables, cash posting and service orders stay where they are. Agree the interface contract early, because that boundary is the whole design.
Should a small municipal utility replace its billing system?
Replacing is usually right when the incumbent is genuinely end of life, but replacing with a custom build almost never is below 80,000 customers. Buy a package sized for municipals, insist on seeing your three worst tariffs modelled during evaluation rather than after signature, and budget conversion honestly. Then, if the rating gaps remain, build only that layer around the package.
What is the difference between a CIS and a billing engine?
The customer information system holds the customer, the premise, the service point, the account, receivables, payments, service orders and collections. The billing engine, or rating service, converts meter reads and other determinants into charges under your tariffs. Vendors sell them as one product, which is why rating gets treated as configuration during evaluation and then consumes the implementation. They are separable, and separating them is the point.
How much does CIS conversion cost, and why is it the biggest line?
Budget 10 to 25 percent of the total and expect the upper end. Conversion is expensive because the difficult objects are not customers and balances. They are deposits with accrued interest, levelised billing plans mid cycle, payment arrangements with instalments remaining, in flight service orders and decades of consumption history. Gaps are found by reconciliation rather than inspection, which is why three mock conversions is the minimum.
Can a build handle net metering and distributed generation properly?
It can, and this is one of the strongest reasons utilities commission a rating service. Export credits with carry forward across months, an annual true up, and a separate treatment for the energy and the delivery components are a distinct calculation problem rather than a variation on a standard rate. Ask any vendor to demonstrate a true up on a real account before you accept that it is supported.
What happens if we disconnect a customer we should not have?
Assume it will be a public matter and design so it cannot happen quietly. Every consumer protection should be a rule object with an effective date and a source citation, and the disconnect candidate list should be a deterministic output that can be explained account by account as a rendered chain of rules. When a council member asks why an account appeared on that list, a database query nobody can interpret is not an answer.
Should we build the customer portal before or after the rating layer?
After. Portals are visible and get funded first, but usage presentment, payment arrangements and high bill explanations all depend on determinants the rating layer produces. Build rating, prove it through a full seasonal cycle including one rate change, then put the portal on top of it. Done in that order the portal is a thin layer. Done first, it becomes a second integration project.
How do I calculate the ROI on a custom ERP?
Add up three lines: hours of manual work removed at loaded labor cost, subscription licenses you cancel, and error costs like mispicks and double entry that disappear. In Digital Heroes delivery experience, mid-market ERP builds typically reach payback in 18 to 30 months, faster when they replace a per-seat platform at 30 or more users. Run the math over five years, because that is where a one-time build beats recurring licenses decisively.
How do we migrate years of data from our old system without losing anything?
Through a staged migration with a parallel run, never a single cutover weekend. The data gets extracted and cleaned early, loaded into the new ERP while the old system stays live, and both run side by side for two to four weeks so your team can verify counts, balances, and open orders match. In Digital Heroes ERP projects, data cleaning consistently takes longer than the technical transfer, so it starts in week one, not at the end.
Is a custom ERP cheaper than NetSuite over five years?
Often yes once you pass roughly 20 to 30 users. NetSuite is commonly quoted at $999 per month for the base platform plus about $99 per user per month, so a 30-user company spends over $200,000 on licenses across five years before paying for implementation. A custom build in the $120,000 to $250,000 range is a one-time cost, and in Digital Heroes projects annual upkeep runs 15 to 20 percent of build cost with no per-seat fees as you hire.
Is SAP overkill for a mid-sized company?
For most companies under about 500 employees, yes. SAP S/4HANA is built for multi-entity, multi-country enterprises with implementations measured in years and seven figures, while SAP Business One, the mid-market product, still forces your processes into its mold. If your competitive edge lives in how you operate, a custom ERP scoped to your actual workflows ships faster and costs a fraction of an SAP program.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
Who can build a custom ERP software system?
Digital Heroes builds custom ERP 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 ERP 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
More from Sophie.
Account Manager · UK Retail & Fashion · London · 4 posts on the site
Published · Last updated .
