Water Utility Billing Software Tools and Selection Guide
Choosing water utility billing software is not just a finance decision. The system controls customer accounts, meter reads, rate tables, penalties, deposits, payment posting, shutoff lists, leak adjustments, service orders, online portals, ACH, IVR, audit trails and public trust. Use this guide to shortlist tools, write better demo scripts, avoid migration surprises and score vendors against real water-department workflows.
Quick Answer: What Good Water Utility Billing Software Must Do
Small water system
Prioritize simple account setup, rate-table flexibility, manual or spreadsheet meter import, ACH, printed bills, owner/tenant handling, leak notes and responsive support. Avoid buying an enterprise suite if one clerk and one meter reader will run the whole cycle.
City or town utility
Prioritize integration with general ledger, cash receipting, permits, work orders, code enforcement, service requests, bank lockbox, eBills, IVR, phone payments, delinquency workflow and annual audit reports.
AMI / smart meter utility
Prioritize import/export reliability, high-read-volume performance, exception management, leak alerts, customer usage portal, billing determinants, synchronization rules and a clean data model for interval consumption.
Selection rule: do not select a product from a feature list alone. Run a scripted demo using your real rates, one high-bill case, one landlord/tenant case, one payment arrangement, one returned payment, one meter changeout, one inactive account and one month-end reconciliation.
Water Utility Billing Software Tools to Shortlist
This is not a sponsored ranking. Treat the tools below as common categories and official starting points. The best product depends on utility size, staffing, integrations, procurement rules, meter technology, security requirements and support expectations.
Tool / vendor |
Best-fit shortlist use |
Official positioning to verify |
Demo questions to ask |
|---|---|---|---|
Municipal utilities that want utility billing tied into a broader public-sector ERP environment. |
Utility billing for metered and non-metered services, including water, gas, electric and one-time charges. |
Show rate setup, payment posting, GL interface, permissions, bill corrections, audit trail and implementation path from our current system. |
|
Water/sewer/refuse utilities that want a cloud CIS and water-utility-focused billing workflow. |
Cloud-based CIS/billing platform for municipalities and utility providers, with water, sewer, refuse and related services. |
Show a complete billing cycle, meter-read import, leak note, customer portal, delinquent workflow and payment integration. |
|
Local governments and authorities that need CIS, billing, collections and payment integrations in one public-sector suite. |
Utility Billing, Collections and CIS with optional tools such as online bill pay, IVR and point-of-sale integration. |
Show collections workflow, IVR posting, point-of-sale balancing, eBilling, service orders and finance integration. |
|
Mid-size to large public agencies that already use or plan to use CentralSquare public administration products. |
Public-sector utility billing, online account access and payment experience; NaviLine/GovAsyst-style suite paths may apply. |
Show integration with finance, citizen portal, payment partners, work orders, conversion from legacy NaviLine or other systems and reporting. |
|
Small towns, villages, rural agencies and special districts that want a cloud utility billing workflow with municipal operations tools. |
Cloud-based utility billing software for daily workflows, billing, account management and municipal operations. |
Show one-person billing cycle, landlord account, shutoff list, meter-reading automation, utility payments and support response process. |
|
Local governments, small utilities and districts that want utility billing with fund accounting/payroll ecosystem options. |
Designed for water, storm water, sewer, electric, gas, garbage, recycling, submeters and combo meters. |
Show tiered rates, sewer based on water use/average periods, ACH, online customer portal, reports and fund accounting link. |
|
Utilities that bill multiple service types and need a focused billing application rather than a full municipal ERP. |
Utility billing for metered services such as water, sewer, electric, cable television, trash and gas. |
Show company/entity handling, meter read import, deposit handling, multi-service bill, payment posting and reporting. |
|
Payment layer for utilities that already have a billing/CIS system but need modern digital bill presentment and payment adoption. |
EBPP platform supporting web, mobile, text, phone/IVR, kiosk, reminders, refunds, reporting and AutoPay/paperless adoption. |
Show integration with current CIS, real-time balance behavior, payment reversals, IVR script, reminders, chargebacks and PCI responsibilities. |
|
Payment layer for utilities needing many customer payment channels, IVR, quick pay, text, email and retail payment options. |
Utility payment platform with web/mobile, live-agent, IVR, in-person/retail, text, email, AutoPay and scheduled payment channels. |
Show customer portal, IVR, text-to-pay, reconciliation file, fees, convenience-fee rules, payment posting and exception handling. |
|
Meter-data layer for water utilities using Neptune AMR/AMI and needing billing-file import/export and consumption visibility. |
Includes customer inquiry, billing services import/export, utility management, AMR/AMI dashboards and meter-reading reports. |
Show billing export, exception report, multiplier rules, read sequence, leak investigation, meter changeout and customer-usage data flow. |
Best shortlist practice: include at least one full municipal ERP option, one water-focused CIS option, one small-utility option and one payment-platform option. Many utilities need both billing software and a payment processor; they are not always the same product.
Selection Matrix: Match the Software to the Utility Type
Utility profile |
Best software pattern |
Must-have features |
Avoid buying |
|---|---|---|---|
Very small water system, 300-1,500 accounts |
Simple cloud utility billing or small local-government billing system. |
Manual reads/imports, tiered rates, minimum charges, deposits, late fees, printed bills, ACH, basic online pay and clean support. |
Heavy ERP suite with complex implementation, expensive integrations and modules staff will not use. |
Town or city, 1,500-15,000 accounts |
CIS/utility billing with finance, cash receipting, service orders and customer portal. |
Rate table history, multiple cycles, service addresses, owner/tenant, work orders, bank draft, IVR, delinquency, audit trail and reports. |
Standalone billing that cannot reconcile to GL or accept payment-channel integrations. |
Regional water/sewer authority |
Scalable CIS with multi-service, multi-cycle, customer portal, payment processor and reporting warehouse. |
Multi-jurisdiction rates, wholesale/retail accounts, landlord/management accounts, high-volume posting, lockbox, call-center notes and API access. |
Desktop-only billing with limited roles, limited exports and manual reconciliation. |
AMI / smart-meter utility |
Billing/CIS plus meter data management or AMI vendor integration. |
Interval reads, leak alerts, estimated read handling, meter changeout, customer usage portal, exception workflow and strong data retention. |
Billing system that only accepts one monthly read and cannot handle interval or exception data cleanly. |
Utility inside a city ERP replacement |
ERP-backed utility billing or billing system with proven finance integration. |
GL posting, cash receipting, budget/fund accounting, payroll/HR separation, audit exports, permissions and month-end close controls. |
Payment portal first, billing core later. Payment convenience cannot fix weak account and rate data. |
Private water company or investor-owned utility |
Utility CIS with regulatory reporting, service territory, deposits, customer history and complaint tracking. |
Tariff/rate versioning, consumer notices, service orders, PUC/PSC complaint records, refund rules and customer communication logs. |
Municipal-only workflows that cannot support regulated utility documentation. |
Must-Have Features for Water Utility Billing Software
Billing engine
- Metered and flat-rate billing.
- Tiered, seasonal and drought rates.
- Water, sewer, trash, stormwater and fees on one bill.
- Minimum charges, caps and surcharges.
- Rate effective dates and history.
Meter reads
- Manual entry and handheld imports.
- AMR/AMI imports and exports.
- Estimated, zero, rollover and negative-use exceptions.
- Meter changeouts and multipliers.
- Read route and sequence management.
Payments
- Online quick pay and registered portal.
- ACH/bank draft and card AutoPay.
- IVR phone payment and counter payment.
- Lockbox, retail and cashiering support.
- Reversals, NSF, chargebacks and refunds.
Customer records
- Owner, tenant and landlord handling.
- Multiple accounts per customer.
- Service address vs mailing address.
- Deposits, refunds and final bills.
- Call notes and contact preferences.
Communication
- E-bills and paperless billing.
- Late notices and shutoff notices.
- Boil-water or outage messages.
- SMS/email alerts and returned-mail tracking.
- Customer portal PDFs and history.
Security and audit
- Role-based permissions and MFA.
- Audit logs for adjustments and write-offs.
- PCI scope and payment tokenization.
- Backups, disaster recovery and retention.
- Vendor SOC report or equivalent controls.
Real Water Billing Workflows the Demo Must Prove
Complete one live-style billing cycle
Import or enter reads, run exceptions, correct two problem accounts, calculate water/sewer/trash/stormwater, preview bills, approve bills, generate PDFs, publish to portal, produce mail file and post receivables.
Process a high-bill complaint
Open customer record, view 12-month use, inspect meter-read history, add customer note, request reread/data log, apply leak-adjustment rule, produce corrected bill and keep audit trail.
Handle late payment and disconnection
Apply penalty, generate late notice, exclude protected accounts, create shutoff list, post field result, accept reconnect payment, remove field order and document the customer conversation.
Start and close service
Create new account, collect deposit, connect meter, produce service order, move tenant out, calculate final bill, apply deposit, refund credit and preserve owner/tenant history.
Reconcile payments and finance
Post card, ACH, cash, check, IVR, lockbox and online payments; handle NSF/reversals; balance cashier drawer; post to GL; produce aging, deposit liability and revenue reports.
RFP Checklist: Requirements to Put in Writing
RFP area |
Ask for this exact evidence |
Why it matters |
|---|---|---|
Rate configuration |
Show water, sewer, stormwater, garbage, base charge, tiered volume, caps, drought surcharge, tax/fee and effective-date setup. |
Weak rate configuration causes manual work and billing errors every month. |
Meter integration |
List supported AMR/AMI/handheld vendors, file formats, API options, exception rules and sample import/export files. |
Meter reads are the billing input. Bad integration creates rework, estimates and customer disputes. |
Payment integration |
Describe portal, quick pay, registered account, IVR, AutoPay, ACH, cards, lockbox, cashiering, refund, NSF and chargeback workflow. |
Payment adoption affects call volume, delinquency, PCI scope and daily reconciliation. |
Customer communications |
Show bill PDFs, email/SMS notices, returned mail, language options, boil-water notices, shutoff notices and customer portal history. |
Communication gaps turn billing issues into public meetings and complaint escalations. |
Accounting integration |
Show GL posting, revenue by fund/object, cash receipts, bank reconciliation, deposit liability, aging and year-end audit reports. |
Finance must trust the billing subledger. |
Security |
Require MFA, role-based permissions, audit logs, encryption, backup/RTO/RPO, incident notification terms and payment-token handling. |
Utility billing data includes customer identity, service location and payment records. |
Migration |
Ask for a field-by-field conversion map, mock conversion, trial bills, parallel billing, historical bill retention and rejected-record report. |
Most failed projects fail in data cleanup, not in the demo. |
Implementation |
Request project plan, named project manager, customer responsibilities, training plan, go-live support and sample acceptance criteria. |
“Included implementation” means little without deliverables and dates. |
Support |
Ask for support hours, emergency support, ticket SLA, user community, release notes, training library and escalation route. |
Billing deadlines cannot wait for vague support queues. |
Total cost |
Require itemized subscription/license, implementation, data conversion, integrations, payment fees, training, travel, support, storage and future-year increases. |
The cheapest first-year quote can become the most expensive five-year system. |
Vendor Demo Script: Make Them Use Your Real Scenarios
Send this before demos: “Please do not give a generic overview. Demonstrate the workflows below using our sample rates, account types, billing cycles, payment rules, meter files and delinquency policy. We will score the demo only on completed workflows, not slide claims.”
Demo scenario |
Vendor must show |
Score note |
|---|---|---|
Tiered water + capped sewer |
Base charge, 3 water tiers, sewer cap, trash fee, late fee and bill preview. |
Reject if staff must manually override common bills. |
AMI import with exceptions |
Import file, missing read, zero read, high read, negative use, meter rollover and exception resolution. |
Ask for sample import/export file after the demo. |
Leak adjustment |
Customer history, 12-month average, repair receipt attachment, adjustment calculation, audit note and revised bill. |
Confirm whether adjustment is reversible and reportable. |
Payment arrangement |
Past-due amount, extension date, notice suppression, broken arrangement and reporting. |
Important for customer service and collections. |
Owner/tenant transfer |
Final bill, deposit application, landlord notification, new tenant, same service address and old account history. |
Common source of bad debt if not handled cleanly. |
Returned payment |
Reverse payment, apply NSF fee, restore balance, notify customer and update delinquency workflow. |
Must not require database support for routine corrections. |
Month-end close |
Payment batch, revenue by service, aging, unapplied payments, deposits, adjustments and GL export. |
Finance should attend this part of the demo. |
Security review |
User roles, MFA, audit log, payment visibility, password controls and support access controls. |
IT should attend this part of the demo. |
Data Migration: The Part Most Utilities Underestimate
Clean before conversion
Standardize names, mailing addresses, service addresses, inactive accounts, meter sizes, routes, account classes, deposits, penalty flags and landlord records before go-live.
Run trial bills
Use at least one full cycle of converted accounts. Compare old-system bills to new-system bills and explain every variance before launch.
Keep history usable
Decide how many years of bills, payments, adjustments, deposits, notes and service orders must be searchable in the new system or archive.
Data object |
Common migration problem |
Fix before go-live |
|---|---|---|
Accounts and customers |
One person appears under many spellings; account holder and service address are mixed. |
Create naming standards and separate customer, account and location records. |
Meters |
Meter size, multiplier, route, read sequence or install date is missing. |
Audit against field inventory and AMI/AMR system. |
Rates |
Old system used hidden manual overrides. |
Document each ordinance/tariff rule and build test cases. |
Deposits |
Deposits stored as notes or balances instead of liability records. |
Reconcile deposit liability to finance before conversion. |
Payment history |
Only summary balances convert, not transaction detail. |
Decide whether to convert history or preserve searchable archive. |
Service orders |
Open work orders disappear or lose assigned staff. |
Export open orders separately and reconcile after go-live. |
Notes and attachments |
Customer complaint history, leak documents and payment promises are not mapped. |
Define which notes convert, which archive and which are purged under retention rules. |
Cybersecurity, PCI and Customer Data Questions
Minimum account controls
- MFA for staff and administrators.
- Role-based access by job duty.
- Separate cashier, billing admin and IT admin rights.
- Audit logs for adjustments, write-offs and rate changes.
- Automatic deactivation for former employees.
Payment security
- Tokenized card storage through payment processor.
- No full card numbers visible to utility staff.
- PCI responsibility matrix.
- Chargeback, refund and reversal controls.
- Daily payment reconciliation reports.
Resilience
- Backup frequency and restore testing.
- RTO and RPO in contract.
- Incident notification timeline.
- Business-continuity plan for billing deadlines.
- Export path if vendor relationship ends.
Security warning: do not treat billing software as “just accounting.” Utility billing systems expose addresses, shutoff status, payment behavior, contact information, service orders and sometimes meter/usage patterns. Ask legal, IT and finance to review the contract before signing.
Integration Checklist: What Must Connect
Integration |
What to verify |
Failure symptom |
|---|---|---|
Meter reading / AMI |
Vendor, file format, import frequency, exception file, meter size/multiplier, route and endpoint mapping. |
Manual imports, wrong multipliers, estimated reads and unreadable exception reports. |
Payment processor |
Real-time balance, convenience fee rules, AutoPay, IVR, text, refunds, chargebacks and batch reconciliation. |
Payments show in portal but not in billing, or staff cannot explain balances. |
General ledger |
Fund/object/account mapping, revenue by service, deposits, penalties, write-offs and cash receipts. |
Finance rebuilds monthly reports in spreadsheets. |
Work orders |
Connect/disconnect, meter changeout, reread, leak check, service request, crew notes and completion posting. |
Billing cannot see what field crews did. |
GIS |
Service address, parcel, meter location, route, pressure zone, district, taxing area and outage boundary. |
Wrong provider/rate/district applied to accounts. |
Customer notifications |
Email/SMS vendor, opt-in, language, templates, bounced messages, paper fallback and emergency notices. |
Customers claim they never received bills or shutoff notices. |
Document management |
Applications, leases, IDs, leak receipts, payment agreements, inspection forms and retention rules. |
Attachments live on staff desktops instead of the account record. |
Pricing and Budget: What to Include Beyond the License
Software
Subscription, license, user count, account count, modules, portal, reporting and annual increases.
Implementation
Project management, configuration, training, testing, go-live support and travel if on-site.
Data
Conversion, cleanup, historical bills, attachments, trial bills, archive access and rejected-record repair.
Payments
Card fees, e-check fees, IVR, text, kiosk, lockbox, convenience-fee model and PCI responsibilities.
Cost line |
Question to ask |
Budget risk |
|---|---|---|
Base subscription/license |
Is price based on users, accounts, meters, modules, services or population? |
Growth can push the utility into a higher tier. |
Implementation |
How many hours are included, and what costs extra? |
Scope gaps become change orders. |
Data conversion |
How many conversion passes and trial bills are included? |
One conversion pass is rarely enough. |
Payment processing |
Who pays card/e-check/IVR fees: utility or customer? |
Convenience-fee rules affect adoption and complaints. |
Integrations |
Is each AMI, GL, lockbox, GIS or payment integration priced separately? |
Integration costs can exceed the billing module price. |
Support |
Is support unlimited, ticket-based, premium, after-hours or emergency-only? |
Billing-day emergencies need fast response. |
Reporting |
Are custom reports included, and can staff build them? |
Custom report dependence slows month-end and audits. |
Exit costs |
What does a full data export cost at termination? |
Vendor lock-in becomes expensive during the next replacement. |
Simple 100-Point Scorecard
Category |
Points |
How to score |
|---|---|---|
Billing and rate flexibility |
20 |
Can it handle all current and planned rates without manual overrides? |
Meter reading / AMI integration |
15 |
Can it import reads, manage exceptions and support future AMI needs? |
Payments and customer portal |
15 |
Does it support quick pay, registered portal, ACH, AutoPay, IVR, eBills and reminders? |
Accounting and reconciliation |
12 |
Does finance trust GL exports, deposits, aging, cash receipts and audit reports? |
Customer service workflows |
10 |
Can staff handle leaks, transfers, notes, arrangements, shutoff lists and complaints quickly? |
Security and audit controls |
10 |
MFA, roles, logs, payment controls, backups and incident terms are clear. |
Implementation and migration |
8 |
Project plan, data conversion, trial bills and go-live support are specific. |
Support and training |
6 |
Support hours, SLA, training materials and escalation are credible. |
Total five-year cost |
4 |
Cost is transparent and defensible, not just lowest first-year quote. |
Decision threshold: if two vendors are close, choose the one that performs better on migration, support and security. Those three areas determine whether staff can bill accurately six months after go-live.
Red Flags Before You Sign
Vendor red flags
- Cannot run your actual rate structure in the demo.
- Uses “custom report” for routine audit questions.
- Cannot explain payment posting and reversals.
- Does not provide sample conversion map.
- Refuses to document implementation responsibilities.
- Vague security answers or no MFA.
- Support SLA is missing from contract.
Utility-side red flags
- No one owns data cleanup.
- Finance is not involved in GL testing.
- Meter team is not involved in import testing.
- Customer service staff do not attend demos.
- Old rates and ordinances are undocumented.
- Historical deposits are unreconciled.
- Go-live is scheduled during peak billing or budget season.
Water Utility Billing Software FAQ
What is water utility billing software?
Water utility billing software is a customer information and billing system used to manage service accounts, meter reads, rate calculations, bills, payments, deposits, penalties, adjustments, shutoff lists, customer notices and reporting for water, sewer and related services.
Is utility billing software the same as a payment portal?
No. Billing software calculates charges and manages customer/account records. A payment portal or EBPP platform helps customers view and pay bills online, by phone, text, kiosk or AutoPay. Some vendors provide both, while others integrate with a separate payment processor.
What features should a small water utility require first?
A small utility should require reliable rate tables, meter-read entry/import, printed and emailed bills, ACH, basic online payment, deposits, final bills, late fees, owner/tenant handling, simple reports, backups, user permissions and responsive support.
What features matter most for cities and towns?
Cities and towns should prioritize utility billing plus general ledger integration, cash receipting, service orders, customer portal, IVR, bank draft, eBills, delinquency notices, payment arrangements, deposits, audit logs, role-based access and month-end reconciliation.
How should a utility compare vendors?
Use a scripted demo with real rates, sample accounts, meter files, payment rules, leak cases, transfers, returned payments, delinquency and month-end reconciliation. Score completed workflows instead of relying on feature checklists or sales slides.
What is CIS in utility billing?
CIS means Customer Information System. In utility billing, it usually refers to the system of record for customers, service addresses, meters, account history, bills, payments, deposits, notices, service orders and customer communications.
Does billing software need AMI integration?
Not every utility needs AMI on day one, but the software should support your meter-reading method and future plans. AMI-heavy utilities need reliable interval-read handling, exception reports, meter changeouts, customer usage views, billing exports and leak/high-use alerts.
What are the biggest implementation risks?
The biggest risks are dirty data, weak rate documentation, incomplete meter inventory, poor GL mapping, unclear payment integrations, limited staff training, no trial billing and a go-live date too close to a major billing cycle or audit deadline.
What security questions should be asked?
Ask about MFA, role-based access, audit logs, encryption, backups, disaster recovery, support access, payment tokenization, PCI scope, incident notification, data ownership, retention, user deactivation and exit-data exports.
Which water utility billing software is best?
There is no universal best product. Small utilities, municipal governments, regional authorities, private water companies and AMI-heavy utilities need different combinations of billing, CIS, finance, payment, meter-reading and customer-service features. The best choice is the system that handles your real workflows with the least manual work and strongest support.
30-Second Buying Checklist
Start with workflows: rates, reads, bills, payments, delinquencies, leaks, transfers, deposits and month-end close.
Shortlist by fit: small-utility tool, water-focused CIS, municipal ERP-backed billing and separate payment platform if needed.
Demo with real data: sample rates, sample accounts, real meter file, real payment rules and real high-bill scenario.
Protect finance: require GL posting, deposit liability, aging, cash receipts, adjustments and audit reports.
Protect customers: portal, quick pay, ACH, AutoPay, eBills, IVR, notices, language needs and contact preferences.
Protect operations: AMR/AMI imports, meter changeouts, service orders, shutoff lists, field notes and leak workflow.
Protect data: MFA, roles, audit logs, backups, PCI controls, incident terms and exit exports.
Protect go-live: clean data, trial bills, parallel testing, staff training and a support plan for the first two billing cycles.
Editorial Team
WaterBillGuide.us
The content on WaterBillGuide.us is researched and prepared by our editorial team. Our writers and researchers review publicly available information from official utility websites and service portals to create clear, step-by-step informational guides.
Water Bill Payment, Leak & Utility Help Toolkit
Use this free helper to find the official water bill portal, avoid unsafe payment pages, handle late bills, troubleshoot high usage, prepare start/stop service documents, and contact the utility office with the right details.
Official Water Bill Portal Finder
Enter your city, state, and utility name. This tool creates safe search shortcuts for the official bill pay portal, customer service page, outage line, and start/stop service page.
Safe Water Bill Payment Checklist
Before paying online, use this checklist to reduce the risk of wrong payment, duplicate payment, missed receipt, or third-party confusion.
Late Bill, Shutoff Notice & Reconnection Action Plan
Select your situation and get practical next steps. This helps users act quickly without guessing.
High Water Bill & Leak Troubleshooter
A high bill can be caused by leaks, irrigation, estimated readings, seasonal use, or account/meter issues. Choose the closest problem below.
Start, Stop or Transfer Water Service Checklist
Moving in or out? Choose your situation and prepare the details most utilities commonly request.
Your preparation checklist
Payment Assistance & Arrangement Finder
If you cannot pay the full water bill, this guide helps you decide what to ask before disconnection or extra fees.
Water Department Call Script Generator
Generate a clear call or email script before contacting the utility billing office.