Back to solution library
B3

Trigger New Accounts from Connections, Occupancy, or Service Activation

Account Triggers

Overview

What This Option Does

Make new accounts automatic wherever a clear trigger exists. When a user connects to a service, takes over a municipal stall, receives waste collection, begins using a slaughter facility, or activates another service point, that event should immediately create or update the billing account. This turns service growth into revenue without waiting for special clean-up drives.

Most Useful When
  • Service activation already happens through a formal step somewhere in the municipality.

  • New users are often missed because there is a slow or informal handover to billing.

  • Coverage gains from past campaigns fade quickly because new accounts are not created automatically.

Legal requirements

The relevant office needs authority to pass the necessary user details to the billing authority, usually through a standing instruction or simple interdepartmental agreement.

Administrative requirements

Define the trigger list, use a short handover form or digital feed, and review monthly exceptions so the city can see where the trigger is not working.

Usually Not Best First Move
  • Service uptake happens almost entirely informally with no identifiable trigger or no office able to validate it.

Full details

Overview

Make new accounts automatic wherever a clear trigger exists. When a user connects to a service, takes over a municipal stall, receives waste collection, begins using a slaughter facility, or activates another service point, that event should immediately create or update the billing account. This turns service growth into revenue without waiting for special clean-up drives.

Practical implementation path
  • Identify which operational events should automatically trigger account creation, such as a new connection, first occupancy, reactivation, or service start.

  • Embed a short revenue step into that operational workflow so the account is created before the service is fully live.

  • Assign responsibility clearly so neither the service department nor the revenue department assumes the other side has opened the account.

  • Review trigger failures monthly and fix the workflow where new service points are still appearing without a billable account.

Legal and institutional requirements

The relevant office needs authority to pass the necessary user details to the billing authority, usually through a standing instruction or simple interdepartmental agreement.

Administrative Setup

Define the trigger list, use a short handover form or digital feed, and review monthly exceptions so the city can see where the trigger is not working.

When this is a strong fit
  • Service activation already happens through a formal step somewhere in the municipality.

  • New users are often missed because there is a slow or informal handover to billing.

  • Coverage gains from past campaigns fade quickly because new accounts are not created automatically.

When this is less suitable
  • Service uptake happens almost entirely informally with no identifiable trigger or no office able to validate it.

  • There is too little operational capacity to verify additions and keep the newly expanded register accurate after the first push.

Risks And Design Notes
  • Do not create accounts that cannot be matched to a real service point, user, or occupancy event. Weak account creation can produce a second round of billing disputes later.

  • Where households are vulnerable, explain that better coverage is about fair billing and service continuity as much as it is about revenue.