Collection pools
A collection pool is a queue of overdue cases that one team works. Each case sits in exactly one pool. The Collection Pools tab under Settings is where you set the pools up.
Collectors work cases from the pool queue. For the cases themselves, see chasing arrears.
What a pool holds
A pool holds the cases of every customer routed to it. One customer’s cases stay together. They all land in the same pool, with the same collector.
| Column | What it tells you |
|---|---|
| Description | The pool’s name, as collectors see it |
| Team | The group of users who work this pool |
| Allocation mode | How cases reach a collector: AutoAssign or Pull |
| Default | Whether this is the pool that catches unmatched cases |
| Active | Whether the pool can receive new cases |
How cases reach a collector
The allocation mode decides who picks a case up.
| Mode | What happens when a case is routed in |
|---|---|
| AutoAssign | The case goes to the team member with the fewest open cases |
| Pull | The case waits unassigned. A collector claims it |
Open cases are those waiting to be worked or being worked. If an AutoAssign pool has no team members, its cases wait unassigned. A claim is refused if someone else already holds the case.
How a case chooses its pool
Your routing rules choose the pool. The customer’s most overdue case decides. The first rule it matches wins.
If no rule matches, the case goes to the default pool.
An inactive pool is skipped. A rule naming an inactive pool does not match. Routing runs again after each end-of-day ageing run. If the pool changes, all of the customer’s cases move together. The collector stays if they belong to the new pool’s team. Otherwise the new pool’s allocation mode applies.
Statutory default can override the rules. When a customer’s account becomes eligible for a notice, their cases move to the pool named on the regime’s rule, whatever the days overdue say. See statutory default gates.
A worked example
The South African retail template (za-retail, built on the retail-bank package)
sets up these pools and rules. All counts are calendar days past due.
| Pool | Mode | Days past due |
|---|---|---|
| Early arrears | AutoAssign | 1 to 59 |
| Late arrears | AutoAssign | 60 to 119 |
| Pre-legal | AutoAssign | 120 to 179 |
| Legal | Pull | 180 or more |
Early arrears is the default pool. Alex’s most overdue case is 75 days past due. It matches the Late arrears rule, so Alex’s cases go to a member of that team.
At 180 days the same cases move to Legal. No one is assigned. A collector in the legal team claims them.
The template also sets up Tracing, Debt review and Deceased estates as Pull pools.
Adding and editing a pool
- Open Settings and select Collection Pools.
- Select the add button, enter a description, and save.
- Edit the new row to set its team, allocation and whether it is active.
The edit form offers two allocation choices. Cases are assigned automatically means AutoAssign. Collectors claim cases means Pull.
A pool needs a description. The description cannot be empty.
The Default column shows which pool catches unmatched cases. This tab does not change it.
What your organisation configures
- The pools. How many, and what each is called. The list above is one choice.
- The team and allocation mode on each pool.
- The default pool.
- The routing rules that send cases to each pool, by days overdue, amount outstanding and account type.
- Which pool receives statutory notice cases. That is set per regime.
The whole capability switches off per tenant. See switching features on and off.
From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.