ERP vs. Practice Management Software: What Law Firms Actually Need
A 45-attorney litigation firm spent eight months evaluating a full ERP platform, drawn in by the pitch that it would replace their aging practice management system entirely. Midway through the evaluation, their COO realized the ERP had no concept of matter-based trust accounting, the rule, enforced by state bar associations, that client retainer funds must be held in segregated trust accounts and tracked matter by matter, never commingled with the firm's operating funds. The ERP vendor's answer was a custom module, quoted at an additional $85,000. The firm ultimately kept their practice management system for trust accounting and time tracking, and layered a much smaller ERP deployment underneath it just for general ledger and vendor payables. That split is more common in legal than the replace-everything pitch suggests.
What practice management software already does well
Purpose-built legal practice management systems (Clio, ProLaw, Aderant) are built around three things a generic ERP typically handles poorly or not at all:
- Matter-based trust accounting: segregating client funds by matter, with the specific reporting formats state bar associations require, and hard controls preventing commingling.
- Conflict-of-interest checking: cross-referencing a new client or matter against every party the firm has ever represented, opposed, or had a relationship with, across the firm's entire history.
- Time and billing tied to matters: billable hour capture, matter-level budgets, and the specific invoice formats corporate clients require (LEDES billing codes, for instance) for outside counsel spend.
These aren't generic business processes with a legal skin on them. They're built around obligations that come from bar association rules and client billing guidelines that have nothing to do with how a manufacturer or distributor runs its books.
Where a general ERP genuinely adds something practice management doesn't
Practice management systems, in turn, are usually weak at the things a general ERP is built for:
- Firm-wide financial consolidation: a firm with multiple offices or practice groups needs consolidated financial reporting that most practice management tools don't do well, since they're built around matters and billing, not multi-entity accounting.
- Vendor and operational procurement: office leases, IT vendors, facilities, research subscriptions (Westlaw, Lexis), the operational side of running the firm as a business, separate from client matters.
- HR and payroll: practice management tools generally don't touch this at all.
- Budgeting and forecasting: firm-level financial planning across practice groups, which requires the kind of general ledger detail an ERP is designed around.
The integration pattern that actually works
Rather than choosing one system to replace the other, the pattern that shows up most often in firms above roughly 30 attorneys is running both, integrated: practice management stays the system of record for matters, trust accounting, time entry, and client billing; the ERP handles firm-level general ledger, AP, HR, and operational procurement, with billed revenue and trust transactions syncing from practice management into the ERP's GL on a scheduled basis, usually nightly. Below roughly 15 to 20 attorneys, the operational complexity often isn't there yet to justify running two systems, and a practice management tool with basic accounting built in is usually sufficient on its own.
What to ask before treating an ERP as a PMS replacement
Firms that go into an ERP evaluation assuming it will replace practice management entirely tend to discover gaps mid-implementation, the way the litigation firm above did. Four questions surface most of the gaps early:
- Does the system support matter-based trust accounting with the specific segregation and reporting your state bar requires, natively, not as a custom-built module?
- Does it run conflict checks against the firm's full historical client and matter list, not just active matters?
- Can it produce LEDES-format invoices, or whatever billing format your largest corporate clients require?
- What's the actual cost of the gap-filling custom modules, quoted up front, not discovered during implementation?
What happens when a firm skips this evaluation
The failure mode isn't usually a dramatic system crash, it's a slow accumulation of workarounds. A firm that discovers mid-implementation that its ERP can't handle trust accounting properly often ends up running trust transactions in the old system anyway while the rest of the firm moves to the new one, creating exactly the two-system reality it was trying to avoid, except now unplanned and unbudgeted, built during a live implementation instead of designed deliberately from the start. The litigation firm above at least caught the gap during evaluation, before go-live, which is what kept the $85,000 custom-module quote from becoming a forced mid-project change order instead.
E-billing and outside counsel guidelines
Corporate clients with in-house legal departments increasingly require outside counsel to submit invoices through an e-billing platform (Legal Tracker, Collaborati, or a client's own portal), formatted to specific outside counsel guidelines that dictate everything from how travel time gets billed to which timekeepers are pre-approved for a matter. This is a practice-management-side requirement, not a general-ERP one, and it's worth confirming during evaluation whether the practice management system integrates with the specific e-billing platforms your largest clients actually use, since a mismatch here creates the same kind of manual rework the trust accounting gap did for the litigation firm above, just recurring every billing cycle instead of showing up once.
Multi-jurisdiction firms face an added wrinkle
Firms with offices in multiple states face a complication that's easy to miss during a single-office demo: trust accounting rules are set at the state bar level, and a firm licensed in three states may need to satisfy three separate sets of trust accounting reporting requirements simultaneously. Practice management platforms built for multi-jurisdictional firms handle this natively; smaller or single-state-focused platforms sometimes don't, which is worth testing specifically with a firm's actual jurisdictions during a vendor demo rather than assuming multi-state support because a vendor's marketing page says it serves firms nationwide. None of this changes the underlying two-system recommendation. It just means the practice management half of that pairing needs its own careful evaluation against the firm's specific jurisdictions and client billing requirements, the same way the ERP half needs evaluation against firm-wide financial consolidation needs.
A realistic timeline for evaluating both halves properly, practice management fit and ERP fit, separately rather than assuming one vendor's combined pitch covers both, runs 3 to 5 months for a firm in the 30 to 75 attorney range: roughly six weeks for practice management requirements gathering and demos with the firm's actual jurisdictions and top clients' billing guidelines represented, six weeks for ERP evaluation focused on financial consolidation and HR needs, and the remainder for integration planning between the two systems before any contract gets signed.
Pricing reality
Legal-specific practice management platforms typically price per attorney seat, often in the $80 to $150 per user per month range for the mid-market tier, with paralegals and support staff usually priced lower. A general ERP layered on top for firm operations adds its own per-user cost on top of that, usually for a much smaller user count (finance and HR staff, not every attorney). Running both isn't cheap, but it's usually still less expensive than paying for custom trust-accounting development inside a general ERP. It's worth checking against a cost-per-user calculator using your actual attorney and staff headcount before assuming a single-platform approach is the cheaper path.
The core decision isn't ERP or practice management, it's recognizing that they solve different problems, and that most firms past a certain size end up needing both rather than picking a winner.