Exception management in mortgage processing: where settlement risk concentrates

The lending industry has spent the better part of a decade making the standard loan faster. Property settlement is electronic, mortgage documents are e-signed, and data now moves between systems that once required the same details to be entered three times. For a file that fits the template, a residential purchase with clean title, a straightforward structure and no surprises, the process works, and it works well.

That progress deserves credit. It also changes where attention should go next. Losses rarely originate on the standard path. When a settlement is delayed, a security position proves weaker than expected or a borrower’s settlement date moves, the cause is usually a file that has fallen outside the standard process.

The underinvestment in exception management

Ask me where the industry underinvests in mortgage processing and my answer is exception management. The mortgage industry tends to invest heavily in improving the standard, straightforward mortgage settlement process, but not enough in managing the exceptions; that is, the files that don’t follow the normal path. If you improve that workflow, the benefit is obvious and quantifiable. For example, if you reduce processing time by one day, that improvement can be measured across thousands of loans.

Files that fall outside the standard process can be more difficult to justify investing in, as any particular title issue, structuring query or settlement complexity may only affect a small proportion of matters each year. Collectively, however, these exceptions are an ongoing feature of every loan portfolio and often account for a disproportionate share of operational, legal and compliance risk. A lender’s greatest exposure frequently arises in the files that require specialised handling, regardless of whether that need was identified and addressed.

Legal expertise earns its place in mortgage origination by recognising early that a file needs a different approach, and by giving everyone involved a framework for managing the risk without holding up settlement any longer than the issue requires. Recognition without a framework produces escalations that stall files. A framework applied too late produces well-managed problems that should have been identified weeks earlier.

Why mortgage processing exceptions exist

Exceptions are often described as failures of process or documentation. However, in my experience, they rarely are. Mortgage processing was never a one-size-fits-all exercise, because lending never was, and the market continues to move towards greater variety. Brokers now write 81% of new residential home loans, a record the MFAA attributes to borrowers navigating an increasingly complex lending environment. Every file carries its own particulars. The borrowing structure might involve a trust or a company rather than individuals. The lending arrangement might layer securities and guarantees in ways a standard workflow was never built to assess. The title might carry a dealing no one expected. The settlement itself might involve more parties, more consents or more sequencing than the template allows for.

These are ordinary features of property and lending transactions, and no amount of process design can eliminate them entirely. Technology has delivered measurable improvements in efficiency, consistency and scalability, and its value should not be understated. What technology cannot do, however, is exercise legal judgment when a matter becomes complex or presents an atypical risk. A system can route a file, identify missing documents and enforce a checklist, but it cannot assess whether a lender’s security position has been compromised by a circumstance that falls outside the scenarios the checklist was designed to address.

The objective should not be to eliminate exceptions altogether, but to build processes that anticipate exceptions and ensure they are escalated and managed appropriately when they arise.

When a non-standard file is forced through a standard process

Push a file that needs different handling through the standard process and one of two things usually happens.

Sometimes the process simply cannot see the risk. The file passes through the standard process and settles without issue, but the underlying risk only becomes apparent later, when it is far more difficult and costly to address.

More often, the file stalls because it requires a decision rather than a process. The matter circulates between teams, each recognising the issue but none clearly responsible for resolving it. As days pass, pressure builds and settlement dates become harder to maintain.

Both scenarios typically surface near settlement, when deadlines are fixed and multiple parties are relying on the transaction proceeding as planned. The longer an exception remains unidentified, the fewer solutions remain available and the greater the consequences become.

A caveat on title, discovered before settlement

A matter I see versions of regularly shows how this unfolds. A file is progressing towards settlement. Nothing about it has suggested it needs special handling. Then a title search reveals a caveat that was lodged in connection with some other dealing, that no one anticipated when the transaction began.

From that moment the file has left the standard process, whether anyone has acknowledged it or not. There’s now uncertainty about whether the lender’s security position will be affected, and about what has to happen before settlement can proceed. Those are legal questions, and they need answers quickly, because the settlement date hasn’t moved to accommodate them.

What happens next depends almost entirely on how the processing operation is structured. Where legal review sits outside the process, as a checkpoint or an external referral, the file usually stops while the matter is referred for advice. Advice takes time, options take longer, and each step depends on the completion of the last. While that runs, the operational side of the file sits idle and the parties wait.

Where legal and operational capability sit together, the same matter runs in parallel. The legal team assesses the caveat, forms a view on the security position and advises on the options, whether that means seeking a withdrawal, negotiating with the caveator or adjusting the settlement arrangements. At the same time, the operations team manages communications with the parties and keeps every other element of the transaction progressing, so that once the path forward is agreed, the file is ready to settle.

The complication is identical in both scenarios, but the time can differ significantly. In the first, the file loses the time the advice takes, plus the time it takes to restart everything around it. In the second, the legal question is resolved while the transaction keeps moving. On many files, that difference determines whether a mortgage settlement is delayed or completed on time.

Why legal and operations must work side by side

That example points to a principle I’d apply across the industry. Exception management belongs to neither legal nor operations on its own; it requires both, and each is limited without the other.

Operations drives the transaction forward, coordinates the stakeholders, tracks  milestones and keeps the file moving, which is exactly what a file under pressure requires. Without legal support, operations is left to choose between making assumptions or stopping progress, and neither outcome benefits the lender.

Legal supplies the judgment. It identifies the issue, assesses the risk and frames the options. Advice on its own doesn’t settle a loan, though. An opinion that arrives without anyone coordinating the parties, managing the timeline and executing the chosen option does not move the file forward.

Put the two side by side, working the same file at the same time, and issues are identified and resolved while the transaction continues to progress. Much of the industry’s default architecture still separates them, with legal positioned as a gate the file passes through near the end. I’d argue the gate model was only ever tolerable because the loan book used to be simpler than it is now.

What investing in exception management would mean

If exception management is the underinvested area, it’s fair to ask what investment would look like in practice. I’d point to three things.

Early identification comes first

Most of the cost of an exception comes from discovering it late, so the single highest-value change any operation can make is moving the discovery point forward, building the capacity to recognise at the start of a file’s life that it will need a different approach.

A framework matters as much as headcount

Operations that handle exceptions well don’t treat each one as a novel crisis. They have a considered way of assessing risk, a known set of options for the common complications and a clear view of who decides what. That’s what allows an exception to be managed without stalling the file around it.

The third piece is structural

Legal and operational capability have to be able to work the same file at the same time. However an organisation achieves that, the test is simple. When a complication surfaces, does the transaction keep progressing while the question is resolved, or does it wait?

There’s a timing argument for doing this now

As lending continues to digitise and volumes move through increasingly automated processes, the standard path will continue to get faster, and the gap between how the standard file and the exceptional file are handled will continue to widen. Automation raises the stakes on the controls that sit behind it, a point we’ve made before in the context of embedding legal expertise from the application stage rather than the end of the process. Digitisation won’t create more exceptions, but an industry organised around the automated path can become progressively worse at noticing the files that fall outside it.

The role is finding the path through

Everyone in lending has encountered a certain version of legal involvement. The file goes to legal, and legal says no. Legal names the risk, flags the problem and returns the file, leaving operations to determine how the transaction can proceed.

I don’t want the solicitors on my team working that way, and I’d suggest that version of legal input is part of why legal rigour attracts so little investment. If it only ever means slower files and flagged problems, the incentive to minimise it is obvious. The value of legal expertise in an exception lies in finding the practical path that lets the transaction proceed while the risk is properly managed. The advice worth paying for moves past “this is a problem, you can’t do it” to “here are the options for how to make it work”.

That’s also the measure I’d hold the industry to. Any operation can settle the file that fits. The real test of a mortgage settlement is what happens to the file that doesn’t.

---

Natasha Paige is Head of Legal at Lextech, a national law firm and technology partner for Australia’s banking and financial industry. The firm provides mortgage settlement and fulfilment services to lenders and banks nationally. Lextech’s practical guide to modern mortgage processing, Settlement Without Friction, includes a short self-assessment for lenders on where their own process stands, including how it handles the files that fall outside it.

Download the guide.

Article Posted 10 August 2026 3:35 am