Can Software Prevent Trust Accounting Errors? What It Catches and What It Can't

Can software prevent trust accounting errors? Yes, for a specific class of them: the mechanical errors that come from mixing balances, re-keying numbers, and moving money without a matching record. No, for the judgment errors: a deposit a person assigns to the wrong client, a fee someone marks as earned too early, a reconciliation nobody runs, a call on disputed funds. Good trust accounting software makes the first group structurally hard to commit. The second group still depends on people, and the lawyer remains responsible for both.

Start with what software can’t catch

These come first because they’re the limits a firm has to plan around.

A deposit coded to the wrong client

A retainer check arrives, and someone records it against the wrong matter. The software will keep that client’s sub-ledger perfectly balanced, around the wrong number. One client now appears to have money they don’t, and another appears short. No system can know which client a check was meant for if the person entering it chooses the wrong one; it can only make the choice visible (a required client field, a source on every deposit) so a reviewer has something to check.

Withdrawing a fee before it’s earned

ABA Model Rule 1.15(c) says advance fees are “to be withdrawn by the lawyer only as fees are earned or expenses incurred.” Software can tie a transfer to an invoice. It can’t confirm the work behind the invoice was done. If someone bills ahead or marks a fee earned that isn’t, the transfer will look orderly and still be premature.

Not reconciling at all

A reconciliation compares records; software can prepare one, but someone has to sit down and do it, and do it on schedule. Required frequency depends on your state. Massachusetts, for example, requires a reconciliation report at least every sixty days, including a three-way reconciliation for accounts holding funds for more than one client matter. Washington’s RPC 1.15A(h)(6) requires trust records to be reconciled “as often as bank statements are generated or at least quarterly.” A system with perfect data and no one reviewing it still fails the rule.

Judgment calls on disputed funds

Model Rule 1.15(e) requires property claimed by two or more persons to be kept separate “until the dispute is resolved,” while undisputed portions are distributed promptly. Deciding what counts as disputed, and how much, is a lawyer’s call. Software can hold the funds once someone decides. It can’t make the decision.

Where can software prevent trust accounting errors?

The baseline for what a firm has to track is in Model Rule 1.15(a), which requires client funds to be held separate from the lawyer’s own and says “complete records of such account funds and other property shall be kept by the lawyer.” The ABA Model Rules for Client Trust Account Records spell that out: receipt and disbursement journals, a ledger for each client, bank records, and periodic reconciliations, with each state setting its own intervals.

Against that baseline, well-built trust software can turn several common trust accounting mistakes into things the system won’t let happen quietly.

Per-client sub-ledgers that keep balances apart. In a pooled account, the bank sees one number. A per-client sub-ledger tracks what each client actually has. When every deposit and withdrawal posts to a specific client, one client’s money can’t silently cover another’s invoice. Some states make this a bright line; Massachusetts says a lawyer “shall not disburse funds from the trust account that would create a negative balance with respect to any individual client.” Without per-client tracking, a firm can end up overdrawing a client’s trust funds without knowing it, because the account balance looks fine while one client’s balance has gone negative.

Transfers tied to invoices. When a trust-to-operating transfer can only happen against an invoice for that client, every withdrawal has a reason attached. That doesn’t prove the fee was earned, but it means an auditor can trace each dollar to a bill.

Records that land in the accounting system without re-keying. Each time someone retypes a transfer from one system into another, there’s a chance to get the amount, the date, or the client wrong. A trust system that writes transfers directly into the firm’s books removes that step. With one set of records to review, a firm expense paid from the wrong account is also easier to spot; if it does happen, here’s how to fix a firm expense paid from trust.

A record of who did what. For electronic transfers out of trust, the ABA’s model records rule calls for keeping the name of the person who authorized the transfer, the date, and the recipient, along with the bank’s confirmation. Software can attach those details to every transfer as it happens, instead of leaving someone to reconstruct them from emails months later.

A reconciliation that starts from clean data. Three-way reconciliation compares the bank statement, the trust account’s book balance, and the total of all client ledger balances. When client ledgers are complete and transfers were never re-keyed, a difference is more likely to mean something real, so the person reconciling spends time on actual discrepancies instead of typos.

Where LeanLaw fits

LeanLaw is built on QuickBooks Online and runs on it as the firm’s financial source of truth, so QuickBooks Online is a requirement. LeanLaw keeps a trust sub-ledger for each client, automates trust transfers, and lets firms pay an invoice from trust; those transfers, invoices, and payments land in QuickBooks Online without re-entry. Reconciliation, including three-way reconciliation, is performed in QuickBooks Online. More on how LeanLaw approaches trust accounting.

That covers the mechanical side. The judgment side is a matter of process: who enters deposits, who reviews them, who approves transfers, and who reconciles. Our internal control checklist for trust accounting is a practical place to start assigning those roles.

Whose name is on the account

Rule 1.15 puts the duty on the lawyer. The bookkeeper may enter the deposits and the administrator may run the reconciliation, but a bar audit or a client complaint about trust funds lands on an attorney at the firm, usually a managing partner. Software doesn’t change that, and no vendor should suggest it does.

What software can change is how much of the risk sits in places nobody is looking. When per-client balances can’t mix, transfers carry their invoices, and records reach QuickBooks Online without being typed twice, the remaining risk concentrates in a handful of human decisions. When an auditor asks for the client ledgers, journals, and reconciliations for a given period, the firm can produce them without a weekend of rebuilding. The decisions that remain are ones a partner can supervise: a review of new deposits, a sign-off on transfers, a reconciliation completed on the schedule your state requires. A firm that knows which errors its system prevents, and which ones it doesn’t, can put its oversight where the remaining risk is.