Does LeanLaw Process Payments Itself, or Do I Need to Keep Using LawPay?

LeanLaw includes its own built-in payment processing as part of every plan, so you don’t need LawPay to accept client payments. Whether to route through LawPay anyway, or move fully to LeanLaw’s built-in processing, comes down to how your trust accounting, reconciliation, and existing merchant relationship are set up.

What changes when payments run through the same system as billing

When a client payment flows through LeanLaw’s own processing instead of a separate tool, the payment and the invoice it’s paying live in the same system from the start. That matters most for trust: a retainer payment that needs to land in your trust liability account and a payment against earned fees that needs to land in operating are two different things, and how cleanly that split happens depends on which system is making the call.

LawPay is a long-standing, purpose-built processor for the legal market, and plenty of firms have a reconciliation routine already built around it. Switching processors is a separate decision from switching billing platforms, and nothing about using LeanLaw requires making that call on day one.

The questions that actually decide it

• Does your current setup already split trust payments from earned-fee payments correctly, or does someone reconcile that by hand after the fact?
• Does your bookkeeper’s reconciliation process run around your existing processor’s reporting, in a way that’s working well enough to leave alone?
• How far into a contract or relationship are you with your current processor, and does that make switching now more disruptive than what you’d gain?

None of those questions has one answer for every firm. A firm with a clean trust workflow and a processor relationship it trusts has less to gain from switching immediately than a firm still matching payments to invoices by hand every month.

What a transition actually looks like

A firm doesn’t have to reconcile every historical transaction across both systems at once to make the switch. A cleaner approach is picking a cutover date and moving new engagements, new retainers, and new invoices to LeanLaw’s processing from that point forward, while whatever activity already lived in the old processor stays there to be closed out on its own timeline. That keeps the transition scoped to what’s actually changing, rather than turning it into a project to rebuild history that was never in question.

What this depends on

• How your trust and operating accounts are currently structured, and whether payments already route correctly between them.
• Whether your bookkeeper’s reconciliation habits are built around your current processor’s exports.
• How far into a contract or relationship you are with your existing processor.
• Whether your firm runs a single operating model or several, since that changes how payments need to be split once they arrive.

Before deciding whether to keep a separate processor, it’s worth asking where reconciliation actually happens today: in the processor’s own reports, in your books, or in someone’s memory of what each payment was for. That answer says more than which name is on the receipt.

Related questions

Do you use LawPay? No. LeanLaw includes its own built-in payment processing, so LawPay isn’t required to accept client payments through your invoices.

So you don’t link with LawPay, you go through your own provider? Right. Payments run through LeanLaw’s built-in processing rather than an integration with an outside processor, which is why they land against the ledger in step with the invoice itself.