What a three-way reconciliation actually is
A three-way escrow reconciliation checks three independently-derived numbers against each other: what the bank says the trust account holds, what your own books say it holds, and what the sum of every individual open file's ledger says it should hold. When all three agree, the account is proven clean for that period — not merely balanced on paper, but backed by every file it's made of.
This guide walks through the process step by step, the way most title agencies and their examiners expect to see it done, from pulling the statement to filing a signed-off record — the same process whether you're running it by hand on a spreadsheet or with document-reading software doing the extraction for you.
Why the process matters more than the spreadsheet
The formula behind a three-way reconciliation is simple arithmetic — three sums that should be equal. What actually determines whether a reconciliation is trustworthy is the process behind those three sums: whether every document was actually read, every transaction correctly tagged to its file, and every discrepancy chased down rather than smoothed over to make the numbers agree.
A reconciliation that ties because every input was carefully verified is worth something in an examination. A reconciliation that ties because a rounding adjustment was quietly inserted to close a small gap is worth considerably less — and is usually the first thing an experienced examiner learns to look for.
Pull the bank statement for the period
Start with the actual bank statement covering the exact period the reconciliation is for — not an online banking snapshot taken mid-month, which can miss transactions still pending settlement. The statement's own closing balance is the anchor the other two numbers get checked against.
Confirm your book balance for the same period
Pull the trust account's book balance from your accounting or title production system for the identical period. If the bank and book balances already disagree before you even reach the file-by- file comparison, resolve that gap first — it usually points to a transaction recorded in one system but not the other, and chasing the file-level detail before fixing this makes the whole process harder than it needs to be.
Gather every open file's supporting documents
Collect the closing statements, wire confirmations and disbursement records for every file that had activity during the period, plus the carried-forward balance for every file that stayed open with no activity at all. A quiet file still needs to be included — its balance simply shouldn't have moved.
Read and tag every transaction to its file
Every deposit and disbursement on the bank statement needs to be matched to the file it belongs to, using the file number, wire reference or payee name printed on the statement or the supporting document. This is the single most time-consuming step done by hand, and the one where reading software removes the most manual re-keying — every transaction extracted and tagged automatically, with anything genuinely unclear flagged for a human decision instead of guessed at.
Sum every file's ledger balance
Once every transaction is tagged, add up every open file's own running balance into one grand total. This is the number the bank balance and book balance both need to agree with — the actual proof that the account is made up of exactly the right files holding exactly the right amounts.
Compare the three totals
Line the bank balance, the book balance and the file-ledger sum up side by side. If all three match, the period is clean and you move to sign-off. If any two disagree, the gap between them is your starting point for step seven.
| Total | Example |
|---|---|
| Bank statement closing balance | $1,284,610.22 |
| Book balance | $1,284,610.22 |
| Sum of every open file's ledger | $1,284,610.22 |
Investigate every discrepancy individually
A gap between any two totals traces back to a specific cause almost every time: a transaction tagged to the wrong file, one missed entirely, a bank fee never allocated, or a stale file that never got closed out. Work through the possibilities systematically rather than adjusting a total to force agreement — the point of this step is finding the real cause, not making the numbers match.
Document the resolution
For every discrepancy found, write down what caused it and exactly how it was corrected — which file, which transaction, which document confirmed the fix. This record is what turns a resolved gap from a loose end into evidence the process is actually working, and it's the first thing an examiner will ask to see if a discrepancy shows up in a sample review.
Sign off and file the reconciliation
Once the three totals tie, sign and date the reconciliation and file it with its supporting documents — the bank statement, the file-level detail and any discrepancy notes — in the same place every period, so a prior period can be pulled quickly if it's ever needed for reference or review.
A worked example, start to finish
A two-person escrow office runs its monthly reconciliation on 61 open files. The bank statement closes at $412,880.15. The book balance, pulled from the title production system, also shows $412,880.15. Summing every file's own ledger comes to $411,930.15 — a $950 gap.
Working through the files individually, one file's disbursement was recorded at $8,950 in the title system but the bank statement shows $8,000 actually left the account — a $950 keying error on the disbursement amount, corrected the same day once the underlying wire confirmation is pulled and compared. The reconciliation ties on the second pass, and the correction is documented against that specific file before sign-off.
A printable checklist
Bank statement pulled for the exact period
Book balance confirmed for the same period
Every open file's supporting documents gathered, including quiet files
Every transaction read and tagged to its file
File-ledger sum calculated
Three totals compared
Every discrepancy traced to a specific cause
Every correction documented
Reconciliation signed, dated and filed with support
A second example: a discrepancy that isn't a shortage
A different agency's reconciliation shows the bank and book balances agreeing perfectly, but the file-ledger sum comes in $400 higher than both. Since the file side is the one that's out of step here, the search starts there rather than with the bank statement.
Tracing it, a file that closed two months earlier was never marked closed in the ledger system — its small remaining balance was correctly disbursed at the bank, but the ledger entry for that disbursement was never entered, so the file's ledger still shows $400 more than it actually holds. The fix is a ledger correction, not a bank-side investigation, and it's a useful reminder that a discrepancy can originate on either side of the comparison — the bank record, or the books — and the direction of the gap is usually the first clue which one to check first.
How much time each step actually takes
For a moderate-volume office, gathering documents and reading transactions is the biggest time sink by far when done manually — often more than half the total effort — while the actual comparison and sign-off take minutes once the file-level totals are correct. Reading software shifts most of that time out of the process entirely, leaving investigation and documentation, which genuinely need a human, as the bulk of what's left.
Common mistakes worth avoiding
Adjusting a total to force a tie
Papers over the real cause and leaves it to resurface, usually at a worse time — an examination, not a routine month.
Skipping quiet files
A file with no activity this period still needs its carried-forward balance checked, not assumed unchanged.
Reconciling from a mid-month online banking snapshot
Misses transactions still settling and produces a bank total that doesn't match the actual statement once it's issued.
Treating a small gap as immaterial
A $12 discrepancy left unresolved is a process gap, not a rounding error — and it's usually a sign of a larger one hiding behind it.
How often this should actually run
Monthly is the floor most state trust accounting rules set, tied to when the bank statement itself arrives. Many agencies with a higher file volume run a lighter version weekly or even daily — checking that new activity is tagged correctly as it happens rather than waiting for a month of transactions to pile up before the first look.
Doing this with software vs. by hand
By hand, the process is entirely achievable on a well-organized spreadsheet — plenty of smaller agencies run exactly that. What software changes is the reading step: instead of re-keying every bank statement line and closing document figure manually, the documents are read once, tagged to their file automatically, and any transaction that can't be confidently tagged is flagged for you rather than silently mis-assigned.
If this is your first reconciliation ever
Start with the most recent complete period rather than trying to reconstruct every prior month at once. Get one clean reconciliation done, filed and signed off, then work backward if a prior period genuinely needs to be reconstructed — usually only necessary if an examination specifically asks for it.
Who this guide is for
Escrow officers running their own reconciliation, compliance managers overseeing several branches, and outside bookkeepers or CPAs supporting a title agency's trust accounting will all recognize this process — the steps are the same regardless of who's doing them or how large the agency is.
Doing this across several branches
Each branch's trust account is reconciled on its own — the three-way tie is an account-level proof, not something that averages cleanly across branches. What changes at multi-branch scale is coordination: making sure every branch runs the same process on the same cadence, with a consistent way to escalate a discrepancy that doesn't resolve at the branch level.
When a discrepancy doesn't resolve cleanly
Occasionally a gap resists explanation even after a thorough review — a small, genuine shortage with no clear cause found. Most state trust accounting rules have a specific process for this: notification to the regulator, a defined timeline to make the account whole, and documentation of the search already performed. This is a compliance and legal step, not a document-reading one — the honest move is escalating it promptly, not extending the search indefinitely while the account stays out of balance.
What to look for in reconciliation software
Whether it's a dedicated escrow accounting platform or a document-reading tool feeding a spreadsheet, a few capabilities matter more than the rest for this specific process: reading a bank statement's own printed structure rather than a fixed template, tagging transactions to a file automatically with a visible confidence level, and flagging — never silently guessing — anything genuinely unclear. A tool that gets those three things right removes the slowest, most error-prone part of the process without pretending to make the judgment calls that should stay with a person.
What matters far less is whether the tool performs the final three-way comparison itself. That comparison is simple arithmetic once the underlying figures are accurate — the real value is in getting accurate, file-tagged figures out of a stack of PDFs reliably, every period, without a manual re-keying pass.
A small office's process vs. a large agency's
A two-person office reconciling a dozen files a month can run this entire process on a well-organized spreadsheet, checking each file by eye. The nine steps above still apply — they're just faster to execute at that scale, and the investigation step in particular rarely turns up more than one or two items worth a closer look.
A larger agency running several hundred open files across multiple escrow officers needs the same nine steps, but the volume changes what's practical: manually re-keying that many transactions every month becomes the process's biggest bottleneck, and a missed or mis-tagged transaction is far easier to lose track of in a larger pool. The steps don't change with scale — what has to change is how much of the reading and tagging work is automated versus done by hand.
An annual review on top of the monthly cycle
Beyond the recurring monthly reconciliation, many agencies run a deeper annual review — checking not just that each period tied, but that every period's reconciliation record actually exists, that no month was quietly skipped, and that every open file carried forward correctly across the full year. This is less about finding a new discrepancy and more about confirming the discipline itself held up consistently.
An annual review is also a natural point to clear out files that should have closed months earlier but never got a final disbursement, before they become a stale-file finding in someone else's review first.
| Annual review check | What it confirms |
|---|---|
| Every period has a filed, signed reconciliation | No month was quietly skipped |
| Every open file carried its balance forward correctly | No file quietly drifted across a year of periods |
| Every closed file ended at zero, or with a documented reason otherwise | Nothing was left half-disbursed |
| Every discrepancy from the year has a documented resolution | Nothing was left as an open question |
A short glossary for this process
| Term | Meaning |
|---|---|
| Trust/escrow account | The pooled bank account holding client funds for every open file |
| Book balance | The trust account balance as recorded in your own accounting system |
| File ledger | One file's own running balance, built from its own transactions |
| Shortage | The trust account holding less than the files' ledgers say it should |
| Escheatment | Remitting unclaimed, dormant funds to the state after a defined period |
A final quality check before filing
Before signing off, confirm every open file was actually included in the ledger sum — not just the files with activity this period — and that every documented discrepancy has a clear cause and a clear correction attached, not just a note that it was "resolved." A reconciliation that passes this check is one that will hold up under a sample review months later, not just at a glance today.
Adjusting the process as file volume grows
A process that works comfortably at twenty open files a month starts to strain at a hundred, not because the nine steps change, but because the reading and tagging step that used to take an afternoon now takes days if it's still done by hand. The usual first response — hiring more staff to re-key more transactions — treats the volume problem as a headcount problem, when it's really a reading-speed problem.
Automating the reading and tagging step keeps the process's shape identical regardless of growth, so an agency scaling from twenty files to two hundred a month doesn't need to restructure how reconciliation works — only the review step, which still needs a person's judgment, scales with volume at all.
Digital bank feeds vs. PDF statements
Some banks offer a live transaction feed or API alongside the traditional monthly PDF statement, and it's tempting to treat the feed as the more authoritative source since it updates continuously. For reconciliation purposes, the issued statement is usually still the record that matters — it's what a bank stands behind as the final, closed record for the period, where a live feed can include pending transactions that haven't fully settled yet.
A live feed is genuinely useful for a mid-period sanity check — confirming a large wire actually cleared before disbursing against it, for instance — but the formal reconciliation should tie to the statement the bank issues, not to a snapshot that might still change before the period closes.
When bookkeeping is outsourced to a third party
Some smaller agencies outsource their bookkeeping, including trust account reconciliation, to an outside bookkeeper or CPA firm rather than keeping it entirely in-house. The process doesn't change — the same nine steps apply — but the handoff of documents between the agency and the outside party becomes its own point where something can get lost if it isn't deliberate.
Sharing read, organized data rather than a folder of raw PDFs is what keeps that handoff clean: the outside bookkeeper receives figures already tagged to their file, with the source document still attached for reference, rather than starting from the same manual re-keying step the process was trying to remove in the first place.
Handing this off to someone else
A reconciliation process that lives only in one person's head is a real business risk — an escrow officer's sudden absence shouldn't mean the trust account goes unreconciled that month. Keeping the checklist above, the source documents and the discrepancy notes organized the same way every period is what makes handing this off to a colleague, or a new hire, straightforward rather than a reconstruction project.
A useful test of whether the process is actually documented well enough to hand off: could someone who has never touched this specific trust account before follow the nine steps above, using only the prior period's files as a reference, and produce a reconciliation that would pass a review? If the honest answer is no — if it genuinely requires tribal knowledge only one person has — that gap is worth closing before it's tested by an actual absence rather than a hypothetical one. See the trust accounting overview for how this process fits into the fuller compliance picture.
A brief written summary of the process — even a one-page version of this guide, annotated with your agency's own specific file-numbering conventions and document sources — is often enough to make the handoff work in practice, without needing a lengthy formal training manual most small offices never actually have time to write.