The billing manager at a42,000-meter municipal water system in Michigan spends roughly 11 hours a week on manual billing exceptions, catching meter read errors, correcting misapplied rates, and fielding customer calls about charges that should never have gone out. Her utility's 14-year-old CIS doesn't flag anomalies. It just bills them. According to AWWA, billing inaccuracies are among the top three contributors to non-revenue water losses at US utilities — yet most directors searching for a fix don't know what to look for until they've already bought the wrong software.
This guide is for the Utility Director or General Manager who has decided it's time to replace their legacy billing platform and now needs to evaluate the options honestly. It covers what utility billing software should actually do, the eight features that separate functional platforms from expensive liabilities, how to assess vendors against criteria that matter for a system your size, and what the transition really looks like.
Utility billing software is defined as a platform that automates the full meter-to-cash billing cycle for water, electric, or gas utilities, from reading ingestion and rate application through invoice generation, exception management, payment processing, and regulatory reporting. For utilities managing 3,000 to 100,000 meters, the right platform replaces manual CIS workflows and reduces billing errors by catching anomalies before invoices are issued.
That definition sounds straightforward. The complication is that billing software in the utility sector spans a wide range, from standalone billing modules with no integration to unified platforms that connect billing to CIS, meter data management, customer portal, and work orders. The right question is not "does this software bill customers?", every platform does that. The right question is: "does it catch what our current system misses, and does it connect to everything our operation depends on?"
When evaluating utility billing software, look for these eight capabilities in every platform you shortlist. If a vendor cannot demonstrate all eight with a live workflow, not a slide deck, then that is a red flag.
Your rates are not simple flat charges. The platform must handle inclining block rates, time-of-use rates, budget billing, seasonal adjustments, and demand charges without manual workarounds. Confirm it handles your state's specific regulatory rate structures.
If you are running or planning smart meters (Sensus, Itron, Landis+Gyr), the billing platform must ingest interval data natively. Platforms with 25+ pre-built integrations, including major AMI vendors, eliminate the custom API cost that adds months to implementation.
This is the feature most legacy systems lack and the one with the highest ROI. Platforms with automated exception flagging, catching high-consumption anomalies, zero reads, and estimated bills before they go out, reduce billing errors and protect revenue. SMART360's exception management delivers up to 50% improvement in billing accuracy for utilities that migrate from manual CIS.
Customers expect to view their bill, pay online, set up autopay, and submit service requests without calling your office. A built-in portal reduces inbound call volume by 60% in utilities that migrate from phone-based service to digital-first customer management.
The platform must support multiple payment methods, ACH, credit card, IVR, in-person kiosk, without requiring your team to reconcile multiple systems manually. Verify PCI compliance is native.
Annual and quarterly reporting to state PUCs, EPA Safe Drinking Water Act compliance documentation, and audit trails for rate case proceedings require structured data. Billing software that doesn't generate regulatory reports forces manual data extraction, a compliance risk and a staff burden.
Billing disputes require documented proof. Every rate change, bill adjustment, payment application, and override must be timestamped, attributed, and reportable. If your current system doesn't have this, your exposure in a rate case or customer dispute is significant.
Your billing platform will need to connect to your GIS, ERP, and payment systems. Evaluate whether integration is through pre-built connectors or custom development, custom development means cost, time, and ongoing maintenance liability.
Most utility software evaluations fail for the same reason: the team evaluates features without evaluating fit. A platform built for a 2-million-meter investor-owned utility is architecturally and commercially wrong for a 40,000-meter municipal water system. Use these six evaluation criteria to separate genuinely suitable platforms from enterprise software your team will be fighting for years.
Ask every vendor directly: what is your smallest live utility customer? Enterprise platforms rarely have customers under 200,000 meters. If the software isn't designed for your system size, the pricing, support model, and implementation process will all reflect that mismatch.
Industry average for CIS replacement is 12–18months. Cloud-native platforms built for mid-sized utilities implement in 12–24 weeks. Ask for a written implementation schedule with milestone accountability, not a verbal estimate.
See Section 4 on pricing models. Ask specifically: what are the per-meter rates, what modules are included, what triggers additional charges, and what does year-3 cost look like? Vendors who resist this question are not your partners.
If you have or are planning an AMI deployment, the billing platform's AMI integration is not optional. Ask whether integration is pre-built (included in base pricing) or custom. Custom AMI integration can add $50,000–$150,000 and 6+ months to an implementation.
Cloud-native SaaS platforms require no on-premise infrastructure, no servers, no database administration, no manual patching. For utilities with a lean IT team (or no dedicated IT team), this is a requirement. Ask: where does the software run, and who manages uptime?
Your customer accounts, billing history, and meter records are mission-critical. Ask every vendor for their data migration methodology, who owns the migration work, and what the rollback plan is if data integrity issues emerge post-migration.
A per-meter pricing model refers to a fee structure where the utility pays a set monthly rate based on the total number of active meters in their system, regardless of how many staff members access the platform. This model is the most financially predictable for small and mid-sized utilities because the cost scales directly with the size of the system being managed.
Compare the three dominant pricing models before committing to any platform:
For a utility running 30,000 meters, per-meter pricing is typically the most cost-transparent model available. The full cost is visible upfront and scales only if your system grows. Annual license models frequently carry hidden costs, module unlocks, user seat fees, support tier upgrades, that make the 5-year TCO significantly higher than the headline figure suggests.
Enterprise utility software, the platforms built for major investor-owned utilities and large municipal systems, is not the wrong technology. It is the wrong technology for a utility managing 3,000 to 100,000 meters. The implementation models, pricing structures, and support expectations of enterprise vendors assume a large IT department, a multi-year implementation budget, and dedicated system administrators. Most municipal and rural water utilities have none of these.
The consequence is a market gap that has persisted for decades: small and mid-sized utilities either bought oversized enterprise platforms they couldn't fully implement, or they stayed on aging on-premise CIS software long past its useful life. The risk of the second option compounds annually: older systems accumulate security vulnerabilities, lose vendor support, and increasingly fail to meet state regulatory reporting requirements.
SMART360 is purpose-built for this underserved segment, utilities managing between 3,000 and 100,000 meters that need full-platform capability (billing, CIS, MDM, customer portal, workorders, asset management, analytics) without the enterprise cost structure. The pay-per-meter pricing model means a 20,000-meter utility pays for a 20,000-meter system, not for a license priced for a utility ten times its size. The platform's approximately 50% reduction in operational expenditure reflects the elimination of manual processes, IT maintenance costs, and billing error remediation that currently consume staff time at utilities on legacy systems.
Implementation fear is the number one reason utility directors delay replacing a system they know is broken. The fear is not irrational, a botched CIS migration can disrupt billing operations for months, damage customer trust, and create regulatory reporting gaps. The fear is, however, specific to how older enterprise implementations were executed. It does not describe what modern cloud-native implementations look like.
A structured cloud implementation for a mid-sized utility follows a defined sequence: data extraction and validation, configuration to your rate structures and workflows, parallel testing, staff training, and cutover. With a purpose-built platform and a vendor that owns the migration process, this sequence takes 12–24 weeks, not 12–18 months.
Island Water Authority implemented SMART360 and went fully live in 9 weeks. Their migration covered full customer account data, billing history, and AMI integration, with no billing cycle disruptions during the transition.
When assessing implementation risk with any vendor, ask for three things:
• A written implementation plan with named milestones and accountability for each phase
• A reference from a utility your size that implemented the platform in the last 24 months
• A data migration methodology document explaining how your customer records, billing history, and meter data are extracted, validated, and loaded
Vendors who cannot provide all three should not be on your shortlist.
For small and mid-sized water utilities managing 3,000 to 100,000 meters, the best utility billing software is a cloud-native SaaS platform with per-meter pricing, built-in AMI integration, and a sub-12-week implementation model. SMART360 by Bynry is purpose-built for this segment, it includes billing, CIS, customer portal, and MDM in a single platform without enterprise pricing or IT infrastructure requirements.
Utility billing software pricing depends on the model: per-meter plans typically run a fixed monthly rate scaled to your active meter count; per-user plans charge per staff seat; annual license models carry a fixed annual fee with variable add-on costs. For utilities under 100,000 meters, per-meter pricing is the most cost-predictable model. Always ask for a 5-year TCO estimate that includes implementation, data migration, training, and any module unlock fees.
Enterprise CIS implementations historically take 12–18 months. Modern cloud-native platforms purpose-built for small and mid-sized utilities implement in 12–24 weeks. SMART360's implementation timeline is 12–24 weeks for utilities up to 100,000 meters, including data migration and staff training. Island Water Authority went fully live in 8 weeks. The difference is architectural: cloud platforms require noon-premise server setup, no database configuration, and no custom middleware.
The eight essential features for utility billing software are: multi-rate and tiered billing engine, AMI/AMR integration, automated exception management and anomaly detection, customer self-service portal, payment gateway integration with PCI compliance, regulatory reporting automation, full audit trail with bill correction workflow, and API integration flexibility for GIS and ERP connectivity. A platform missing any of these will require manual workarounds that increase staff burden and billing error risk.
