Inside LawAccounting's AR Aging, Client Statements & Collections Engine: How Mid-Size Firms Turn 90-Day Receivables Into Collected Cash Without Nagging Clients (2026 Feature Spotlight)

📉 The Gap Between Billed and Collected

Across the mid-market, firms are billing more than they were two years ago. They are also waiting longer to get paid. That combination produces a specific and uncomfortable pattern: a revenue line that looks excellent, a bank balance that does not match the mood, and a partner meeting where somebody eventually says "where is the money?"

The money is in accounts receivable. And in most firms, AR is managed the way it was managed in 1998: a report is run at month-end, printed, discussed briefly, and then nothing structural happens until the next month-end.

🔍 What the AR Engine Actually Does

📅 Live aging, not a month-end snapshot

The aging report is generated from the live ledger, so current, 31-60, 61-90, and 90-plus buckets reflect today, not the last close. You can slice it by responsible attorney, originating attorney, practice group, client, or matter, which matters because "the firm has $1.2M in AR" is a useless sentence and "three clients account for 61 percent of everything past 90 days" is an action item.

🧾 Client statements that consolidate across matters

Clients with several open matters routinely pay one invoice and ignore two others, not out of bad faith but because they never saw a single view of what they owe. Consolidated client statements pull every open invoice across every matter into one document, with payments and trust credits applied, so the number at the bottom is the actual number.

🔁 Structured follow-up tied to the bucket

Each aging bucket gets a defined next step: a statement at 31 days, a documented reminder at 61, an attorney-level review at 91, and a collections decision at 121. The system creates the task and assigns it. Nobody has to remember, and more importantly, nobody has to decide whether today is the day to make an awkward call.

💳 A payment path attached to the ask

Every statement carries a link to the client payment portal, which accepts card and ACH and routes operating payments to operating and trust deposits to trust. Removing the friction between "I should pay that" and "paid" is worth more than any additional reminder.

💰 Trust credits applied before the client is chased

This one saves relationships. If a client has funds sitting in trust against an earned invoice, the statement should reflect that before anyone asks for money. The engine surfaces available trust balances against open AR so the firm applies what it already holds and only asks for the genuine gap.

⚙️ How It Fits the Rest of the Ledger

📐 The Metrics That Should Move

If an AR workflow is working, four numbers change within a quarter:

• Days sales outstanding drops, because follow-up happens on schedule rather than on mood.
• Percentage of AR over 90 days falls, because problems get named while they are small.
• Realization rate improves, because fewer aged invoices get written off out of embarrassment.
• Time spent on collections goes down, because the work is distributed across the month instead of compressed into the last three days of it.

None of those require a firm to become aggressive with clients. They require the firm to be consistent, which is exactly the kind of thing software is good at and humans, understandably, are not.

🔗 Why This Only Works With Unified Accounting

An AR module bolted onto practice management software can tell you an invoice is old. It cannot tell you that the same client has $8,400 sitting in trust, that $6,200 of it is already earned against this invoice, and that the correct next action is a trust-to-operating transfer rather than a dunning email. That requires the billing ledger, the trust ledger, and the general ledger to be the same system.

LawAccounting runs all three on one Salesforce-based foundation, standalone or inside CaseQube. That is the whole reason the AR engine can be trust-aware in the first place.