For heads of collections, hardship and customer outcomes at Australian lenders who need every hardship notice handled fairly and on time, with the evidence to prove it.
Key takeaways
- In 2024, ASIC reviewed how 10 large home lenders handle financial hardship. More than one in three customers dropped out of the process at least once, and 40% were back in arrears soon after their assistance ended.
- Under the National Credit Code, a hardship notice starts a 21-day clock. Missed notices, collections that keep chasing, and hand-written decision letters are where lenders fall short.
- Agento runs the hardship case workflow on your Salesforce, with income verified through Basiq, the 21-day clock tracked in code, and a hardship officer approving every decision.
- Letters are drafted from the calculator's numbers and checked before they go out. A refusal without reasons is stopped before it is sent.
The gap ASIC found
In May 2024, ASIC published Report 782, its review of how 10 large home lenders support customers in financial hardship. Hardship notices were up 54% year on year, and the findings were blunt:
- 35% of customers dropped out of the hardship process at least once.
- 40% of customers fell back into arrears once their assistance ended.
- In the worst cases, lenders ignored hardship notices altogether.
"In the worst cases, lenders ignored hardship notices." Joe Longo, ASIC Chair, 2024
None of this comes from a shortage of policy. Every lender has a hardship policy. The failures happen in the handoffs: a notice arrives through a channel nobody is watching, collections are not told to stop, and the decision letter is assembled by hand at the end of a long day.
A customer in hardship starts a 21-day legal clock
When a customer tells their lender they cannot meet their repayments, that is a hardship notice under section 72 of the National Credit Code. The lender then has 21 days to respond, and its process has to meet ASIC's expectations in RG 271 on internal dispute resolution, with AFCA as the external escalation path.
That clock starts whether or not anyone has noticed the message. In practice the work breaks down in three places:
- Notices get missed. Customers rarely use the word "hardship". They write "I lost my job" in an app message, a web form, a call or a branch visit.
- Collectors keep chasing. The case is open in one system while collections activity carries on in another.
- Decision letters are written by hand. Amounts are retyped from a spreadsheet, and mandatory content is easy to leave out.
The hardship case workflow, inside the law
That is why we built the hardship case workflow into Agento. It runs on the Salesforce org you already use, with verified income from Basiq, and it is mapped to the National Credit Code s72, ASIC RG 271 and AFCA requirements. Here is how one case runs.
1. A customer writes in
The notice can arrive through the app, a web form, a call note or a branch, in the customer's own words. Agento reads the message and recognises it as a hardship notice, a complaint, or both, even when the customer never uses the word.
2. The notice is registered and the case is opened
Agento registers the notice, opens a hardship case against the right loan in Salesforce and records the date it was received. From that moment the 21-day clock is running, and it is tracked in code rather than in someone's calendar.
3. The loan goes on hold
Collections calls, letters and enforcement activity are paused on the loan. The customer gets an acknowledgement that tells them their request is being reviewed, when they will hear back, and that collection activity has stopped. The acknowledgement is checked before it is sent.
4. Basiq verifies the customer's income
With the customer's consent, Agento pulls verified income and expense data through Basiq. The hardship officer works from the customer's actual financial position rather than an estimate.
5. Every option is modelled in code
Repayment pauses, reduced repayments and term extensions are calculated by a deterministic calculator, not by a language model. Each option shows exactly what the customer would pay and for how long.
6. The hardship officer decides
Nothing goes to the customer until a hardship officer approves it. The officer reviews the options side by side in Salesforce and records the decision, for example a three-month repayment pause.
7. A checked letter is sent
Agento drafts the decision letter with every amount taken straight from the calculator. It checks that all mandatory content is present, including the customer's AFCA rights, before the letter is sent.
A refusal with no reasons? Agento stops it
The law expects a lender that declines a hardship request to explain why and to tell the customer where they can take a complaint. If a refusal letter has no reasons, Agento blocks it before it is sent and routes it back to the officer. The safeguard is part of the workflow, not a reminder in a training manual.
What changes for the hardship team
- Every clock in code. Each notice is timestamped on arrival and its 21-day deadline is visible on the case from day one.
- Loan held from day one. Collections stop as soon as the notice is registered, not when someone remembers to tell them.
- An officer approves every decision. Agento prepares the work; a person makes the call.
- Every letter checked. Amounts come from the calculator and mandatory content is verified before anything reaches the customer.
- Evidence by default. Every step records its inputs, the decision and the output, so the full case history is ready for internal QA, AFCA or ASIC.
How much time this saves depends on your notice volumes, channels and existing Salesforce setup. We scope each rollout against your current process before quoting outcomes.
