Your Law Firm Runs a Treasury Function It Never Staffed: Why 2026's Money-Movement Volume Has Outgrown the Controls Most Firms Actually Have

🏦 The Business Inside Your Business

Think about what actually flows through a mid-market firm in a year.

Client retainers arrive and sit in trust. Government filing fees go out — and in immigration and corporate practice, those fees have risen sharply enough in 2026 to change the size of the flow, not just its cost. Expert witnesses, court reporters, medical records vendors, and process servers are paid on advance. Settlements arrive, sit while liens resolve, and disburse to three or four parties. Earned fees move from trust to operating. Clients pay by card and ACH through a portal. Vendors are paid by check, ACH, and wire.

A firm with fifty people can easily move eight figures a year across those channels. A business of comparable size in any other industry would have a treasury function: segregation of duties, dual authorization above a threshold, positive pay on its check stock, callback verification for payment instruction changes, and a daily reconciliation cadence.

Most law firms have a bookkeeper, a partner who signs things, and a shared inbox.

📈 Three Things Changed at Once

1️⃣ The dollar volume went up without the headcount

Government fee increases, higher expert and e-discovery costs, and larger settlements have all pushed more money through the same back office. The pass-through nature of much of it makes the growth invisible in revenue reporting — a firm can double the money it handles without the P&L moving much at all.

2️⃣ Payments got faster and less reversible

Instant and same-day rails are convenient right up until a payment goes to the wrong account. The window in which a mistaken or fraudulent transfer can be recalled has narrowed considerably, which shifts the entire value of controls from detection to prevention.

3️⃣ Fraud got specific to law firms

Payment fraud aimed at law firms is no longer generic phishing. It targets the moments where a firm is known to move large sums to parties it has not paid before: a settlement disbursement, a real estate closing, a lien payoff, a new expert vendor. The attacker's job is to change one set of banking instructions at exactly that moment — and the firm's job is to have a control that makes changed instructions a stop, not a formality.

🧱 What a Law Firm Treasury Function Actually Looks Like

The point is not to hire a treasurer. It is to encode treasury behavior into the workflow, so the controls apply whether or not anyone is thinking about them that day.

🔎 The Test That Reveals Where You Stand

Pick the last five disbursements over your firm's informal "large payment" threshold. For each one, answer without asking anyone:

1. Who created the payment, and who released it? Were they different people?
2. What evidence exists that the payee's banking details were verified?
3. If the payment came from trust, what confirms the client's ledger had cleared funds at that moment?
4. How many days elapsed between the payment and the reconciliation that would have caught an error?

A firm that can answer all four from the system, for all five payments, has a treasury function. A firm that has to reconstruct the answers from email has a habit.

⚙️ Why This Belongs in the Platform, Not Beside It

Every one of the controls above depends on the payment, the matter, the client ledger, and the approval sitting in the same system. Cleared-funds enforcement requires the disbursement workflow to see the trust ledger in real time. Duplicate detection requires payment history. Separation of duties requires roles that mean something across both the practice and the books.

This is where the architectural question stops being philosophical. In a stack where practice management holds the matter and a separate accounting product holds the money, the control has to be reimplemented on the accounting side with information it receives on a delay — which is why so many firms end up enforcing the important controls manually.

LawAccounting handles disbursement as a controlled workflow: approval routing on vendor bills and expenses, matter-linked accounts payable, check printing and payment runs that cannot cross the trust and operating boundary, cleared-funds controls on trust disbursement, real-time compliance alerts for overdrafts and negative client ledgers, and AI-assisted bank reconciliation across 15,000+ institutions so the matching cadence can be weekly rather than monthly. Inside CaseQube, those controls inherit Salesforce role-based permissions and a complete audit trail, so who did what — and who was allowed to — is a query rather than an investigation.

🧭 Where This Goes

The direction of travel is clear enough. State compliance programs are asking firms to certify their trust practices rather than simply follow them. Malpractice carriers are asking about payment controls at renewal. Clients — particularly institutional ones — are asking about them in outside counsel guidelines. Each of those is a request for evidence, and evidence is a property of systems, not of intentions.

Firms that treat money movement as a first-class operational function will find those requests routine. Firms that continue to treat it as bookkeeping will find them expensive.