What is actually changing
Clio's integration with LawPay, a payment processor long used by law firms for trust account management and client invoicing, will naturally conclude in August 2026. Clio notified affected customers and is positioning Clio Payments as the built-in replacement.
LawPay as a standalone product is not going away. What ends is the data connection between LawPay and Clio. Firms that use LawPay outside of Clio are not directly affected. The change matters if you currently route client payments through LawPay inside your Clio account.
The short-term answer: Clio Payments
For most firms, the migration path is straightforward. Clio Payments is built directly into Clio, which means no third-party middleware, no API token rotation, and no separate vendor relationship to manage. You enable it in your account, update trust account payment instructions, and notify clients how they will pay going forward.
The operational complexity is mostly communication: updating retainer agreements or engagement letters that name LawPay as the payment method, and letting existing clients know the link they used before is changing. For a firm with a clean billing setup, this is a few hours of admin, not a project.
If continuity is the goal and billing is working, switch to Clio Payments and move on. The rest of this post is for firms that want to use the disruption moment to fix the workflow that LawPay never touched.
The billing problem a payment processor cannot solve
Law firm billing frustration is not mostly about which processor handles the transaction. The recurring pain, the one that shows up in every Clio user forum, is the workflow upstream of the invoice: drafting billing narratives, reviewing time entries, reconciling what was actually billed against what was entered, and catching the kind of inconsistency that gets flagged during a client dispute.
The pattern is consistent: attorneys or paralegals spending two to four hours per billing cycle doing a task that is mostly mechanical, pulling time entries from Clio, drafting the description for each, grouping by matter, and reviewing for anything a client might question. The work requires judgment at the edges but most of it is transcription.
Switching from LawPay to Clio Payments does not change any of this. The draft workflow is the same either way. If the billing side of running cases takes more time than it should, the payment processor is not where that time is going.
What Clio MCP changes in the billing workflow
Clio MCP is an open-source connector that lets Claude read your Clio data through a controlled interface. For billing, that means Claude can see your open matters, time entries by attorney, and client records in the current session. What the attorney or paralegal then asks Claude to do with that data is where the workflow changes.
What it handles well
- Drafting billing narratives from time entries, in the firm's established billing style
- Summarizing unbilled hours by matter or attorney before the billing cycle closes
- Flagging entries that are likely to be challenged: vague descriptions, unusually short or long time units for the task type, or duplicate entries
- Grouping related time entries across attorneys for matters that have multiple timekeepers
- Identifying matters that have significant unbilled work but no billing activity in the last 30 days
What it does not do
- Send invoices automatically. An attorney reviews every billing draft. The MCP connector handles data access; the judgment call stays with the attorney.
- Replace Clio Payments or LawPay. The connector reads and writes Clio's data layer; payment processing is Clio's system, not the connector's scope.
- Replace trust accounting review. Billing narratives are one thing; IOLTA compliance is a separate check that stays with the attorney.
The privilege configuration
Billing narratives contain fee information and often reference matter details that qualify as attorney work product. The configuration that matters here is zero-data-retention on the Anthropic side: under an Enterprise API agreement with ZDR enabled, data that passes through the API is not stored or used for model training after the session ends. The MCP connector reads from Clio and passes data to Claude in the session only. Nothing persists. This is not optional for law firm billing use; it is the baseline.
Three responses to the LawPay change
The $1,700 Guided Setup includes connecting your Clio instance to the MCP connector, configuring a Claude workspace scoped to billing tasks, and running billing draft tests against your real matters. You leave with a working setup, not credentials to figure out yourself.
If the LawPay email prompted a bigger question
Most firms will handle the LawPay change in a day. The firms that use the moment to also look at billing drafts, time-entry review, and the broader Clio workflow tend to find the real time sinks were never in the payment processor at all.
If you got the Clio notification and started wondering whether there was a better time to fix more than just the payment side, that is the right question. The connector is open source, the architecture is auditable, and the 30-minute call is free.
Common questions
What happens to LawPay in Clio after August 2026?
Clio notified customers that its LawPay integration will naturally conclude on August 31, 2026. Clio Payments becomes the recommended path for payment processing within Clio after that date. LawPay itself continues as a standalone product; the Clio integration is what ends.
Is switching from LawPay to Clio Payments complicated?
For most firms, no. Clio Payments is built directly into Clio: no third-party middleware, no API tokens to rotate. The work is mostly communication: enabling Clio Payments in your account settings, updating trust account payment instructions, and notifying clients of the change.
Can Clio MCP automate billing drafts?
Yes, within limits. A Clio MCP connector lets Claude read your open matters, time entries, and client records. Claude can draft billing narratives, summarize unbilled hours by matter, and flag entries that look inconsistent. What it cannot do is send invoices autonomously or replace the attorney review step. The MCP connector handles the data layer; the attorney owns the judgment call on every billing draft.
Is billing data safe to pass through Claude?
The safe configuration uses a zero-data-retention path. Under Anthropic Enterprise with ZDR enabled, billing data that passes through the API is not stored or used for model training after the session ends. Billing narratives contain fee information and sometimes matter details that qualify as attorney work product, so ZDR is not optional for law firm billing use: it is the baseline.
What does Clio billing automation cost?
The starting point is the $1,700 Guided Setup: we connect your Clio instance to the MCP connector, configure a Claude workspace scoped to billing tasks, and run billing draft tests against your real matters. You leave with a working setup. Larger integrations with custom billing workflows, matter-type-specific prompts, and paralegal access controls are scoped after a free discovery call.
Talk through your Clio billing setup
30-minute call. Free. We will tell you what is possible with your current Clio configuration, what the billing draft workflow could look like, and whether the Guided Setup makes sense for your firm size and billing volume. No pitch.
Book a Free CallWe also maintain the open-source Clio MCP connector. The connector is free to self-host if your team wants to start there.
