Utility Operations · October 3, 2026 · 7 min read
Utility billing modernization: fix the controls before changing the system
A practical review of rates, meter data, customer records, reconciliation, and exception handling before a municipal utility billing migration.
By Altioras Civic
Key takeaways
- Trace a bill from the approved rate and meter reading through payment and ledger posting.
- Test unusual accounts and corrections alongside standard bills.
- Set acceptance conditions for customer balances, billing results, and financial reconciliation.
Follow a bill through the entire process
Utility Billing (UB) and customer information system (CIS) migrations need more than a matching total. A resident reports a surprising bill. Staff can see the amount but cannot quickly explain whether it came from a meter reading, an estimated usage rule, a rate change, or a previous adjustment. That is an operating problem worth examining before selecting replacement software.
Map the process from account setup and meter readings through calculation, billing, payment, adjustments, and financial posting. Include the staff who correct bills and answer customer questions. Their workarounds often reveal requirements that a standard demonstration will miss.
Validate the rate rules and their effective dates
Build a rate inventory from adopted schedules and authorized policies. Record the service, customer class, unit of measurement, fixed charges, usage charges, tiers, minimums, and effective dates that apply. Have the appropriate agency owner approve it before configuration.
EPA's explanation of water bills describes different measurement units and rate structures, including fixed and usage-based components. That variation is a reason to test the utility's own rules rather than rely on a generic billing example.
Create independently checked expected bills for representative accounts. Include changes that cross a rate effective date, partial service periods, meter replacements, estimated readings, and adjustments where those situations apply. The finance and utility teams should agree how to handle rounding and proration.
Clean up account and meter relationships
Separate the customer, service address, account, and meter in the data review. Confirm which identifiers connect them and how the history is retained when someone moves or a meter changes. Look for duplicate accounts, missing service dates, inconsistent units, and unexplained balances.
Review how readings reach billing. Define checks for missing readings, unusual usage, changed meter multipliers, and duplicated imports. Assign the exception queue to a role with enough time and authority to investigate it before bills are released.
Reconcile revenue and preserve approval controls
Connect billing totals to the receivables ledger, cash receipts, adjustments, and the general ledger. Define who prepares each reconciliation, who reviews it, and how unresolved differences are recorded. Use the same definitions in operational and finance reports.
GFOA's guidance on receivables recommends written invoicing and collection procedures, reconciliation controls, and separation of receiving and recording responsibilities, with mitigating controls when staffing is limited.
Apply that principle to credits, refunds, write-offs, and payment reversals. A small team may need a documented independent review instead of a full separation of every task. The agency should approve the arrangement and retain a record of the review.
Sources: GFOA — Receivables and Handling Receipts in the Treasury Office
Test exceptions and the resident experience
Include a move-in, a final bill, a leak adjustment if authorized, a returned payment, a disputed charge, and a payment plan where offered. Verify the customer balance, financial posting, notices, and staff steps for each case.
Review the bill and portal as a resident would. Check whether the service period, usage, rate, prior balance, adjustments, and amount due can be understood. Test accessibility and assisted service arrangements so residents can resolve an issue even when they cannot use the online channel.
Set clear conditions for migration and cutover
Reconcile opening balances by account and in total. Decide which transaction history, meter history, notices, and attachments will move, and how staff will retrieve retained records. Rehearse the conversion and document every unresolved difference.
Where practical, use shadow billing on approved test data to compare old and new calculations for a representative cycle. Do not issue duplicate customer bills or collect twice. Investigate differences before accepting the result.
- Approve rate configuration and expected test results with agency owners.
- Confirm migrated balances and supporting records can be traced.
- Test payments, reversals, and ledger interfaces end to end.
- Plan extra customer support for the first bills issued after launch.
Utility billing migration reconciliation worksheet
Agree on the same cutoff and definition for the legacy reference and target check before comparing results. Investigate differences at the account level rather than accepting a matching net total. Use this blank working aid to assign owners and record dispositions; no row represents completed evidence.
| Control | Legacy reference | Target check | Acceptance record |
|---|---|---|---|
| Customer balances | Approved cutoff extract | Account and total comparison | Difference, owner, disposition |
| Credits and deposits | Separate approved listing | Customer links and balances | Finance sign-off |
| Meter and service links | Active service and meter extract | IDs, serials, units, and dates | Exception log |
| Billing run | Independently approved expected bills | Charges by account and rate | Explained variance |
| Payments and reversals | Receipts and reversal control | Customer and financial postings | Reconciliation reference |
| Open service orders | Outstanding work register | Transferred ownership, status, and billing effect | Operations approval |
EAM and UB: follow a meter exchange across both systems
Initiate a service request and identify the service point and meter asset. Record the old meter’s final reading and new meter’s initial reading with units, multiplier, effective timestamps, and the person authorized to complete the work. Check that the appropriate asset and service records update and that billing follows service chronology and adopted rate rules. Verify financial postings and both histories after the change.
Test a duplicate completion, a rejected update, an offline late entry where supported, and a rollback or correction. Assign the field tool, interface, and API responsibilities in the contract. Tyler describes Enterprise Utilities as billing and customer information software; confirm the exact EAM and UB handoff for the contracted products and interfaces. These scenarios are proposed tests, not a description of an installed integration.
Sources: Tyler Technologies — Enterprise Utilities billing and customer information
UB cutover acceptance checklist
Have agency owners record evidence, open exceptions, and an approval or deferral decision for the contracted scope.
- Approved rate cases and independently expected bills
- Reconciled customer balances, credits, and deposits
- Proven imports, rejection handling, and duplicate prevention
- Payments, reversals, and ledger reconciliation
- Service order and meter exchange history
- First-billing support plan and fallback
Begin with one recent billing cycle
Ask staff to walk through a completed cycle, including the exception report and financial reconciliation. Select several accounts that needed corrections and establish why.
That review gives leadership a grounded choice about data cleanup, configuration, training, integration repairs, or replacement. It also creates specific requirements for any new system.