Skip to main content

Collections overview

The collections workflow tracks tenant arrears cases from initial detection through to resolution. Each case provides a structured timeline, health scoring, and integration with notice generation and evidence bundles.

When a case is created​

A collections case is created when rent arrears are detected on a lease. Each case tracks:

  • The associated lease and tenant
  • Outstanding arrears amount
  • Related N4 notice (if issued)
  • Payment intents and arrangements
  • LTB hearing dates and orders
  • Evidence bundle references

Case stages​

Cases progress through 9 sequential stages:

StageDescription
Arrears detectedRent payment is overdue
N4 servedN4 notice served to tenant
Void period14-day period for tenant to pay and void the N4
L1 filedL1 application filed with the LTB
Hearing scheduledLTB hearing date is set
Hearing completeHearing attended, awaiting order
Order issuedLTB order received
Collections referredDebt referred to external collections
ResolvedCase closed

Resolution types​

A case can be resolved as:

  • Paid — Tenant paid the full arrears
  • Evicted — Tenant vacated after LTB order
  • Agreement — Payment arrangement reached and completed
Auto-resolution

Cases are automatically resolved when all associated invoices are paid in full. The collections orchestrator monitors payments and updates case status.

Accessing collections​

Navigate to Collections in the sidebar to see all active cases, listed as a table rather than cards. Columns are: Case (an ID prefix, not the tenant's name), Stage, Arrears, Opened date, and a link to view the case. You can filter by Stage. Tenant name and property aren't shown in this list — open the case to see those. The health score isn't surfaced anywhere in the UI today (it's computed nightly on the backend, but no page displays it yet).

Click a case to view the full detail page with timeline, events, and actions.