Inside LawAccounting's Multi-Bank Account Engine: How Firms Run Operating, IOLTA, Escrow, and Payroll Accounts Side by Side Without Ever Crossing the Line

Most law firms do not have one bank account — they have five or six, and at least two of them are legally untouchable. This feature spotlight walks through how LawAccounting's multi-account architecture handles operating, IOLTA, non-interest client trust, escrow, and payroll accounts in one ledger, with deposit tracking, per-account reconciliation, and hard boundaries that stop a transfer before it becomes a bar complaint.

Published: 2026-08-17T12:12:45.507Z · Category: Trust Accounting · 7 min read

💡 IN SHORT

A mid-market law firm typically runs an operating account, a pooled IOLTA account, one or more separate interest-bearing client trust accounts, sometimes a real-estate or settlement escrow account, and a payroll account. Generic accounting software treats all of these as interchangeable "bank accounts." LawAccounting does not. Each account carries a type, a set of permitted transaction rules, its own reconciliation cycle, and its own compliance posture — so the software itself prevents the movements that produce commingling findings.

👥 Who should read this: Managing Partners Firm Administrators Law Firm Controllers Trust Account Signatories

🏦 The Problem: Not All Bank Accounts Are the Same Kind of Object

Open any general-purpose accounting system and add a bank account. You will be asked for a name, a number, and an opening balance. That is the entire model. Every account you create behaves identically: money can move between any two of them, any transaction can be coded to any of them, and reconciliation is the same procedure everywhere.

That model is fine for a manufacturing company. It is structurally wrong for a law firm, where the difference between two accounts is not administrative — it is the difference between a routine transfer and a rule violation.

🚫 Red Flag

If your accounting system allows a one-click transfer from your IOLTA account to your operating account with no earned-fee documentation, no matter-level validation, and no approval step, your software is not protecting you. It is a neutral tool sitting between you and a bar complaint — and neutrality is not a defense during a compliance review.

🧩 How LawAccounting Models Accounts Differently

In LawAccounting, a bank account is a typed object. The type determines what the system will and will not let you do with it.

🏛️

Operating Account

Firm funds. Full flexibility — AP, payroll funding, expense reimbursement, earned fee deposits. Standard reconciliation, no client-level ledger required.

🔒

Pooled IOLTA

Client funds. Every transaction must carry a matter. Balances tracked per client ledger. Negative matter balances blocked. Three-way reconciliation required.

💠

Separate Interest-Bearing Trust

For large or long-held client funds where interest belongs to the client. Same matter-level rules as IOLTA, plus interest allocation to the client ledger.

📜

Escrow / Settlement Account

Third-party funds — real estate closings, settlement proceeds pending lien resolution. Disbursement controls, payee validation, and hold tracking.

👥

Payroll Account

Funded from operating on a schedule. Segregated so payroll timing never distorts operating cash visibility or triggers a false overdraft alert.

💳

Merchant Settlement Routing

Card and ACH payments route by payment type — earned fees to operating, advance retainers to trust — with processing fees never drawn from client funds.

🚦 The Rules Engine: What the System Refuses to Do

The value of a typed account model is what becomes impossible. LawAccounting enforces boundaries at the point of entry rather than surfacing them during a year-end review:

No matterless trust transactions. A deposit or disbursement in a trust-type account cannot be saved without a matter. There is no "miscellaneous" bucket in a client trust account, because there is no such thing in the rules.
No negative client ledgers. A disbursement that would push a single matter's trust balance below zero is blocked, even when the pooled account has plenty of money in it. One client's funds can never quietly cover another's.
No undocumented trust-to-operating transfers. Moving earned fees out of trust requires an underlying invoice or fee entry. The transfer is generated from the earned amount, not typed in freehand.
No processing fees against client funds. Merchant fees on a trust deposit are drawn from operating, never netted out of the client's balance.
No cross-type journal entries without approval. Any entry touching both a trust-type and a non-trust account routes through an approval workflow and lands permanently in the audit trail.

⚠️ Watch Out

The most common commingling finding is not theft — it is convenience. A firm leaves earned fees sitting in IOLTA because nobody ran the transfer, or funds an unexpected filing fee from trust before the client's replenishment clears. Both are unintentional. Both are still violations. A rules engine that blocks them in the moment removes the judgment call from a busy Friday afternoon.

🔄 Per-Account Reconciliation, Not One Big Reconciliation

Because each account is typed, each account reconciles on its own cycle with its own procedure.

💼 Operating and Payroll Accounts

Standard two-way reconciliation: beginning balance, cleared deposits, cleared payments, statement ending balance, difference detection. LawAccounting's AI matching engine connects across 15,000+ banks and proposes matches for the bulk of the register automatically, leaving the accountant to resolve exceptions rather than tick and tie every line.

🔐 Trust and Escrow Accounts

Three-way reconciliation, which is a different exercise entirely. Three numbers must agree at the same cutoff date:

Balance	Source	What a Break Means
Adjusted bank balance	Bank statement + deposits in transit − outstanding checks	Timing item, or a transaction never entered
Trust GL / book balance	General ledger trust cash account	Posting error or unapproved journal entry
Sum of all client ledgers	Every matter's individual trust balance, added up	❌ The dangerous one — funds allocated to the wrong client

When those three do not match, LawAccounting isolates the break rather than reporting a single unhelpful difference figure — showing which matters changed, which transactions are unmatched, and which entries posted outside the normal workflow.

📊 Did You Know?

Three-way reconciliation has moved from best practice to explicit requirement in a growing number of states, with several jurisdictions tightening both the frequency and the documentation standard through 2026. The practical implication for multi-account firms is that every trust-type account needs its own three-way reconciliation on its own schedule — a pooled IOLTA and a separate client trust account are two separate compliance obligations, not one.

📥 Deposit Tracking Across Accounts

Multi-account firms lose more time to deposit ambiguity than to reconciliation itself. A single client payment might need to split across three destinations: earned fees to operating, an advance cost deposit to IOLTA, and a filing fee reimbursement to operating.

LawAccounting handles this as a single deposit event with split routing. The payment is recorded once, allocated by component, and each component lands in the correct account with the correct matter attribution. The client's ledger reflects one payment; the firm's books reflect three correctly-typed postings.

💡 Pro Tip

Set a standing rule that any client payment received without written allocation instructions goes to trust first, then gets applied to invoices from there. Trust-first is always the recoverable error. Operating-first, when the money turns out to have been an advance deposit, is a commingling event you have to unwind and explain.

🧭 What This Looks Like on a Monday Morning

A firm running LawAccounting with five accounts opens a single dashboard and sees, per account: current balance, uncleared items, last reconciliation date, and any open compliance alerts. Trust accounts additionally display total client ledger sum and any matter approaching a zero balance.

The administrator's first action of the week is not assembling that picture from five bank portals and a spreadsheet. It is responding to the two exceptions the system already surfaced.

⚖️ The Verdict

Multi-account complexity is not an edge case for mid-market law firms — it is the normal condition. The question is whether your accounting system understands that an IOLTA account and an operating account are categorically different objects, or whether it treats them as two rows in the same table and leaves the distinction entirely to human discipline. LawAccounting encodes the distinction. That is the difference between software that records compliance and software that enforces it.

✅ Key Takeaways

Law firms run multiple account types — operating, pooled IOLTA, separate client trust, escrow, payroll — and generic accounting software models them all identically.
LawAccounting types each account, so the rules engine blocks matterless trust entries, negative client ledgers, undocumented trust-to-operating transfers, and fees drawn from client funds.
Operating accounts reconcile two ways with AI matching across 15,000+ banks; trust and escrow accounts require three-way reconciliation, each on its own schedule.
The client ledger sum is the most important of the three trust balances — a break there means funds are allocated to the wrong client.
Split deposit routing lets one client payment land correctly across operating and trust in a single recorded event, with full matter attribution.

See Every Account, Every Balance, One Screen

Watch LawAccounting run operating, IOLTA, escrow, and payroll accounts side by side — with three-way reconciliation, AI bank matching, and compliance rules that stop violations before they post.

Schedule Your Demo →