iCollectPRO is the multi-tenant arrears management platform for municipalities, collection agencies and independent collectors — each on their own isolated tenant, with their own client entities and debt books. From import to legal handover, in one system.
Pick a tenant type to see how the same platform reshapes itself — one entity for a municipality, several for an agency, a single portfolio for a sole collector.
iCollectPRO supports five distinct tenant types on shared infrastructure — with the older managed-service and hybrid models kept migration-compatible underneath.
Runs its own internal collectors against its own ratepayer book. The tenant and the client entity are the same organisation.
Manages debt books on behalf of several client entities under one tenant — each entity's data kept separate within the agency's workspace.
A sole collector or small practice working a single portfolio, registered with a trust account where one is required.
A registered firm coordinating multiple collectors and trust accounts across client mandates, with firm-level reporting.
Enterprise and corporate debt portfolios — the platform's fourth planned category, built on the same isolation model.
Every account, case, payment and document belongs to a debt book, which belongs to a client entity, which belongs to a tenant. A tenant ID supplied by a browser or API client is never, on its own, enough to reach another tenant's data.
Existing import functionality carries over unchanged — debt books are additive structure, not a rebuild of the ingestion pipeline.
The lifecycle is a state machine, not a hard-coded funnel — segments, strategies and exit conditions are set per client, per debt book.
Canonical schema, validation, dedupe, immutable storage.
Ageing buckets and per-client scoring rules.
SMS, email, WhatsApp and call tasks run on strategy.
Promise-to-pay capture and plan negotiation.
SLA-driven escalation triggers before handover.
Structured handoff, disputes side-flow throughout.
Paid, settled, written off, or prescribed / deceased.
Features are configurable per tenant, not per deployment — a superadmin turns capability on or off without a code change.
A normal tenant user cannot reach another tenant's debtors, cases, payments, documents or audit records — the active-tenant context is checked on every request, and an invalid or unassigned tenant returns 403.
Role-based access control and tenant authorization enforced at the platform layer, not left to individual endpoints.
Tenant lifecycle changes, access, and data-subject actions are all recorded for review.
Tenant-level data isolation, retention rules, access logging and data-subject workflows built into the model.
Architecture supports deployment in South Africa and avoids unnecessary cross-border movement of debtor data.
No credentials in source control, no credentials in model defaults, least-privilege access throughout.
Every schema change ships with an upgrade path, a downgrade path where practical, and a regression suite.
Debt review status, prescription, and Section 129/130 notice procedures checked before a collector can act on an account.
Every agent operates inside the same tenant boundary as its human collectors — no agent sees across tenants, and every action is permission-checked like any other user.
Runs the day-to-day collections strategy across an assigned segment.
Tracks promise-to-pay commitments and follows up on missed dates.
Watches SLA timers and triggers escalation before a breach occurs.
Drafts and sequences SMS, WhatsApp and email touches per strategy.
Flags malformed records, duplicate accounts and enrichment gaps.
Surfaces portfolio-level trends and ageing risk to tenant admins.
Answers a collector's questions about a case, in context, on demand.
Tracing, affordability checks and risk scoring lean on the same bureau data your collectors already trust — the Data Services entitlement is built to work alongside these partners.
Consumer and commercial credit bureau data for tracing, risk scoring and account enrichment.
Credit and identity data supporting debtor verification and portfolio risk segmentation.
South African bureau data supporting trace, scoring and affordability checks across debt books.
“We handed over a book of defaulting ratepayers and kept our own dashboard the whole time. Nothing about our data touched another municipality's tenant.” Tenant administrator, reference deployment
“Onboarding a new client entity took an afternoon, not a new environment. The debt book import worked exactly like before.” Collection agency operator, pilot programme
Setup, subscription, usage, per-account, per-seat, AI and communications fees are all billed centrally — never embedded in the collections logic itself.
A single small portfolio, a handful of collectors, the core collections workflow.
Larger portfolios with SLA management, communications and the AI assistant.
Multi-entity portfolios with API access, automation and the full AI agent set.
Negotiated limits and pricing, custom integrations, dedicated support.
