Inside LawAccounting's Check Printing & Payment Run Engine: How Law Firms Cut Trust and Operating Payments in Batches Without Ever Crossing an Account (2026 Feature Spotlight)

🧾 The Twenty Minutes Where Compliance Actually Fails

Ask a firm to describe its trust controls and you will hear about the chart of accounts, matter ledgers, and monthly three-way reconciliation. All of that matters. But look at the disciplinary summaries any state bar publishes and the recurring pattern is not a design flaw in the ledger. It is a disbursement that should never have gone out: a check written against a client's funds before the settlement deposit cleared, a payment drawn on the IOLTA account because that was the checkbook in the drawer, a voided check that was never reversed in the books.

Those are all process failures at the moment of payment. Which means the control has to live at the moment of payment too.

⚙️ How the Payment Run Engine Works

1. Account-scoped from the first click

A payment run begins by selecting the disbursing account - operating, IOLTA, a non-IOLTA trust account, escrow, or payroll. From that moment, the batch is scoped. Only obligations legitimately payable from that account appear as selectable. A vendor bill coded to firm overhead simply cannot be picked up in an IOLTA run, because it never enters the candidate list.

2. Client-ledger validation before the batch will build

For trust runs, the engine validates each proposed payment against the individual client ledger, not just the account balance. A $9,400 medical lien payment on a matter holding $9,150 is rejected at build time with the specific shortfall named - long before anything prints and long before the bank produces the overdraft notice that goes to the state bar.

3. Cleared-funds enforcement

The engine distinguishes deposited funds from collected funds. Disbursing against a settlement check that has been deposited but has not cleared is one of the most common serious trust violations, and it is invisible in a system that only tracks book balances. Payment runs flag or block uncollected-funds disbursements according to the rule your jurisdiction applies.

4. Approval gates that match how firms actually sign

Most firms have thresholds - a paralegal can release a $200 filing-fee reimbursement, but a $47,000 settlement disbursement needs a partner. Approval routing is configurable by amount, account type, and payee category, with each approval time-stamped and attributed. Trust runs can require a second approver regardless of amount.

5. One posting, three places

When a run is released, a single transaction posts the general ledger entry, the matter-level ledger entry, and the payables settlement together. There is no overnight sync, no export file, and no window in which the check exists but the books do not reflect it. That window is where reconciliation differences are born.

💳 Checks Are Not Going Away - But They Are Not the Whole Run

Legal disbursement remains stubbornly paper-heavy: courts, some medical providers, expert witnesses, and many lienholders still want a physical check. The engine treats check and electronic payment as two output methods of the same controlled run, so a single approved batch can produce printed checks for the lienholders and ACH payments for the vendors who accept them - with one posting, one audit trail, and one reconciliation.

📉 What It Changes in Practice

Firms that move disbursement into a controlled run typically report three shifts. Check runs that took most of an afternoon compress to under an hour, because the eligibility checking that used to be manual now happens at build. Month-end trust reconciliation gets shorter, because outstanding-check lists and void handling are already accurate. And the anxious partner question - "are we sure nothing went out of trust that shouldn't have?" - gets answered by a report instead of a memory.