The audit that isn't about fraud
Most people picture a trust account examination as a hunt for stolen money. In practice, the overwhelming majority of findings are nothing so dramatic — a file whose ledger doesn't quite tie to the bank record for a period, traced back to a mis-tagged transaction, a missed document, or a disbursement keyed at the wrong amount. The money is almost always still there. What's missing is the proof.
That distinction matters, because it changes what actually helps an agency prepare. Preparing for fraud detection means very little if fraud was never the risk. Preparing for a documentation and process review — proving that every file's balance can be traced, every period, to a source document — is what an examination actually tests.
Who actually runs these examinations
Depending on the state, an examination can come from a state insurance or real estate licensing regulator, from the title insurance underwriter whose policies the agency issues, or occasionally from an independent CPA engaged for a compliance review. The exact authority, cadence and scope varies meaningfully by jurisdiction — an agency operating in several states may face different examination schedules and expectations from each one.
What's consistent across almost all of them is the core question: does the trust account's money, file by file, tie to what the books and the bank both say it should be.
Why a sample, not every file
A busy agency can have hundreds of open and recently-closed files at any given time — reviewing every one in detail isn't practical for a routine examination. Instead, examiners typically pull a sample sized to the agency's volume, chosen to be broadly representative: a mix of file sizes, closing dates and, often, different escrow officers if more than one handles files.
The sample is a starting point, not the whole test. What the examiner does with what the sample reveals is the part that actually determines how the examination goes.
The core check: does the three-way tie
For every sampled file, and for the account as a whole across the period under review, the examiner is checking the same three-way relationship a routine internal reconciliation checks: the bank statement balance, the book balance, and the sum of every open file's own ledger. If those three numbers agree for the period, and each sampled file's individual history ties cleanly to its own documentation, the account passes that part of the review.
Everything else the examination looks at — documentation quality, negative balances, stale files — is really just a closer look at the same underlying question from different angles.
The documents an examiner actually pulls
| Document | What it's expected to show |
|---|---|
| Closing/settlement statement | Every dollar in and out of the file at the moment of closing |
| Bank statements for the period | Every deposit and disbursement the bank actually recorded |
| File ledger / running balance | A complete, dated history of the file's own balance |
| Wire confirmations | Proof a specific incoming or outgoing wire matches the amount claimed |
| Three-way reconciliation records | Proof the account was checked on the required cadence, not just at exam time |
An agency that can produce all five, promptly, for any sampled file is in a fundamentally different position than one that needs days to reconstruct them — even before a single number is checked, that speed says something about how well the underlying process actually runs day to day.
The patterns that turn a routine sample into a deeper look
One discrepancy that repeats across multiple sampled files
A single error is a mistake; the same kind of error on three unrelated files is a process gap worth understanding fully.
Reconciliation records with gaps in the period covered
A missing month's reconciliation reads very differently than twelve consecutive, clean ones — it suggests the process isn't actually running every period.
A file whose documentation takes unusually long to produce
Slow retrieval on its own isn't a violation, but it's often the first sign a file's paper trail isn't as organized as the ledger suggests.
Several files handled by the same person with similar issues
Not an accusation on its own — but it does tell an examiner where a closer, individual look is worth the time.
A trust account that occasionally runs at a lower balance than expected
Even briefly, this is exactly the shape of finding that expands a sample fastest, since it touches the core solvency question directly.
Why negative file balances get pulled first
A file with a negative running balance at any point — money disbursed before it was fully on deposit — is one of the fastest things an examiner checks, because it's the clearest possible signal that a file's own money was, even briefly, insufficient to cover what left the account. Most of the time it's a short-lived timing artifact: a wire in transit, cleared the next business day. What matters to an examiner is whether it was noticed and explained quickly, or sat unaddressed.
Shortage vs. simple error — why the distinction matters
| Shortage | Bookkeeping error |
|---|---|
| Actual funds missing from the pooled account | All funds present; a record is simply wrong |
| Requires notification and a defined correction timeline | Corrected by fixing the record once found |
| Treated as a serious compliance finding | Common, and generally treated as routine when documented |
| Root cause investigation is mandatory | Root cause worth understanding, but lower stakes |
Both start the same way — a number that doesn't tie. The difference is what a full trace reveals: whether the money genuinely isn't there, or whether it's there and a record simply pointed to the wrong place. Getting to that answer quickly and confidently is exactly what a clean, file- level paper trail is for.
Stale files and unclaimed funds
A file that closed, or was cancelled, with a small remaining balance and no clear next step is a common finding on its own — not because the balance is large, but because it represents a file that was never properly closed out. Most states set a defined dormancy period after which unclaimed funds need to be remitted to the state under escheatment rules, following a documented, diligent search for the rightful owner first.
What 'good documentation' actually means to an examiner
Good documentation isn't volume — it's traceability. A file with fewer documents but a clear, unbroken chain from deposit to disbursement, each figure matching the next, reads better than a file with a thick folder where the numbers don't quite connect. What an examiner is really testing is whether the agency's process would catch a real problem on its own, before an outside review ever had to.
What a finding actually costs in time
A clean sample with no findings typically closes an examination in days. A single genuine discrepancy, once traced and documented, rarely extends the timeline dramatically on its own. What actually stretches an examination out is a documentation gap — files that take a long time to retrieve, or a reconciliation record with missing periods — because reconstructing that history under examination pressure takes far longer than it would have taken to keep current in the first place.
A sample review, walked through
An examiner samples 15 files from an agency with 340 closings over the prior year. Fourteen tie cleanly to their bank record and closing statement within minutes. The fifteenth shows a $1,200 gap between its ledger and the bank record for the month it closed.
| Step | Outcome |
|---|---|
| Trace the $1,200 to its source | Disbursement wire confirmation shows $1,200 less than the ledger recorded |
| Check for a repeat pattern | Two nearby files from the same period checked; both tie cleanly |
| Classify the finding | Isolated keying error, not a shortage — funds fully accounted for |
| Resolve and document | Ledger corrected to match the wire confirmation, noted in the file |
The examination closes with one minor finding, corrected and documented, rather than expanding into a full-agency review — precisely because the pattern check came back clean on the surrounding files.
A clean file vs. a flagged one
| Clean file | Flagged file |
|---|---|
| Every transaction traces to a specific document | A transaction with no clear supporting document |
| Balance ties to the bank record for every period | A gap between the ledger and the bank statement |
| Closed at exactly zero, or with a documented reason otherwise | Closed with an unexplained remaining balance |
| Included in every period's reconciliation while open | Missing from one or more periods' reconciliation record |
What keeps a file out of the flagged pile in the first place
Almost every clean-file characteristic above traces back to the same underlying habit: reading every bank statement and closing document carefully, tagging every transaction to the right file the first time, and running the three-way reconciliation on the required cadence without exception. None of it is exotic — it's the same discipline this whole guide has been describing, applied consistently enough that an examination finds nothing more interesting than routine, well-documented business.
How often these examinations actually happen
This varies significantly by state and by underwriter relationship — some agencies see an annual underwriter audit as a matter of course, others are examined on a longer or risk-based cycle by their state regulator. An agency that's had a prior finding is generally examined more frequently afterward until a clean track record is re-established.
How the examination differs for a small office vs. a large agency
A single-office agency closing a handful of files a week typically faces a smaller sample and a shorter examination window, simply because there's less total volume to sample from and fewer staff whose individual patterns need checking. That doesn't mean a smaller office faces less scrutiny per file — the same three-way tie and documentation standard applies regardless of size.
A larger, multi-branch agency faces a bigger sample, often specifically structured to cover more than one branch and more than one escrow officer, precisely because a finding at one branch raises the question of whether the same gap exists elsewhere in the organization. The core check stays identical; what scales with size is how broadly the examiner looks before concluding the account is clean.
An underwriter's audit vs. a state examination
An underwriter's own audit team and a state regulator's examination look at broadly similar things — the three-way tie, documentation quality, file-level traceability — but they serve different purposes and carry different consequences. An underwriter's review is fundamentally about whether the agency remains a safe party to issue that underwriter's policies through; a state examination is about whether the agency continues to meet the legal requirements to hold a license at all.
In practice, an agency that stays audit-ready for one is almost always audit-ready for the other, since both are testing the same underlying discipline from slightly different angles. The main practical difference worth knowing is that some underwriters conduct their reviews more frequently than a state's statutory examination cycle, making the underwriter relationship the one that actually keeps the process sharp between formal state reviews.
Running your own review before the real one
Many agencies run an internal self-review on the same logic an external examination would use — pulling a sample of files, checking the three-way tie, confirming documentation is complete — before a regulator or underwriter ever asks. Catching and correcting an issue this way, on your own schedule, is a meaningfully better position than having the same issue found first by someone else. See the reconciliation guide for the exact process to run.
Where document reading actually helps here
Preparation for an examination is mostly a speed and completeness problem: can every sampled file's full paper trail be produced quickly, and does it actually tie. Reading bank statements and closing documents automatically, tagged by file as they're processed, is what keeps that paper trail current all year rather than something reconstructed under pressure once a request arrives.
What preparation can't fix
A genuine shortage still has to be reported
No amount of good documentation changes the obligation to notify and correct a real shortfall once found.
A weak internal control still needs a real fix
Good record-keeping around a broken process documents the problem clearly — it doesn't replace fixing the process.
State-specific rules still require your own compliance advisor
The general shape described here doesn't substitute for your state's specific trust accounting requirements.
What happens after a finding
A minor, isolated finding — the keying error in the worked example above — typically closes with a correction and a note in the exam record. A more serious finding, particularly a genuine shortage, usually triggers a formal corrective action plan with a deadline, and in serious or repeated cases can escalate toward licence consequences. The response process itself is a legal and compliance matter, not a document-reading one — your underwriter or counsel should guide the actual response to any real finding.
How long records actually need to be kept
Retention periods for closing files and trust account records vary by state, but many require several years at minimum — long enough that an examiner requesting a file from three or four years back is a realistic, not hypothetical, scenario. Retrieving a well-organized file from that far back is a very different task than retrieving one from last month, and it's exactly the kind of request where a paper trail that was never fully digitized turns into a genuine search through storage rather than a quick lookup.
Keeping every closed file's documentation in the same organized, traceable format it was built in — rather than only the currently-open files — is what keeps a years-old request answerable in the same way a current one is, instead of becoming its own small project the moment it's asked for.
What a serious finding actually costs an agency
Beyond the direct correction and any regulatory consequence, a serious trust account finding carries costs that are easy to underestimate going in: the staff time spent on the investigation and response itself, often at the expense of normal closing volume; the underwriter relationship, which can become more cautious or more closely supervised afterward; and, in a small local market, the reputational cost if word of a finding spreads among the referral sources — real estate agents, lenders, attorneys — an agency depends on for business.
None of that is a reason for alarm about a routine, well-documented process — the overwhelming majority of agencies never see a finding beyond a minor, quickly-corrected discrepancy. It's the reason the discipline described throughout this article is worth the modest ongoing effort it takes: the cost of getting it right every period is genuinely small next to the cost of a serious finding.
Two common misconceptions about these examinations
The first misconception is that a clean bank balance means a clean trust account — an account can sit at a perfectly reasonable overall total while one specific file inside it is quietly wrong, invisible until someone checks file by file rather than just the account total. The second is that a fast, confident response to a document request is itself proof of a healthy process — speed matters, but an examiner is checking whether the documents actually tie, not just whether they arrived quickly.
Both misconceptions point to the same underlying truth: the account total and the response time are surface signals. The real test is always the file-level detail underneath them, which is exactly why this whole guide keeps returning to the same point — traceability at the file level, not a healthy-looking summary number, is what actually survives a close look.
A short summary checklist
Three-way reconciliation run and documented every required period, no gaps
Every open file's balance traceable to a specific source document
Negative and stale file balances reviewed and explained promptly
Closing statements and bank statements retained for the required period
A documented process for handling a genuine shortage, should one occur
Who this is actually for
Escrow officers preparing for a first examination, compliance managers building an internal self- review process, and agency owners trying to understand what an underwriter's audit actually looks for will all find the same core lesson here: the process matters more than any single number, and consistency across every period is what an examination is really testing.
A new escrow officer joining an agency benefits from reading this before their first reconciliation cycle rather than after their first examination — knowing what the check is actually testing, and why, tends to make the routine monthly discipline feel purposeful rather than procedural, which is usually what determines whether a process gets followed consistently or starts slipping the first time a busy month makes it inconvenient.
Anyone evaluating an escrow accounting tool or considering how to strengthen an internal process will find the same lesson useful too — the questions worth asking of any system are ultimately the same ones an examiner asks: can every file's balance be traced, and how quickly.
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.