Utility Billing System Conversion and Smart Meters: A 2026 Guide
How to sequence a utility billing system conversion with an AMI smart meter rollout: data conversion, parallel bill testing, exceptions, and cutover.
On this page
- At a glance
- What a utility billing system conversion involves
- Should you convert utility billing before, after, or alongside a smart meter rollout?
- Plan the conversion: who decides what
- Utility billing data conversion: what has to move
- Parallel billing: test rates and bill calculation before customers see them
- Read-to-bill exception handling after cutover
- How to handle the high-bill complaint spike
- Billing cycle cutover checklist
- Staffing a utility billing conversion
- Lessons from recent municipal conversions
- FAQ
- Planning your conversion
A utility billing system conversion goes best when you change one major thing at a time. For most cities, that means stabilizing the new billing system (the CIS) on your current meters first, then rolling out smart meters (AMI) in phases. Run them together only if you have extra staff for the exception queue and a single integration design covering both.
The rest of this guide covers what each piece does, how to choose a sequence, what data has to move, how to test bills before customers see them, and how to get through the first billing cycles without a wave of high-bill complaints. Recent public examples from Billings, Englewood, Banning, Jackson and Toronto show what each decision looks like in practice.
At a glance
Billing first, then meters, is the lower-risk default. Concurrent projects make it harder to tell whether a bad bill came from the meter, the read or the rate.
Converted accounts, premises, service points, meter history, rates, deposits, payment plans, liens and balances should reconcile to the penny before go-live.
Calculate real bills in both systems for at least two cycles (our rule of thumb) and explain every difference.
Plan staff for a surge of estimated, high, low and zero reads right after cutover.
Tell residents before the first new bill arrives that its layout, mailing date and possibly its period length will change.
Keep rate changes and peak season away from the cutover month.
What a utility billing system conversion involves
A utility billing system conversion replaces the software that turns meter reads into bills, payments and account history. When smart meters are part of the plan, the conversion touches several connected systems, and each one has its own vendor, data and failure points.
Swipe to see all columns →
| Component | What it does | Who usually owns it |
|---|---|---|
| CIS / utility billing | Accounts, premises, service orders, rates, bill calculation, collections | Finance or utility billing |
| Meter data management (MDM) | Stores and validates interval and register reads, flags gaps and anomalies | Utility operations or IT |
| Head-end system | Software that talks to the meters and collects reads from the network | AMI vendor, utility IT |
| AMI network | Radios, collectors or cellular endpoints that carry reads from meters | Utility field operations |
| Customer portal | Usage views, leak alerts, online bill pay, paperless enrollment | Customer service |
| GL / ERP integration | Posts revenue, receivables, deposits and refunds to the general ledger by fund | Finance |
| Payments | Lockbox, online, IVR, kiosk and in-person payment posting | Treasury or finance |
Smaller utilities without AMI often skip the MDM and send handheld or drive-by reads straight into the CIS. Once you move to hourly or daily reads, an MDM (or an MDM-like function inside the CIS) becomes the place where reads get validated before billing.
If your city runs Tyler Munis as its ERP, the suite includes a utility billing module, so the choice between billing inside the ERP and buying a standalone CIS deserves a real evaluation. Billing inside the ERP can simplify GL posting and cash receipting. A standalone CIS may offer deeper AMI and portal features. For a market view of the options, see our roundup of utility billing software for municipalities.
Should you convert utility billing before, after, or alongside a smart meter rollout?
For most municipal utilities, converting billing first and rolling out AMI second carries the least risk. Running both at once can work, but only with dedicated staff, a single integration design, and a plan for the exception volume both projects create.
Toronto made this decision in public. A June 30, 2026 report to the Infrastructure and Environment Committee states that staff plan to replace the city’s billing system, in place since 1999, before installing AMI meter transmission units, which are planned to begin field deployment by 2032. The report says this sequencing reduces the risk of implementing two major systems at the same time.
Englewood, Colorado shows the other path. CBS Colorado reported in May 2025 that after Englewood replaced a billing system more than two decades old in summer 2024, bills showed wrong consumption data and arrived late, and meter modernization happening at the same time delayed data collection. The city suspended late fees and shutoffs from fall 2024 into early spring 2025 and fielded thousands of calls over roughly six months.
Portland chose a third route: keep billing steady and phase the meters. Portland’s 2023 council ordinance authorized up to $76 million for AMI and a new customer engagement portal, noted that meters were read manually about once every three months, and described phasing the move to AMI across the city between 2025 and 2030.
Swipe to see all columns →
| Sequence | When it fits | Main advantages | Main risks |
|---|---|---|---|
| Billing first, then AMI | Legacy CIS is fragile or near end of support; meters are still readable | One variable at a time; clean read history in the new CIS before interval data arrives; staff learn the new system on familiar reads | Two projects stretched over more years; AMI benefits arrive later; CIS must be specified for future AMI interfaces |
| AMI first, then billing | CIS is stable and supported; meter failures or manual reads are the bigger pain | Fast relief on read accuracy and leak detection; better read history to convert later | Old CIS may not handle new read volumes; interfaces get built twice; portal features wait |
| Alongside (concurrent) | Both systems are failing, or a single funded program requires it | One cutover for customers; one integration design; shorter total calendar | Bad bills are harder to trace; field crews and billing staff are overloaded at once; exception volume compounds |
As a rule of thumb, we treat “concurrent” as a choice that needs a written reason. If the reason is only “the grant cycle lines up,” that is usually not enough to justify the added exposure.
Plan the conversion: who decides what
A conversion succeeds or fails on decisions made months before go-live. Put these in writing early and get them approved by the people who will answer for the bills.
Form a steering group with finance, utility operations, customer service, IT and the city manager’s office, and name one accountable project owner.
Freeze the rate calendar so no rate change takes effect within one billing cycle before or after cutover.
Pick the go-live month outside your peak season (summer for most water utilities, winter peaks for some electric systems).
Decide whether account numbers stay the same; keeping them reduces payment-posting and customer confusion.
Define what “ready” means: data reconciled, parallel bills explained, exception staffing in place, communications sent.
Write the rollback plan, including which legacy interfaces stay untouched until the new system has billed cleanly.
Budget for backfill so the billing supervisor and lead clerks can work on the project without the daily queue falling behind.
Step 6 matters more than most project plans admit. The City of Banning introduced new utility billing software in November 2024, decided by late December to revert to its legacy system, and found that several related systems had been changed or replaced for the new software. Reconfiguring them took months, and water, sewer and electric bills paused for about six months, with November 2024 consumption billed in April 2025. Moneywise reporting syndicated by Yahoo Finance put the number of affected ratepayers above 11,000.
Council approvals, procurement code requirements and any cooperative contract you plan to use also belong on this plan. Check with neighboring agencies, your state, and associations for existing cooperative contracts for CIS or AMI, and confirm your own procurement rules before relying on one. Government ERP implementations typically run 12 to 24 months, and our ERP implementation timeline guide shows where a utility billing phase fits.
Utility billing data conversion: what has to move
Utility billing data conversion means moving every account, premise, meter and dollar from the old system into the new one, then proving it arrived intact. Treat conversion as a series of rehearsals (mock loads), with reconciliation after each one.
The records to convert, roughly in dependency order:
The read transition is where conversions most often break. When the Billings, Montana metering and billing audit compared the last read in the old system with the first read in the new one, it found that differences and duplicates in read values and dates were the source of the exceptions that overloaded staff. The audit cites 730 meters with a matched date but a mismatched read value, which staff later corrected.
Units of measure deserve their own test. In Jackson, Mississippi, a 2015 report on that city’s meter and billing transition described meters calibrated to gallons instead of cubic feet, a mismatch that could make bills spike about 600 percent. Precision loss is a quieter version of the same problem. In our work with the City of Farmers Branch, the issue was consumption data losing precision in storage, calculation and export, which mattered for showing residents usage down to a single gallon.
Reconciliation checks to run after every mock load:
Account, premise and active meter counts match source, by service type.
Total receivable balance and aging buckets match the legacy trial balance, by fund.
Deposit totals match the deposit liability account in the GL.
Every active meter has a last read, a read date, a unit of measure and a multiplier.
Every active service point has exactly one rate assignment.
A sample of accounts (include commercial, multi-unit, irrigation and inside/outside city) is checked line by line by billing staff.
Parallel billing: test rates and bill calculation before customers see them
Parallel billing means running the same reads through the old and new systems, then explaining every difference before the new bills go out. In our experience, no other test catches as many bad first bills.
Start with rate configuration. Build each rate schedule from the adopted ordinance or resolution, not from the old system’s settings, because legacy systems often carry workarounds nobody documented. Then have someone outside the configuration team check tiers, minimums, fixed charges, proration rules and outside-city multipliers against the source document.
Then run parallel cycles:
Pick at least two full billing cycles (a KCT rule of thumb), including one with a month-end or fiscal year-end if possible.
Load the same reads into both systems.
Compare bill totals account by account, and by charge line.
Set a tolerance (for example, rounding differences of a cent or two) and investigate everything above it.
Classify each difference: conversion error, configuration error, intentional policy change, or legacy error.
Fix, reload and rerun until unexplained differences are zero.
Sign off in writing, with finance and utility billing leadership both approving.
A real comparison shows why. The Billings audit tested consumption charges against rate schedules and found 290,614 charges matched while 4,732 did not, mostly by one or two cents of rounding, for 98.4 percent accuracy on water and wastewater charges. The same audit found that a July 1, 2024 rate change, applied during the system change and during peak summer use, added complexity, and it concluded that the added complexity would have been eased if the utility had delayed implementing the new rates.
Some cities run this with internal staff. When a city needs someone on its side to hold the vendor to the test plan, manage mock loads and sit in the go/no-go meeting, KCT’s ERP implementation service covers data migration with repeated mock loads, parallel runs and cutover, and stays through the first cycles after go-live. At the Town of Little Elm, KCT ran a focused assessment and got a utility billing implementation back on track.
Read-to-bill exception handling after cutover
Read-to-bill exceptions are reads the system holds for review instead of billing automatically: missing reads, estimates, unusually high or low usage, and zero consumption. Expect the volume to jump in the first cycles after go-live, and staff for it in advance.
The Billings audit is direct about the cause of that city’s trouble: an overload of exceptions from a rushed go-live, which delayed bills, changed billing periods and drove up calls. The audit adds that high fall 2024 bills came from seasonal peaks, inaccurately low estimated bills that pushed consumption into the next bill, and the rate change.
Swipe to see all columns →
| Exception type | Common causes after conversion | First action | Owner |
|---|---|---|---|
| No read / estimated read | Missing endpoint ID, radio not mapped, route not loaded | Fix the meter-to-endpoint mapping; field read if not resolved within the cycle | Meter services |
| High usage | Leak, seasonal irrigation, read history converted wrong, unit or multiplier error | Check unit and multiplier first, then history, then dispatch a re-read | Billing analyst |
| Low usage | Stuck or failing meter, wrong dial count, vacancy | Re-read; open meter test or change-out order | Meter services |
| Zero consumption | Vacant premise, meter swap not recorded, endpoint reporting zeros | Confirm occupancy; verify swap date and final read on old meter | Billing analyst |
| Long or short bill period | Read date mismatch at conversion, delayed cycle | Prorate per policy; flag account for customer notice | Billing supervisor |
| Rate or tier mismatch | Wrong rate code converted, proration across a rate change | Correct assignment; rebill; log root cause | Rate/configuration lead |
Two policies prevent repeat damage. First, cap consecutive estimates so the system requires an actual read after a set number of estimated bills. Second, decide how catch-up bills will be handled before you need to. Reporting from WWNO in March 2024 described Jackson customers with balances over $1,000 that included water used in earlier months and never billed, and noted there is no standard for how far back a utility can bill. Rules on back-billing vary by state and by local ordinance, so have your attorney confirm what applies to you.
To size the workload, KCT’s free utility billing exception calculator estimates the annual labor cost of exceptions from your account count, billing frequency, exception rate and minutes per exception. Run it once at your normal exception rate and again at a higher post-cutover rate to see the staffing gap.
How to handle the high-bill complaint spike
High-bill complaints after a conversion often start with bills that look different, arrive late or cover more days than usual, even when the charges are correct. Plan your communication around those changes.
The Billings audit found that bills were incorrect because of human error, not systemic problems, and were corrected, yet the change in billing period length caused a significant trust gap. It also judged that the city’s communications underestimated the challenges of a major billing system shift. In Englewood, the city told CBS Colorado there were no errors in total amounts owed, while customers saw a confusing bill layout and consumption graphs that displayed incorrectly.
A communication plan that holds up (timings are KCT rules of thumb, adjust to your billing cycle):
Sample wording for the bill insert: “Your utility account is moving to a new billing system this month. Your next bill will look different and may cover a few more or fewer days than usual. Charges are based on the same adopted rates. If anything looks wrong, call [number] and we will review it with you before any late fee applies.”
Decide in advance, and get council approval where required, on suspending late fees and shutoffs for the first cycles. Billings nearly doubled the staff handling billing inquiries after thousands of resident calls, which is easier to arrange before the calls start than after.
Billing cycle cutover checklist
Billing cycle cutover is the window when you stop billing in the old system and start in the new one. Cut over at a cycle boundary, with every read and payment accounted for on both sides. The timings below are planning rules of thumb, not fixed standards.
Swipe to see all columns →
| Task | Owner | Timing |
|---|---|---|
| Final mock load reconciled; parallel differences explained and signed off | Project lead, finance | 3 to 4 weeks before |
| Go/no-go meeting with written criteria and decision recorded | Steering group | 1 to 2 weeks before |
| Customer notices sent; call scripts and FAQ ready | Customer service | 2 weeks before |
| Late-fee and shutoff hold approved for the transition | City manager, council if required | 2 weeks before |
| Payment processors, lockbox and online pay notified of cutover dates | Treasury | 2 weeks before |
| Last bill run in legacy system; balances frozen | Billing supervisor | Cutover day minus 1 |
| Final balances and reads extracted and loaded; totals tied to GL | Finance, IT | Cutover day |
| Legacy system set to read-only; interfaces left intact for rollback | IT | Cutover day |
| First read file processed; exception queue reviewed | Billing analysts, meter services | First cycle |
| First bill run sampled by hand before mailing | Billing supervisor | First cycle |
| Revenue, receivables and deposit postings reconciled to GL by fund | Finance | First month-end |
| Daily exception, call and payment-posting report to project lead | Billing supervisor | First 30 days post go-live |
| Rollback decision point reviewed and closed | Steering group | After first full cycle |
Keep the legacy system available in read-only mode through at least your first fiscal year-end and audit, since auditors and customers will ask for history the new system may not hold.
Staffing a utility billing conversion
Staffing is the factor cities most often underestimate. You need people who know your billing rules and people who know the technology, freed from enough daily work to do both the project and the queue.
The Billings audit is unusually candid here. It found the billing area was staffed too lean for the project, that a technology subject matter expert who understood a water utility’s needs was needed from the planning stage, and that with that person the go-live would likely have moved into spring 2025. Its next steps call for documented operating procedures, upskilling and more technology staffing in public works, and tracked performance metrics.
Roles to fill, by name, before kickoff:
Bargaining unit rules may affect overtime, temporary assignments and changes to job duties, so bring HR and labor relations in early.
Lessons from recent municipal conversions
Public conversions from the last few years point to the same handful of decisions. Read the source documents for the cities closest to your size before you set a go-live date.
Swipe to see all columns →
| City | What happened | Lesson |
|---|---|---|
| Billings, MT (2024) | New CIS, July 1 rate change and peak season overlapped; exception overload delayed bills (audit) | Separate rate changes from cutover; staff for exceptions; add a technology SME at planning |
| Englewood, CO (2024 to 2025) | Billing replacement ran alongside meter modernization; wrong consumption display and late bills (CBS Colorado) | Concurrent projects make data gaps harder to trace; test the printed bill, not only the calculation |
| Banning, CA (2024 to 2025) | Software could not produce bills; city reverted to its legacy system (City of Banning) | Keep legacy interfaces intact until the new system has billed cleanly |
| Jackson, MS (2015, still felt in 2024) | Meter replacement and new billing system at once; estimates and missed accounts (Mississippi Free Press, WWNO) | Verify units of measure; set catch-up billing policy before cutover |
| Toronto, ON (2026 plan) | Chose to replace billing before AMI deployment (staff report) | Sequence the two projects to avoid running two major systems at once |
KCT is currently supporting utility billing phases at the City of Oxnard and the City of Richardson, both inside larger ERP programs where Finance and HCM went first. In our experience, utility billing often comes later in a multi-module program because it touches the most residents.
FAQ
How long does a utility billing system conversion take?
A utility billing system conversion usually runs as one phase of a larger ERP or CIS program, and government ERP implementations typically take 12 to 24 months overall. Toronto’s 2026 plan allows about five years from advisor to switchover because it must fit around an AMI program.
Should we install smart meters before replacing our billing system?
Smart meters can go first when your current billing system is stable and supported, because better reads improve the history you convert later. If the billing system is fragile or near end of support, replacing billing first is usually safer, which is the sequence Toronto chose in its June 2026 report.
What is the difference between a CIS and an MDM?
A CIS (customer information system) manages accounts, rates, bills and payments. An MDM (meter data management system) stores and validates meter reads, especially hourly or daily AMI data, before sending billing determinants to the CIS. Smaller utilities without AMI often run without a separate MDM.
Why do bills go up after a new utility billing system?
Bills often rise after a new utility billing system because the first bill covers more days, earlier estimates were too low, or the conversion coincided with a rate change or peak season. The Billings audit traced its fall 2024 high bills mainly to seasonal peaks, low earlier estimates and a rate change.
What is parallel billing in a utility billing conversion?
Parallel billing is running the same meter reads through the old and new billing systems and comparing results account by account. Every difference above a set tolerance gets explained and fixed before go-live, so configuration and conversion errors are caught before residents see a bill.
Can we suspend late fees during a billing system transition?
Many cities suspend late fees and shutoffs during a transition, but the authority depends on your ordinances, rate resolutions and state law, which vary. Englewood and Banning both paused late fees during their transitions. Confirm with your attorney and seek council approval where your code requires it.
Planning your conversion
The conversions that made the news in Billings, Englewood and Banning shared timing problems: a rate change in the same month, meters and billing switching at once, too few people on the exception queue, or no clean way back to the old system.
Decide the sequence first, then protect the calendar around cutover. Your residents will judge the project by the first two bills they receive, so plan those bills as carefully as the configuration.
If you are planning a CIS replacement, an AMI rollout, or both, and want someone on your side managing the vendor and the cutover, KCT’s ERP implementation team can help at any stage. Book a conversation with KCT to talk through your sequence and timeline.