One shortage, one licence
Ask an escrow officer what actually keeps them up before a state examination, and the honest answer is rarely the closing itself — closings are the part of the job that's rehearsed weekly. What actually costs sleep is the trust account behind every closing: hundreds of open files, each with its own running balance, all sharing the same bank account, and a regulator whose only real question is whether every one of those balances still adds up to the bank's own number.
Under RESPA and the trust accounting rules most states layer on top of it, an escrow or title agency doesn't get to treat its trust account as one pool of money. Every open file has its own ledger, and the sum of every file's ledger has to equal both the agency's own book balance and the bank's statement balance — a three-way tie, checked on a recurring cycle, not an annual formality. A trust account that can't prove that tie isn't a bookkeeping inconvenience; it's the single finding most likely to put a title licence at risk.
This page describes how the documents behind that reconciliation — escrow bank statements, closing statements, wire confirmations — are read and organized by file into one traceable workbook, not to replace the escrow officer's own judgment on how a specific shortage gets resolved, but to remove the manual re-keying step where a file's ledger most often quietly drifts from what the bank actually shows.
Where escrow accounts actually break
Trust account shortages are almost never theft. Regulators who examine title agencies for a living will say the same thing: the overwhelming majority of findings trace back to ordinary clerical drift in a manual process, repeated across hundreds of files a year until the errors add up to something real. A handful of patterns show up again and again.
A disbursement posted to the wrong file
Two files closing the same week, similar dollar amounts, and a wire confirmation gets keyed against the wrong file number — leaving one file overstated and another understated by the same amount, invisible on the bank total.
A deposit that clears the bank before the file is opened in the books
Earnest money hits the bank account days before the corresponding file is set up in the trust ledger system, so the bank balance is briefly ahead of the book balance with no obvious explanation.
A stale file that never got closed out
A cancelled transaction leaves a small balance sitting in a file's ledger indefinitely, because nobody circled back to disburse or escheat the remaining funds once the deal fell through.
A bank fee or interest credit that never gets allocated
The bank charges an account-level fee or pays interest on the pooled trust account, and it sits unallocated in the book balance instead of being assigned to a specific file or an operating account transfer.
A wire confirmation read at the wrong amount
A transposed digit on a hand-keyed wire amount — $186,000 entered as $168,000 — throws off one file's balance by exactly the kind of round, plausible-looking gap that's easy to miss on a quick review.
None of these need a dramatic explanation — they're the ordinary cost of hand-keying figures from PDF bank statements and wire confirmations into a ledger system, file after file, closing after closing. Reading every source document the same way, with every figure traceable back to it, closes most of this gap simply by removing the re-keying step where drift creeps in.
Why this isn't a simple bank reconciliation
A one-account bank reconciliation — matching a bank statement to a single checkbook register — is a task most bookkeeping software already does well. An escrow trust reconciliation is a different shape of problem: one bank statement covering the whole account has to be split correctly across every open file that touched it that month, and each of those files' own ledgers has to independently sum back to the same bank total.
Multiply that splitting task across a busy month — dozens of closings, each generating a deposit, one or more disbursements, and sometimes a refund or a correction — and what looks like an afternoon's reconciliation on a handful of transactions becomes a recurring exercise that's easy to fall behind on, right up until an underwriter's auditor asks for a specific file's support and the answer takes longer to find than it should.
What a three-way reconciliation actually proves
A three-way trust reconciliation checks that three independently-derived numbers agree: the bank's own statement balance for the trust account, the agency's book balance for that same account, and the sum of every individual open file's ledger balance. When all three match, the account is proven clean — not because nothing could possibly be wrong, but because a shortage or a misallocation large enough to matter would almost certainly break at least one of the three ties.
The bank balance and the book balance are usually close to automatic — most agencies already reconcile those two against each other monthly. What actually takes the time, and what most manual processes struggle to keep current, is the third leg: proving that every individual file's ledger, added together, produces the exact same total.
The documents a file's balance depends on
| Document | What it contributes to a file's ledger |
|---|---|
| Escrow trust account bank statement | Every deposit, disbursement, fee and running balance the bank actually recorded |
| Closing / settlement statement | The full breakdown of a file's incoming and outgoing funds at the moment of closing |
| Wire confirmation | Amount, sender/recipient and date for a specific incoming or outgoing wire |
| Earnest money deposit receipt | The initial deposit that opens most files' trust ledger balance |
| Disbursement ledger or check register | Every outgoing payment issued from the account, itemized by payee and file |
Every one of these documents typically exists as its own PDF, generated by a different system or a different party to the closing — the underwriter's title system, the wiring bank's confirmation, a lender's closing disclosure. Reading each one the same way, and tagging every figure to the file it belongs to, is the actual document work behind a reconciliation that ties.
What gets read
Amounts, dates, file numbers, payer and payee names, and running balances are extracted from each document exactly as printed. A figure that can't be read with confidence — a stamped-over total, a smudged fax, a handwritten correction — is flagged rather than filled in with a best guess, so a reviewer's time goes to the handful of lines that genuinely need a second look.
How it works
Upload the month's escrow bank statement and closing statements
For the account and the period the reconciliation needs to cover — however many files that involves.
Each document is read on its own
Amounts, dates, file references and running balances extracted from each document's own layout.
Transactions organized by file
Every deposit and disbursement tagged to the file it belongs to, ready to sum against each file's own ledger.
Gaps and mismatches flagged, not guessed
A transaction with an unclear file reference, or a total that doesn't foot to the bank statement, is marked for review.
Exported
Excel, CSV or JSON, with every figure traceable back to the document it came from.
A month of files, reconciled
A three-branch title agency uploads a month's escrow trust account bank statement alongside the closing statements for every file that transacted that month, ahead of its internal monthly reconciliation.
| Result | Count |
|---|---|
| Bank statement lines processed | 412 |
| Closing statements processed | 87 |
| Files with a clean three-way tie | 84 of 87 |
| Flagged for a file-reference confirmation | 9 transactions |
The three files that didn't tie on the first pass turn out to share one root cause — a disbursement wire confirmation whose file number was one digit off from the closing statement it actually belonged to — caught and corrected the same afternoon, rather than surfacing weeks later during an underwriter's sample audit.
Shortages, overages and unclaimed funds
A genuine shortage — money that should be in the trust account but isn't — is a serious finding that usually triggers a specific notification and correction process under your state's trust accounting rules. An overage is less alarming but still needs resolving: often it's a file that closed with a small surplus never disbursed, or a bank interest credit never allocated to a file or swept to the operating account as your agreement with the bank allows.
Unclaimed funds — a file with a lingering small balance and no clear owner still reachable — fall under state escheatment rules that vary by jurisdiction and typically require a defined dormancy period and a diligent search before funds are remitted to the state. None of these are document- reading decisions; what a clean, file-level reconciliation does is surface exactly which files carry an unresolved balance clearly enough that your compliance process can act on the list, instead of discovering it during an exam.
Manual vs. automatic
| Manual | Automatic |
|---|---|
| Bank statement lines re-keyed against a file list by hand | Every document read and organized automatically |
| A misfiled wire found only when an auditor samples a file | An unclear file reference flagged for review as it's processed |
| Source document retrieval means searching a shared drive | Every figure links directly back to its source document |
| Reconciliation effort grows with every new open file | Same method applies regardless of how many files are open |
From one office to a multi-branch agency
A single-office agency closing a handful of files a week can reconcile its trust account by hand, if tediously. A multi-branch agency running several trust accounts across offices, with hundreds of open files at any time, turns the same exercise into a recurring job that consumes real staff time every month — and a single missed reference across that volume is far easier to lose track of.
Reading and organizing each month's documentation the same way, regardless of how many branches or files are involved, keeps the effort per document flat as the agency grows — what changes is only how many lines need a human look, which accurate extraction keeps small.
Who uses this
Escrow officers and title agency owners
A traceable, file-level reconciliation ready before a monthly close or an underwriter's review.
Trust account compliance managers
Escrow bank statements and closing statements read and organized without a manual re-keying pass.
Underwriters and outside auditors
A structured starting point instead of a stack of unrelated statement and wire-confirmation PDFs.
Small and independent title agencies
The same document-level rigor a larger agency's back office applies, without needing the same headcount.
Edge cases worth knowing
A wire that arrives split across two deposits — a lender's proceeds wire and a separate borrower deposit landing on different days for the same file — needs both matched back to the one file rather than treated as two unrelated transactions that leave the file's ledger looking short until the second piece arrives.
A file that closes, then reopens for a post-closing correction — a recorded document error requiring a small additional disbursement weeks later — needs its balance re-tied to the same file rather than booked as a new, unrelated transaction with no history behind it.
Why file-level evidence beats a single balance
A reconciliation that shows only the bank total and the book total, without every file's own ledger behind it, is easy to trust until an underwriter samples five files and asks for support. Reconstructing that support later means going back through a month — or a year — of bank statements and closing files and starting over under a deadline.
Keeping the source document attached to every figure in every file's ledger — statement date, page reference, confidence level — turns that reconstruction from a scramble into a detail already sitting in the data, ready the moment a sample request comes in.
What this doesn't do
Doesn't perform the reconciliation's final sign-off
It lines up the bank-side and file-side figures so a mismatch is visible — confirming the tie and resolving any genuine shortage stays your escrow officer's step.
Doesn't determine escheatment or notification obligations
It surfaces files carrying an unresolved balance clearly — applying your state's specific trust accounting and escheatment rules is a compliance judgment.
Doesn't replace a title production or trust accounting system
It's the document-reading layer many agencies use alongside their books to gather and organize supporting evidence.
Doesn't give legal or compliance advice
Any question about RESPA obligations, state trust account rules or examination strategy belongs with your underwriter or counsel, not this tool.
What it does fits in one sentence: turn a month of escrow bank statements and closing statements into one consistent, file-traceable workbook, so a three-way reconciliation doesn't have to be rebuilt from scratch every time it's due — or an examiner asks for it early.
Feeding into a RESPA or state examination
A state trust account examination typically samples a set of files and asks for the full paper trail behind each one — the closing statement, every deposit and disbursement, and proof the file's ledger ties to the bank record for the period. Every one of those documents draws on the same underlying source material this tool reads.
Building the examination response itself — assembling exactly what the examiner requested, in the format they expect — stays a step your compliance officer or underwriter typically owns. What this tool changes is how much of the underlying legwork, pulling and organizing a period's worth of escrow documentation, is already done by the time that response needs to go out. See the step-by-step reconciliation guide for how that process fits together.
Security and privacy
Uploads are encrypted with TLS from end to end.
Processing runs on infrastructure with SOC 2-aligned controls.
Original documents are deleted shortly after processing.
Nothing you upload is ever used to train AI models.
For financial records carrying client closing funds, that matters — details are on the security page.