Is Built-In Trust Accounting Enough, or Do You Need Separate Software?
Most practice management suites now include a trust ledger. What you need to know is whether it meets your regulator's reconciliation, audit and record-keeping rules, or only appears to.
What "Built-In" Trust Accounting Actually Has to Prove
You're renewing or replacing a practice management system. The vendor says trust accounting is included, and a separate tool would mean more cost and one more integration to maintain. Before you accept that, ask one question: can the built-in module produce the records your regulator would ask for in an inspection, without help from spreadsheets?
"Trust accounting software" covers very different products. At one end is a per-matter trust ledger. It records receipts and payments against each client and prints a balance report, while office accounts sit in a separate system, often Xero or QuickBooks. At the other end is full legal accounting: general ledger, client ledger, office ledger and bank reconciliation in one system, built around the rules. Many vendors use the same label for both.
Our position: a single-jurisdiction firm with moderate trust volume is usually well served by a mature built-in module, as long as the vendor has a real customer base in that jurisdiction. If you have high transaction volumes, more than one jurisdiction or entity, or complex office accounting, you usually need dedicated law firm accounting software. That can run alongside the practice system or replace its accounting layer.
What Client Money Rules Generally Require, Jurisdiction by Jurisdiction
The details differ, but most common-law client money regimes rest on the same obligations. Client funds are kept separate from the firm's money. Each client has its own ledger. The firm reconciles at fixed intervals and keeps records for a set period. Some form of external review takes place.
| Jurisdiction | Governing rules (typical) | Reconciliation cadence | External oversight |
|---|---|---|---|
| England and Wales | SRA Accounts Rules | At least every five weeks, comparing bank, cash book and client ledgers | Annual accountant's report unless the firm qualifies for an exemption; the COFA is responsible for compliance |
| US states | Each state's version of ABA Model Rule 1.15, plus IOLTA rules | Varies by state; monthly or quarterly reconciliation is common, often three-way | Overdraft notification by banks in most states; some states run random audits or require annual certification |
| Australian states | Legal Profession Uniform Law (in NSW, Victoria and WA) or the local Act elsewhere | Monthly, within a set number of working days after month-end | Annual external examination of trust records |
| Canadian provinces | Law society by-laws or rules (for example Ontario's By-Law 9 or the Law Society of BC Rules) | Monthly, within a set number of days after month-end | Annual trust reporting to the law society; spot audits |
Outside these jurisdictions, practice varies. Singapore has detailed solicitors' accounts rules. India and several Gulf jurisdictions say less about format but still expect client funds to be segregated and traceable. In US states, IOLTA adds another layer. Interest on pooled accounts goes to a state program, often run by a bar foundation, and large or long-held client funds may need a separate interest-bearing account. Use the table for orientation only. What counts is your regulator's current rulebook.
Mapping Each Rule to the Software Feature That Satisfies It
Every demo will show you a tidy trust balance screen, and that screen proves very little. Check instead that each obligation maps to a control the software enforces.
| Obligation | Feature that satisfies it | What to test in a demo |
|---|---|---|
| No client ledger may go overdrawn | Hard block on payments above a matter's cleared balance | Try paying out more than the matter holds. A warning you can click past isn't enough. |
| Periodic reconciliation | Three-way reconciliation: bank statement vs. trust journal vs. sum of client ledgers | Confirm the report reconciles all three. Many tools compare only bank and journal. |
| Records retained and unaltered | Posted entries can't be changed, corrections are made by reversal rather than deletion, and there's a full audit trail | Try editing a transaction from last month. |
| Closed periods stay closed | Period locking after reconciliation sign-off | Ask who can reopen a locked period and whether that's logged. |
| Separate accounts for specific clients | Multiple trust and designated deposit accounts, with interest allocation | Set up a second trust account and a designated account in the trial. |
| Transfers to office only against a bill | Trust-to-office transfers tied to an issued invoice | Try transferring funds before an invoice exists. |
| External review | Reports in the format your examiner or accountant expects | Send sample reports to your accountant before signing. |
A module that passes every row is doing real compliance work. If it fails two or more, what you have is a ledger, and you'll need other tools around it.
Where Built-In Modules Typically Fall Short
Most built-in trust features cope with basic use. The gaps show up in five situations:
- Office accounting lives elsewhere. The trust ledger may be sound while office accounting runs in a general ledger that knows nothing about matters. Bills, disbursements and trust-to-office transfers then get re-keyed or synced, and each sync is a point where the two sets of records can drift apart.
- Thin localization. A product built for US IOLTA accounting may not handle SRA residual balance rules, Australian controlled money or Canadian provincial reporting formats. Ask how many firms in your jurisdiction use the trust module itself, not the product overall.
- Bank feeds that auto-post. A feed that creates ledger entries without review is convenient, and it's also how receipts end up on the wrong matter.
- Volume. Conveyancing and personal injury practices can post thousands of trust movements a month. A reconciliation screen designed for a few hundred becomes unworkable at that scale.
- Multiple entities or currencies. Offices in two countries, or clients paying in several currencies, often go beyond what a single-entity ledger can do.
None of these rules a product out on its own. But they're where firms most often discover that their reconciliation quietly depends on spreadsheets.
What Each Route Typically Costs
These are typical 2026 market ranges in USD. They vary by contract, region and firm size, and local pricing often differs, so confirm current figures with each vendor.
| Route | Typical cost | Main cost drivers |
|---|---|---|
| Trust module bundled in practice management | Included in plans of roughly $50–$150 per user per month; often only on mid or upper tiers | Having to move up a tier just to get trust features |
| Practice management plus a dedicated trust or legal accounting add-on | Roughly $30–$150 per month, per firm or per user, on top of the practice system | Keeping the integration working; separate training |
| All-in-one legal accounting and practice system | Roughly $80–$200 per user per month | Data migration; reconciling opening balances |
| Enterprise financial management (large firms) | Implementation often runs to six figures, plus annual licensing | Configuration, consultants, multi-entity setup |
The license is rarely the largest cost. Staff time is. A few extra bookkeeper hours a month reconciling across two systems, plus a longer annual examination or accountant's report, can easily outweigh any difference in license fees. Ask your accountant what they would charge to review records from each setup, and include that figure in your comparison.
Two Hypothetical Firms, Two Different Answers
Hypothetical example one. Say an eight-lawyer family and employment practice in England holds client money on around 150 live matters, with a few hundred movements a month. Its UK-localized practice system includes integrated legal accounts. The module blocks overdrawn ledgers, runs the five-weekly reconciliation as a three-way report and locks periods after sign-off, and the firm's reporting accountant accepts its output. Built-in is the right choice. A second system would only give errors another place to occur.
Hypothetical example two. Now take a 30-person property firm with offices in Sydney and Vancouver. It handles high-volume settlements, holds two trust accounts in each country and operates two legal entities. Its practice system's trust module was designed for one jurisdiction and syncs office accounting to a generic general ledger. Each monthly reconciliation takes days. This firm should move to dedicated legal accounting software or an all-in-one system with multi-entity support. Headcount isn't what decides it. The reasons are the two entities, the transaction volume and the two regulators.
A Decision Rule, and Who Should Sign Off
Use built-in trust accounting only if all four of these hold:
- You operate in one jurisdiction through one entity.
- The module passes every row of the mapping table above.
- The vendor has a meaningful base of trust accounting customers in your jurisdiction specifically.
- Your accountant or external examiner accepts its reports exactly as the system produces them.
If any of these fails, shortlist dedicated or all-in-one law firm accounting software. Then run a side-by-side reconciliation trial on a month of real data.
Before you sign, do three things:
- Summarize your regulator's current requirements on one page: cadence, report contents, retention period and approvals.
- Have each vendor run its reconciliation on your sample data while you watch.
- Send the resulting reports to your accountant, and to your compliance officer or trust account supervisor, for written comment.
Rules change and are interpreted locally. Confirm each requirement with your regulator, law society or a qualified accountant before you rely on any system for compliance.
Quick answers
Can we use Xero or QuickBooks alone for trust accounting?
Usually not. General ledger products can record a trust bank account, but they don't natively keep per-client ledgers, block overdrawn matters or produce a true three-way reconciliation. Firms that use them generally add a legal-specific trust ledger or an integration that provides those controls.
What is three-way reconciliation, in plain terms?
It compares three figures at the same date: the trust bank statement balance, the trust journal (cash book) balance and the total of all client ledger balances. Once timing items such as uncleared deposits are accounted for, all three should agree. How often you must do it depends on the regulator. Monthly is common, England and Wales requires at least every five weeks, and some US states allow quarterly.
Do the SRA Accounts Rules require specific software?
No. The rules set duties and outcomes rather than naming products. Those duties include keeping client money separate, reconciling at least every five weeks and keeping accurate records. Whatever system you use has to let the firm meet them, and the COFA remains responsible for compliance.
Does IOLTA accounting need different features from other trust accounting?
The core controls are the same. In US states, you also need to separate pooled IOLTA funds from interest-bearing trust accounts held for larger or longer-held sums, so the software should support multiple trust accounts and track interest correctly for each. Requirements vary by state, so check your state bar's rules.
How long must trust records be kept?
It depends on the jurisdiction. Retention periods commonly run from about five years to ten or more, and some records may have longer requirements. Make sure your software keeps records unaltered for the full period and can export them if you change vendors.
What happens to our trust records if we switch systems?
Time the migration to a reconciled month-end. Carry over opening balances for each client ledger, not just the bank total. Keep read-only access to the old system, or a full export from it, for the whole retention period. Have your accountant review the opening balance reconciliation before the old system is switched off.
Written by the Juris Tdesk Pro editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.