Borrower Correspondence: Stop Paying People to Clear False Exceptions

Major exceptions are rarely what drains a mortgage servicing operation. The bigger cost is the thousands of small discrepancies that don’t matter but still need a person to look at them.

A borrower writes in to update their address. Your servicing system says “123 Main Street.” The incoming document says “123 Main St.” A traditional OCR pipeline compares the two strings, finds a mismatch, and raises an exception.

Someone on your operations team then has to:

• open and review the document,
• compare it against the record,
• decide whether the discrepancy actually matters,
• clear the exception, and
• move the workflow forward.

None of those steps calls for real judgment, yet each one takes a skilled person’s time. Repeat that across every piece of borrower correspondence that arrives in a month and you have a large, invisible workload.

Better extraction alone won’t fix it

It’s tempting to treat this as an OCR accuracy problem. But in this example the extraction was correct: the document really does say “St.” The failure comes after extraction. Nothing in the process decided whether the difference was material, so everything defaulted to a human.

Better text recognition won’t fix that. The fix is a process that knows what to do with what it has read:

1. Classify the document so the system knows it’s handling an address change, not a hardship letter or a payoff request.
2. Extract the relevant values with confidence scores, so the process knows how sure it is about each field.
3. Apply rules to the comparison. Standard abbreviations, punctuation, and formatting differences can be treated as equivalent. A different street number, city, or ZIP code can’t.
4. Route only what’s left. If a discrepancy is material, or extraction confidence is low, the item goes to a worklist for a person to review.

Where QBO fits

In QBO, document intelligence is a step in the workflow, not a separate system you have to reconcile with later. AI can classify incoming documents, label them, and extract data with per-field confidence scores. The results land on the document and its case as ordinary QBO data, so your existing rules and workflows can act on them.

From there, the orchestration layer takes over:

• Rules decide. Scoring and rules evaluate the extracted values against the record. You define what counts as material, and every case follows the same definition.
• Exceptions go to the right person. Items that need a human are added to smart worklists and assigned by rule to the right team and priority. When a reviewer clicks “Next”, they get the most important item waiting for them.
• Everything is recorded. The document, the extracted values, the confidence scores, and the decision all stay on the loan, so you can show an auditor why an exception was cleared, not just that it was.

QBO orchestrates the AI, not the other way around. The model reads the document, and your workflow decides what happens next.

Spend human attention where it matters

When false exceptions stop reaching your team, the exception queue goes back to holding what it was meant for: discrepancies that could affect the borrower, the investor, or your compliance position. Reviewers spend their time on judgment calls instead of comparing abbreviations, and managers can see which exceptions are real and how long they take to resolve.

The same approach works beyond address changes. Any correspondence where the document needs to agree with the system of record, such as contact updates, authorizations, or third-party notices, follows the same pattern: classify, extract, compare by rule, and route by exception.

To see how classification, confidence scoring, and exception routing fit into default servicing workflows, read about QBO for mortgage servicing.