How Civic Utility Billing Compares

Purpose-built for Canadian municipal water, sewer, stormwater, and waste billing (5,000–100,000+ accounts) — rate structures, AMI/AMR integration, consumption analytics, and regulatory compliance are native to the platform.

Legacy COBOL-based systems (Harris Utility, Cogsdale) designed decades ago. Modern rate structures require vendor customization at $150+/hour.

General-purpose billing platforms with no municipal-specific features. Utility rate structures, meter integration, and water loss tracking require custom development.

Full source code licence — perpetual software asset your municipality owns and controls. No recurring SaaS subscription. Optional managed hosting and support.

Annual maintenance fees on legacy software. Vendor controls all updates. Source code unavailable. Migration assistance not included.

Per-account or per-transaction SaaS with annual escalation. No source code access. Data migration and exit costs can be significant.

Vendor-agnostic integration supporting Sensus, Neptune, Badger, Itron, and Kamstrup. Hourly interval data for leak detection and time-of-use billing. Configurable import schedules. All included in licence.

Vendor-specific integrations that require professional services to configure. Limited to daily reads. No interval data analysis. Each AMI vendor connector priced separately.

No built-in AMI/AMR support. All meter integrations require custom development or middleware at additional cost and timeline.

Visual rate builder supporting flat, tiered, inclining block, declining block, seasonal, time-of-use, and combined structures. Effective dating with scheduled activation. Rate impact analysis for council. Configurable without code.

Rate changes require vendor involvement (COBOL modifications) at premium rates. Limited rate structure options. No rate impact analysis tools. Changes take weeks to implement.

Basic flat and tiered pricing. Complex municipal rate structures (seasonal, time-of-use, bylaw-specific formulas) require custom development.

AI-powered leak detection with 24-hour alerting. IWA/AWWA non-revenue water tracking. Infrastructure Leakage Index. Consumption benchmarking. Customer alerts. All included in licence.

No consumption analytics beyond basic reporting. Leak detection is manual — discovered when customers complain or at next billing cycle. No NRW tracking methodology.

Third-party analytics add-ons available at additional cost. No municipal-specific leak detection, water loss methodology, or conservation program tools.

Built-in portal with account dashboard, online payment, consumption charts, usage alerts, e-billing, PAD enrollment, service requests, and budget billing management — all AODA-compliant.

No self-service capability. Customers must call or visit for all account inquiries. Some vendors offer basic web view at additional cost.

Basic customer portal. Municipal-specific features (consumption alerts, leak notifications, budget billing) require custom development.

IWA/AWWA water balance methodology, Infrastructure Leakage Index, CARL benchmarking, annual water loss audit generation, and NRW reduction target tracking — all built in.

Water loss tracked in spreadsheets. No IWA/AWWA methodology. No automated audit report generation. Manual calculations prone to errors.

No water loss tracking capabilities. Requires separate analytics tools or manual processes for regulatory NRW reporting.

Device registry, annual testing compliance tracking, certified tester management, non-compliance escalation, and cross-connection control program — all integrated with utility accounts.

Backflow tracking in separate spreadsheets or standalone databases. No integration with billing system. Compliance monitoring is manual.

No backflow prevention features. Requires separate system or manual tracking.

Consumption tracking, water loss reporting, rate sufficiency analysis, full-cost recovery tracking, and MECP report generation — built into the platform as regulatory compliance features.

Compliance data extracted manually from billing runs. Rate sufficiency analysis done in spreadsheets. MECP reports assembled manually.

No Canadian regulatory compliance features. All Safe Drinking Water Act reporting must be built or maintained manually.

All data stored exclusively in Canadian data centres (Ontario + Quebec). Contractually guaranteed. Source code licence enables on-premises deployment for maximum sovereignty.

Data stored locally on municipal servers (aging infrastructure). Cloud-hosted options may not guarantee Canadian residency. Backup and DR capabilities limited.

Canadian region available but not all data and backups guaranteed in-country. Sub-processor access from outside Canada possible.

PCI-DSS compliant hosted payment page. CPA Standard 005 PAD file generation. Counter payment integration. Online, bank, and drop box payments. All included.

Basic payment posting. PCI compliance is the municipality's responsibility. PAD file generation may require manual formatting. No online payment.

Payment processing available via third-party integrations. PCI compliance scope depends on integration model. CPA Standard 005 not natively supported.

Independently deployable services for account management, meter management, billing, payments, analytics, and portal. Scale components independently. Source code for each service.

Monolithic architecture with tightly coupled modules. Updates require full system testing and planned downtime. Scaling limited to vertical.

Modern architecture but designed for generic billing. Municipal-specific services require custom layers and ongoing maintenance.

One-time source code licence with transparent pricing. No per-account fees, per-bill charges, or per-transaction surcharges. Optional managed hosting billed separately.

Complex licensing with per-module, per-user, and per-account charges. Annual maintenance fees. Professional services billed hourly for any changes.

Per-account or per-transaction pricing. Add-ons for analytics, portal, integrations, and reporting can double or triple annual cost.

Under 14 weeks for mid-size municipalities. Pre-configured rate structures, AMI connectors, and billing workflows reduce customization time.

12–24 months for legacy system replacement. Data migration from COBOL systems requires specialized expertise. Training on green-screen interfaces.

6–12 months depending on scope. Municipal-specific rate structures and AMI integrations add significant configuration time.