One account, many balances
A bank sees one escrow account with one balance. A regulator, an underwriter and the agency's own compliance officer see something entirely different: potentially hundreds of individual files, each holding client money that belongs to that file and no other, each needing its own balance that can be proven at any moment. The bank's single number is the least useful figure in the whole trust accounting picture — it says nothing about whether any one file is actually right.
Keeping every file's own balance current, from the moment earnest money lands to the moment the file disburses and closes, is the day-to-day discipline a three-way reconciliation is checking once a month. This page is about the discipline itself — reading the transactions and keeping each file's ledger accurate as they happen, not just reconciled after the fact.
Why a pooled account hides so much
Because every file shares the same physical bank account, a healthy overall balance tells you almost nothing about any individual file. An account can sit at a comfortable six-figure balance while one file inside it is quietly negative — overdrawn on paper because a disbursement went out before its matching deposit fully cleared — and the account total will never say so on its own.
Finding that one negative file inside a pool of hundreds means either a purpose-built per-file ledger that's kept current in real time, or a manual reconstruction that only happens when someone thinks to look — usually at month-end, sometimes only when an examiner asks.
What a clean file balance actually requires
A file's balance is only as good as every transaction that's been correctly tagged to it — its opening deposit, every subsequent deposit or refund, and every disbursement, each read from the bank statement or closing document that actually recorded it. Miss one tagged transaction, or tag one to the wrong file, and both files involved are wrong until someone catches it.
Why a negative file balance is the figure that matters most
A negative balance on a single file — money disbursed before it was fully on deposit — is the clearest early warning sign a trust account examination looks for. It doesn't always mean something went wrong; a wire that's in transit but not yet cleared can create a brief, explainable negative balance. What matters is whether it's caught and explained quickly, or left sitting unnoticed inside a healthy-looking pooled total for weeks.
Surfacing every file's current balance clearly — not just the account total — means a negative figure gets seen the same week it appears, not the month it's finally reconciled.
What gets read
| Field | Typical source |
|---|---|
| File / order number | Bank statement memo line, wire confirmation, closing statement |
| Transaction date and amount | Bank statement line item |
| Deposit vs. disbursement | Bank statement transaction type |
| Payer / payee | Wire confirmation, check register |
| Running balance | Computed per file from every tagged transaction |
How it works
Upload escrow bank statements and closing documents
For the account and period you want tracked.
Each transaction is read and tagged
File reference, amount and type extracted from every line.
A running balance is kept per file
Every tagged transaction rolls into that file's own ledger, not just the account total.
Unclear references are flagged
A transaction that can't be confidently tagged is surfaced for a human decision.
Exported
Excel, CSV or JSON, one row per transaction, traceable to its source and its file.
A file, tracked start to finish
A single residential purchase file opens with an earnest money deposit, receives the buyer's remaining funds and the lender's wire ahead of closing, then disburses to the seller, the lender payoff, recording fees and the agency's own fee — five transactions in total, spread across two monthly bank statements.
| Transaction | Running balance |
|---|---|
| Earnest money deposit | $5,000 |
| Buyer's remaining funds | $62,400 |
| Lender's wire | $286,000 |
| Disbursement to seller and payoff | $4,900 |
| Recording fees and agency fee disbursed | $0 |
Every one of those five figures is read from the bank statement or wire confirmation it actually appeared on, tagged to the same file number, and the file closes at exactly zero — the balance a clean file is supposed to end at once every dollar is accounted for and disbursed.
What a confidence score actually tells you
Every figure extracted carries a confidence score, not just a value. A high-confidence read means the text was clean and the number unambiguous — a printed amount on a well-scanned bank statement, for instance. A lower score means the figure was legible but came with some genuine uncertainty: a faint fax line, a total partially covered by a stamp, a handwritten correction next to a printed amount.
The point of showing the score rather than hiding it behind a single pass/fail flag is that a file balance built from ten high-confidence transactions and one flagged one is a very different situation than a balance where every figure carries the same low confidence — the first needs one quick check, the second needs a fuller review of the source document itself. Knowing which situation you're actually in saves a review pass that would otherwise treat every file the same regardless of how reliable its underlying documents actually were.
Files that stay open across a full year or more
Most residential purchase files close within weeks, but not every file follows that pattern — commercial transactions, files tied up in a title dispute, or an escrow holding funds against a repair holdback can stay open for months or, occasionally, over a year. A file like that accumulates transactions across many separate bank statements, sometimes with long quiet stretches in between.
Keeping that file's balance current means every one of those statements, however far apart, needs to be read and tagged the same consistent way, with the file's running balance carrying forward correctly across each gap. A file that goes quiet for four months and then has activity again needs its balance to still be exactly right the moment that activity resumes — not reconstructed from scratch because the file fell out of anyone's regular attention during the quiet stretch.
Bringing historical files into the system
An agency adopting this for the first time usually isn't starting with an empty trust account — there are open files already carrying a balance, built up under whatever process was used before. Getting those files' history into the same traceable format means uploading their prior bank statements and closing documents alongside new activity going forward, so a file's balance is fully backed by source documents from the moment it opened, not just from the day the agency started using a new process.
This is usually worth doing gradually rather than all at once — starting with the files still open and active, then working backward to recently-closed files if a specific one is ever needed for reference, rather than trying to re-read every historical document across the whole account in a single pass.
Manual vs. automatic
| Manual | Automatic |
|---|---|
| File balance rebuilt from scratch when someone asks | Every file's running balance kept current as documents are read |
| A negative file found only at month-end review | A negative balance visible as soon as it's read |
| Tracing a file's history means searching several folders | Every transaction stays linked to the file it belongs to |
| Gets slower as the number of open files grows | Same method applies regardless of how many files are open |
From a handful of files to hundreds
A small office with a dozen open files can keep track by memory and a shared spreadsheet, more or less. An agency running several hundred open files across branches can't — the only realistic way to know every file's balance at any moment is to read every transaction the same way, consistently, regardless of volume.
Who uses this
Escrow officers
A current balance for any file, without rebuilding it from a bank statement on demand.
Trust account compliance managers
Negative or stale file balances surfaced early, before they become an exam finding.
Agency owners running multiple branches
The same file-level visibility across every branch's trust account.
Outside auditors
A file's full transaction history, already organized, when a sample review is due.
Edge cases worth knowing
A file that receives a refund after closing — an overpayment returned weeks later — needs that refund tagged back to the original, already-closed file rather than treated as an unrelated new deposit with no history behind it.
A transfer between two files sharing the same buyer or seller, used to cover a shortfall on one file from a surplus on another, needs to be tagged as a matched pair — a disbursement on one file and a deposit on the other — rather than as two unrelated, unexplained transactions.
Why per-file evidence beats a single total
An account total that's correct on the last day of the month says nothing about whether it was correct on any other day, or whether it stayed correct file by file the whole time. Per-file tracking that's kept current turns "is this file okay" from a question that needs a reconstruction into one with an answer already sitting in the data.
Giving a whole team the same view
When file balances live only in one escrow officer's head or personal spreadsheet, covering for a colleague on vacation, or picking up a file after someone leaves, means starting from a partial picture. A shared, current view of every file's balance — the same view for anyone who needs it — removes that gap: any team member can check a file's standing without first tracking down whoever normally handles it.
That shared visibility also matters for a principal or owner who isn't in the reconciliation weeds day to day but wants a quick, honest read on whether anything needs attention — a negative or stale file balance is visible the same way to an owner checking in periodically as it is to the escrow officer working the file directly.
What this doesn't do
Doesn't replace your trust accounting system's own ledger
It's an independent, document-traceable check built from the same bank statements and closing documents your system relies on.
Doesn't resolve a shortage for you
It surfaces exactly which file and which transaction is out of step — deciding how to correct it stays your escrow officer's call.
Doesn't determine escheatment timing
A stale file balance is flagged clearly; applying your state's specific dormancy and escheatment rules is a compliance decision.
Doesn't give legal or compliance advice
Any question about trust accounting rules or RESPA obligations belongs with your compliance officer or counsel.
Catching a problem the moment it appears
The value of per-file tracking drops sharply if it only gets checked once a month, right before the formal reconciliation is due — a negative balance that appeared on the third of the month is just as real a problem on the fourth as it is on the thirtieth, and the earlier it's seen, the smaller and easier the correction usually is.
Building the habit of a quick weekly glance at any file carrying a negative or unusually stale balance, rather than waiting for the monthly cycle to surface it, is what actually keeps small issues small — a five-minute check that replaces what would otherwise be a longer investigation once a month has passed and the trail has gone cold.
Getting your first file tracked
Upload one month's escrow bank statement to see every transaction read and organized — then add the closing statements for that period to see individual files come into full view, each with its own balance. See the three-way reconciliation guide for how per-file tracking feeds into the monthly reconciliation itself.
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.
