Trust Account Compliance and Payment Processing: An Evaluation Guide for Law Firms

Law firms evaluating payment processors for trust account use need to verify more than product claims. Fund routing, fee separation, dispute protection, and audit trail requirements are set by ABA Model Rule 1.15 and state bar rules, and each one needs to be built into the payment platform itself rather than managed around it. Most general-purpose processors were not designed to handle that level of specificity. This piece explains what compliance actually demands, how to evaluate the processors available to law firms, and what to verify before going live.

IOLTA (Interest on Lawyers' Trust Accounts) is a state-administered program that pools interest earned on short-term or nominal client funds held in lawyer trust accounts and directs those funds to legal aid and bar programs. See the ABA's IOLTA program overview for a full program description.

The obligation to hold client funds in a separate trust account comes from professional conduct rules — not from IOLTA program requirements themselves. Not all client funds must go into an IOLTA account. Only funds that are nominal in amount or held for a short period — where the interest earned would not justify a separate interest-bearing account for the client — belong in IOLTA. Larger or longer-term client funds should be held in a separate interest-bearing account for the client's direct benefit.

Legal payments were held back for years not by resistance to change, but by compliance requirements that most general-purpose payment platforms were not designed to support. The destination of funds matters. The timing of transfers matters. The documentation matters. The audit trail matters. When those requirements are not built into the payment workflow, firms are forced to build manual processes around the gap.

ABA Model Rule 1.15 establishes the baseline requirements for how lawyers must safeguard client funds and property.

• Rule 1.15(a): Client funds must be held in a separate account, distinct from the firm's own property. Complete records must be maintained for a minimum of five years after the representation ends.

• Rule 1.15(c): Advance fees and cost deposits must be placed in the trust account and withdrawn only as fees are earned or expenses are incurred.

State bar associations layer jurisdiction-specific requirements on top of this baseline. Firms must confirm rules with their specific state bar before selecting a payment processor.

The four ABA Model Rule 1.15 compliance requirements that directly affect payment processing:

Fund segregation:

Client funds must be held in a trust account separate from the firm's operating account. A payment processor must be able to route funds to the correct account based on transaction type — Rule 1.15(a)

Fee separation:

Processing fees cannot be deducted from trust account deposits. Fees must be billed to the firm's operating account or passed to the payer as a permitted convenience fee — Rule 1.15(c); Oregon Bar Formal Opinion 2005-172.

Chargeback and return protection:

Card chargebacks and ACH returns must resolve against operating funds, not trust balances. A reversal that hits the trust account directly creates an underfunding violation regardless of intent.

Audit trail and records:

Client-level transaction records must be retained for a minimum of five years after representation ends, and must support three-way reconciliation for state bar audits — Rule 1.15(a).

Card payments introduce two specific risks for IOLTA trust accounting.

Fee deduction risk: Some processors settle net of fees — the processing fee is deducted before the deposit reaches the destination account. If that deduction hits a trust deposit rather than being billed to the firm's operating account, the trust account is underfunded. That shortfall is a Rule 1.15(c) violation regardless of intent. Oregon Bar Formal Opinion 2005-172 addresses this directly: lawyers may not credit client accounts with the net amount of a credit card transaction after service charges are assessed.

Chargeback and dispute risk: Card payments carry dispute windows — typically 60 to 120 days depending on card network rules. A client who pays a retainer by card and later initiates a chargeback can trigger a reversal. If the processor is not configured to route disputes against operating funds, that reversal can hit the trust account directly.

ACH reduces, but does not eliminate, dispute risk for trust deposits. ACH payments do not carry card-style chargebacks, but they are subject to reversal and return under NACHA Operating Rules and Regulation E. Originators may reverse entries within five banking days for specific permissible errors. Consumers can dispute unauthorized debits within 60 calendar days under Regulation E. ACH disputes are narrower in scope and shorter in window than card chargebacks, which makes ACH meaningfully lower-risk for trust deposits — but processors still need to be configured to handle ACH returns against operating accounts, not trust balances. An ACH-first approach for larger trust deposits — with card accepted for lower-dollar invoices and consultation fees — reduces both compliance exposure and processing costs.

On convenience fees and IOLTA: Some state bars permit passing processing fees to the client as a convenience fee, which eliminates the fee deduction problem for the trust account. Rules vary by jurisdiction. NYSBA Ethics Opinion 1258A (2024) permits passing merchant processing fees to clients provided the fee is reasonable and the client consents in advance. Oregon and North Carolina have issued similar guidance with jurisdiction-specific conditions. Firms should confirm what their state bar permits before implementing a convenience fee model, and obtain written documentation from their processor confirming how fees are handled relative to trust deposits.

Eight capabilities to verify — and request written documentation for — before selecting a processor:

• Trust and operating account routing configured at the platform level, not managed manually per transaction. See Payload's Processing Accounts documentation as an example of how this is documented by a compliant processor.

• Processing fees never deducted from trust account deposits — fees billed to operating or passed to the payer as a permitted convenience fee under applicable state bar rules.

• Card chargebacks and ACH returns resolved against the operating account, not the trust account.

• Client-level transaction records with matter or case tagging for bar audit preparation, retained in line with Rule 1.15(a)'s five-year minimum.

• Three-way reconciliation reporting that maps to state bar audit requirements.

• ACH, Same Day ACH, RTP, and card payments supported on a single platform.

• Payment links and invoicing that fit the legal billing workflow — client-facing, with automated reminders and recurring billing for retainer replenishment.

• Outbound payment support for settlement disbursements, co-counsel fees, referral payments, and client refunds from trust.

Law firms send money out as well as in. A processor that handles only inbound collections requires a separate payables solution, which creates reconciliation gaps and additional compliance surface area.

Compliance verification: ABA Model Rule 1.15 and state bar ethics opinions set the baseline for trust account handling. Before going live with any processor, request written documentation confirming how processing fees, card chargebacks, and ACH returns are handled relative to trust accounts, and confirm alignment with your state bar's specific IOLTA rules.

Two categories of payment platforms serve law firms, and the distinction matters before any evaluation begins.

The first are legal-specific tools built around a single vertical. These typically offer turnkey client billing — payment links, invoicing, and trust routing for the most common legal payment scenarios. They are designed for firms that want a quick setup and do not need deep API access or multi-directional money movement. IOLTA compliance is built around the narrow set of workflows those tools support.

The second are full-platform processors that build compliance configurations into their core infrastructure. Fund routing, fee separation, dispute resolution paths, and audit trail requirements are handled at the platform level — not addressed by manual workarounds. These processors can handle both inbound collections and outbound disbursements, expose those configurations through an API for legal tech platforms embedding payments, and support payment rails beyond the basics.

For firms with straightforward billing needs and no plans to integrate payments into practice management software, a legal-specific tool may be sufficient. For firms that handle outbound payments alongside collections, operate across multiple practice groups or matter types, or use legal tech platforms with embedded billing, a full-platform processor built for compliance-critical industries is the more defensible foundation. The compliance requirements are the same either way. What differs is how much of the operational burden the processor handles versus how much the firm has to manage manually.

Payload is built for industries where payment workflows carry real compliance requirements, and legal trust accounting fits within that infrastructure by design. The fund routing, fee separation, dispute handling, and audit trail requirements that Rule 1.15 establishes are configurable at the platform level — not managed around after the fact.

Payload meets each of the four ABA Model Rule 1.15 compliance requirements that directly affect payment processing:

• Fund routing: Trust and operating accounts are configured at the platform level. Funds route to the correct account based on transaction type — no manual intervention required per transaction. See Payload's Processing Accounts documentation.

• Fee separation: Processing fees do not touch the IOLTA account. Fees are billed to the operating account or passed to the payer as a convenience fee where state bar rules permit.

• Dispute and return protection: Card chargebacks and ACH returns resolve against operating balances, not trust funds.

• Audit trails: Client-level transaction records, matter tagging, and reconciliation reporting are built into the platform, with retention aligned to Rule 1.15(a)'s five-year minimum.

Supported payment rails: ACH, Same Day ACH, cards (all major brands), RTP, FedNow — inbound and outbound on a single platform.

Collections workflow: Payment links, branded client portals, recurring billing for general counsel retainers, and automated invoice reminders — without requiring manual initiation per transaction.

Outbound payments: Settlement disbursements, co-counsel fees, referral payments, and client refunds from trust run on the same platform as inbound collections, with unified reporting and audit trails across both.

Yes. Payload supports solo and small firm deployments with no technical integration required.

Small firms can get started with off-the-shelf tools — payment links, invoicing, a virtual terminal, and a full dashboard. The same IOLTA compliance configurations that apply to enterprise deployments are available from day one, at any firm size. Firms that want modern payment infrastructure — secure payment links, automated reminders, recurring retainer billing — can have it without building anything custom.

For firms that grow, or for legal tech platforms building payments into practice management software, Payload's API layer exposes the same underlying compliance configurations. Practices do not need to re-platform as volume or complexity increases.

Payload's API layer allows legal tech platforms to embed IOLTA-compliant payment flows directly into case management and billing tools.

Trust and operating account routing, fee separation, dispute handling, client-level ledgers, and audit trail exports are all configurable through the API. The compliance logic is built into the integration, not bolted on afterward. Platforms can deliver the full legal payment workflow — inbound and outbound — without requiring law firm clients to log into a separate payment portal.

Legal payments carry compliance requirements that standard business payment processing was not designed to handle. The fund routing, fee separation, dispute protection, and audit trail requirements set out in ABA Model Rule 1.15 are non-negotiable and they need to be built into the payment platform, not managed around it.

Verify compliance documentation from any processor before going live, and confirm alignment with your state bar's specific IOLTA guidance.