Why Legal Needs Its Own Payment Infrastructure

At my last company, LegalSoft, we built software for hundreds of law firms. Case management, intake workflows, and document automation; we touched nearly every part of how a law firm operates. I thought I understood the industry.

Then I launched my own law firm and sawd what happened after a case settled.

A paralegal would pull up the settlement sheet, open a separate spreadsheet to track medical liens, print a stack of checks, wait for signed lien releases to come back by fax, and then manually reconcile everything against the trust account, sometimes days later, sometimes weeks later. At firms processing dozens of cases a month, this was a typical Tuesday.

The software we'd built had modernized everything up to the moment money needed to move. And then it all fell apart.

The Disbursement Problem Nobody Was Talking About

Personal injury law firms sit at the center of a multi-party financial ecosystem. When a case settles, a firm must orchestrate a disbursement across clients, medical providers, co-counsel, lienholders, and sometimes courts. Every payment needs documentation. Every dollar that touches a trust account needs to be tracked, reconciled, and defensible to a state bar auditor.

The stakes are high. IOLTA violations and mismanaged trust accounts are among the leading causes of attorney discipline in the United States. In California, compliance audits by the state bar’s Client Trust Account Protection Program (CTAPP) are becoming more frequent and exacting. The consequences of getting it wrong can include hefty fines or potentially even losing your legal license.

And yet, in 2024, the standard workflow at most PI firms was still printing checks, chasing fax confirmations, and reconciling manually in a spreadsheet that maybe one office manager understood.

I kept asking myself: why hasn't anyone fixed this? Not just with a better UI, but at the infrastructure level, the actual movement and tracking of money?

What I Found When I Started Looking at Legal Payments

When I left LegalSoft and started doing customer discovery for what would become Disbo, I expected to find firms that were unhappy with their current tools. What I didn't expect was how universal the pain was or how resigned people were to it.

"This is just how legal works," I heard, over and over.

Office managers had developed elaborate workarounds. Managing partners had accepted that reconciliation errors were a cost of doing business. Medical providers were waiting 60, 90, or sometimes 120 days for lien payments after cases closed. The disbursement process was so manual; nobody had gotten around to cutting the check yet in all that time, even with the money in place.

The $154 billion legal disbursement market was, in large part, running on paper.

What made this stranger was that the infrastructure to fix it already existed. Real-time rails — ACH, RTP, FedNow — were all available. Banking APIs had matured. Reconciliation logic could be automated. Other industries had already solved this: real estate closings, healthcare billing, and payroll. Legal had simply been left behind.

Why This Vertical Needed a Ground-Up Architecture

Building for legal payments isn't like building a generic payout flow and adding a compliance checklist on top. The disbursement process is structurally different because every payment is contingent.

Before a single dollar can leave a trust account, a firm typically needs to confirm lien release signatures, co-counsel fee agreements, client authorizations, and W-9s from each payee. In most firms today, that's a manual checklist, and it's rarely complete before payments start moving. Reconciliation happens after the fact, if at all, leaving the bank account and the firm's internal records perpetually out of sync.

That dynamic shaped how we had to build. A generic payment processor with a compliance layer bolted on wouldn't work. We needed disbursements to be blocked until the required documents were actually in place, a ledger that tracked balances by case rather than just by account, and transaction records structured well enough to be audit-ready without any cleanup after the fact.

That's a payment operations architecture problem, which a workflow tool cannot solve.

How Modern Treasury Fits In

When we started designing the payments layer for Disbo, we evaluated what to build versus what to buy. The core question we had was, precisely, how much of the infrastructure work was generic enough that someone had already solved it?

Modern Treasury had already developed the components that would have taken us two years to perfect independently: multi-bank connectivity, programmable payment flows with configurable approval logic, a double-entry ledger that links every transaction to structured metadata, and immutable transaction records. The API design also enabled attaching custom fields to each payment object, allowing us to automatically carry the matter ID, case number, and recipient type through to the ledger entry, without a separate reconciliation step.

What that unlocked for us architecturally: we could build the compliance and document-gating logic as the control layer, with Modern Treasury handling the execution and ledger layer beneath it. The trust account's subledger stays in sync with the bank in real time. Reconciliation becomes a continuous state.

For a product where every transaction has legal consequences, the ideal architecture is to separate concerns, with compliance logic on top and payment infrastructure on the bottom.

What I've Learned Building in Legal

Here are a few things I didn't completely understand until I built Disbo:

Trust is the product. Law firms don't adopt software they aren't sure they can rely on. Moving client funds is the most sensitive thing an attorney does. The bar for reliability, security, and auditability is higher here than almost anywhere in B2B SaaS. We've had to earn that trust one conversation at a time.

The compliance angle is a feature. Early on, I assumed "IOLTA compliance" would be a hard sell: dry, technical, and something firms wanted to avoid thinking about. The opposite was true. Firms are acutely aware of their audit exposure. When we frame Disbo as audit-ready infrastructure rather than faster payments, the conversation changes immediately.

Legal is ten years behind fintech, and that's an opportunity. Healthcare, real estate, and logistics have all had their payment modernization moment. Legal is at the beginning of that curve. The firms building modern payment systems now will have a structural advantage. The builders who get the compliance layer right first will own the infrastructure layer that follows.

Where This Goes

When I tell law firm partners about what we're building, the reaction I hear most often is, "Why didn't this exist before?"

I think about that question a lot. My answer is that legal payments sit at the intersection of fiduciary obligation, multi-party coordination, and outdated bank infrastructure, and no one was motivated to untangle all three until the underlying rails became accessible enough to make it worthwhile.

That time is now. The infrastructure is there. The last step is to build the compliance and workflow layer that will make it usable for legal businesses that have relied on paper checks and spreadsheets for years.

We built Disbo on Modern Treasury so we could spend those two years on the legal layer instead of the rails.

Finally, Legal is getting its payment stack.