Request a Demo
Shared Functional

Arrears & Collections

Unified overdue account management across all revenue streams — aging, collection workflows, payment arrangements, agency integration, write-offs, and tax-roll transfer under a single collections workbench.

≤1hr

Aging Calc (Nightly)

Real-time

Stage Automation

≤30min

Agency File Gen

99.9%

Availability

Purpose-Built for Canadian Municipalities

Ontario Compliant
MFIPPA Ready
AODA Accessible
Bilingual Support
Canadian Hosted
SOC 2 Aligned

Purpose & Scope

What this module owns

Clear ownership boundaries prevent duplication and ensure every capability has exactly one authoritative home.

Owns

8

Delegated to

4

Original bill/invoice generation

billing-invoicing

Rate & penalty interest calculation

rate-fee-engine

Payment processing & receipt

payment-engine

Notification delivery (email, SMS, mail)

notification-engine

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 8 discrete capabilities — each with API surface, business rules, and data ownership.

Automatic aging bucket calculation (current, 30, 60, 90, 120+); aging snapshots; configurable bucket boundaries per service type.

Bucket Calculation

Automatic nightly aging across current, 30, 60, 90, and 120+ day buckets for every outstanding account.

Configurable Boundaries

Aging bucket boundaries configurable per service type — property tax may differ from utility or parking.

Aging Snapshots

Point-in-time aging snapshots preserved for month-end reporting and trend analysis.

Configurable multi-stage workflow per service type: friendly reminder → formal notice → demand letter → service restriction → collection agency → legal/tax-sale; automated stage progression based on days overdue.

Multi-Stage Pipeline

Friendly reminder → formal notice → demand letter → service restriction → collection agency → legal/tax-sale.

Automated Progression

Stages advance automatically based on configurable days-overdue thresholds per service type.

Per-Service Configuration

Each service type (tax, utility, parking, court) has its own workflow stages and timing rules.

Template-based demand letters (bilingual); batch generation; registered mail tracking; final notice before agency referral.

Template Engine

Bilingual demand letter templates auto-populated with account details, amounts, and deadlines.

Batch Generation

Generate hundreds of demand letters in a single batch run for efficient mailing operations.

Mail Tracking

Registered mail tracking for proof of delivery; final notice before agency referral documented.

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

4 entities with 5 relationships — the authoritative schema for this bounded context.

Entities

Select an entity to explore its fields and relationships

API Surface

Integration Endpoints

11 RESTful endpoints across 7 resource groups — plus 6 domain events for async integration.

|
GET

/api/v1/collections/accounts

List collection accounts (filter: stage, service, officer, priority)

GET

/api/v1/collections/accounts/{id}

Collection account detail with history

POST

/api/v1/collections/accounts/{id}/advance-stage

Move to next collection stage

Technical Specifications

Performance, Compliance & Configuration

Aging Calculation (Nightly)

Target≤ 1 hour for all accounts

Collection Stage Automation

TargetReal-time trigger on overdue threshold

Agency File Generation

Target≤ 30 minutes

Payment Arrangement Creation

Target≤ 5 seconds

Write-Off Audit Trail

TargetComplete and immutable

Availability

Target99.9%

FAQ

Frequently Asked Questions

Ready to Integrate

Build on Arrears & Collections

Request an architecture brief, integration guide, or live demo environment for your team.