A step-by-step guide to performing three-way reconciliation iolta. Learn the process, fix common discrepancies, and see how software can help.
A familiar pattern plays out inside many law firms. The bank balance looks right, the bookkeeper says the trust account is reconciled, and no one notices that one client ledger is short while another carries money that doesn’t belong there. For a solo practice handling estate planning retainers, a small family law firm moving funds frequently, or a mid-size litigation shop managing settlement proceeds, that false sense of accuracy is the underlying risk.
Three-way reconciliation for IOLTA exists to expose that problem. It is not a bookkeeping preference. It is the process that proves client money is intact, properly allocated, and supported by records that could survive bar scrutiny.
Three-way reconciliation for IOLTA is more than a bank match. It requires exact agreement among three different records, each serving a different compliance purpose. Pagelight Prime’s guide to IOLTA account reconciliation states that three-way IOLTA reconciliation is a mandatory monthly process requiring exact matching of the IOLTA bank statement balance, the firm’s combined or control trust ledger, and the sum of all individual client trust ledger balances.
A simple bank reconciliation answers only one question. It asks whether the account balance shown by the bank can be explained by the firm’s internal records after timing adjustments. A three-way reconciliation asks a harder question. It asks whether every dollar in trust is assigned to the correct client matter.
The first pillar is the bank statement for the IOLTA account. This is the external record. It shows what the financial institution says is in the trust account as of the statement date.
The second pillar is the firm’s control ledger, sometimes called the master trust ledger or book balance. This is the internal running total of trust funds across all matters. If this record is wrong, the firm’s internal accounting is already off, even before individual client balances are reviewed.
The third pillar is the sum of all individual client trust ledgers. This is the safeguard that prevents hidden allocation errors. A firm can have the right total in trust and still have the wrong client balances. That is exactly why three-way reconciliation exists.
Practical rule: If the total trust balance matches the bank but the client ledgers don’t add up to the same amount, the firm does not have a clean reconciliation.
This distinction matters in every practice area. A criminal defense solo may hold flat-fee deposits. An immigration practice may carry filing-cost advances. A personal injury firm may hold settlement funds pending disbursement. A litigation firm with multiple attorneys may have dozens of active trust transactions in a single month. In each setting, the allocation by client is what turns raw cash into compliant fiduciary accounting.
The third leg of the process catches mistakes that a normal business accounting workflow can miss. A retainer posted to the wrong family law matter might leave the total trust balance untouched, yet still create a client harm issue. The same is true if settlement proceeds in a personal injury matter are posted partly to another matter by mistake.
That is why firms evaluating software should understand the trust-accounting standard before comparing dashboards or billing tools. Caseledge’s overview of client trust accounts is useful background because the core issue is not software convenience. It is whether the records can prove that funds were held separately and assigned correctly.
The firms that struggle with reconciliation usually don’t fail at arithmetic first. They fail at preparation. Missing statements, incomplete registers, and stale client ledger reports create avoidable confusion before the main review begins.
Beancount’s 2026 guide to IOLTA trust accounting describes three-way reconciliation as a mandatory fiduciary duty and notes that state bars require attorneys to perform it at the same time every month, ideally when the official bank statement becomes available on the first business day of the following month. That monthly cadence matters because a short review window keeps errors contained and traceable.
A workable monthly packet should include the following records before any balancing starts:
Without the client ledger summary, the firm cannot complete the third leg of the reconciliation. That missing report is often the hidden reason some firms think they are compliant when they are only doing a two-way bank match.
Most firms benefit from a fixed sequence rather than an informal reminder. The compliance-friendly schedule is straightforward:
| Task | Timing |
|---|---|
| Download official bank statement | First business day after month-end, or as soon as available |
| Run trust control ledger | Same day |
| Run client trust ledger summary | Same day |
| Reconcile and investigate variances | Immediately after reports are generated |
| Final partner review and sign-off | After all differences are resolved |
Reconciliation works best when all three records are pulled to the same date. A clean process can still fail if one report is dated later than the others.
For firms comparing software stacks, system design starts to matter. A platform such as CosmoLex review and pricing analysis is relevant because it is a cloud practice management system with built-in trust and business accounting. That doesn’t eliminate the lawyer’s oversight duty, but it can reduce the manual work of assembling the monthly packet.
State-specific procedural differences still matter, especially for firms operating across offices or jurisdictions. Caseledge’s IOLTA compliance by state tool is a practical reference point for firms that need to align internal schedules with jurisdiction-specific trust rules.
A proper three-way reconciliation starts outside the firm’s books, then moves inward. That sequence matters because the bank statement provides the fixed month-end anchor. Internal records are tested against it.
Disbo’s IOLTA compliance guide states that the bank statement balance must be adjusted for pending items such as outstanding checks and deposits in transit to calculate an adjusted bank balance, and that any variance of even one dollar must be investigated and resolved before the document is signed. That standard leaves no room for a “close enough” month.
The bank statement rarely equals the books on sight because timing differences are normal. A check issued late in the month may not have cleared yet. A deposit recorded by the firm may still be in transit at statement cutoff.
The first calculation is therefore:
That adjusted bank balance is the number that should match the firm’s trust control ledger.
A family law example is common. The firm receives a retainer deposit near month-end and records it to the client trust ledger immediately. If the bank processes it after the statement closes, the books will show the deposit before the statement does. That timing difference is reconciled by adding the deposit in transit to the bank balance.
Once the adjusted bank balance is established, the next comparison is to the control ledger, sometimes called the trust book balance. This tests whether the firm recorded all trust activity correctly.
If the adjusted bank balance and the control ledger do not agree, the error is usually one of these categories:
A personal injury settlement illustrates the risk. If a settlement deposit is entered into the trust account for the right amount but a later disbursement to a medical provider is recorded against operating instead of trust, the control ledger won’t track the account accurately even if the matter file looks complete.
The third step is the one many firms underweight. Add every individual client trust ledger balance as of the same date and compare that sum to the control ledger.
If the control ledger matches the bank but the client ledgers do not add up, the trust account may still be balanced in the aggregate while being misallocated by matter. That creates an ethical problem, not just an accounting problem.
Examples include:
A practical worksheet helps here. Caseledge’s IOLTA reconciliation template gives firms a structured format for documenting the adjusted bank figure, control ledger amount, and client-ledger total in one place.
Software can accelerate the process, but it doesn’t remove judgment. A legal platform may generate the reports quickly. Someone still has to confirm that the underlying entries were posted to the correct matter and date.
For firms evaluating systems in this range, Practice Management for Small Law Firms is relevant as a shortlist resource because small firms often need a platform that handles matter management and trust-related workflows without requiring a separate accounting patchwork.
A visual walkthrough can help teams standardize the sequence before assigning responsibilities.
The point of the procedure isn’t speed. The point is proving that each client’s money is present, traceable, and correctly assigned at month-end.
A mismatch should be treated as evidence, not irritation. It signals either a timing item that has not been documented properly or a real error inside the books. Steph’s Books on IOLTA three-way reconciliation states that exact alignment is mandatory among the adjusted bank statement balance, the trust account master ledger, and the summed total of all client ledgers, and that even a one-dollar variance must be investigated and resolved before sign-off.
That requirement changes the mindset. The firm is not trying to make the report look balanced. It is trying to identify why the records diverged.
A disciplined investigation usually moves from the simplest causes to the most serious:
This sequence prevents a common mistake. Staff often jump straight into historical records when the issue is merely a report run with mismatched dates.
| Discrepancy type | Likely cause | Corrective action |
|---|---|---|
| Bank and books differ, client ledgers tie to books | Missing or mistimed bank-side item | Update reconciling items or record missing transaction |
| Books and bank tie, client ledgers don’t | Matter-level misposting | Move the transaction to the correct client ledger with full documentation |
| One client ledger is negative or unexpectedly low | Disbursement or fee transfer posted to wrong matter | Reverse and repost correctly, then document reason |
| Unknown small variance persists | Data-entry mistake or incomplete support | Trace transaction by transaction until source is identified |
A frequent example is the transposed amount. A deposit entered internally with digits reversed may not be obvious at the control-ledger level if later activity offsets the difference. The client-ledger review usually exposes it because one matter balance looks wrong even when the total discrepancy seems minor.
Another recurring issue is the unrecorded electronic item. Interest, a returned payment, or another bank-generated entry can appear on the statement before anyone books it internally. The corrective response is not to force the numbers together. It is to record the item appropriately and preserve supporting documentation.
A variance carried into the next month is not a reconciliation. It is an unresolved exception.
If a client cost was paid from trust when it should have been paid from operating, the correction needs to restore the proper client balance and create a clear audit trail. That means identifying the erroneous disbursement, entering the correcting transaction in the proper account, and preserving the explanation with the monthly packet. Silent cleanup entries are risky because they may balance the report while obscuring what occurred.
The hardest truth in trust accounting is that some systems can produce a balanced-looking result without producing a compliant one. That distinction sits at the center of software selection.
Accounting Atelier’s analysis of IOLTA reconciliations that do not really match identifies a neglected risk. Systems not built for IOLTA can invite “plug entries” that force a balance while hiding underlying record defects, and it notes that general accounting software such as QuickBooks cannot natively generate the required individual client ledger summary for this workflow.
The critical weakness is architectural. General business accounting tools are built to reconcile accounts at the account level. IOLTA compliance requires reconciliation at the client-matter level as well.
When software cannot produce a reliable client ledger summary, firms often resort to side spreadsheets, manual matter schedules, or ad hoc journal fixes. That is where phantom reconciliations appear. The bank ties out. The control ledger appears reasonable. But the third pillar, the client-by-client proof, exists only as a patched document assembled outside the accounting system.
That creates at least three risks:
For legal operations buyers, the useful question is not whether a vendor mentions trust accounting on a pricing page. The useful question is whether the platform can support the records needed for an authentic three-way reconciliation workflow.
Examples in the legal software market illustrate different approaches:
Some firms will still choose a mixed stack. Others will prefer a platform with trust and business accounting built into the same environment. The key point is that software should generate the records the reconciliation requires, not force staff to rebuild those records outside the system every month.
A report that balances after manual plug entries is not evidence of compliance. It is evidence that the firm needs to inspect the system design before the next audit does.
This is especially important for solo practice and small firm operators who inherited generic bookkeeping software from a prior consultant. The low-friction setup can become the high-risk setup once trust activity grows.
A reconciliation that isn’t documented might as well not exist. During a bar review, the firm needs more than a statement that the account was checked. It needs a record package showing what was reviewed, what differed, how it was resolved, and who accepted responsibility for the final match.
A defensible reconciliation file usually includes the month-end bank statement, the outstanding-check and deposit-in-transit detail, the trust control ledger, the client ledger summary, and the signed reconciliation page. The sign-off matters because responsibility for client funds cannot sit entirely with a bookkeeper. The process described in the earlier compliance guidance also emphasizes partner review and dated certification as part of an audit-ready routine.
In a mid-size firm, separation of duties is the cleanest control. One person enters transactions, another prepares the reconciliation, and a partner reviews and signs it. That reduces the chance that one employee can both create and conceal an error.
In a solo practice or a very small firm, full separation is often unrealistic. The alternative is independent review. That can mean an outside bookkeeper, accountant, or experienced administrator reviews the monthly packet before final sign-off. The point is not bureaucracy. The point is creating evidence that someone with authority examined the trust records.
Documentation turns a monthly task into proof of fiduciary conduct. Without the packet, a firm may remember that it reconciled. It cannot prove how it reconciled, whether a variance existed, or whether the issue was fixed properly.
Caseledge’s law firm bookkeeping article is a practical reference for firms formalizing monthly accounting controls alongside trust review. For software buyers, that broader bookkeeping process should sit next to procurement discussions, not after them. A weak system can produce weak records, and weak records are often what turn a correctable accounting mistake into a compliance problem.
Law firms comparing practice management platforms can use caseledge as a factual reference point for vendor reviews, pricing analysis, firm-size shortlists, and head-to-head legal software comparisons while evaluating how each option fits trust accounting and reconciliation workflows.