Free tools Windows power users keep installed
One-click scans. No signup required.
Choose trust-accounting software by requiring it to keep separate client or beneficiary ledgers and produce a reviewable reconciliation that ties those ledgers to the trust general ledger and adjusted bank statement. Then test its records, controls, security, migration, and exports against your firm’s workflow. No product makes a firm compliant by itself: the lawyer remains responsible for client funds, and applicable rules depend on jurisdiction.
What three-way reconciliation must show
A complete reconciliation compares three balances for the same reporting date:
As an Amazon Associate I earn from qualifying purchases.
- Adjusted bank statement balance: the bank’s balance, adjusted for timing items such as outstanding checks and deposits in transit.
- Trust general ledger or control balance: the account-level record, calculated from the prior balance plus receipts less disbursements.
- Total of individual client or beneficiary ledgers: the sum of the balances held for each client or beneficiary.
The adjusted bank balance, control balance, and individual-ledger total must agree. If the report omits one of these balances or they do not tie, the reconciliation is incomplete. Arizona guidance also calls attention to an administrative ledger for bank fees and other non-client transactions where needed. Arizona Bar trust accounting guidance
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →The ABA describes the same bookkeeping relationship: total the client ledgers, compare that trial balance with the control balance, then account for outstanding checks and deposits in transit to reconcile to the bank statement. Reviewing regularly helps isolate errors. The ABA commentary recommends monthly reconciliation as preferred practice and identifies quarterly as a minimum recommendation; those are ABA recommendations, not a universal rule. ABA client trust account records and commentary
#1 Best Overall
What to require in a software demonstration
Separate matter-level ledgers
Ask the vendor to show a receipt and disbursement posted to a specific client or beneficiary ledger. Each entry should retain its source, date, amount, purpose, payee, and resulting balance. Check whether the system makes negative balances and unapplied funds visible rather than burying them in a general account total. The ABA model records rule describes ledger records showing the source and amount of funds, charges or withdrawals, and recipients of disbursements. It is model guidance; local adoption and rules control. ABA Model Rule on Client Trust Account Records
A genuine three-way report
Require one report, for one reporting date, that displays the client-ledger total, the general-ledger or control balance, and the adjusted bank balance. Have the vendor show how outstanding transactions appear and what happens when a ledger is missing or the balances differ. A report that merely lists bank activity or displays a trust-account total is not enough to verify all three legs. Alabama Bar trust-accounting resources
Rank #2
Complete transaction and supporting records
Use the ABA model list as a practical checklist, then confirm the binding requirements where the firm practices. Records to ask about include:
- Receipts and disbursements journals, client or beneficiary ledgers, and check registers.
- Engagement or other agreements, client accountings, bills, and supporting disbursement documents.
- Bank statements, deposit records, and monthly trial balances and reconciliations.
- Electronic transfer details, including who authorized the transfer, the recipient, the trust account number, and the completion date and time.
- Related documents maintained in the client file.
The ABA model text includes a bracketed five-year retention period; that is not a universal retention rule. Check local requirements before setting retention schedules. ABA Model Rule on Client Trust Account Records
Rank #3
Exceptions a person can review
Automation can calculate balances and categorize transactions, but the person responsible for review needs to be able to inspect stale checks, unapplied funds, negative client balances, unmatched transactions, bank charges, and unusual changes. Look for a documented resolution trail showing what was investigated, who handled it, and how it was resolved. Bank feeds and bulk edits can save entry time, but they can also introduce categorization or overwrite errors; speed is not a substitute for reviewing exceptions. Arkansas Bar law-firm accounting software guide
Compare software approaches by workflow, not label
| Approach | What to verify | Best-fit considerations |
|---|---|---|
| Legal-specific accounting or practice-management software | Client and matter ledger design, three-way reconciliation output, exception controls, record exports, security, and support. | Legal applications may provide trust reconciliation reports, and some perform three-way reconciliation. Assess whether the system handles the firm’s account and matter volume rather than assuming all products do. |
| General accounting paired with trust-specific ledgers or practice-management software | Make the boundary between operating funds and client funds explicit, and test the trust module’s reports and controls directly. | This can be workable when the trust-specific component is properly configured. A familiar general-ledger product name alone does not establish that its trust workflow is adequate. |
| Spreadsheet templates | Check formula integrity, access controls, versioning, and whether the person maintaining the workbook can use automated spreadsheets reliably. | Alabama’s bar makes workbook templates available but says its practice-management program recommends them for smaller, lower-volume firms that cannot use suitable software and have experience with automated spreadsheets. The bar describes software automation as generally preferable. |
These are categories, not a comparative product ranking. Alabama Bar resources describe software applications that report or perform three-way reconciliation. The State Bar of Arizona lists Smokeball Bill as trust accounting and billing software available to its members, but that listing does not establish its current feature set relative to competitors, pricing, or independent test results. Verify current features and member availability directly before relying on either claim. Alabama Bar trust-accounting resources · State Bar of Arizona trust accounting
Rank #4
Check security, access, and exit options
Ask the vendor for specific evidence and demonstrations, not just assurances. The Arkansas Bar selection guide identifies configuration, controls, and review as central concerns. Arkansas Bar law-firm accounting software guide
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Access controls: multi-factor authentication, role-based restrictions on trust entries, and logs showing who changed what and when.
- Data protection: encryption in transit and at rest, documented backup and incident-response practices, and clarity about where client data is stored.
- Portability: confirmation that the firm can export records in usable formats, including transaction detail and reconciliation reports.
- Operational fit: support processes and a clear way to resolve accounting or access problems without losing the audit trail.
Test migration before going live
Do not treat a successful import as proof that the books are correct. Use a test migration and reconcile the opening position before staff rely on the new system.
Best Value
- Import a representative set of matters and trust transactions into a test environment.
- Verify opening client-ledger balances and the general-ledger balance against the firm’s existing records.
- Check outstanding checks, deposits in transit, and unapplied funds individually.
- Generate the three-way report and confirm that the figures tie for the same reporting date.
- Export sample reports and records to confirm they remain usable outside the system.
- Run a pilot long enough to complete at least one full billing and reconciliation cycle before go-live.
These checks help expose conversion problems while the firm can still correct them without relying on the new system for live trust activity. Arkansas Bar law-firm accounting software guide
Match the system to the firm and its jurisdiction
A solo firm with few matters and a midsize firm running several trust accounts across practice groups do not have the same needs. Consider the number of trust accounts and matters, who enters transactions, who reviews reconciliations, and whether the system can preserve a clear client-fund boundary as volume grows. Legal-specific ledger architecture may be more dependable for meaningful trust-account volume than a workaround layered onto generic bookkeeping, but a properly configured general-accounting product paired with trust-specific ledgers can also be workable. Test the actual workflow rather than inferring it from the product category.
Trust-account rules, reconciliation frequency, record retention, and handling of account activity vary by jurisdiction. For example, Texas Bar guidance calls for monthly review and reconciliation; ABA commentary describes quarterly as a minimum recommendation and monthly as preferred practice. Arizona guidance emphasizes comparing client and administrative ledgers, the general ledger, and the adjusted bank statement. These examples should not be treated as nationwide legal requirements. Consult the applicable court and bar rules for the firm’s location. Texas Bar trust account resources · ABA client trust account records and commentary · Arizona Bar trust accounting guidance
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

