Inside LawAccounting's Merchant Fee & Payment Settlement Engine: How Law Firms Book Gross Client Payments, Net Bank Deposits, and Processor Fees Without Ever Shorting a Trust Ledger (2026 Feature Spotlight)

💰 The $146.50 That Breaks Reconciliations

Here is the scenario that shows up in bar complaints more often than most firms realize. A family law client pays a $5,000 replenishing retainer by credit card. The money is client money, so it belongs in the IOLTA account and the client's matter ledger must show $5,000.

The processor takes its fee. The deposit that lands in the bank is $4,853.50. If the bookkeeper simply records what the bank shows, the client's ledger now says $4,853.50 - and the firm has effectively paid its own merchant fee out of client funds. Multiply that by four hundred payments a year and the trust account is short by a number nobody budgeted for and nobody can explain.

⚙️ What the Settlement Engine Actually Does

LawAccounting treats a client payment as three distinct accounting events, not one:

The gross payment. $5,000 is recorded against the matter's trust ledger on the date the client paid. The client ledger and the client's statement both show the full amount, because that is what the client actually remitted.

The processor fee. $146.50 posts as a firm operating expense in the merchant fee account - funded from operating, never from trust. For firms in jurisdictions that permit passing surcharges to clients, the engine supports that configuration separately and explicitly, with the surcharge treated as its own billable line rather than a silent deduction.

The settlement deposit. The processor batches payments and deposits a net figure - often covering several clients at once, often a day or two later. The engine holds the expected deposit in an undeposited-funds style clearing position until the actual batch arrives, then matches the batch to its component payments.

🔑 The Six Capabilities That Make It Work

⚖️ Why This Shows Up in the Three-Way Reconciliation

A three-way trust reconciliation requires the bank balance, the book balance and the sum of all matter-level client ledgers to agree. Card and ACH payments attack all three legs at once:

The bank balance reflects net batch deposits that arrive on the processor's schedule. The book balance reflects whatever the bookkeeper entered. The client ledgers should reflect gross amounts on payment date. Without a settlement layer, those three views drift apart every single month, and the difference is usually written off as a timing issue - until an auditor asks what the timing issue is made of.

📝 A Practical Setup Checklist

1. Confirm your processor agreement specifies which account fees are drawn from - and that it is never the trust account.
2. Create a dedicated merchant fee expense account in the operating chart of accounts rather than lumping fees into bank charges.
3. Configure separate processing paths for trust-destined and operating-destined payments so retainers and invoice payments never share a route.
4. Set a cleared-funds hold period for ACH that matches your bank's actual availability, not the optimistic version.
5. Reconcile the processor's monthly settlement statement to the general ledger every month, the same way you reconcile a bank account.
6. Review the chargeback log quarterly - it is a leading indicator of both billing disputes and intake quality issues.