Every billing cycle, the same problem surfaces: a customer calls to dispute a charge that doesn't match their meter read. Your team pulls up the account, finds a manual entry from three weeks ago, and spends 45 minutes untangling it. Multiply that by dozens of disputes per month, and you're not running a billing operation, you're running a recovery operation.
According to the American Water Works Association (AWWA), US water utilities lose an estimated 15–25% of billed revenue to billing errors, undetected leakage, and uncollected accounts. For most small and mid-sized utilities, the root cause isn't a meter problem. It's the billing software or more precisely, the gap between what that software can do and what your operation actually needs.
This guide gives you a structured framework for evaluating utility billing software: the criteria that matter, the features you cannot compromise on, the pricing models to understand, and the questions that most utilities forget to ask until it's too late.
Utility billing software refers to a platform that manages the full meter-to-cash cycle for water, electric, and gas utilities, from reading meter data and calculating charges, to generating bills, processing payments, and handling exceptions. Purpose-built platforms integrate with AMI systems, customer portals, and financial reporting tools to reduce billing errors and protect revenue.
The definition matters because a lot of software marketed as 'utility billing' handles only one part of that cycle, usually the invoice generation step. A real billing platform owns the entire workflow: AMI/meter data ingestion, rate calculation across multi-rate structures, exception flagging, bill presentment, payment processing, and reporting back to your finance team. If any of those steps still requires a spreadsheet or a manual handoff, your billing software isn't doing its job.
Most utilities evaluate billing software on two dimensions: price and feature list. That's not enough. Here are the seven criteria that determine whether a system actually works for your operation and whether your team will still be using it in five years.
On-premise systems require your IT team to manage servers, patches, and backups. A cloud-native SaaS platform handles infrastructure, security updates, and uptime guarantees, critical for utilities with lean or shared IT resources. Ask vendors: "Where does my data live, and who owns the patch schedule?"
Your billing system must consume interval data from your AMI network without manual exports. Shallow integrations create lag, misreads, and the manual corrections you are trying to eliminate. Ask for a specific list of AMI vendor integrations, Sensus, Itron,Landis+Gyr, and test the data sync in a demo environment.
Water utilities run tiered rates, seasonal rates, inclining block rates, and budget billing programs simultaneously. Electric utilities add time-of-use rates. Your billing engine must handle all of them without custom programming for each rate change.
Billing exceptions, estimated reads, negative consumption, zero consumption, happen in every cycle. The question is whether your software flags, routes, and resolves them automatically, or whether a staff member manually hunts through are port. Automated exception workflows are the single biggest driver of billing accuracy improvement.
Customers expect to pay online, enroll in autopay, and view their usage history without calling your office. Your billing platform must connect to your payment processor and feed your customer portal without a nightly file transfer.
State PUC filings, EPA reporting, and internal audit preparation all draw from billing data. Ask whether the software can generate those reports natively or whether your team compiles them manually from exports.
A billing system that takes 18 months to implement carries real risk, staff turnover, budget overruns, and a long period of running parallel systems. Ask for the vendor's median implementation timeline for utilities of your size, and ask for three references you can call directly.
Use this checklist when comparing vendors. Every item in the left column is a non-negotiable for a utility managing 3,000–100,000 meters. Any vendor that cannot check every box requires a workaround and workarounds become your team's problem, not the vendor's.
Utilities using automated exception management reduce billing errors by up to 50% compared to operations relying on manual reconciliation, a meaningful revenue protection outcome for any utility experiencing revenue leakage.
The pricing model your vendor uses determines more than your monthly invoice, it determines how your costs scale as your utility grows, and whether the software remains affordable if you add a new service territory. There are three primary models in the market.
What to watch for: Most enterprise vendors do not publish pricing. That creates negotiation leverage for large utilities and information asymmetry for small ones. If a vendor quotes you an annual license and cannot give you a per-meter breakdown, ask why. Transparent per-meter pricing, where your cost scales with your service footprint, not with arbitrary license tiers, is the ICP-appropriate model for mid-sized utilities.
Hidden costs to ask about: data migration fees, training fees, custom report development, API access charges, and the cost of adding modules (AMI integration, customer portal) that some vendors sell separately.
A billing platform does not exist in isolation. It is the revenue engine of your operation, and it must exchange data cleanly with every system that touches the billing cycle. Before you sign with any vendor, map your integration requirements against their pre-built connector library.
A platform with 25+ pre-built integrations across these categories eliminates the custom development work that typically adds months to implementation timelines and becomes a maintenance burden on your IT team. Ask vendors for their integration library, not a brochure claim, but a live list of production integrations with reference utilities you can call.
Utility billing systems hold sensitive customer data, account numbers, payment history, usage patterns, and in some cases, personal health information for customers on medical baseline programs. Ransomware attacks on municipal utilities have increased sharply since 2021. The vendor you choose becomes part of your security posture.
Ask every vendor these questions before any commercial discussion:
• What is your SOC 2 Type II certification status and can you provide the report?
• Is data encrypted at rest and in transit (AES-256 minimum)?
• What is your penetration testing schedule, and when was the last test conducted?
• How are role-based access controls configured, can we limit billing adjustment authority to named users?
• What is your data residency policy, where are our customer records hosted geographically?
• What is your recovery time objective (RTO) and recovery point objective (RPO) in the event of an outage?
A cloud-native SaaS platform eliminates the on-premise patch management burden that leaves legacy systems vulnerable between upgrade cycles. For utilities with lean IT teams, often a team of one or two, this shift from maintaining infrastructure to consuming a managed service is one of the most significant operational benefits of modern billing software.
Most utilities spend months evaluating features and pricing, then sign a contract without pinning the vendor to a go-live date. That is how 'implementation' becomes an 18-month project that outlasts the staff who signed the contract.
Implementation timelines vary widely by vendor type:
Island Water Authority went live on SMART360 in 9 weeks, including data migration from their legacy system and staff training. That is not a project timeline exception. It reflects what becomes possible when the platform is designed for utilities of that size, not adapted down from an enterprise product.
When evaluating any vendor, ask for their median implementation timeline for utilities within 20% of your meter count. Then ask for three references from utilities that have gone live in the past 12 months. The gap between what vendors quote and what references report is the most reliable data point in your entire evaluation process.
SMART360 by Bynry is a cloud-native utility operations platform built specifically for small and mid-sized water, electric, and gas utilities in North America. It is not an enterprise product adapted downward, it is built from the ground up for the 3,000–100,000 meter segment that large vendors chronically underserve.
Utility billing software handles the meter-to-cash billing cycle, rate calculation, bill generation, payment processing, and exception management. A Customer Information System (CIS) manages account data, service history, contact information, service orders, and payment history. Modern platforms unify both in a single system, eliminating the data silos that create billing errors when the two systems don't communicate in real time.
Implementation timelines range from 8 weeks (cloud-native, purpose-built platforms for mid-sized utilities) to 18 months (large enterprise systems). The primary variables are data migration complexity, the number of rate structures requiring configuration, and integration depth with your existing AMI and financial systems. Utilities that select a platform with pre-built integrations and standardized data migration tooling consistently go live faster than those requiring custom integration development.
For utilities managing 3,000–100,000 meters, pay-per-meter pricing is typically the more cost-effective model. It eliminates upfront license fees, scales proportionally with your service footprint rather than with staff headcount, and converts a large capital expenditure into a predictable operating cost. Enterprise license models are designed for large utilities with dedicated procurement teams and the negotiating leverage to extract favorable terms, that leverage doesn't exist at mid-market scale.
At minimum, require SOC 2 Type II certification, this confirms the vendor has undergone an independent audit of its security, availability, and data integrity controls over a defined period. Beyond SOC 2,ask about data encryption standards (AES-256), penetration testing cadence, data residency policy, and role-based access control configuration. If a vendor cannot produce a SOC 2 Type II report on request, treat that as a disqualifying response in your evaluation.
