Utility Billing Software: A Buyer's Guide for Small Towns and Special Districts
A vendor-neutral guide to utility billing software for water, sewer and trash service: the features that matter, the accessibility and security rules public bodies face, and what to ask.
Updated October 16, 2026
What utility billing software does
This kind of software turns meter readings and approved rates into bills, then tracks each payment until the account is current. The core jobs:
- Accounts: who is billed, where service is delivered and which services (water, sewer, trash, stormwater) apply.
- Meter reading import: hand entry, handheld readers or files from automatic (AMR) or advanced (AMI) metering systems, with checks for zero, negative or unusually high usage.
- Rate tables: flat charges, a base charge plus usage, tiered rates, minimum bills and sewer charges based on water use.
- Billing cycles: monthly or other cycles, sometimes split into routes, with prorated first and final bills.
- Penalties and notices: late fees, delinquency lists and shutoff notices, applied the way your ordinance says.
- Payments: counter, mail, drop box, bank lockbox files, online payments and autopay.
- Customer portal: residents view bills and history, pay and update contact details.
- Reports: aging, receivables, consumption and the totals your general ledger needs.
Rates, billing cycles and penalties: details to test before you buy
Every rate ordinance has quirks, and the software must apply yours exactly. Bring your current rate sheet to each demo and ask the vendor to bill a few real accounts with it.
- Tiered rates: confirm how tiers are defined and how they are prorated for a partial period.
- Rate history: when the board changes a rate, the old one should be kept with its effective dates so past bills can be explained.
- Sewer and trash: check winter averaging, per-cart charges and unmetered accounts.
- Penalties: late fees, interest and reconnect charges must follow your ordinance and state law, and any waiver should require a written reason.
- Shutoff notices: notice periods and protections, for example for medical needs or extreme weather, vary by state and local rules. The software should record each notice and leave the decision to staff.
- Approval first: a billing run should produce a draft that staff review for exceptions before bills are final.
Payments, lockbox files and the customer portal
Ask how each payment channel reaches the account, and how fast. A payment that reaches the bank but not the account is how good customers get shutoff notices.
- Counter and mail: receipts, cash drawer balancing and batch totals by clerk.
- Lockbox: if a bank processes mailed payments for you, the software must import the bank's file and flag any payment it cannot match.
- Online and autopay: ask who the processor is, who pays the fees and whether card data stays on the processor's hosted page. PCI DSS sets security requirements for organizations that handle payment card data, so get each party's duties in writing.
- Portal: residents should see bills, usage and payment history, choose paperless bills and reach a person. Try it on a phone.
Data migration and accounting integration
A new billing system is mostly a data project. Every account should open on day one with the right balance, rate and meter.
- List what you have: customers, service addresses, meters, reading history, balances, deposits, payment plans and notes.
- Get a full export in an open format such as CSV, and confirm your contract lets you take it.
- Clean up duplicates, closed accounts and bad addresses before conversion, not after.
- Run a trial conversion and compare account counts, balances and deposit totals with the old system's reports.
- Bill at least one cycle in parallel and compare bills account by account before you switch.
- Keep read-only access to the old system, or a full archive, for audits.
The billing system is a subledger. Ask how it posts to your general ledger: summary journal entries, an import file or a direct connection. Water and sewer are often accounted for in separate enterprise funds, so confirm the postings match your chart of accounts and that your auditor can trace a bill to the ledger.
Accessibility is a legal requirement for public bodies
In April 2024 the U.S. Department of Justice adopted a rule under Title II of the ADA that requires the web content and mobile apps of state and local governments to meet WCAG 2.1 Level AA. Special district governments are covered too. An interim final rule published on April 20, 2026 extended the compliance dates:
- Population of 50,000 or more: April 26, 2027.
- Population under 50,000, and every special district government: April 26, 2028.
The rule reaches content a government provides through contractors, and ada.gov names payment systems as an example, so a resident billing portal generally must be accessible even when a vendor runs it. ada.gov's water-bill examples show where the line falls: a PDF bill in a resident's secure account may be excepted, while a bill shown as a web page is not.
Ask vendors for documented accessibility test results for the portal, bills and notices, and a written commitment to fix problems. An automated scan is a useful check, not proof of conformance. The dates have already changed once, so confirm them on ada.gov.
Security, backups and records retention
Billing systems hold personal and bank data. The Top Cyber Actions for Securing Water Systems fact sheet from CISA, EPA and the FBI applies to the billing office too:
- Change default passwords immediately and give each user their own account.
- Turn on multifactor authentication for staff and administrators; CISA recommends it wherever it is available.
- Expose to the internet only what residents need, and ask what the vendor exposes.
- Back up billing data, keep a copy offline or offsite, and practice a restore.
- Keep a written incident response plan, and train staff to spot phishing, including fake requests to change a vendor's bank details.
Small systems can ask for help: CISA offers no-cost vulnerability scanning for water utilities, and EPA lists free cybersecurity assessment resources for drinking water and wastewater systems.
Records retention rules for bills, payments, meter readings and customer files vary by state, and sometimes by record type. Check the local government retention schedule from your state archives or records office, and make sure the software can keep, export and dispose of records on that schedule.
Questions to put in a municipal utility billing software RFP
A request for proposals (RFP) works best when every vendor answers the same specific questions in writing:
- Will you bill ten of our real accounts with our rate sheet during the demo?
- Which meter-reading systems and file formats do you import, and who pays for a new interface?
- What does conversion include, and who reconciles balances after the parallel cycle?
- What WCAG 2.1 AA test results can you show for the portal, bills and notices, and how quickly do you fix issues?
- Are bills, notices and the portal available in Spanish or the other languages our residents read?
- Do staff logins support multifactor authentication, and how quickly can you restore our data?
- Can we export all our data, with history, in open formats at any time and at contract end, at no charge?
- What is the five-year total cost, including conversion, training, payment processing and support?
Red flags when comparing vendors
- A demo that uses only the vendor's sample data and never your rate sheet.
- Rate changes that overwrite the old rate, so past bills cannot be explained.
- No complete data export, or a fee to get your own data back.
- Accessibility claims with no test results behind them.
- Penalties that cannot be set to match your ordinance.
- Shared staff logins, no multifactor authentication or no proven restore.
Where ASL Municipal Utilities fits
ASL Municipal Utilities is designed for small towns and rural water, sewer and sanitation districts with a few hundred to a few thousand accounts, where one clerk bills water, sewer and trash and also runs the rest of the town office.
It is designed to combine meters and readings, the town's own rates (tiers included), billing runs that produce a draft for staff approval, payments and deposits with work orders, a staff roster and an English and Spanish public website. Rates in use are superseded, not overwritten, and all data exports to ordinary spreadsheet files.
Know its limits. It has no late fees, penalties or reconnect charges at all, so a town whose ordinance requires them would need that work scoped. It has no automatic meter-reading device integration; readings are entered or imported. Online card payment needs the utility's own processor account. Its accessibility checks, run on every release, are its own, not a third-party audit. Pricing is quoted after a conversation.
Frequently asked questions
What is utility billing software?
It is software that turns meter readings and a utility's approved rates into bills, records payments and balances, produces notices and sends totals to the general ledger. Small towns and districts use it for water, sewer, trash and sometimes stormwater.
Does the ADA web rule cover a billing portal that a vendor runs for us?
Generally, yes. ada.gov says content and payment systems a government provides through contractors or other arrangements are covered. Ask the vendor for accessibility test results, and ask your attorney about your specific case.
When does a small town or special district have to comply?
After the April 2026 extension, public entities with a population under 50,000 and all special district governments must comply by April 26, 2028; those with 50,000 or more by April 26, 2027. Check ada.gov for any later change.
How long do we have to keep utility billing records?
It depends on your state, and often on the record type. Many states publish retention schedules for local governments through the state archives or a records office. Follow that schedule and your auditor's advice.
What should a municipal utility billing software RFP include?
Your rate sheet and sample accounts, meter-reading formats, conversion steps, general ledger needs, accessibility and language requirements, security questions, data export rights and a five-year total cost.
Related guides
- Prepare a Software or Website Project Brief
- Website Audit Checklist: What to Check and What to Fix First