Case Management vs. Billing and Trust vs. Payment Processing

Legal software buyers often shop for one category, but three separate jobs are being solved: managing the work, managing the money it produces, and moving that money. LeanLaw handles the middle job, connecting to a firm’s case system on one side and its payment processing on the other.

Three jobs, one shopping list

When a firm evaluates software, it’s easy to treat “legal software” as a single category and compare tools as though they compete for the same job. They don’t. Three genuinely different jobs sit inside that shopping list, and conflating them is where buying mistakes start: managing the legal work itself, managing the money that work generates, and moving that money between accounts once it’s due. A tool built for one job can look thin when judged by the standards of another, not because it’s a worse product, but because it was never trying to do that job.

The conflation happens for an understandable reason. From a lawyer’s chair, all three jobs touch the same matter, the same client, and often the same afternoon: draft a document, log the time, send the invoice, watch for the payment. It feels like one continuous piece of work, so it’s natural to want one piece of software to match that feeling. The jobs underneath stay separate even when the experience of doing them doesn’t, and a firm that shops as though they were one thing usually ends up evaluating the wrong feature list against the wrong vendor.

The work layer and the money layer

The work layer owns the legal work: matters, documents, calendaring and docketing, intake, and the timeline of what happened on a case. It’s where a lawyer and their team spend most of a working day, and it’s the layer most firms picture first when they say “our software.” A practice or case management system runs that side of the business, and it’s a different discipline entirely from what happens to the revenue that work eventually produces.

The money layer is where legal work turns into revenue, and it’s the layer this comparison is really about. It covers time and expense capture, invoicing, trust and IOLTA accounting, and the reporting that shows whether a firm’s revenue cycle is actually healthy. There’s a full name for this discipline: Legal Revenue Operations is the management of a matter’s revenue from open work in progress, through a billed invoice, to a collected payment, plus the reporting that shows whether that path is working. Four numbers describe whether it’s healthy: utilization, how much of a timekeeper’s capacity turns into billable work; realization rate, how much of what’s billed survives to the invoice; collection rate, how much of what’s invoiced actually gets paid; and billing velocity, how long the trip from work performed to cash actually takes. Where a firm leaks depends on its operating model: hourly firms tend to leak through realization, flat-fee firms through margin, and contingent firms through cash velocity. Legal RevOps is the layer LeanLaw occupies, and it’s a genuinely different job from either the work layer above it or the movement layer below it.

Realization and collection rate are worth separating explicitly, because this is exactly where the middle layer gets confused with the other two. Realization asks whether the value of the work actually made it onto an invoice; that’s a billing question, answered entirely within the money layer. Collection rate asks whether an invoiced amount actually turned into cash; that’s a question the money layer can only answer once the movement layer reports back that a payment landed and was matched to the right invoice. A firm that only watches one of those numbers is watching one layer and assuming it describes both.

The movement layer, and where the handoffs leak

The movement layer physically moves funds between accounts: a client’s card or bank payment landing in trust or operating, a disbursement going out, a transfer from trust to operating once fees are earned. LeanLaw includes its own built-in payment processing as part of every plan, so for many firms that movement happens inside the same system that produced the invoice; a firm with an existing processor relationship it trusts, LawPay or otherwise, can keep using it instead. Either way, moving client funds between trust and operating stays governed by the same bar-level rules about who can hold those funds and how, rules no piece of software resolves on a firm’s behalf.

Each layer hands data to the next, and the handoff is where realization quietly leaks. Time gets logged in the work layer but never reaches an invoice in the money layer. Picture a hypothetical firm that logs 100 hours of attorney time on its matters in a month; if 8 of those hours never make the trip into an invoice, because someone forgot to transfer them or applied the wrong rate, that’s a hypothetical 8 percent of the month’s work gone before collections even start, and no report catches it unless something is actually watching the handoff. Or the handoff runs the other way: a client pays through a processor, the payment lands in the firm’s bank account, but nothing links it back to the invoice it was meant to settle, so the receivable stays open on paper long after the cash has cleared.

Neither failure looks like a crisis from inside the firm on the day it happens. A timekeeper assumes the hours will get billed eventually. A bookkeeper assumes a mismatched payment will sort itself out at reconciliation. What actually happens is that both gaps sit quietly inside whichever report a firm is looking at, understating utilization on one side and overstating how current the receivables list actually is on the other, until someone happens to compare the work layer, the money layer, and the movement layer against each other directly and finds the difference.

What this depends on

• Which practice or case management system a firm runs upstream, and whether it exports the data the money layer actually needs.
• Which payment processor and bank sit downstream, and how cleanly their data matches back to an invoice.
• The firm’s operating model, since hourly, flat fee, and contingent matters hand off between these layers differently.
• Who’s actually watching the handoffs today: a partner, a bookkeeper, an office manager, or no one in particular.

Which layer are you actually buying

A firm shopping for “legal software” is usually judging tools built for one job against a list built for three. The better question is which of those three layers is leaking today, and whether the tool in front of you was built to close that specific gap or just to touch it in passing.