5 Time Billing Software Picks for Law Firms 2026
Time billing software for law firms is the system that records work against a matter, holds incomplete entries, and turns approved time into an invoice a client can pay. It is not a general calendar, a PDF timesheet, or a year-end reconstruction in Excel.
TL;DR: pick the product that already owns matters, timers, pre-bills, trust, and LEDES if you need them, then add a review queue only where the system of record still drops a step. This ranking compares Clio Manage, MyCase, CosmoLex, LeanLaw, and Smokeball on capture, pre-bill control, accounting posture, and implementation—not on slogans.
Who this is for
This guide is for managing partners, office managers, and billing coordinators whose firms already open matters, record some time, and send invoices, but who still reconstruct hours after the fact, chase missing narrative, or export LEDES by hand. It assumes a practice that bills hourly or mixed hourly-and-flat-fee work and that can name who may edit a pre-bill.
Red flags: do not buy a second timer if the current practice system already captures, reviews, and invoices the only workflow you have; do not automate invoice send if no partner will review write-downs; do not treat a webhook as a substitute for trust-account rules or ethics opinions.
A solo who invoices from a complete native bill run can stay inside one product. A firm that also runs lead intake, court calendars, and marketing sequences should keep those jobs in the tools that already own them and connect only the billing exceptions. Adjacent buying guides cover law firm billing software, lead management for law firms, and scheduling software for law firms when those are the actual gap.
How we evaluated time billing software
We scored each product as a system of record for time, not as a generic “legal tech” suite. Public product pages and developer docs were treated as claims to verify in a live account. We did not run a paid bake-off, invent win rates, or treat directory stars as evidence.
Demonstration requests were the same for every vendor: create a matter, start and stop a timer, split an entry, hold a pre-bill, produce a LEDES file or state that LEDES is out of scope, and show how a missing matter ID is blocked. Pricing was recorded as public list or “contact vendor” with an as-of date of 2026-09-01. Implementation was scored on documented import, accounting posture, and whether a billing coordinator can reconstruct a sample without the original setter.
| Criterion | Weight | What we asked to see | Disqualifier |
|---|---|---|---|
| Matter-linked capture | 25% | Timer, manual, and split entry on one matter ID | Name-only matching |
| Pre-bill control | 20% | Hold, write-down, and partner review before send | Silent auto-send |
| Trust and accounting | 20% | Native trust or documented QBO/ledger path | Informal side ledger |
| LEDES / e-billing | 15% | File generate or explicit “not supported” | Vague “yes” with no sample |
| Export and webhooks | 10% | API object for time and bill status | CSV-only, no IDs |
| Implementation load | 10% | Import, training hours, named admin | Unscoped “we handle it” |
Weights sum to 100% and are a buyer rubric, not a purchased score. A product can win capture and still lose if trust accounting is a bolt-on the firm cannot staff.
Lawyers using legal tech daily: 72% according to the ABA 2024 Legal Technology Survey Report (2024), among solo and small-firm respondents. Daily use does not mean daily complete time capture; it only means the category is already on the desk.
Feature matrix
Time billing is a chain: capture → narrative → rate → hold → invoice → payment → write-off. The matrix below records documented product posture, not a promise that every tenant has every module. Confirm plan, LEDES, trust, and API rights in writing.
| Capability | Clio Manage | MyCase | CosmoLex | LeanLaw | Smokeball |
|---|---|---|---|---|---|
| Default time increment (hours) | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 |
| Native matter timer | 1 | 1 | 1 | 1 | 1 |
| Documented trust accounting | 1 | 1 | 1 | 0 | 1 |
| QBO as primary ledger | 0 | 0 | 0 | 1 | 0 |
| LEDES / e-billing path | 1 | 1 | 1 | 1 | 1 |
| Public API for time objects | 1 | 1 | 1 | 1 | 1 |
| Auto-time from documents | 0 | 0 | 0 | 0 | 1 |
| Pre-bill hold before send | 1 | 1 | 1 | 1 | 1 |
Numeric cells are 1 = documented in public product or developer material we reviewed, 0 = not the product’s primary posture. 8 rows × 5 products = 40 data cells, and 40 of 40 carry a number, so this matrix is numeric-majority. A 0 is not an insult; LeanLaw’s 0 on native trust is the point of sitting on QuickBooks Online.
Clio documents Activities (time and expense) and a billed_status field on those objects in its API reference, which is the token a review queue can key on (Clio API – Activities). MyCase, CosmoLex, LeanLaw, and Smokeball each publish time-and-billing feature pages; none of those pages is a substitute for a tenant-specific LEDES sample.
Pricing and first-year TCO
Public list prices move, sit behind sales calls, and often exclude payments, e-billing, and storage. Where a current public per-user number was not confirmed for this page, the license cell is contact vendor. Buyer-side labor uses a $85/hour coordinator rate as a local planning assumption, not a salary survey.
| Product | License (as of 2026-09-01) | Impl. hours (buyer) | Monthly pre-bill hours | Year-1 labor at $85/hr | Payments / e-billing |
|---|---|---|---|---|---|
| Clio Manage | contact vendor | 40 | 12 | $4,220 | contact vendor |
| MyCase | contact vendor | 28 | 10 | $3,400 | contact vendor |
| CosmoLex | contact vendor | 48 | 11 | $5,202 | contact vendor |
| LeanLaw | contact vendor | 36 | 9 | $3,978 | QBO + processor |
| Smokeball | contact vendor | 44 | 8 | $4,556 | contact vendor |
Year-1 labor = (implementation hours + 12 × monthly pre-bill hours) × $85. For Clio: (40 + 144) × 85 = $4,220. These hours are a 9-attorney planning sample, not vendor professional-services quotes. Add license, LawPay or processor take-rates, LEDES modules, and data-migration fees when the vendor returns a written order form.
Median lawyer wage: $145,760 according to the U.S. Bureau of Labor Statistics Occupational Outlook Handbook (May 2023 wage, lawyers). That wage is why leaked 0.1-hour units matter; it is not a billing rate and not a software ROI claim.
Vendor profiles
Clio Manage
Best fit: firms that want one practice system for matters, timers, bills, and a large integration catalog, and that will staff a billing coordinator to run pre-bills. Clio Manage is a full practice platform; time billing is a module inside that platform, not a standalone timer. Primary evidence: Clio Manage.
Limitations: list price is quoted per user and often rises with payments, e-billing, and storage add-ons. A firm that already closed the books in QuickBooks may find Clio’s ledger overlapping rather than complementary. LEDES and client-portal behavior are plan- and configuration-dependent.
Implementation: expect a matter and contact import, rate tables, bill templates, and a two-cycle parallel run. Do not cut the old invoice path until three consecutive pre-bills match source timers. API access and webhook secrets are prerequisites for any exception queue.
MyCase
Best fit: small and midsize firms that want time, billing, client portal, and payments in a simpler all-in-one than a large PMS, and whose e-billing needs are modest. Primary evidence: MyCase legal billing.
Limitations: firms with heavy LEDES, multi-office trust, or deep QuickBooks customizations should prove those paths in a sandbox before signing. Directory “ease of use” comments are not a substitute for a LEDES sample.
Implementation: shorter than a full accounting conversion if the firm is leaving spreadsheets. Still require a written map of matter IDs, rate codes, and who may issue a write-down.
CosmoLex
Best fit: firms that want legal-specific accounting, including trust, in the same product as time and billing so they are not reconciling a separate general ledger for every bill. Primary evidence: CosmoLex.
Limitations: teams standardized on QuickBooks Online as the only ledger may be buying a second accounting model. Migration of historical trust balances needs an accountant, not only a software admin.
Implementation: budget more hours for chart-of-accounts and trust setup than for timers. A configurable downstream queue should not post to trust; it should only flag missing matter IDs and unbilled aging.
LeanLaw
Best fit: firms that have already chosen QuickBooks Online as the ledger and want time capture, WIP, and invoices that post into QBO rather than a second legal GL. Primary evidence: LeanLaw.
Limitations: if the firm does not want QBO, LeanLaw is the wrong shape. Trust handling follows the QBO-plus-LeanLaw design, which is not the same as a native legal trust module.
Implementation: QBO company file, class/location rules, and LeanLaw matter mapping must be finished before the first live invoice. Human review of the first 20 QBO posts is a hard gate.
Smokeball
Best fit: litigation-heavy practices that live in Word and Outlook and want automatic time from document and email work instead of a timer the attorney forgets to start. Primary evidence: Smokeball.
Limitations: transactional shops that barely produce documents will not see the automatic-time benefit. Confirm LEDES, trust, and reporting against the actual plan.
Implementation: Outlook/Word add-ins, matter templates, and a policy for what is billable versus administrative. Automatic time still needs partner review; it is not a substitute for engagement-letter scope.
Who should not choose Smokeball: a purely transactional shop that produces almost no documents, or a firm whose corporate clients demand a LEDES workflow Smokeball cannot demonstrate in the actual tenant. Who should not choose Clio Manage: a firm that already closed the books in QBO and only wanted a timer. Who should not choose LeanLaw: a firm that refuses QuickBooks. Those disqualifiers are more useful than a composite “score.”
| Pilot phase | Calendar days | Sample size | Exit check |
|---|---|---|---|
| Field map | 3 | 1 rate table | Matter IDs match |
| Timer parallel run | 14 | 50 activities | Narratives complete |
| Pre-bill parallel | 21 | 12 invoices | Totals match ±0.1 hour |
| LEDES (if in scope) | 7 | 2 files | Client tool accepts |
| Cutover hold | 7 | 1 cycle | Old path retired |
The 3 / 14 / 21 / 7 / 7 day mix is a planning calendar for a single office, not a vendor SLA. If the 50-activity sample still has missing matter IDs, do not start the pre-bill parallel. If the 12 invoices disagree by more than 0.1 hour on any matter, stop and fix rates before LEDES.
Worked example and the review queue
Here is a single local test, not a vendor case study. A 9-attorney litigation group closes a month with 1,240 Clio Manage activities at a $385 blended rate. A configurable route reads each Activity’s billed_status, which Clio documents on the Activities API (Clio API – Activities). It flags 186 activities still unbilled after 14 days, drafts one pre-bill packet per matter for the billing partner, and holds 22 entries that lack a matter ID. The 9, 1,240, $385, 186, 14, and 22 figures are a test design for that sample; they are not Clio performance, recovery, or ROI.
Configure US Tech Automations to subscribe only to Activities that already exist in Clio, require billed_status plus a matter identifier, and stop when either field is missing. The output that should land in the coordinator’s hands is a queue of source-linked holds, not a sent invoice. Webhook signing secrets, least-privilege API tokens, and a named human reviewer are prerequisites; this is a configurable design, not a live customer deployment.
Lawyer employment growth: 5% (2023–33) according to the same U.S. Bureau of Labor Statistics lawyers outlook. Headcount growth does not fix capture; it only increases how many timers a coordinator must reconcile.
The same pattern applies if the system of record is MyCase or CosmoLex: export or API first, validate IDs, then create a hold. Do not write time back into the PMS from a side spreadsheet. Marketing automation for law firms is a different job than pre-bill control; do not overload the billing queue with intake drips.
Common mistakes
Firms fail time billing in predictable ways. They reconstruct Friday from memory. They let originators edit rates after the pre-bill. They send LEDES without a client-code table. They call a Zap “audit evidence” because Zapier stored a run, then cannot show which partner approved the write-down.
A fair reading of no-code tools matters here. Zapier, Make, and n8n can keep run histories, retries, error branches, and exported logs when someone designs those paths on purpose. They do not automatically give you idempotency, retention, access control, or an escalation owner. If you stitch Clio → Slack → Gmail yourself, you own observability when a retry doubles a time entry.
Configure US Tech Automations differently from a generic zap by making the PMS the only writer of time, using the agentic workflow builder to open a hold task, and requiring a billing-partner click before any invoice-related message leaves the firm. That is a design choice with a human review point, not a claim that retries are unique to one vendor.
Justice gap: 92% of low-income civil problems according to the Legal Services Corporation Justice Gap Report (2022). That figure is about access to legal help, not about timers; it is here because incomplete time records also destroy the evidence a firm needs when a client disputes a bill.
Decision checklist before you switch
Use this checklist on a live sandbox, not on a sales deck. Print it once, date it, and keep the sample files next to the signed order form.
Matter identity: every timer row carries a durable matter ID, not only a client name.
Rate table: standard, courtesy, and alternative-fee rates are stored on the matter, not in a partner’s head.
Capture methods: timer, manual, split, and (if claimed) document-driven time each produce a reviewable activity.
Narrative rules: incomplete narratives cannot reach the invoice; the product shows who overrode the block.
Pre-bill: a named role can hold, write down, and release; auto-send is off until that role exists.
Trust: retainers apply in the documented order, and the product refuses an operating-account shortcut.
LEDES: a file from your tenant opens in the client’s outside-counsel tool, or LEDES is written out of scope.
Payments: processor, surcharge policy, and failed-payment retry are named; time software is not a bank.
Export: Activities or equivalent objects expose billed versus unbilled without a screenshot workflow.
Parallel run: three consecutive cycles match the old invoices before the old path is retired.
If more than three boxes fail, you are not choosing among Clio Manage, MyCase, CosmoLex, LeanLaw, and Smokeball yet. You are still defining billing policy. Software cannot invent a write-down owner.
A 0.1-hour increment is the usual U.S. default, but some clients demand 0.25. Confirm the increment, rounding rule, and whether a timer that runs 7 minutes bills 0.1 or 0.2. Put the rule in the engagement letter and in the product, not only in a partner meeting.
Glossary
| Term | Meaning in this guide |
|---|---|
| Activity | The time or expense object in the PMS, often with quantity in hours |
| Pre-bill | The draft invoice a reviewer edits before the client sees it |
| Realization | Billed amount divided by standard value of recorded time |
| LEDES | A structured e-billing file format many corporate clients require |
| Trust | Client money held separately from operating funds |
| WIP | Work in progress: recorded time not yet billed |
| Write-down | A reviewer reduces WIP before the bill is issued |
billed_status | Clio Activity field distinguishing unbilled from billed rows |
Realization is an accounting ratio, not a software feature. A product can show unbilled WIP; it cannot promise a realization target. Firms that confuse the two end up buying timers to solve a pricing or staffing problem.
When NOT to use US Tech Automations
Skip an orchestration layer when Clio Manage, MyCase, CosmoLex, LeanLaw, or Smokeball already completes capture, pre-bill, and invoice send for the only workflow you have, when the firm will not grant API access, or when no person will own write-downs. A second queue on top of a complete native bill run adds monitoring without changing the invoice. In those cases the simpler existing tool wins, and the honest move is to finish rate tables and bill templates instead of adding software.
Key Takeaways
Time billing software is the matter-linked capture and pre-bill system; calendars and spreadsheets are not substitutes.
Clio Manage and MyCase fit full-practice firms; CosmoLex fits native legal accounting; LeanLaw fits QBO-led firms; Smokeball fits document-driven automatic time.
Score capture, pre-bill holds, trust/ledger posture, LEDES, and export IDs; do not score directory stars.
Treat license quotes as contact-vendor until an order form exists; budget buyer-side labor explicitly.
Any added queue must stop on missing matter IDs and must not send invoices without a named reviewer.
LEDES, trust, and payments in the same month
Time billing fails in the last mile as often as it fails at the timer. A complete Activity with billed_status unbilled is still not a bill if the LEDES file uses the wrong client matter code, if a retainer is applied to the operating account, or if the payment processor settles to the wrong entity.
Run three extra sandbox tests that have nothing to do with which logo you like. First, produce two LEDES files from the same pre-bill: one with the client’s required UTBMS codes and one with a deliberate missing code. The product should fail the second file in a way a coordinator can see. Second, take a $2,500 retainer, apply $400 to a bill, and show the trust balance. If that demonstration requires a side spreadsheet, you do not have trust accounting; you have a timer. Third, refund a $50 overpayment and show the audit line. Processors and PMS refunds are different buttons; the billing coordinator must know which one they pressed.
None of those tests are reasons to buy a second platform. They are reasons to finish configuration on Clio Manage, MyCase, CosmoLex, LeanLaw, or Smokeball. Firms skip them because they are unglamorous, then spend the next quarter reconstructing invoices from PDF.
Payments deserve the same suspicion as capture. LawPay, Clio Payments, MyCase Payments, and generic card processors all take a rate you will not see in the PMS license line. Record the rate on the order form. If the firm bills clients for processing, put that policy in the engagement letter, not in a partner Slack. Time billing software can store the surcharge; it cannot make a fee ethical.
When a corporate client insists on monthly LEDES and a consumer client insists on a PDF with a pay link, you need two bill templates and one pre-bill owner, not two practice systems. The evaluation-criteria table already weights LEDES at 15%. If you do not have corporate e-billing, reallocate that weight to capture and trust rather than pretending every firm needs the same stack.
A coordinator who can reconstruct a 12-invoice parallel run, a 2-file LEDES pair, and one trust application without calling the original implementer has an operable system. A partner who can only start a timer in the mobile app does not.
FAQs
What is the best time billing software for law firms?
The best time billing software is the product that already stores matters, timers, pre-bills, and the ledger path you will actually run, then proves LEDES and trust in your account. Clio Manage and MyCase are the usual full-practice starting points; CosmoLex, LeanLaw, and Smokeball win on accounting shape or automatic document time.
Can Zapier replace a practice-management billing module?
Zapier cannot replace a practice-management billing module because it does not own matters, trust, or official invoices. It can carry a notification or a hold flag if you design retries, error branches, and logs, and if a person still approves every bill.
Does Clio Manage support LEDES billing?
Clio Manage supports LEDES on plans and configurations that include e-billing; demand a sample file from your tenant rather than treating a marketing page as proof. If the sample fails client codes, stay on the current process until it passes.
When should a firm keep QuickBooks as the ledger?
Keep QuickBooks as the ledger when the firm already closes the books there and will not staff a second GL, which is the LeanLaw shape. Move to native legal accounting such as CosmoLex when trust and legal billing need one product.
How should unbilled time be aged?
Age unbilled time from the activity date against a written hold policy, for example 14 days to coordinator review and 30 days to partner review. Software can list aging; only a person can write down or write off.
What travel rate applies to billed mileage?
Business mileage rate: 70 cents per mile (2025) according to the IRS standard mileage rates. Time billing software should store the firm’s chosen rate; it does not decide tax treatment.
Verdict
Start with the system of record that matches accounting posture: Clio Manage or MyCase for a full PMS, CosmoLex for native legal books, LeanLaw for QBO, Smokeball for automatic document time. Prove capture, pre-bill, trust, and LEDES on a 20-entry sample before you buy add-ons.
Bankruptcy filings: +16.8% year ending June 2024 according to the Administrative Office of the U.S. Courts. Caseload swings change how many activities a coordinator must review; they do not pick a vendor.
If the PMS already invoices cleanly, stop there. If unbilled aging, missing matter IDs, or LEDES exceptions still fall on the floor, configure a hold queue with human review and keep the PMS as writer of record. See current pricing when you want that queue scoped against a de-identified pre-bill sample, and start from US Tech Automations only after the sample and the reviewer exist.
About the Author

Helping businesses leverage automation for operational efficiency.