When the problem is now and the collections platform decision is months away

The conversations we’re having with Australian banking collections leaders in 2026 have a pattern to them.

The operational problems are real and pressing. Hardship volumes are elevated. Commercial and SME problem loan portfolios are under genuine stress. Compliance obligations under ASIC's conduct risk framework are active and unforgiving. Workforce reductions are landing on collections floors that are already stretched.

And sitting behind all of it, in multiple institutions simultaneously, is a platform decision that hasn’t yet been made.

The operational collections platform is end of life or approaching it. The vendor is offering an upgrade path nobody wants to rush into, because the history of being an early adopter of the previous version is still fresh. The technology review is underway, or about to start, or waiting for the new CRO/CTO to get through their first 90 days.

So the question becomes: what do you do in the meantime?

The answer isn’t to wait.

The portfolio that can’t wait for the platform decision

Here’s something we see consistently in Australian banking right now. Within every major institution's collections operation, there are portfolios generating disproportionate operational complexity relative to their size.

Acquired portfolios still being integrated. Commercial and SME problem loan books needing case management workflows the retail configured platform wasn’t built for. Secured lending portfolios running on different systems from the unsecured book, managed by teams trying to apply consistent compliance standards across two environments.

These portfolios can’t wait three years for a full platform replacement decision to be made and implemented. They’re generating compliance exposure today. They’re consuming operational resources, too. And in some cases, they’re the portfolios a regulator would examine first if they came looking.

Take the integration challenge as an example, without naming any specific transaction, because the pattern is consistent across multiple institutions. When a bank completes a major acquisition and absorbs a significant loan book, the collections operation inherits customers whose history lives in a different system. Their previous arrangements may not be visible. Their vulnerability flags may not have carried across. Their treatment strategy may have been designed for a different portfolio profile.

Managing these customers well from day one, with the evidence trail the NCCP and ASIC expect, isn’t something that can wait for the technology integration to complete. It requires a collections workflow capable of operating across two data environments coherently, right now, in a way that produces consistent, documented outcomes regardless of where the underlying data lives.

This isn’t a platform replacement conversation. It's a discrete, deployable capability that can be in production in a fraction of the time a full platform migration takes.

The case for starting small and proving fast

Debt Manager isn’t a rip and replace proposition. It’s an execution layer that deploys alongside existing decisioning infrastructure. Along with its own decision engine, it takes the output from whatever analytical capability the organisation already has and converts it into controlled, documented, operational action.

This means it can be deployed against a specific portfolio, or a specific operational problem, without requiring the underlying platform to be replaced first.

We’ve done this with banks globally. An institution mid-acquisition integration uses Debt Manager to manage the acquired portfolio while the broader technology harmonisation continues at its own pace.

A bank with a growing commercial problem loan book deploys Debt Manager to handle the case management complexity its retail configured platform can't support.

An institution navigating a hardship volume surge uses Debt Manager to build the orchestration layer automating timeframe controls and evidencing trail production. All the while, never touching the decisioning infrastructure already in place.

In each case, the deployment is measured in months, not years. The operational improvement is measurable. And the evidence base built during the deployment becomes the business case for the broader transformation, documented in production rather than modelled in a spreadsheet.

This matters in the current environment for three reasons.

First, it closes the compliance gap now. The regulatory obligations don’t pause pending the platform decision. The hardship assessment requirements are active. The evidence trail standard is being applied. Starting with a specific portfolio or operational problem means the most acute exposure is addressed while the strategic decision runs at the pace it deserves.

Second, it de-risks the eventual platform transition. Collections floors run on good workflow discipline. Case management processes work and evidence trails are clean. These migrate faster and with less disruption than operations held together by institutional knowledge and manual workarounds. The deployment work done now becomes a migration asset, not a migration problem.

Third, it gives the new technology review a live reference point rather than a vendor claim. A C&R deployment in a specific portfolio, delivering measurable outcomes in the Australian market, in a comparable regulatory environment, is a different kind of evidence from a reference call with a bank in another country. It’s a proof of concept already running in the organisation's own operation.

What starting small actually looks like

The portfolios that tend to generate the strongest return from a targeted Debt Manager deployment share a few characteristics.

They’re operationally complex relative to their volume. They’re commercial and SME problem loans, acquired portfolios mid-integration, and secured lending books sitting outside the main retail collections workflow.

These are the portfolios where the gap between what the current platform can do and what the regulatory environment requires is widest, and where the cost of managing this gap manually is highest.

They have active compliance exposure. Think hardship obligations that aren’t met consistently and evidence trail requirements that are being reconstructed rather than produced. Vulnerability identification that relies on collectors remembering to check a notes field rather than a structured system field that can’t be missed.

And they have a defined operational problem that’s already costing the organisation something measurable. Whether this is handling time, QA failures, complaint volumes, or the number of hours the compliance team spends reconstructing case histories when questions arrive.

A deployment against a portfolio like this produces three things. An operational improvement that can be measured against the baseline. A compliance posture that can be shown. And a deployment track record in the organisation's own environment that informs the broader technology decision with data rather than projections.

The platform decision matters

None of this is an argument against conducting the full platform review properly. The decision about which collections technology to run for the next decade deserves the diligence it requires.

Choosing under operational pressure, in a compressed timeframe, without examining live deployment experience and total cost of ownership, is how institutions end up in the same position again in five years.

It’s an argument for separating the operational urgency from the strategic decision. They aren't the same timeline. The portfolios generating compliance exposure today can’t wait for the review to conclude. The review can’t be rushed to address the operational pressure without creating different risks.

The organisations handling this well are the ones addressing the operational floor now, running the strategic review at the right pace, and arriving at the platform decision from a position of operational evidence rather than operational crisis.

C&R Software’s Debt Manager is built for exactly this. It’s a proven execution layer, running in production in hundreds of institutions across 62 countries. The debt collection software deploys alongside existing decisioning infrastructure to close the gap between what the platform can do and what the regulatory environment requires. Deployable against a specific portfolio now. Scalable to the full operation when the broader decision is made.

The conversation about where to start doesn’t require the platform decision to have been made. To learn more, reach out to inquiries@crsoftware.com.