Trust Accounting & IOLTA

Compiled: 2026-03-18 — Product research for law firm software vertical (Trust Accounting module design). Sources: ABA, state bar websites, competitor product pages, market research firms, legal tech publications.

1. What Is IOLTA / Trust Accounting?

Every attorney who handles client money — retainers, settlement funds, escrow deposits — is legally required to hold those funds in a separate trust account, entirely segregated from the firm’s operating funds. These accounts are called IOLTA accounts (Interest on Lawyers’ Trust Accounts).

• The interest earned goes not to the attorney or the client, but to the state’s legal aid fund. This is mandatory in all 50 states and DC.
• The principal always belongs to the client until it is earned by or released to the firm.
• Commingling client funds with firm funds — even accidentally, even briefly — is a disciplinary offense that can result in suspension or disbarment.

2. Core Compliance Requirements (All States)

The Three-Way Reconciliation (Non-Negotiable Core Feature)

Three components that must agree:

1. Bank statement balance — what the financial institution shows
2. Trust ledger balance — the firm’s running total of all trust activity
3. Sum of all client sub-ledger balances — each individual client’s running balance, added together

If any two of these three numbers don’t match, there is a compliance problem. State bars require this to be performed monthly, documented in writing, signed off by an attorney, and retained for audit review.

3. State-by-State Variations

Audit Frequency

4. Competitive Landscape

Tier 1: Full Trust Accounting Native (Best-in-Class)

CosmoLex

Positioning: “The only legal practice management software with full legal accounting built in.”

Pricing: $89/user/month (annual) / $99/user/month (monthly)

TrustBooks (Standalone Specialist)

Positioning: Purpose-built trust-only accounting software; integrates with Clio, LawPay.

Pricing: $59–$249/month (firm-level, not per-user)

Tier 2: Strong Trust Accounting within Full PM Platform

5. Common Pain Points

1. Manual Reconciliation Is a Time Sink. Firms not on purpose-built software spend hours per month manually comparing three data sources. The manual process is also the primary source of bar violations.
2. Overdraft Notification Is Terrifying. In most states, if a trust account is overdrawn even by $1, the bank is required to notify the state bar automatically. This triggers an investigation regardless of cause.
3. QuickBooks Doesn’t Know the Rules. QuickBooks has no concept of trust accounting rules — it will happily let you commingle, overdraft, or mis-record transactions. Estimate: 30–40% of small firms use QuickBooks or spreadsheets.
4. Software That Doesn’t Match State Rules. Most platforms don’t surface jurisdiction-specific requirements clearly.
5. Payment Processor Fees in Trust. If a processing fee is deducted from the trust account, that is a violation. Compliance-aware processors route fees to the operating account. Generic processors (Stripe, Square) do not.
6. Disconnected Systems Create Reconciliation Gaps. When billing software and trust accounting are in separate systems, every transaction requires double-entry and manual reconciliation.
7. Reporting for Audits Is Ad-Hoc. Audit-ready reporting should be one-click. It rarely is.

6. Market Data

• $1.2B — global trust accounting software market value (2023)
• $3.5B — projected market by 2033, CAGR 11.3%
• 78% of law firms use financial management software with trust accounting as a key selection criterion (ABA 2022)
• 10% of lawyers faced disciplinary action for trust account violations in 2021
• ~25% of all attorney disciplinary actions involve trust account violations
• 83% of California firms had non-compliant trust journals in state bar audit sampling; 89% had non-compliant client ledgers; 83% failed three-way reconciliation — yet 94% achieved compliance once given proper tools

7. Module Design: Trust Accounting

Core Feature Set (MVP)

Architecture Considerations

• Ledger integrity: Trust ledgers must be append-only. No editing or deleting past transactions — only correcting entries with a new transaction and audit trail note.
• Double-entry backbone: Every trust deposit credits the client’s sub-ledger and debits the trust bank account. Must be enforced at the database level.
• Bank reconciliation state machine: unreconciled → reconciled → locked. Locked periods cannot be edited.
• Immutable audit trail: Every write operation creates an audit log entry. Cannot be modified by any user, including admins.

8. Integration with Other Modules

Trust Accounting ↔ Billing (Critical Integration)

1. Client pays retainer → Trust Accounting receives and records deposit to client sub-ledger
2. Attorney performs work → Billing tracks time and generates invoice
3. Invoice approved → Billing signals Trust Accounting to apply trust funds
4. Trust Accounting records disbursement from client sub-ledger
5. Earned amount transfers to operating account (separate transaction, separate ledger)
6. Invoice marked paid in Billing

9. Pricing Recommendation

10. Regulatory Risk

The attorney bears 100% of the liability. Software vendors do not accept legal liability for bar violations caused by their software. If a bug in Trust Accounting causes an erroneous disbursement, the attorney faces:

1. Bar investigation — overdraft reports are automatic; any complaint triggers audit
2. Disciplinary action — censure, suspension, or disbarment depending on nature and amount
3. Civil liability — clients can sue for misappropriated funds
4. Criminal exposure — intentional misappropriation is embezzlement

Trust accounting is a zero-defect domain. Overdraft prevention must be a hard constraint at the database level, not a UI warning. All write operations must be atomic.