Days past due is about the invoice. Not the payer.
A customer who is reliably thirty days late is a different problem from one who is late for the first time. Setliva treats them differently, so you collect without burning the relationships you rely on.
A score you can argue with.
Built from the payment record you already hold — median lag against terms, the spread around it, promise-keeping, part-payments, responsiveness and tenure — and shown band by band.
- +10Past dueEV-8801-01
- -17Propensity to settle unaidedEV-8801-02
- +0Contact headroom remainsEV-8801-04
The softest step that will work.
Agency placement takes 25–35% and the relationship rarely survives it, so the ladder favours the softer rung. Above a propensity of 82, a recently-due account is left alone.
Hold and wait
Reliable payers inside their usual lag are left alone. Doing nothing is a first-class outcome.
Email or WhatsApp nudge
On the channel the account actually uses — and only where consent for it is recorded.
Payment plan
Built from the payer’s own part-payment pattern, not a template.
Phone contact
Queued inside local contact windows and under Reg F 7-in-7 caps.
Final notice
The last step before external recovery — always confirmed by a person.
Where the contract is a WhatsApp thread.
Collections software assumes an email address, a signed contract and a days-past-due counter. Across much of the world, terms are agreed verbally, the working channel is WhatsApp, settlement runs over PIX, UPI or M-Pesa, and part-payment is normal rather than a default.
- G-INSOLVENCYInsolvency proceedings
- G-UNAPPLIED-CREDITCredit note covers the balance
- G-DISPUTEDOpen deduction on the invoice
- G-STATUTEBeyond the limitation period
- G-CONTACT-CAPContact frequency cap reached
- G-BELOW-FLOORBelow the pursuit floor
- G-PROMISE-OPENUnexpired promise to pay
Collect without burning good customers.
Open the demo workspace and work a real queue end to end — the evidence, the decision, the representment it produces. No card, no call.