Legal Marketplace Payments: Trust Accounts, Earned Fees and Client Funds

Route legal payments by whose money it is#

A legal marketplace cannot treat every payment as ordinary platform revenue followed by a provider payout. Client advances, earned legal fees, settlement proceeds and the firm’s payments to staff or vendors have different owners and purposes. Determine that character before selecting the destination account. A processor balance, wallet label or split-payment feature does not establish that client funds are being held in a compliant lawyer trust account.

ABA Model Rules provide a starting point, while the jurisdiction’s adopted rules and other applicable law govern the actual arrangement. This guide uses the Model Rules and Washington’s published trust-account rules to show concrete controls. It does not approve a platform’s business model in every state. Map the lawyer, client, platform, payer, bank and processor for each proposed flow.

Trust funds and operating money need different destinations#

Model Rule 1.15 requires separation of client/third-person property, records, advance-fee/expense deposits into trust until earned or incurred, and prompt delivery of amounts to their entitled recipients. Disputed portions remain separate while undisputed portions are promptly distributed. These duties cannot be replaced by a platform-wide “payment pending” status.

The table describes common fund characters, not universal account treatment for every fee agreement. Some states have specific retainer or flat-fee exceptions. Washington’s RPC 1.15A references its Rule 1.5(f) exceptions. Confirm the actual agreement and rule rather than deciding that any payment called a “retainer” belongs in operating funds.

Washington’s account selection turns on the net return to the client: qualifying small/short-held funds use pooled IOLTA, while positive-return funds follow its client-interest account requirements. IOLTA is not a generic escrow wallet.

A concrete model: client pays the firm’s designated account#

For an initial product design, consider routing the client directly through an approved processor to the firm’s correctly designated account, with the platform supplying scheduling, invoice references and controlled records. Have the firm’s responsible lawyer approve trust disbursements. This can reduce platform custody touchpoints, but it does not automatically resolve fee sharing, confidentiality, unauthorized practice or payment-service obligations.

A platform that collects into its own pooled balance and later pays several firms needs a different analysis. Identify the legal owner of funds at every holding point, who may authorize movement and what happens if the platform or processor fails. Do not describe the platform’s balance as the lawyer’s trust account merely because the platform has a client subledger. Software records support an account arrangement; they do not create it.

Before offering either model, confirm supported trust/operating destinations, fee debits, chargeback funding, reserves and bank settlement with the processor and responsible lawyer. Require an actual sample of gross payment, fee, deposit and any return. A vendor’s statement that it serves law firms is useful for discovery, but your configuration and agreement determine how this particular payment moves.

Worked trust ledger: two clients and one earned fee#

Assume a properly established trust account receives collected advance deposits of $5,000 for Client A and $3,000 for Client B. Opening client balances were zero. The firm has earned and properly billed $1,500 on A’s matter, with required notice completed and no dispute over that fee. An authorized $500 court cost for A is incurred and paid to the named recipient. All figures are illustrative; no tax or other transactions are included.

The firm separately pays a paralegal $400, a hypothetical approved software subscription $100 and a $150 processor charge from operating funds. Of the $1,500 transferred earned fee, $850 remains before other operating expenses: $1,500 − $400 − $100 − $150. Those operating payments do not reduce B’s $3,000 or silently use A’s remaining advance. This software-charge example assumes its commercial structure has already passed the applicable legal review.

Washington requires collected deposits before disbursement subject to its bank-guarantee exception, notice before earned-fee withdrawal, and no cross-client funding. In the example, check A’s deposit and balance; the account’s total alone cannot explain which client funded the instruction.

Hold the disputed amount and distribute the undisputed portion#

Continue the example: A requests return of the remaining $3,000. The lawyer claims $600 of additional fees and A disputes that claim. Assume A is entitled to the other $2,400 and no other restriction applies. Keep $600 in trust while taking the required steps to resolve the dispute; promptly refund the undisputed $2,400. The total trust book balance becomes $3,600: A’s disputed $600 plus B’s untouched $3,000.

Do not freeze B’s balance or A’s undisputed refund because one fee claim is disputed. Washington RPC 1.15A(g) addresses both retention and prompt distribution of undisputed portions. Give the case a responsible lawyer, next action and preserved accounting history. A platform’s general risk label cannot decide entitlement or justify an indefinite blanket hold.

A chargeback creates a separate payment event requiring immediate reconciliation and legal review. It is not automatically a resolution of the fee dispute, permission to debit another client’s balance or an instruction to pay the lawyer twice. Use the agreed proper funding source for fees and reversals; if a trust shortfall occurs, escalate restoration and applicable reporting without using unrelated client money.

Three-way reconciliation means bank, trust books and client ledgers#

Trust reconciliation compares the adjusted bank balance, trust-account register/book balance and combined client-ledger balances. Provider events add transaction evidence but do not replace any of those three components. Washington’s Monthly Reconciliation and Review Report lays out this comparison and the supporting statements, outstanding items and client records.

For a separate illustrative month-end, suppose the bank statement ends at $3,800 and one $200 disbursement recorded in the books has not cleared. There are no outstanding deposits. Adjusted bank balance is $3,800 − $200 = $3,600. It should match a $3,600 trust register and client balances totaling $3,600. The outstanding item must have its own supporting client allocation; matching totals does not excuse missing or negative individual records.

Investigate any discrepancy by receipt, disbursement and client. A $100 unexplained reduction is not solved by reducing every client ledger proportionately. Reconstruct the actual fee, posting error or unauthorized movement, obtain the responsible decision and retain the correction. Check negative client balances separately even when the overall bank account is positive.

The current Washington rule calls for reconciliation as often as bank statements are generated, or at least quarterly. A monthly statement therefore requires a monthly reconciliation, and the WSBA form supplies a monthly operating template. Do not misstate monthly as an identical statutory frequency across every jurisdiction. Set the cadence to the actual state rule and account statements.

Third-party payment does not make the payer the client#

Model Rule 1.8(f) permits compensation from another person only with the client’s informed consent, no interference with professional judgment or the lawyer-client relationship, and protection of representation information under Rule 1.6. Map those conditions to the adopted local rule before accepting a parent’s, employer’s or other funder’s payment.

For example, a parent paying an adult client’s advance may receive an authorized payment receipt without receiving the client’s case notes or strategy. Record the client’s consent and permitted disclosures, then restrict payer access accordingly. Do not make the lawyer’s advice or an undisputed distribution conditional on the payer approving the strategy. Resolve who is entitled to any refund from the actual arrangement; the payment-card holder alone does not settle that question.

Platform fees and paralegal compensation need their own review#

Model Rule 5.4 generally prohibits sharing legal fees with nonlawyers, subject to specified exceptions, and protects independent professional judgment. A platform keeping 10% of every lawyer fee therefore raises a different question from charging for ordinary software. Calling the percentage a “technology fee” does not resolve its substance. Adopted state rules and authorized alternative arrangements can differ.

A fixed subscription is also not automatic clearance: assess the actual advertising/referral arrangement, fee reasonableness, ownership and unauthorized-practice issues. Keep the platform fee agreement and payer separate from the client advance. If the fee model is unresolved, do not enable automatic deductions from legal-service receipts while treating review as a later paperwork task.

Paralegal compensation in the ordinary firm model is payment for supervised work from operating funds. It is not an automatic entitlement to a percentage of client trust money. Model Rule 5.3 addresses lawyer responsibilities for nonlawyer assistance. Separate the compensation agreement from client billing and authorized client-cost disbursements, and verify local rules for any different service model.

Map one jurisdiction before expanding#

Use a launch record with the adopted trust rule, fee classification/exception, qualified account, authorized signatory, fee-sharing analysis, third-party consent and reporting/retention requirements. For Washington, RPC 1.15A supplies the fund-handling rules and RPC 1.15B specifies account/client records and at least seven-year retention after the recorded events. That is a concrete jurisdiction map; it is not an ABA-wide seven-year rule.

Preserve fee/cost agreements, bills, client accountings, supporting disbursement documents, bank evidence and reconciliations. The platform’s export should connect those records through matter and transaction references with controlled access. Expose enough for finance to trace funds while avoiding unnecessary representation details in processor metadata or support logs.

The launch diagram illustrates the record categories, not an approval or rejection of the pictured states. For a new jurisdiction, populate it with that jurisdiction’s actual authorities and the proposed funds flow. Resolve account and fee-model blockers before accepting new funds; preserve prompt lawful delivery of existing undisputed amounts during any operational repair.

Payment integrations also need stable disbursement identifiers, separate attempts and durable event history. Recover an unknown external outcome before replacement; one reusable request key has only the provider’s documented scope and lifetime. A corrected account or callback must not generate a second client obligation. Keep the lawyer’s authorization and account/client allocation attached to every attempt.