The lifecycle is a state machine, not a hard-coded funnel — segments, strategies and exit conditions are set per client, per debt book.
Every import runs through a canonical schema, validation and dedupe, with the raw file kept in immutable storage. Existing import functionality is preserved — a debt book is additive structure around the same pipeline, not a replacement of it.
Accounts are grouped into ageing buckets and scored against rules set per client, so a municipality's rates book and an agency's water book can run different strategies from day one.
SMS, email, WhatsApp and call tasks run in an ordered sequence defined by the strategy attached to each segment — not a single blanket reminder to every debtor.
Promise-to-pay commitments are captured against the case, and payment plans are negotiated and tracked from here through to reconciliation.
SLA timers watch each case; a missed promise or a breached SLA target triggers escalation before the account is handed to legal, not after.
A structured handoff packages the case for legal action, with a disputes side-flow running alongside the main path at every stage, not bolted on at the end.
Every case exits as paid, settled, written off, prescribed, or on account of the debtor's death — each a distinct, reportable outcome rather than a single generic “closed” status.
