Three-way reconciliation for title agencies: the missing queue

A May 2026 Texas consent order against Champion Title Agency LLC is a good example of a problem many title and escrow owners only see at audit time. The order imposed a $25,000 administrative penalty and described three invalid outgoing wires, a dummy file holding unidentifiable money, over-disbursed files in debit balance, and a missing scanned outgoing-wire authorization form. Read together, those are not four separate issues. They are one missing daily exception queue.

That is the practical point of three-way reconciliation for title agencies and escrow companies. The bank balance, the book balance in the general ledger, and the total of individual file balances all have to agree. When they do not, the gap is where fraud, misposting, stale checks, unreimbursed receivables, and missing evidence hide. If you run a title office, the question is not whether you can produce a month-end reconciliation. It is whether you can see the exceptions early enough to fix them before they become an audit finding.

In this context, the wire callback matters too. A verified outgoing wire is not just a security step. It is part of the accounting evidence that should live in the file, because the missing proof and the bad disbursement often fail together.

What three-way reconciliation means

Three-way reconciliation is the process of proving that three records match: the bank statement balance, the book balance in your accounting system, and the sum of all individual file ledgers. If any one of those three differs from the other two, you have a problem to investigate.

For a title agency, that is more than a bookkeeping exercise. The file ledger shows what should have happened on each closing file. The bank shows what actually cleared. The general ledger shows what your business books believe is true. When those do not tie out, the difference can point to a bad wire, a duplicate disbursement, an unposted receipt, a stale check, or a file that was opened to park money you could not identify.

Texas now states the monthly rule plainly in its Minimum Escrow Accounting Procedures. The agency must complete a monthly trial balance by the end of the next month, complete three-way reconciliation within 45 days of the bank statement closing, keep the preparer separate from receipt and disbursement duties, and get manager approval. ALTA Best Practices 4.2 still points owners to a shorter operational standard in its guidance and educational materials: complete reconciliations within ten business days of the statement close. The two statements are not really in conflict. They answer different questions. Texas describes the legal floor. ALTA describes the stronger control expectation many agencies use to stay ahead of problems. The safer operating choice is to run to the shorter cadence and keep the monthly deadline as the outer limit.

ALTA's live Best Practices resources name seven pillars: Licensing, Escrow Trust Accounting, Protecting NPI, Settlement Processes, Policy Production, Insurance Coverage, and Consumer Complaints. The wire and disbursement controls in this article sit mainly in Escrow Trust Accounting and Settlement Processes, not in Protecting NPI. That matters because it keeps the accounting control in the right place.

The exception queue your software should show you every morning

The title software, the bank, and the general ledger each see a different slice of the truth. That is why owners often end up paying a person to reconcile the account. The better artifact is a daily exception queue that lists the items most likely to turn into regulatory findings.

Escrow exception queue by item

• Deposits in transit over three business days - Source system: bank and file ledger. Regulatory concern: money recorded in the books but not actually cleared, which can hide timing problems or missing deposits.
• Outstanding wires over three business days - Source system: bank, wire logs, and file ledger. Regulatory concern: disbursements that should have cleared but did not, or wire activity that was not properly supported.
• Invalid outgoing wires that cleared same-day - Source system: wire log, file ledger, and bank. Regulatory concern: these can distort all three legs of the reconciliation if the wire was not tied correctly to the file.
• Stale payoff and tax checks over ten business days - Source system: bank and file ledger. Regulatory concern: aged disbursements that may need follow-up, stop payment, or reissue.
• Aged outstanding checks approaching dormancy - Source system: bank and file ledger. Regulatory concern: checks that may eventually fall under escheatment or dormant property rules.
• Unidentified funds or unidentified ledger balances - Source system: file ledger and general ledger. Regulatory concern: money parked in a dummy file without a clear owner or disbursement path.
• Negative or debit file balances - Source system: file ledger. Regulatory concern: over-disbursement or unreimbursed shortfalls in a specific file.
• Escrow receivables past 45 days - Source system: general ledger and file ledger. Regulatory concern: amounts owed back to trust that have not been reimbursed within the state deadline.
• Files open three years or more with credit balances - Source system: file ledger and general ledger. Regulatory concern: dormant or abandoned balances that need cleanup, research, or possible escheatment treatment.
• Missing signed outgoing wire authorizations - Source system: file record and scanned document archive. Regulatory concern: the file lacks proof that the wire was approved and verified.

The thresholds above are practical operating thresholds, not universal statutes. Some come from Texas requirements, some from common audit practice, and some from the way regulators describe the risk. The point is to group them in one queue instead of discovering them one at a time during a trust audit.

The Champion Title order is useful because it shows how these failures compound. The order cites invalid outgoing wires that understated the reconciliation, a dummy file holding money that should have been identified, over-disbursed files in debit balance, and a missing signed outgoing wire authorization in the scanned file set. Those are different symptoms of the same problem: no system was assembling the exceptions in one place with the supporting evidence attached.

Why the missing artifact matters more than the month-end report

Most title systems know how to hold file-level ledgers. The bank knows what cleared. QuickBooks or another general ledger knows the book balance. But those systems do not share a common key that makes the exceptions obvious across all three sources, and they usually do not carry the wire callback or signed authorization as part of the accounting record.

That is why a reconciler, whether in-house or outsourced, spends so much time moving between screens and files. They are assembling the queue by hand because the queue is not built into the software.

That missing artifact also explains the recurring owner complaint in operator groups: people ask whether they should reconcile in Qualia or in QuickBooks, or whether the software is enough. The answer is usually no, not by itself. The system can help produce the ingredients, but someone still has to prove that every exception was found, aged, researched, and cleared.

"Qualia reconciliations. For those using Qualia, do you only use Qualia to reconcile your Escrow account or do you do it in QuickBooks as well"

That comment, from a title industry discussion, captures the real issue. The question is not which screen to use. It is which artifact tells you, every morning, whether the trust account is clean.

How the wire callback fits into escrow accounting

Wire fraud is usually discussed as a security problem. In title operations, it is also an accounting control problem. A callback confirms who approved the wire instructions and when. If that proof never makes it into the file, the agency may be able to say the call happened, but it may not be able to show it on demand.

That is why the outgoing wire authorization form and the callback record belong with the file, not only in an email thread or a security policy manual. If the wire was used to disburse trust money, the evidence needs to travel with the transaction. Otherwise the agency may have a cleared wire with no auditable support, which is exactly the kind of gap that shows up in a consent order.

This is also where ALTA Pillar 2 and Pillar 4 matter most. Pillar 2 covers Escrow Trust Accounting. Pillar 4 covers Settlement Processes. The wire callback sits in the control chain for both.

Build versus buy: what the vendors cover, and what they do not

Most vendors in this space have responded to reconciliation pain by selling a service person. That can be the right answer for some agencies, but it is worth being precise about what you are buying.

Buying a managed service makes sense when you have one office, a modest file volume, a reconciler you trust, and no signs of recurring exceptions. It can also be the right choice if you need help getting to a stable process after an acquisition or a turnover event.

Owning the artifact matters more when you have multiple offices, more than one bank account or underwriter relationship, a recent regulator inquiry, or a pattern of aged exceptions that keeps showing up in different forms. In those cases, the agency needs a queue that survives staff changes. The reconciler can still do the work, but the owner should be able to see the state of the trust account at a glance.

That is the distinction Better Software's fintech examples point to in adjacent financial workflows. In loan servicing and investor reporting, the business does not rely only on a monthly spreadsheet; it needs a durable system of record for exceptions and approvals. Title and escrow need the same kind of operating discipline, even if the underlying software stack is different.

What to ask your manager or reconciler on Monday

If you want to know whether your process is real or just month-end theater, ask for these five things:

• A daily exception queue with aging by item type.
• File-level evidence attached to each outgoing wire.
• A list of debit or negative file balances and who owns each one.
• Aged outstanding checks and deposits in transit over the agreed threshold.
• Escrow receivables past 45 days and any open files with credit balances older than three years.

If the answer comes back as a reconciliation report with no evidence trail, you probably have bookkeeping, not control. If the answer is a person who spends a morning stitching together bank activity, file balances, and email confirmations by hand, you have a service process that may work, but you still do not have an owner-level queue.

The practical next step is simple. Choose the shorter reconciliation cadence, build the exception queue around the items most likely to become findings, and make sure the wire callback and signed authorization are filed with the transaction. If a vendor service helps you do that, use it. If it only gives you a cleaner monthly report, it is solving the wrong problem.