Law firms researching Acumatica get most of the way to "yes" on the billing side and then hit a wall that isn't really an Acumatica problem — it's a category of accounting most general-ledger ERPs don't model natively: client trust accounting, the IOLTA-style segregation of client funds from firm operating funds required by bar regulations in most jurisdictions. Being upfront about that gap early saves everyone a bad surprise mid-implementation.
Billing and matter management: the solid part
Matters map cleanly onto Projects, the same way engagements do for consulting or accounting firms — a Project per matter, tasks per phase of work, time and expense captured against the matter, billing rules for T&M (the dominant pattern in litigation and most corporate work) or fixed-fee (increasingly common for defined-scope transactional work). Attorney and paralegal rate tiers resolve the same way as consulting billing rates: employee override, then task, then a default. None of this needs customization.
The trust accounting gap, honestly
Client trust funds are not the firm's money and must be tracked separately, per client, reconciled independently, and never commingled with operating cash — that's the IOLTA principle common across US states and mirrored by similar client-account rules in other jurisdictions (including Kenya's Law Society trust account rules). Acumatica's Cash Management module does not ship a purpose-built trust-accounting mode with per-client sub-ledger segregation and the specific compliance reporting bar associations expect. This is not an Acumatica failing exactly — most horizontal ERPs share the gap; it's specialized legal-practice-management software (Clio, PracticePanther and similar) that natively owns this, which is why so many firms run one of those alongside a real accounting system, or exclusively, for the trust side.
The workaround that actually holds up
The pattern I use when a firm insists on running trust accounting inside Acumatica rather than a separate trust tool:
- A dedicated Cash Account per trust bank account, flagged as a controlled/restricted account so nothing posts to it except through Cash Management documents — the same discipline described in bank-reconciliation setups generally, but non-negotiable here.
- A required Subaccount or a custom "Client Matter" dimension on every trust transaction, so the ledger can produce a per-client trust balance, not just a firm-wide trust total. A firm-wide balance is worthless for compliance; regulators want to know client X's balance never went negative even for a day.
- A three-way reconciliation report (bank balance = book trust balance = sum of individual client ledger balances) run at least monthly, ideally as a scheduled GI-based report, because the whole point of trust accounting rules is catching a shortfall before a client or regulator does.
I have seen a well-intentioned automatic sweep/overdraft-protection integration briefly move funds between a firm's operating and trust accounts during a cash crunch. That is exactly the commingling trust rules exist to prevent, and it can be a bar-discipline matter regardless of intent or how quickly it's reversed. If any bank-feed automation touches these accounts, trust accounts need to be explicitly excluded, in writing, from any sweep logic.
Wrapping up
Matter billing, time and expense, and rate tiers are a genuine Projects-module fit for a law firm. Client trust accounting is the honest gap — Acumatica can be configured with restricted cash accounts and a matter-level dimension to approximate it, but firms with serious trust-accounting compliance needs should go in with eyes open about whether that configuration is sufficient or whether a dedicated trust tool integrated via the API is the safer call.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.