In this Article
A firm running 20 flat-fee closings a month can get by with less. A once-a-month reconciliation and a shared spreadsheet can still be technically compliant.
Scale that to 200 closings a month, and bookkeeping often breaks down. The rules haven’t changed. High volume just amplifies the cost of small errors.
Why Flat-Fee Volume Breaks the “Normal” Trust Bookkeeping Model
High volume and thin margins eliminate the buffer that once absorbed minor errors.
At low volume, a misapplied disbursement gets caught fast. So does a ledger that’s off by $40. Someone has time to look closely at each file.
At high volume, margins are thin per file. The same error type can recur across dozens of files before reconciliation catches up. Tracing it back to the source file is genuinely hard, not just tedious.
Flat-fee billing removes another safeguard too. Hourly billing forces periodic review, because someone has to log time entries.
A flat fee collected at intake and disbursed at closing has no equivalent checkpoint. Nothing forces a second look at a file’s trust activity between open and close. The bookkeeping process has to intentionally build that check-in.
⚠️ Watch Out: A monthly cadence that worked at low volume doesn’t scale linearly. At high volume, the same monthly cycle covers more transactions. That means more places for an error to hide before it’s found.
Every Closing Still Needs Its Own Client Ledger; the Fee Structure Doesn’t Change That
The ABA Model Rules on Client Trust Account Records set the baseline. Most states follow this general framework. Attorneys must maintain an individual ledger for each client or matter, not just a running total for the trust account as a whole. That requirement doesn’t bend for volume or fee structure.
A shortcut we see at high-volume shops: batching multiple same-day closings under one “closing department” ledger to save data-entry time. Individual files get tracked informally, outside the trust ledger. This fails the basic test a reconciliation or bar audit applies. Can you show the exact balance held for any single client or matter at any point in time? A batched ledger can’t answer that without reconstruction work. And that reconstruction work is itself a finding.
At minimum, a compliant per-file ledger shows three things: the date and source of each deposit, the date, amount, and payee of each disbursement, and a running balance. All of it matched to that specific closing, not a shared pool.
💡 Pro Tip: If your bookkeeping process requires someone to “figure out which closing that deposit belonged to” after the fact, the ledger structure is the problem. Volume isn’t.
Three-Way Reconciliation at Volume: Monthly Isn’t Enough
Three-way reconciliation compares three numbers that should always agree: the bank statement balance (adjusted for outstanding items), the checkbook or register balance, and the sum of every individual client ledger balance in the trust account. If two of the three agree but the third doesn’t, that’s your entry point. Somewhere there’s a missed deposit, a duplicate disbursement, or a fee pulled from the wrong file.
Quarterly is typically treated as a floor. Monthly is recommended as standard practice. At low volume, monthly is usually enough to catch problems while they’re still traceable.
At high volume, a month is long enough for the same error to recur across many files before reconciliation surfaces it. Once it has, isolating which closings are affected takes time. A thin-margin practice doesn’t have much time to spare.
The practical fix isn’t reconciling more often in the abstract. It’s tying reconciliation to closing cycles instead of the calendar. Reconcile in smaller batches, weekly or after every closing day. That keeps each reconciliation small enough to actually review. Compare that to one month-end reconciliation covering hundreds of transactions, rubber-stamped because no one has time to check it line by line.
When Is the Flat Fee Actually Earned? This Is Where Volume Shops Get Sloppy
This is the piece that’s specific to flat-fee closings. It’s where we most often find problems in practice.
Client funds collected as flat fees prior to closing must remain in trust until the underlying services are fully rendered. This is easy to manage for individual files. But higher volumes create a temptation: batch-transferring earned fees out of trust every week. Fees must be disbursed for each individual file when they’re earned, not through aggregate periodic transfers.
Here’s the distinction. “Earned” isn’t the same moment for every closing. A file that closes cleanly on schedule earns its fee at a different point than one that closes three weeks late after title issues. Both may be identical flat-fee engagements. A batch sweep treats them as identical anyway. That means some fees get moved out of trust before the work they’re tied to is done.
⚠️ Watch Out: Moving unearned fees out of trust is a problem even briefly, even if the file closes successfully days later. Most jurisdictions treat it as commingling or a premature withdrawal, regardless of whether the client was ultimately harmed. Intent isn’t usually the deciding factor.
The safer structure ties each transfer to that specific file’s closing event. Document it in that file’s ledger. Don’t size a periodic batch transfer to whatever closed that week.
Disbursement Timing and “Dead Money” Left Behind
Two related issues show up almost exclusively at volume. At low volume, they get noticed individually and fixed fast.
First: outstanding or uncleared checks. They distort a reconciliation until they clear or get voided and reissued. At volume, a handful of uncleared checks sitting for weeks looks like normal noise. It isn’t. Forty files deep, with no aging report to catch it, it’s a real problem.
Second: small residual balances. A rounding difference. An unissued refund. An overestimated fee left in a file after disbursement. Any single one looks trivial. Across several hundred closed files, unresolved residuals add up to real, untracked trust liability. Most jurisdictions eventually require unclaimed funds to be returned to the client or escheated as unclaimed property after a defined period. They can’t sit indefinitely.
💡 Pro Tip: Run an aging report on open trust ledger balances. Flag anything with a nonzero balance more than 30 days after closing. This catches both problems before they pile up at year-end.
Segregation of Duties Doesn’t Scale Itself
A common structure at growing volume shops: one bookkeeper handles both data entry and reconciliation. Hiring a second person feels like an unjustifiable cost against thin per-file margins.
This is a control weakness regardless of whether anything has actually gone wrong. The same person entering transactions and verifying them removes the check that catches honest mistakes. It also removes the check that catches misappropriation, in the rare cases it happens. An examiner will flag the structure itself, not just evidence of an actual problem.
This doesn’t require a large team at minimum viable scale. It requires one other set of eyes on the reconciliation, someone who didn’t do the data entry. Even a supervising attorney doing a monthly review is enough. A dedicated second bookkeeper isn’t required.
Choosing a Bookkeeping Workflow Built for Volume, Not Adapted to It
Spreadsheet-based trust ledgers tend to work at low volume. So does general small-business bookkeeping software repurposed for trust accounting. Both degrade past a threshold, usually somewhere in the range of a few dozen open files at once. The tool isn’t wrong in principle. The manual reconciliation steps that were manageable at low volume become the bottleneck.
What tends to hold up at volume: per-file ledger structures that generate automatically from each new matter. Clean data transfer between closing or escrow software and the trust ledger, to avoid duplicate manual entry. A built-in audit trail on every transfer out of trust, showing who authorized it, which file it’s tied to, and when.
None of this replaces the discipline described above. It just makes that discipline sustainable once closing count outpaces what one person can track by memory and habit.
Conclusion
Volume and thin margins don’t lower the bar for trust accounting rigor. They raise the cost of skipping it. Errors compound across more files before anyone catches them, and margin is too thin to absorb the cleanup.
The fixes are mostly structural, not exotic: a genuine per-file ledger for every closing, regardless of fee structure. Reconciliation cadence tied to closing cycles rather than the calendar. Fee transfers tied to the specific file’s earning event, not batched. An aging report on open balances. A second set of eyes on reconciliation.
Has your practice’s closing volume grown faster than your bookkeeping process? The lowest-risk next step is a books review or process audit now, while any gaps are still small and traceable. Don’t wait for a bar audit or a client complaint to force the question. And because trust accounting requirements differ by state, pair any process change with a check against your own state bar’s current rules or your malpractice carrier’s guidance.
At The Chamberlain Accounting Firm, we regularly work with attorney trust accounts. Our practice is to check your reconciliation, client ledgers, and record-keeping against New Jersey’s requirements every week, and tell you exactly where you stand.
Contact us or call (201) 371-3344 if you want to ensure your books comply with the New Jersey IOLTA rules.
Frequently Asked Questions
Monthly is the usual floor most bar rules recommend. But at high volume, monthly isn't enough. Tie reconciliation to closing cycles instead. Weekly, or after every closing day, keeps each review small enough to actually check.
No. Every client or matter needs its own ledger, regardless of fee structure or closing volume. A batched "closing department" ledger can't show the exact balance held for a single client at a given moment. That fails a bar audit test.
A flat fee is earned when the underlying work for that specific file is done, not on a fixed weekly schedule. Batch-transferring fees out of trust before each file's work is complete can be treated as commingling, even if the file later closes without issue.
Disclaimer: This article is provided for general informational purposes only and does not constitute accounting, tax, or financial advice. The information contained herein is not intended to be relied upon for specific tax, accounting, or financial decisions, and may not reflect current tax law or guidance. No opinion expressed herein may be used for the purpose of avoiding penalties under federal, state, or local tax laws. Readers should consult with a qualified accounting or tax professional regarding their specific circumstances. This communication does not create an accountant-client or advisory relationship.
