
The utility delinquency and collections workflow, stage by stage: arrears aging, notices, payment plans, penalties, shut-off, and agency handoff.
For US Utilities serving 3,000-100,000 meters and for operations team, billing team and utility managers. For Heads of Billing who own collections accuracy and revenue leakage.
A delinquency management and collections workflow is the defined process a utility follows when a customer does not pay: aging the arrears, sending reminders, offering payment plans, applying penalties, moving eligible accounts to a shut-off list, and, as a last step, handing accounts to a collections agency. The goal is to recover revenue while keeping customers in service and treating them consistently and fairly. A utility billing platform runs this workflow from the same system that holds the bill, so aging, notices, penalties, and the shut-off list are automated rather than tracked by hand. This guide covers the stages of the workflow, how to run it, and where automation replaces manual work.
A complete workflow is more than sending a past-due notice. It covers the full path from a missed payment to recovery:
The reason this belongs in the billing system rather than a spreadsheet is consistency. When the arrears data, the notices, and the shut-off list live in the same place as the bill, every account is treated by the same rules, which the utility bill payment software overview covers from the payment side.
At what day past due does each action happen at your utility, and does it happen automatically?
Each stage of the workflow has a trigger and an action. This table lays out the typical sequence so the process is defined rather than improvised.
The exact days and thresholds are the utility's to set, often shaped by regulation. What matters is that each stage triggers the next action by rule, so no account slips through and none is treated arbitrarily.
Does your team decide who gets shut off, or does the system produce the list by policy?
Running the workflow well is a repeatable sequence:
The step that protects both revenue and customers is the payment plan. A plan that is tracked keeps a customer in service and recovers the balance; a plan tracked on paper is the one that quietly fails.
Shut-off, or disconnection, is the workflow's last resort before recovery, and it carries regulatory and customer-relationship weight. Many jurisdictions restrict when a utility can disconnect, and a well-run workflow treats shut-off as a managed step with exemptions, notice requirements, and reconnection rules, not a switch. The mechanics of managing that step are covered in the planned shut-off workflow guide.
The alternatives matter as much as the disconnection itself. Payment plans, budget billing, and arrears forgiveness programs keep customers in service and often recover more than shut-off does. A workflow that reaches for these before disconnection protects both the customer and the utility's recovery rate.
Do accounts move to an agency cleanly, or does someone rebuild the file by hand?
When an account is uncollectible after the internal workflow, it moves to a collections agency or a write-off. This handoff should be a clean, recorded step: the account, its balance, and its history transfer to the agency, and payments the agency collects flow back to the account. The integration mechanics are covered in the collections agency interface guide.
Done by hand, this handoff is where records get lost and recovered payments fail to post back. Done through the billing system, the account's status stays accurate whether it is being worked internally or by an agency.
The difference between a manual and an automated collections workflow is measured in consistency, staff time, and recovery rate.
The automated column is not only faster; it is fairer. Consistent rules applied to every account is both a recovery advantage and a regulatory one.
A delinquency and collections workflow is a revenue-protection process as much as a customer one. Money that ages without a defined process is money that quietly becomes uncollectible. Running the workflow by rule recovers more of it earlier, which is part of the wider picture in the guide to reducing billing errors and revenue leakage.
Island Water Authority improved customer satisfaction by 22% and cut billing errors by 92% on SMART360, with billing, payments, and the collections process on one platform, because accurate bills and a consistent follow-up process reduce both disputes and write-offs. The workflow works best when the data it runs on is already correct.
A collections workflow is usually more manual than it should be when:
Any one of these means staff judgment is doing what policy and the system should, which costs time and creates inconsistency that regulators and customers both notice.
SMART360 runs the delinquency and collections workflow inside the billing platform, so aging, notices, penalties, payment plans, and the shut-off list all follow the same rules on the same data.
Because the workflow runs on the same platform as billing and payments, an account's status is always current, whichever stage it is in. Island Water Authority ran 10 payment options and its collections process on one platform, and SMART360 is priced per connection for the 3,000 to 100,000 connection range. For evaluating a billing system on this and every other capability, the guide to choosing a utility billing system covers what to look for.
It is the defined process a utility follows when a customer does not pay: aging the arrears, sending staged reminders, offering payment plans, applying penalties by rule, producing a shut-off list of eligible accounts, and handing uncollectible accounts to a collections agency or write-off. The goal is to recover revenue while keeping customers in service and treating every account by the same rules.
The typical stages are: current (bill issued), past due (due date passes, reminder sent), arrears (penalty applied, second notice), pre-shut-off (final notice, payment plan offered), shut-off eligible (added to the disconnection list), and recovery (agency handoff or write-off). The exact days and thresholds are set by the utility and often shaped by regulation, but each stage should trigger the next action by rule.
Automation makes the workflow consistent and faster. Arrears age continuously instead of in a monthly spreadsheet, notices trigger at defined days, penalties apply by rule, payment plans pause and resume collections automatically, and the shut-off list is generated by policy with exemptions. The result is more revenue recovered earlier and every account treated by the same rules, which is both a recovery and a regulatory advantage.
Shut-off should be the managed last resort before recovery, not a default. Many jurisdictions restrict when a utility can disconnect, so the workflow should apply exemptions, notice requirements, and reconnection rules, and reach for alternatives first, such as payment plans, budget billing, and arrears programs. These alternatives keep customers in service and often recover more than disconnection does.
A delinquency management and collections workflow turns unpaid balances from a monthly scramble into a defined process that recovers revenue and keeps customers in service. Age the arrears automatically, send staged notices, apply penalties by rule, track payment plans, and treat shut-off as a managed last resort with alternatives offered first. Run on the same platform as billing and payments, the workflow stays consistent and every account's status stays current. That consistency is also how a utility stops revenue quietly leaking away, covered in the guide to reducing billing errors and revenue leakage. To see how SMART360 runs delinquency and collections inside billing, book a demo.