Utility Account Management
Manage the full lifecycle of utility accounts — from creation through service changes, ownership transfers, and closure — handling water, sewer, stormwater, and waste collection service accounts.
Account Lookup
Move-In/Out
Transfer Workflow
Availability
Purpose-Built for Canadian Municipalities
Purpose & Scope
What this module owns
Clear ownership boundaries prevent duplication and ensure every capability has exactly one authoritative home.
Owns
7Delegated to
5Customer identity, golden record
Property address linkage, tax roll cross-reference
Account notifications, move-in/out confirmations
Deposit collection/refund
Move-in/out, transfer workflows
These capabilities are handled by dedicated modules and consumed via stable API contracts — keeping boundaries clean and ownership unambiguous.
Core Capabilities
What it does
3 capability groups comprising 6 discrete capabilities — each with API surface, business rules, and data ownership.
Create utility accounts linked to property addresses with configurable services per account and multi-account support for multi-unit properties.
Property-Linked
Accounts linked to property addresses; cross-referenced with property tax roll number.
Service Configuration
Define services per account: water, sewer, stormwater, waste — each with independent start dates and status.
Multi-Unit Support
Multiple accounts per property for multi-unit buildings; shared/individual meter configurations.
Configurable Numbering
Account numbering scheme configurable per municipality; auto-generated or manually assigned.
Manage contact information, owner vs. tenant designation, agent authorization, and communication preferences.
Owner vs. Tenant
Distinguish owner and tenant accounts; owner ultimately responsible for charges per bylaw.
Agent Authorization
Record authorized agents/representatives who can act on behalf of the account holder.
Communication Preferences
Preferred contact method, e-billing opt-in, language preference for correspondence.
Every module owns a single bounded context, exposes stable APIs, and can be composed into any Civic product — that's the architecture that scales.
Krutik Parikh
Creator of Civic
Data Model
Entity Architecture
3 entities with 4 relationships — the authoritative schema for this bounded context.
Entities
Select an entity to explore its fields and relationships
API Surface
Integration Endpoints
9 RESTful endpoints across 3 resource groups — plus 5 domain events for async integration.
/api/v1/utility/accounts
Create utility account
/api/v1/utility/accounts/{id}
Get account details
/api/v1/utility/accounts
Search accounts (property, customer, address)
/api/v1/utility/accounts/{id}/services
Update account services
Ecosystem
Products that depend on this module
1 Civic products consume Utility Account Management — making it one of the most critical platform services in the ecosystem.
Technical Specifications
Performance, Compliance & Configuration
Account Lookup
Move-In/Out Processing
Transfer Workflow
Account History
Availability
FAQ
Frequently Asked Questions
Ready to Integrate
Build on Utility Account Management
Request an architecture brief, integration guide, or live demo environment for your team.