Centerbase vs Clio in 2026: Midsize Billing Choice

Key Takeaways

• Choose Centerbase when the firm wants matters, trust, retainers, and the firm ledger in one product and can accept a quote plus a long, included onboarding. Choose Clio when the firm wants a published plan ladder and a much larger review record, and someone will actually read which controls sit above the entry seat.

• Clio's overall review score: 4.7/5 from 1,750 reviews, against Centerbase at 4.4 from 61 reviews, on a page updated October 8, 2026, according to Software Advice (2026). Those samples are not equal evidence.

• Centerbase does not print a license price. For Clio, read Check current pricing on its own pricing page rather than a dollar figure copied from a roundup.

• The entry seat leaves out a conflict check, a client portal, accounting integrations, and automated workflows. Those controls are listed on higher plans.

• A practice system can store the matter and the bill. It does not, by itself, finish a reviewed handoff into the books or a partner exception queue.

• Use the review record to decide how many reference calls you still owe, then confirm trust design and rollout time in writing before anyone signs.

The decision a managing partner is making

Practice management software is the system of record a firm uses to run matters, time, bills, documents, and client money.

A managing partner searches this comparison when the firm is close to a switch. The useful question is which product can hold midsize billing and client funds without a second, silent set of books, which one shows what the cheap seats omit, and which rollout your administrators can staff. Neither product has been renamed, merged into the other, or pulled from sale on the pages reviewed here. Centerbase is still sold as Centerbase. The current public plans on Clio's pricing page are Starter, Core, Signature, and Elite.

The short version is this. Choose Centerbase if you want matter-level trust, more than one trust or retainer on a matter, and a native firm ledger, and you will accept quote-based pricing plus a structured onboarding. Choose Clio if you want a widely reviewed cloud system, trust tools listed on every published plan, and a written ladder from a thin entry seat to plans that add roles, stages, workflows, and outside accounting sync. Do not buy either name because a secondary site invented a starting price. The public record and the quote are the only figures that belong in a partner memo.

Who this is for

This piece is for a managing partner, a firm administrator, or a controller at a midsize firm that already holds client funds, bills in more than one way, and is choosing the system the whole office will live in. A bookkeeper or controller should be in the room. The firm is past a solo startup purchase and is not commissioning a custom build from a blank server.

Walk this list before you spend time with sales. Write down every trust account you operate, including settlement or escrow money that must not pay ordinary bills. List the billing methods you cannot drop: hourly, flat fee, contingency, split payers, and any task codes a client requires. Name who may approve a pre-bill and who may move trust. Decide whether QuickBooks Online or Xero stays beside the practice system. If it stays, the practice system is not your only ledger, and the plan you buy has to say so.

Red flags: you will not sign without a per-user price printed on the website; you need conflict checks, a client portal, and accounting integrations on the lowest published seat; you cannot spare staff for a rollout measured in months.

How we evaluated these tools

The weights below are a buying decision, not a lab score and not a hands-on test. They add to 100 percent. Trust and the firm ledger carry the most weight because a firm that holds client money cannot treat accounting as a side app it might connect later. Billing-method coverage is next, because a single hourly timer does not describe a mixed docket. Time capture matters only if a person can still review the entry before it becomes a bill. Permissions and reporting matter once more than a few people touch a file. Rollout weight is calendar time your administrators must give the project. Published price clarity is real, and it is the smallest weight, because a missing sticker price is a process problem, not proof that the product cannot bill.

A product can clear the ledger bar and still be the wrong buy if the firm cannot staff the weeks or cannot see a price before the call. Tables later in this piece separate what vendor and review pages state from the read we put on those facts. Where a count was not on a page opened for this article, the cell says so. Nothing here is a timed trial, a secret client list, or a rank we computed from private data.

What the review record actually says

Public satisfaction is not the same thing as fitness for a midsize billing cycle, and the samples are not equal. Centerbase's overall score is 4.4 from 61 reviews and Clio's overall score is 4.7 from 1,750 reviews. Reviewers recommend Centerbase at 70 percent and Clio at 88 percent, with ease of use at 4.3 versus 4.6, value at 4.1 versus 4.5, support at 3.8 versus 4.7, and functionality at 4.2 versus 4.5, on a comparison updated October 8, 2026, according to Software Advice (2026). That page also marks Centerbase's starting price as not provided by the vendor. The support gap in that row is the figure a managing partner should not shrug off when the operations bench is thin.

On a separate comparison updated October 6, 2026, Clio's fit score: 84% against 74% for Centerbase, according to Capterra (2026). Fit here means how reviewers rate delivery of features reviewers say they care about. It is not a count of firms that switched, and it is not a bar opinion. Our read: the larger review base is the stronger public satisfaction signal, by a wide margin of reviews. Centerbase's record is too small to treat one warm comment or one angry comment as the firm's future. Use the scores to size your reference calls. Do not use them to skip the trust design.

Capability matrix

The cells stay with published behavior. Centerbase's trust behavior comes from its help center. Plan gates on Clio come from its pricing comparison. "Not published" means the page opened for this article did not give a count.

The trust feature page states a report history: 10 years for reconciliation reports, according to Clio (2026). Centerbase auto-builds a three-way report from reconciliation parts: 3, the bank balance, the book balance, and the client ledger, and the adjusted book figure is supposed to match the client ledger, according to Centerbase (2023). Those are different promises. One is how long reports are kept. The other is a method that puts three totals on the reconciliation itself. A firm that has watched a trust account "tie" only after a spreadsheet rebuild should weight the method. A firm that needs a long archive for a bar exam of the books should weight the retention statement, then ask Centerbase what history the quote actually migrates, because the help article describes the report rather than a ten-year archive.

Our read of the matrix follows the pages, not a demo script. Centerbase's trust guide says every new matter receives a default trust account, and a matter can hold more than one so settlement or escrow funds are not spent on bills. Staff can point each trust at a bank account and a liability account, flag a retainer, set a replenishment level and a minimum balance, and choose whether the account shows on the client bill. Clio's trust pages describe trust requests, evergreen alerts when funds drop under a threshold, separate trust and operating ledgers, and a sync of contacts, bills, time, expenses, payments, and trust transactions into QuickBooks Online. That sync is where many firms actually keep the books. The entry plan lists trust management and reconciliation. It does not list the QuickBooks, Xero, or TrustBooks integrations. Buying "trust" and assuming the accounting sync is included is the mistake the grid is there to prevent.

Pricing checked against the public pages

Pricing checked October 10, 2026. Centerbase's license is quote-based. Its pricing page does not print a per-user dollar amount. It says licensing, onboarding, and add-ons are laid out in the quote, and that onboarding is included rather than sprung as a hidden fee. Clio's license belongs on Clio's pricing page, linked below, and this article does not print a dollar subscription beside that name. Payment processing is not the license. A card rate can look small while the subscription is the real check, or the reverse, once every timekeeper, clerk, and finance seat is counted.

Centerbase's onboarding span: 12-14 weeks, depending on firm size, data complexity, and configuration, with foundation work in weeks 1 to 5, a test import and admin training in weeks 6 to 10, and go-live in weeks 11 to 14, according to Centerbase (2026). That calendar is the total-cost fact a sticker price would have hidden. A firm that wants to be billing in the new system inside a month is outside the published timeline. A firm with dirty matter numbers, old trust history, and several billing templates should treat the long end of that range as the planning number until the statement of work says otherwise.

Our read on cost is deliberately narrow. Do not line a third-party "starting at" rumor against either vendor. Those roundups disagree with each other, and they are not the quote your firm will sign. The costs you can plan from public pages are the onboarding calendar, whether finance staff need their own seats, and whether QuickBooks Online or Xero remains a paid system beside the practice platform. The plan table includes a free accountant license on each listed plan. Centerbase's quote is where you learn whether the controller is licensed like a timekeeper. Ask both vendors for a written seat count that includes attorneys, paralegals, billing clerks, and finance before you compare anything else. Also ask which payment method your clients actually use, because a transaction fee on cards is a different line from the subscription and should be modeled on last year's collection mix, not on a vendor average.

Reading Centerbase for a midsize ledger

Centerbase is the clearer fit when the firm wants one operational system for matters, time, bills, trust, and the firm ledger, and the buyers are willing to configure it. The trust help article describes trust at the matter level, a default account on every new matter, and the option of additional trusts so funds held for a settlement are not the same pocket that pays fees. Replenishment level and minimum balance are fields on that account, not a side spreadsheet. The pricing page groups case and matter management, billing and accounting, document management, calendaring, profitability reporting, a client portal and intake, automated time capture, ePre-bill automation, and payments in the included set. Confirm each of those lines in the quote so a "premium" carve-out does not surprise the controller after the contract.

Reviewers give Centerbase an accounting rating: 4.8/5 against 4.1/5 on Clio in this comparison, with billing at 4.0/5 against 4.5/5 and document management at 3.0/5 on fewer than 10 reviews against 4.2/5, according to Capterra (2026). That accounting edge matches the native-ledger story. The billing score runs the other way. The document score rests on a very small feature sample, so treat it as a flag to test your own templates during a pilot, not as a precise measurement of Word or PDF handling.

The limitations are the quote, the thin review base in the table above, and the weaker support score in that same table. You cannot drop a per-user license into a board memo from the public page. You also should not pretend a small review set maps every midsize litigation or transactional firm. Call current customers about response time after go-live, not only about the sales cycle. Implementation, on the vendor's timeline cited above, is a three-part project: clean data and a test site, a real import plus admin training, then migration and end-user rollout. Primary pages are the Centerbase pricing and onboarding page and the trust account guide. Who should not choose it: a firm that needs a self-serve signup and a published seat price this week. Who should choose it: a firm whose pain is trust structure and firm accounting living in different products, and whose administrator can give the rollout a full quarter.

Reading the plan ladder on Clio

Clio is the clearer fit when the firm wants a mature, widely reviewed practice system and will match the plan to the controls it needs. Trust account management, trust reporting, trust and operating reconciliation, a chart of accounts, bank sync, invoicing, and hourly, flat, and contingency billing are listed across the plans. The entry plan is the one that looks complete in a screenshot and is thin in the grid. Several controls partners treat as standard, including custom fields, a conflict check, a client portal, templates, the app directory, accounting integrations, and automated workflows, are not on that entry row. Matter stages, split billing, multi-currency bills, single sign-on, and live onboarding training sit on the upper plans. The top plan is also the one that folds in the intake product and a website builder. Grow on the middle plans, and advanced document automation, are left as a sales conversation rather than a printed price.

The pricing page lists four plans, an uptime guarantee: 99.9%, SOC 2 Type II certification, unlimited document storage on every plan, data export while the account is active and for 90 days after cancellation, 3 e-signature sends on the entry plan, 15 on the next plan, unlimited sends on the two upper plans, 2 custom roles on the second plan, 3 court-rule calendars per firm on that plan and 10 on the plans above, and 5 saved report views on the second plan, with card payments at 2.95 percent, American Express at 3.75 percent, and eCheck and ACH at 1 percent, according to Clio (2026).

The limitation is that grid. A firm that buys the entry plan and then expects QuickBooks Online, a client portal, and workflow automation will feel mis-sold even though the page disclosed the gap. Export rights are a real exit fact and still not a weekend project for a midsize file room. Firms that already push time from this system into the books should read moving Clio time into QuickBooks Online and connecting Clio to QuickBooks before they assume the entry plan includes that path. The built-in signature allotment is also a different choice from a dedicated signature tool, which is why sending Clio documents out for signature belongs in the same stack review. If the argument is really which product should own the books, use a method for choosing legal accounting software rather than letting the practice-system demo decide it. Firms that still keep a working set of files in Dropbox can read connecting Clio to Dropbox so storage inside the practice system and storage the attorneys already use are not confused.

Migration on the entry plan is self-serve. Higher plans move to guided migration, and the upper plans add live onboarding training. That is a shorter published story than the multi-week project on the other pricing page, and it does not mean a midsize conversion is a spare afternoon. Who should choose it: a firm that values the review record, wants the plan gates in writing, and may keep QuickBooks Online or Xero. Who should not: a firm that needs several trust pockets on one matter, with retainer rules inside a native general ledger, and that will not accept an integration as the accounting design. Primary pages are the pricing comparison and the trust account feature page.

An illustrative month of unbilled time

Picture a commercial group of 36 lawyers that records 1,440 hours in a month. If 6 percent of that time never reaches a draft bill, 86.4 hours stay off the invoice. At an illustrative blended rate of $325, the gap is $28,080 before any partner write-down. The review list keys each open file by its display_number, the matter reference field documented on the Clio Manage matters guide, and a person still approves the draft before it is sent. The headcount, the hours, and the rate are a planning sketch for a partner meeting, not a measured result from a named firm and not a promise that either product will recover that gap on its own.

Where the record stops and the handoff starts

The money usually leaks after the practice system has done its job. Time sits unbilled, a trust balance falls under the replenishment level, or a bill is approved in one product and entered late in another. A proposed US Tech Automations workflow watches a scheduled export of open matters. The trigger is a matter whose matter_stage is the billing stage the firm defined and whose unbilled time is still open after the cutoff. The action writes one review row keyed by display_number, with the hours and the responsible attorney beside it. The output is a partner queue, not a client invoice. Prerequisites are an API token or a CSV the firm is allowed to export, a written field map, and a named approver. Nothing posts to a bill until that person accepts the row. This is a configurable design, not a live deployment.

A second proposed US Tech Automations workflow starts when a trust report shows a matter under its replenishment level. The action builds a replenishment draft and, where the firm also keeps QuickBooks Online, attaches the matter reference so the bookkeeper can match the later operating entry. The output is a draft for the billing partner plus a checklist row. A person sends any client request. The flow does not move trust funds. Prerequisites are an export of the trust balance report, a QuickBooks company the controller already uses, and an approval role that is allowed to release the draft. It is the same idea as the time queue: the practice system remains the system of record, and the handoff stops for a human before money or a client message moves.

When NOT to use US Tech Automations: skip the extra layer when the firm only needs the pre-bill and trust replenishment already inside the practice system and a person already reviews them; when a single monthly accounting export is enough and the controller checks it by hand; or when the firm is still choosing the practice system, because automating a stack that is about to be replaced adds maintenance without a new control.

Zapier, Make, n8n, or a build of your own

The real alternative for many firms is not another practice system. It is a chain in Zapier, Make, or n8n, or a small internal job the IT vendor already hosts. Those tools can keep a run history, retry a failed step, branch on an error, and store enough of a log to answer "who changed this bill" when someone configures them that way. The buyer owns the design. Observability, idempotency, escalation, access control, and maintenance do not arrive because an account was opened. Someone has to decide what a duplicate export means, who is paged when the trust file fails at 6 p.m., which token can read matters, and who patches the chain after a field rename. A proposed US Tech Automations design can configure the review gate, a stored key so a retry does not open a second queue row, and a named escalation role, provided the firm supplies the export or API access and a partner still approves any trust movement or client send. The difference is who designs and watches that control, not a magic absence of failure. An in-house build can do the same work if the firm wants to employ the person who will still be maintaining it two years from now.

Common mistakes on this shortlist

• Comparing a quote to an entry-plan seat and ignoring onboarding weeks, finance seats, and whether QuickBooks stays in the stack.

• Treating "trust is included" as "the accounting integration is included." On the published grid, those are different rows.

• Reading a 61-review record and a 1,750-review record as if they were the same kind of evidence.

• Letting a card rate decide the purchase. Processing is not the license, and the license is not the implementation calendar.

• Turning on an automation that can draft a trust request or a bill without a named person who must approve it first.

• Assuming document automation, intake, or a website builder is inside the seat you circled because the homepage screenshot showed it.

Glossary

• Matter. The file everything else hangs on: time, bills, documents, and trust. In the public matters guide, each matter has a display_number and can carry a matter_stage.

• Trust ledger. The record of client money the firm holds and must not treat as earned fees until it is properly applied or disbursed.

• Three-way reconciliation. A trust check that lines up the bank statement, the book's cleared and uncleared items, and the sum of client balances.

• Replenishment level. The balance at which the firm asks the client to restore a retainer, instead of discovering the shortfall on the next bill.

• Pre-bill. The draft invoice partners mark up before the client ever sees it. Edits at this stage are cheaper than credit memos later.

• Operating account. The firm's own money, kept apart from trust. Moving cash between the two is a controlled step, not a transfer a junior clerk should improvise.

• UTBMS. A task-code scheme some clients require on bills. If your clients demand it, confirm the code set is on the plan you will actually buy.

• Realization. Fees billed, or collected, compared with the value of the time recorded. The worked example above is the unbilled slice of that problem, drawn as a sketch.

Questions partners ask before they sign

Is Centerbase a renamed or discontinued product?

No. It is still sold under that name, and Clio is still sold under its own name with Starter, Core, Signature, and Elite as the current public plans.

Does Centerbase publish a per-user license price?

No. The public pricing page is quote-based, and a comparison site that prints a dollar amount is not a substitute for that quote.

Which published plan includes a client portal and QuickBooks?

Not the entry plan. The pricing grid lists the client portal and the QuickBooks, Xero, and TrustBooks integrations from the second plan upward.

Can one matter hold more than one trust account?

Yes in Centerbase's help center. Every new matter gets a default trust account, and staff can add others, including a retainer with a minimum balance and a replenishment level.

How should a firm read the onboarding calendar?

Centerbase publishes a multi-week range tied to firm size and data complexity, cited in the pricing section above, and says the journey is included in the subscription rather than billed as a surprise.

Should the entry plan be the midsize default?

No, not if the firm needs conflict checks, accounting integrations, automated workflows, or unlimited e-signature sends. Those are listed above the entry row.

When is an extra automation layer the wrong spend?

When the practice system already covers the handoff and a person reviews it, or when the firm has not finished choosing that system. A second tool then adds upkeep without a new control.

Which firm should choose which system

A managing partner who needs one native ledger for trust and the firm, and who can staff a quoted, multi-week rollout, has the clearer case for Centerbase. A managing partner who wants the larger public review record, a written plan grid, and room to keep QuickBooks Online or Xero has the clearer case for Clio, provided the seat is above the entry plan if conflict checks, a portal, workflows, or accounting sync matter. The practice system still ends at the record. The exception queue, the replenishment draft, and the match into the books are a separate design with an export or API prerequisite and a human approval before anything reaches a client or a trust ledger. For how that layer is configured around the system you keep, see how US Tech Automations configures this.