Trust accounting software for law firms must keep a trust journal and a ledger for every client, produce a genuine three-way reconciliation, refuse payments larger than a client's balance, and print the reports a bar auditor asks for. Before buying, test it on a trial month with known errors planted in the data, and see which ones the software catches.
What law firm trust accounting software must record
Law firm trust accounting software must record every receipt and disbursement in the trust account in date order, assign each one to a client or matter, and keep the bank documents that support them. Those three records, the journal, the client ledgers and the bank file, are what state trust rules require a lawyer to keep.
State rules set the exact list, but North Carolina's is a clear example of what a system must hold. Under North Carolina State Bar Rule 1.15-3 on records and accountings, the required records include documents showing the source and date of each deposit, such as deposit slips; canceled checks or other items drawn on the account, or digital images of them; all bank statements for the trust account; and, for a general trust account, a ledger of receipts and disbursements for each person or entity showing the current balance held for them. Records must be kept for six years before the lawyer's most recent fiscal year end.
Translated into software features, that means:
- A trust journal that records each transaction once, with the date, payor or payee, amount, check or reference number and the matter it belongs to.
- Client ledgers that update automatically from the journal, so a transaction cannot be in one without the other.
- Attachments or links to deposit records, check images and bank statements, kept as long as the rule requires.
- A locked history. Once a month is reconciled, changes to it should be blocked or logged with the user, the date and the original values.
The last point is often overlooked. A trust system where anyone can quietly edit last year's entries makes the six-year record far less trustworthy. The full set of records a firm should keep, and how long, is covered in trust account record keeping requirements.
Does the trust accounting software produce a real three-way reconciliation?
Trust accounting software produces a real three-way reconciliation only if its report shows three separately calculated figures: the adjusted bank balance, the trust journal balance and the total of client ledgers. A bank reconciliation on one screen and a ledger total on another is not the same thing.
Ask the vendor to show a finished report and look for these features:
- Three figures from three sources. The bank figure should start from the statement's ending balance and list outstanding items. The journal figure should come from the journal. The ledger figure should be a sum of individual client balances, with the list attached.
- A list of every client balance. A total alone hides a negative ledger offset by an overstated one. The report should show each client and flag any balance below zero.
- A visible difference. If the three do not agree, the report should say so and show the amount. A system that forces the figures to agree, or offers an "adjustment" to make them agree, is hiding problems.
- Sign-off. The report should record who prepared it, who reviewed it and when.
Rules on electronic sign-off vary. North Carolina's rule, for instance, allows trust records to be kept electronically if printed and electronic copies in industry-standard formats can be made on demand, the records are regularly backed up, and electronically created reconciliations that are not printed are reviewed by the lawyer and signed with a digital signature. A system that cannot export a reconciliation to a standard format, or has no way to record a signature, may fall short of a rule like that.
Overdraft guards in law firm trust software
An overdraft guard is a control that stops a user from recording a trust payment larger than the client's available balance. It is the most useful single feature in law firm trust software, because it prevents the error a three-way reconciliation exists to find: paying one client's costs with another client's money.
Test what the guard actually does:
- Does it block, or only warn? A warning the user can click past is weaker than a block that needs a second person to override.
- Does it look at cleared funds? A deposit recorded today may not be collected for days. A guard that counts uncleared deposits as available will let a payment through that the bank later reverses.
- Does it apply to every payment type? Checks, wires, electronic transfers and fee transfers to operating should all be checked against the client balance.
- Is every override logged? An override should record who approved it and why.
Card payments raise a special case. When a client pays a retainer by card into trust and later disputes it, the processor may pull the money back from the account. The client's ledger then needs to absorb the reversal, and the software needs a way to record it without disturbing other clients. How processors handle disputed card payments is explained in how to reconcile chargebacks.
Trust accounting reports a bar auditor asks for
A bar auditor usually asks for the trust journal, the client ledgers, the bank statements and the reconciliations for the period under review, plus supporting documents for selected transactions. Trust accounting software should produce each of these on demand, for any past period, without manual rebuilding.
A practical report list to check in a demo:
- the trust journal for any date range, with running balance
- each client ledger for any date range, including closed matters
- a list of all client balances as of any past date
- the three-way reconciliation for each month, with the sign-off
- a list of outstanding checks with their age
- a list of client ledgers that have been negative at any time in the period
- an audit log of edits and deletions
The reports should be reproducible. Run a report for a past month, change a current-month entry, and run the past report again. If the past figures move, the software is not preserving history, and an auditor comparing a saved report with a fresh one will see the difference.
Other businesses that hold client money need the same reports. Insurance agencies that collect premiums in trust face a parallel set of rules, set out in premium trust account reconciliation for insurance agencies.
How do you test trust accounting software before the firm commits?
Test trust accounting software by loading one real month of trust activity into a trial, adding a short list of deliberate errors, and checking which ones the software catches. A demo with the vendor's clean data shows what the screens look like. A trial with planted errors shows whether the controls work.
The table below is an example test plan. The errors are invented for the trial and should be removed afterwards.
| Requirement | What to look for in the demo | Test to run in the trial month |
|---|---|---|
| Client ledgers tie to journal | Ledger updates from each journal entry | Post a receipt; confirm it appears on the ledger and the journal |
| Three-way reconciliation | Report with three separate figures and a client list | Leave one bank fee unrecorded; confirm the report shows a difference |
| Overdraft guard | Block or approval step on payments above balance | Try to pay 500.00 from a ledger holding 300.00 |
| Cleared funds | Uncleared deposits treated as unavailable | Record a deposit today and try to pay against it the same day |
| Negative ledger detection | Flag on any client balance below zero | Post a check to the wrong client; confirm the flag |
| Locked history | Edits to reconciled months blocked or logged | Edit a reconciled entry; check the audit log |
| Reproducible reports | Past reports do not change | Re-run last month's ledger list after a current edit |
| Export | Standard formats on demand | Export a reconciliation to PDF and spreadsheet |
Score each test as passed, passed with a workaround, or failed. A failure on the overdraft guard or the three-way reconciliation should usually end the evaluation, because those are the controls the firm is buying the software for.
When law firm trust accounting software is not enough
Law firm trust accounting software is not enough when the problem is outside the records it keeps. It trusts the bank data it is given, it cannot tell whether a statement was altered, and it cannot stop a person with full access from recording a false entry. Those gaps need people and separate checks.
Three gaps to plan for:
- Bank data quality. A trust product that imports bank activity from a feed or a file depends on that import. If the feed drops a transaction, or a statement is keyed by hand with an error, the reconciliation starts from a wrong figure. Someone should compare the imported activity to the actual statement each month.
- Segregation of duties. In a small firm, the same person may record receipts, write checks and reconcile. Software cannot fix that. A lawyer who reviews the statement and the reconciliation each month, separately from the bookkeeper, adds the independence the software lacks.
- Judgment about fees. Software can record a fee transfer, but it cannot decide whether the fee was earned. That decision belongs to the lawyer, with the file.
The bank-statement gap is where PreciseBankFlow fits alongside trust software rather than in place of it. It is not a trust ledger. It reads each trust account statement, checks that the statement foots, matches its lines to the trust register and lists what does not match, which gives the reviewing lawyer an independent check on the figures the trust system starts from.