Three-way reconciliation proves that three records show the same number on the same date: the bank statement for an account, your control ledger of what the account holds in total, and the sum of every individual sub-account inside it. When all three agree, the account is reconciled. When they don't, someone's money is misstated, and finding where is the whole job.

If you hold other people's money in a pooled account, this is the check that keeps you out of trouble. Law firms do it for trust accounts. Title companies and brokers do it for escrow. Property managers do it for tenant and owner funds. Medical practices face the same problem when insurance deposits have to tie back to visits. The words change; the mechanics don't.

The three records that must agree

Strip away the jargon and it's one rule: three records, one number, one date.

  1. The bank statement for the account: what the bank says you're holding.
  2. The control ledger: what your books say the account holds in total.
  3. The sub-account ledgers: each individual balance, summed. Every dollar in the account belongs to a specific client, matter, tenant, or file, so the individual balances must add up to the account total.

Say the bank shows $214,508 and your control ledger shows $214,508. Two-way reconciliation stops here and calls it done. But if the sub-account balances only sum to $213,300, then somewhere an individual balance is wrong and you're holding $1,208 you can't attribute. That is the exact condition three-way reconciliation exists to catch, and it's why the check is three-way and not two.

Why two-way reconciliation isn't enough

Bank-to-ledger reconciliation is necessary, but it's blind to the one error that matters most in a pooled account: money attributed to the wrong owner. The bank agrees with the total. The total agrees with the books. And a client's balance is still overstated while another's is short by the same amount. The account looks perfectly reconciled right up until the moment you have to prove whose money is whose. Three-way is the only version that forces that proof every period.

Where three-way reconciliation is required, and what it's called

It's the same procedure everywhere. Only the account name and the rulebook change.

Law firms: trust and IOLTA accounts

Client retainers, settlements, and advanced costs sit in a trust account until they're earned or disbursed. Most state bars require regular three-way reconciliation of that account; Florida requires it monthly, with records kept and producible on request. Commingled or misattributed client funds are one of the fastest routes to a bar complaint. We wrote a full piece on the law firm version: why law firms dread bar audits, and how to stop, and the system behind it lives on our law firm financial operations page.

Real estate, title, and escrow

Earnest money, closing funds, and escrow deposits pass through a single escrow account on the way to many different files. State real estate and title rules require the escrow account to reconcile three ways: bank, escrow control ledger, and the sum of every open file's balance. A shortage in one file hidden by a surplus in another is exactly what the reconciliation is designed to surface, before a closing moves the wrong amount.

Medical and physical therapy practices

Healthcare rarely uses the phrase "three-way reconciliation," but the mechanics are identical and harder. One insurance deposit bundles many claims across patients and dates, the itemized remittance arrives in a different system than the money, and payments land weeks after the visit. Tying the bank deposit to the remittance to the visit is a three-way match under another name. We covered the practice version in why your PT practice can't match bank deposits to payers.

Property management

Security deposits and owner funds sit in trust the same way client money does. The account has to reconcile to the bank and break down cleanly by property and by owner, so that no owner's distribution is ever paid out of another owner's balance.

Why it breaks down

  • It's tedious work done under deadline. The match usually lands at month-end, exactly when billing and closings do. A single transposed digit can take days to find, because a $1,208 gap isn't one error; it's any combination of errors that nets to $1,208.
  • Money crosses accounts. Funds move in, get earned or disbursed, get advanced and reimbursed. Tracing one file's money across every movement is a research project, and every transfer is a chance for the sub-ledgers to drift.
  • Timing differences look like mistakes. Outstanding checks and in-transit deposits mean the bank and the ledger legitimately disagree on any given day. Separating "timing" from "error" is the real skill, and it's the first thing that gets rushed.
  • The software records; it doesn't verify. Your practice-management or accounting system keeps a tidy ledger of what you told it. It doesn't independently check the bank. Enter a deposit against the wrong file and the software will agree with that mistake forever.

The stakes are asymmetric. Nobody gets disciplined for making a reconciliation error. People get in trouble for not catching one: for months of unreconciled records, unattributed balances, or paying out against money that turned out to belong to someone else. Like a data breach, the damage scales with how long it goes undetected.

What good looks like

The fix isn't a heroic month-end. It's changing when the matching happens.

  1. Continuous matching instead of monthly archaeology. Bank activity, the control ledger, and the sub-ledgers compared as transactions land, so an exception is flagged the day it appears, when it's one day old and obvious, not buried under thirty days of activity.
  2. Every exception carries its detail. The flag isn't "off by $1,208." It's "this deposit hit the bank on the 14th and was never posted to a file," with the transaction attached. The person who owns it resolves it in minutes.
  3. Audit-ready output on demand. The reconciliation report becomes a byproduct of a system that's always current, not a document assembled under pressure. "What if they ask tomorrow" stops being a scary question.
  4. One place where the money story lives. Bank, ledger, and sub-account data joined in a single database you own, so tracing a file's money stops being per-file archaeology.

Where automation helps, and where it doesn't

To be precise about the technology: the automated layer reads bank feeds and system exports, matches transactions, and flags what doesn't tie. That's it. It doesn't move money, it doesn't replace your trust or accounting software, and it doesn't make judgment calls. Every exception is resolved by your bookkeeper, attorneys, or owner, who keep full oversight. Data stays encrypted and is never used to train AI models.

We built this reconciliation engine inside a multi-location Florida physical therapy practice first, where it moved the monthly bank match rate from roughly 80% to 98% across thousands of small insurance payments and traced more than $70,000 a month back to a specific payer. The write-up is on our case studies page. Trust and escrow accounts are the same mechanical problem with higher stakes: many small movements of other people's money, across systems that must tie to the bank, provable on demand.

If you're doing it by hand this month

The manual version, done well, looks like this: reconcile on a fixed calendar day every month, no exceptions during the busy stretch. Work at the transaction level, never "the totals are close." Keep the three-way report even when it ties perfectly, because the record of reconciliations is itself what an examiner wants to see. Log every exception and how it was resolved. If you're behind by more than a quarter, block the days and catch up now; discrepancies compound, and the oldest ones cost the most to unwind.

And when the month-end scramble starts eating your bookkeeper alive, that's the point where the continuous version pays for itself. Every engagement we take starts with a fixed-price Discovery Sprint scoped around the account, so you know exactly what you're buying before you commit.

Frequently Asked Questions

What is three-way reconciliation?

It proves that three records show the same number on the same date: the bank statement for the account, your control ledger of what the account holds in total, and the sum of every individual sub-account, such as each client's or each matter's balance. When all three agree, the account is reconciled. When they don't, someone's money is misstated, and finding where is the work.

What is the difference between two-way and three-way reconciliation?

Two-way reconciliation ties the bank statement to the ledger total. That can look perfect while an individual client or file balance is silently wrong. Three-way adds the third check: the sum of every sub-account must also equal the total. It catches a class of errors two-way reconciliation cannot see, which is why trust and escrow rules require it.

Who is required to do three-way reconciliation?

Anyone holding other people's money in a pooled account. Law firms reconcile trust and IOLTA accounts under state bar rules. Title companies and real estate brokers reconcile escrow accounts. Property managers reconcile tenant and owner funds. Medical and physical therapy practices face the same match when insurance deposits have to tie back to remittances and visits, even where no rule uses the words "three-way."

How often should three-way reconciliation be done?

Monthly is the practical standard, and several state bars require it monthly for law firm trust accounts. The deeper answer is as continuously as you can. Errors compound, and a three-month-old discrepancy is far harder to unwind than a three-day-old one. Matching as transactions land turns month-end into a review of a handful of flagged exceptions.

Does it replace my accounting or practice-management software?

No. Your accounting, trust, or practice-management systems stay exactly where they are. A reconciliation layer reads from them and from the bank, ties the records together, and flags what doesn't match. It's a verification step, not a replacement, and every exception is still resolved by your people, who keep full oversight.

← All Resources