Legal Accounting Software: 10 Questions to Ask Before You Buy

Most software demos are built to show you what the product does well. The questions below are built to find out what it does badly, which is the part you will live with.

They assume you already know you need something. They also assume you are buying for a firm with a real finance function, not a solo practice, so the stakes are a year of parallel systems and a painful close rather than a lost weekend.

1. Is this double-entry accounting, or a billing system with an accounting label?

A lot of legal software handles time, invoices, payments and a trust ledger, then calls itself accounting software. That is billing with a trust module attached.

Real accounting means a general ledger, a chart of accounts you control, journal entries, and financial statements that come out of the system rather than out of a spreadsheet someone built.

Ask to see a balance sheet and a profit and loss statement generated in the product, with the journal entries behind a number. If the answer involves exporting to something else, you are buying legal billing software and you will still need an accounting system.

2. Does it replace QuickBooks, or sit next to it?

Both answers are legitimate. Buying the wrong one is expensive.

If it replaces QuickBooks, ask what happens to your accountant''s workflow, whether they can get the reports they need, and what the tax-time export looks like.

If it syncs with QuickBooks, ask what syncs and how often. Do trust transactions sync, or only invoices and payments. Does the sync run both ways. What happens when it fails, and how do you find out. A one-way nightly sync that silently drops trust entries is the kind of thing nobody discovers until a reconciliation stops tying.

3. How does trust accounting work in every state we practice in?

This is where generic accounting software fails and where legal-specific tools differ most.

The floor is a live per-matter balance, a hard block on any disbursement that would overdraw one client even when the pooled account covers it, and strict separation of trust from operating.

Above that, the requirements vary by jurisdiction. California requires a monthly three-way reconciliation. Others differ on cadence and on records. IOLTA participation rules also vary by state, and if you hold accounts in more than one, interest remits to different programs on different schedules.

Ask what the system does when your Texas office and your Florida office have different rules. Ask to see the actual reconciliation report it produces, not a dashboard summary of it.

A bad answer sounds like "it''s fully configurable." Configurable means you will build it.

4. Who moves our historical data, and how much of it survives?

The biggest risk in this purchase is not the software. It is the twelve to sixteen weeks of moving years of trust history, client ledgers, AR, matter balances and unbilled time into it.

Get specific answers. Which records come across and which get archived somewhere read-only. Do open matters keep their full transaction history or arrive as opening balances. Who does the mapping work, their team or yours. How many hours of your staff''s time does the vendor expect to need, and when.

Then ask how the two systems get reconciled to each other before you cut over, and who signs off that the trust balances match to the cent.

5. What does the audit trail record, and how long does it keep it?

The ABA Model Rules on Client Trust Account Records propose keeping trust records for five years after a representation ends, including records of every electronic transfer with the name of the person who authorized it. States adopt their own versions.

So ask what the system logs. Who changed what, when, and what the value was before. Whether a posted entry can be deleted or only reversed. Whether the log is exportable in a form an examiner or an outside CPA can read.

A system where an administrator can quietly edit a posted trust entry is a problem no feature list will mention.

6. What is this actually going to cost us at our size, in year one and year three?

List price per user is the least useful number in the conversation.

Ask for the total: licences, implementation, data migration, training, any integration that costs extra, and payment processing rates if payments run through the platform. Then ask which modules are not in the base price. Trust accounting is a common upsell, and so is advanced reporting.

Then ask what happens when you add fifteen people. Per-user pricing that is fine at 30 users can be the reason you are having this conversation again at 70.

Get the three-year number in writing before you compare vendors, because the cheapest year one is frequently not the cheapest year three.

7. How long is implementation, who runs it, and what do we have to supply?

Vendors quote implementation in weeks. Ask what those weeks assume about your side.

How many hours a week from your controller. Who cleans the data before migration, because someone has to. Is the implementation lead an employee of the vendor or a third-party partner, and if it is a partner, who is accountable when it slips.

Ask what the last three implementations at firms your size actually took, not what the plan says.

8. What does month-end close look like in this system?

Walk the close with them, step by step, using your own process.

When does the trust reconciliation happen and who runs it. Where does the trust liability account tie to the general ledger. How do prebills get reviewed and by whom. Which reports come out at the end and can they be produced without anyone building a spreadsheet.

If close currently takes your team nine days, the question is which of those days this removes. The administrative time that goes into a close is usually the clearest place to see whether a system will pay for itself.

9. If we leave in three years, what do we get back?

Ask this in the sales cycle, because you will not get a useful answer later.

What formats can you export, does that include the full trust transaction history and the audit log, is there a fee, and how long do they keep your data after termination.

A vendor who answers this cleanly is telling you something about how they expect to keep your business.

10. Who picks up the phone on day three of close when the books will not tie?

Support tiers on a pricing page tell you nothing. Ask for the response time commitment in writing, whether it is in the contract or just on a webpage, and what counts as an emergency.

Then ask whether trust accounting questions go to general support or to someone who actually knows the rules. There is a large difference between a support agent who can reset your password and one who can tell you why your three-way reconciliation is off by $340.

Before the demos start

Send these to every vendor in writing and ask for written answers before you book the demo. You will learn as much from which questions get vague responses as from the answers themselves.

Then score the answers side by side. The system that wins a demo and the system that survives your first month-end close are frequently not the same product.