Loan Collections and Recovery: Turning Arrears into Governed Cases

Why collections is a process problem

In many institutions, collections runs on exported arrears lists. Collectors call down a spreadsheet, record outcomes in notes, and escalate when they judge it necessary. Recovery and write-off decisions are made in meetings and recorded in minutes.

That model has predictable weaknesses:

• Late intervention. Arrears are noticed when a report is run, not when a payment is missed.
• No ownership. A loan can sit on a list without anyone being accountable for it.
• Inconsistency. Two similar accounts are treated differently depending on the collector or branch.
• Weak evidence. The institution struggles to show auditors, regulators or courts what was done, when and why.

Start with the case

The central design choice is to represent each delinquent loan as a collections case: a record with an owner, a status, a history of every contact and arrangement, and a defined workflow. Cases are created automatically when a repayment is missed and routed to collector work queues by product, portfolio, branch or days past due.

A case-based model makes performance visible: how many cases are in each stage, how long they stay there, and which collectors and strategies resolve them.

Define escalation as policy

Escalation — from soft reminders to field visits, demand letters, restructuring or recovery — should follow rules, not individual judgement alone. Thresholds by days past due, exposure, product and risk grade belong in governed, versioned policy. Collectors then spend their judgement on the conversation with the customer, not on deciding which rulebook applies.

Separate recovery and govern write-off

When a loan moves beyond collections, a recovery case takes over: legal action, collateral realisation, settlement or sale. Charge-off and write-off decisions are among the most sensitive in lending and should require explicit approval by the right authority, with the decision and its basis recorded.

Collateral changes the playbook

For asset-backed loans, recovery depends on the condition and location of the asset. Collections and recovery should therefore have access to collateral records, valuations and insurance status, and field visits should be recorded in the same system. This is where asset-finance-specific operations add value.

Connect to servicing and the ledger

Collections only works with accurate, timely repayment data. Cases should be driven from the loan schedule and repayment records — whether those live in a servicing platform or the core — and recoveries and write-offs must post correctly to the general ledger.

What to measure

• Time from missed payment to first contact.
• Cases by stage and age.
• Cure rates by strategy and segment.
• Recovery outcomes and time to resolution.

These measures come from the case data itself — another reason to manage collections as a process rather than a list.

Collections operating model by DPD bucket (example)

Bucket	Typical actions	Owner
1–30 days	Automated reminders, call, payment arrangement	Collections agent
31–60 days	Structured follow-up, guarantor notification where applicable	Senior collector
61–90 days	Field visit, restructure assessment, demand letter	Collections supervisor
90+ days	Transfer to recovery, collateral or legal options	Recovery team
Write-off	Governed approval with recovery evidence	Credit committee / authorised officer

Thresholds and actions vary by product and institution and should be held as governed rules rather than fixed in code.

How WEFI approaches it

WEFI Loan OS manages collections cases with work queues and analytics, recovery cases with governed charge-off approval, and loan schedules and statements that drive them. WEFI Sahara adds collateral-centred recovery for asset finance. See the collections solution or request a demo.