The reasons give useful detail about the operational setting. Westpac held the Australian credit licence. St George, BankSA and Bank of Melbourne operated under that licence and were trading brands of Westpac. Westpac’s hardship policies described financial hardship as a situation where a customer was willing but unable to meet existing financial obligations for a period of time. The policies listed examples such as unemployment, reduced income, injury or illness, death of a family member, natural disaster, over-commitment or indebtedness and vulnerability. They also recognised extreme hardship, including severe or terminal illness, disablement, long-term unemployment and long-term loss of contract or supplier.
The policies described forms of assistance that might be offered, including loan extensions, short-term reduced payments, short-term moratoriums, interest rate reductions, debt settlement, debt waiver and other contractual rearrangements. During the relevant period, the policies stated that Westpac would respond to a hardship notice where no further information was required within 21 days of receipt. Once assessed, Westpac was to provide a written decision notice and reasons. The policies also said Westpac would not take enforcement action in circumstances where it had or had cause to issue a default notice unless it had given a written decision notice and 14 days had elapsed. The Court said this mirrored s 89A of the Code.
The reasons also note that Westpac’s hardship policies incorporated commitments under the Banking Code of Practice, and that ASIC submitted, and the Court accepted, that each relevant credit contract incorporated the Banking Code of Practice. That did not change the statutory contraventions being determined, but it helps explain the broader compliance setting in which Westpac was operating.
From 2 October 2015, customers could submit hardship notices online through the public websites of Westpac and the other Westpac brands. Westpac intended those notices to be processed first by an automated system called OneClick, then transferred through other automated systems and then to the Customer Assist team. Which system handled the notice depended on the credit product involved. The Court recorded that at least 1,013 online hardship applications submitted by 1,003 customers were either not sent to the Customer Assist team, or were not processed properly, or at all. Westpac failed to give a written decision notice in response to 277 online hardship notices within the statutory timeframe or at all.
This is the part of the case many businesses should focus on. The Court’s declarations did not simply say Westpac missed deadlines. They identified the underlying operational failures. Westpac did not maintain adequate systems, controls and processes to ensure online hardship notices were received by the Customer Assist team and that written decision notices were given within time. Westpac also did not conduct adequate risk reviews, investigations, monitoring and analysis of its online hardship notice systems and processes. In other words, the problem was not just the missed responses. It was the absence of a control environment capable of detecting and preventing the missed responses.
That distinction matters because many businesses still think of compliance as a policy document plus staff training. This case shows that, in a regulated environment, compliance can also be a workflow design issue. If the legal obligation starts when a customer submits a form, then the business needs a process that can prove receipt, routing, ownership, timing and response. If the process breaks, the business may still be liable even if the failure happened inside an automated handoff.