A move-in / move-out workflow opens, closes, and transfers utility accounts. See the steps, the edge cases, and how a CIS automates account transitions.
A move-in / move-out workflow is the process a utility uses to open, close, and transfer customer accounts when a resident starts or stops service at an address. Done well, it creates or closes the right account, schedules a meter read and service order, produces an accurate final or first bill, and handles the deposit and any outstanding balance without manual rework. Because every one of those steps lives in the customer information system, the quality of the move-in / move-out workflow is really a question of how well the CIS automates account transitions, or how much of it staff have to do by hand.
Every utility has customers who move. A tenant leaves an apartment, a homeowner sells, a new resident starts service. Each of those events is an account transition, and the utility has to handle it correctly or the next bill is wrong. The move-in / move-out workflow is the defined sequence that turns "someone moved" into a correct account, an accurate bill, and a clean handoff of responsibility from one customer to the next.
It sounds routine, and at low volume it is. The difficulty is that move-in and move-out are not one event but several linked ones happening at a single address, often on overlapping dates, and each one touches billing, the meter, deposits, and the customer record at the same time. A workflow that misses a step produces a final bill sent to the wrong person, a deposit not returned, or a new customer billed for a prior tenant's usage.
A single move-in or move-out is not one action. It reaches across the utility's systems, which is why it belongs in the CIS rather than in a spreadsheet:
When these live in one system, the workflow runs as a sequence. When they live in separate tools, staff re-key the same move across each one, and every re-key is a chance for the bill to be wrong.
What happens to an unpaid balance when the customer who owes it has already moved out?
The routine cases are easy. The workflow earns its value on the edge cases, and there are more of them than most teams expect.
Tenant and owner liability is the first. At a rental, the tenant usually holds the account, but the property owner is often ultimately responsible for an unpaid balance, so a move-out that leaves a debt has to roll that balance to the right party rather than write it off. Accessory dwelling units add a variant of the same problem, where one property has more than one billable unit and the move affects only one of them.
Timing is the second. Move-in and move-out dates overlap, and the meter read has to fall on the right day so the departing customer is not billed for the new resident's water or power. Deposits are a third: the departing customer's deposit may need to be refunded, applied to a final balance, or held, while the new customer's deposit is collected. Getting any of these wrong generates a complaint and, often, a manual correction that costs more staff time than the original transaction.
A reliable workflow follows the same sequence every time, whether a person runs it or the system does. The seven steps are:
Run in order, these steps produce a clean transition. The failures happen when a step is skipped or done out of sequence, most often the meter read or the balance handling.
Move-in and move-out mirror each other but are not identical. Each step has a different action on each side:
Most moves are a move-out and a move-in at the same address on the same date, which is why a utility benefits from running both sides as one linked transition rather than two disconnected tasks.
Does your team key each move once, or re-enter it into billing, work orders, and the meter system separately?
The difference between a painful move-in / move-out process and a smooth one is how much of the sequence the system runs on its own. In a manual process, a staff member opens the account, then separately creates the service order, then remembers to schedule the read, then generates the bill, re-entering the same move into each system. Automation collapses that into one action: entering the move once creates the account, the service order, and the read, and queues the bills.
Self-service extends the same idea to the customer. When a resident can start or stop service through an online portal, the request enters the workflow already structured, without a phone call and a manual data-entry step. Building that capability is covered in the utility self-service portal implementation guide, and move-in / move-out is one of the highest-value transactions to move to self-service because it is common, structured, and otherwise staff-heavy.
A capable customer information system treats move-in / move-out as a single, guided workflow rather than a set of separate screens. Entering a move creates the linked service order and read, prorates the closing and opening bills automatically, and prompts for the deposit and balance decisions rather than leaving them to memory. It handles the tenant-and-owner case so an unpaid balance follows the responsible party, and it supports more than one billable unit at an address.
These are the account-transition capabilities to look for when evaluating a CIS, and they sit alongside the broader billing features covered in the features of CIS billing software. The test is simple: enter one move and count how many screens and manual steps it takes. A purpose-built utility CIS makes it one guided flow; a general or legacy system makes it several disconnected tasks.
Move-in / move-out is one of the few moments a customer actually interacts with the utility, and a bad one leaves a lasting impression. A wrong final bill, a deposit that is not returned, or a first bill that includes a prior tenant's usage all generate a call, a dispute, and a correction. A clean transition, by contrast, is invisible, which is exactly what a customer wants from a utility.
Because these moments are measurable, they belong in the customer-experience metrics a utility tracks, as described in the utility customer experience metrics guide. Island Water Authority reported a 22% improvement in customer satisfaction after moving onto SMART360, which included streamlining the account and service workflows that customers touch directly. Getting the routine transitions right is a large part of how a utility earns a reputation for being easy to deal with.
A move-in / move-out workflow is the defined process a utility uses to open, close, and transfer customer accounts when residents start or stop service. It links account creation or closure, a meter read on the move date, a service order, a prorated final or opening bill, and the handling of deposits and outstanding balances, so responsibility passes cleanly from one customer to the next without billing errors.
The move-date meter read is what splits usage correctly between the departing and arriving customers. Without an accurate read on the right day, the departing customer can be billed for the new resident's consumption, or the new customer inherits usage they did not incur. That produces disputes and manual bill corrections, which is why the read is scheduled as part of the workflow rather than left to the next routine cycle.
At move-out, the workflow settles or transfers any outstanding balance to the party responsible for it. In a rental, the tenant usually holds the account, but the property owner is often ultimately liable, so an unpaid balance may roll to the owner rather than being written off. A capable customer information system routes the balance to the correct party automatically instead of leaving it as a manual decision.
Yes. When a utility offers an online self-service portal, customers can start or stop service without calling in, and the request enters the workflow already structured. Move-in / move-out is one of the best transactions to move to self-service because it is common and repetitive, which reduces call volume and manual data entry while giving customers a faster experience.
A move-in / move-out workflow looks routine, but it is where account records, meter reads, billing, deposits, and balances all have to line up at once, often at a single address on a single date. The utilities that handle it well run it as one linked workflow inside the customer information system, so entering a move once creates the account, the service order, and the read, and prorates the bills, instead of re-keying the same transition across separate tools. The payoff is fewer wrong bills, fewer disputes, and a smoother experience at one of the few moments a customer actually deals with the utility. Getting account transitions right is quiet, unglamorous work, and it is exactly the kind of work a purpose-built CIS exists to make automatic.
Bynry Inc.
8 The Green STE.R,
Dover, Kent,
Delaware 19901
+1 732-630-0285
Bynry Inc.
Serene Tower, Pakharbaug
Pune, Maharashtra 411021
+91 93252-51217
.jpeg)
