Inside LawAccounting's Cash Receipts and Deposit Engine: How Law Firms Track Every Incoming Dollar From Check to Deposit Slip to GL and Trust Ledger in 2026

💸 The Problem: Receipts Are the Least-Controlled Part of Legal Accounting

Ask a mid-size firm to describe its accounts payable process and you will get a crisp answer: bill received, coded to a matter, approved, paid, posted. Ask the same firm to describe what happens when a $15,000 check arrives in the mail and the answer gets vaguer — someone photographs it, someone emails the bookkeeper, someone drives to the bank, and somewhere in there it is supposed to hit a client ledger.

That vagueness is expensive and, in trust, dangerous. The classic failure modes are all receipt-side:

🔍 How the Cash Receipts Engine Works

1️⃣ Capture at the point of receipt

Every incoming payment is entered as a receipt record with the fields that matter downstream: payer, amount, payment method (check, ACH, card, wire), check or reference number, receipt date, matter, and — critically — destination ledger: operating or trust. The destination is a required field, not a default. That single design choice eliminates the most common commingling error.

2️⃣ Apply against what the money is actually for

A receipt is not just cash; it is cash for something. LawAccounting applies each receipt to the open items on the matter — a specific invoice, several invoices, an advance cost deposit, or an unapplied trust deposit awaiting instruction. Partial payments split across invoices in one screen, and any unapplied balance stays visibly unapplied rather than silently absorbing into revenue.

3️⃣ Batch into a deposit that matches the bank exactly

This is the step most generic accounting tools get wrong for law firms. Banks do not see fourteen individual payments; they see one deposit of $47,320.18. If your books record fourteen separate lines, your reconciliation will never match cleanly and your bookkeeper will spend the first two hours of every month untangling it.

LawAccounting groups receipts into a deposit batch tied to a specific bank account and deposit date, and produces a deposit slip listing every item. The books now record exactly what the bank records: one deposit, one amount, one date — with fourteen receipts underneath it, each traceable to a matter and a client ledger.

4️⃣ Post the journal automatically — and correctly for trust

Operating receipts post as a debit to cash and a credit to accounts receivable. Trust receipts post as a debit to the IOLTA cash account and a credit to client trust liability — because trust money is not revenue, it is a liability the firm owes back. Generic accounting tools routinely get this wrong, which is precisely how firms end up with trust funds sitting in an income account.

5️⃣ Reconcile as a confirmation, not an investigation

Because the deposit batch matches the bank line, reconciliation becomes a tick-and-tie exercise. AI smart matching across 15,000+ bank connections clears the routine items; the difference detection engine surfaces only what genuinely does not match. Three-way trust reconciliation — bank balance vs. book balance vs. the sum of client ledgers — runs off the same underlying records, so the three sides agree by construction rather than by effort.

🔗 Where Card and ACH Fit

Electronic payments through the LawAccounting client payment portal (Fiserv, Stripe, and ProPay supported) create the same receipt record as a paper check — with one important addition: trust and operating payments are routed to separate merchant configurations, so processing fees never touch the IOLTA account. That is the detail that keeps card acceptance compliant. A processing fee debited from a trust account is a Rule 1.15 violation regardless of intent, and it is the single most common way well-meaning firms get into trouble with online payments.