Map the handoffs before you build anything
Picture a small law office on a Monday morning. A check arrives in the mail for a client matter. A bank notice says a wire came in, with only a last name in the memo. A client says they paid online Saturday. The check lands on the paralegal's desk, the wire notice sits in the office manager's inbox, and the bookkeeper will see the online payment when the processor report comes in. By Wednesday, three people each know one piece, and nobody can say where each payment stands.
That scene is an illustration, not a TwoQM client. Many law firms use practice management and accounting software and still pass incoming payments from person to person by hand. TwoQM builds custom software that records those handoffs: who received what, when, who has it now, and what step is still open.
Start with the boundary. Which funds belong in trust, how quickly they are handled, how the account is reconciled, and what clients are told are decisions for the firm's lawyers under the rules that apply to them, with their bank and accountant. This article does not answer those questions, and software should not either. A receipt log records the steps people take. It is not the firm's trust ledger.
This is also not consultation intake and document collection, which covers first inquiry to a complete matter file. This piece starts when a payment shows up.
Here is an original example, not a measured result. A four-lawyer Rio Grande Valley firm sketches its process on a whiteboard and finds five handoffs:
Arrival. A payment or notice reaches the firm by mail, at the front desk, from the bank, or from a payment processor.
Matter match. Someone connects the payment to a client and matter, or flags that they cannot.
Lawyer decision. The responsible lawyer, or the person the firm designates, records how the funds are to be handled.
Bank step. An authorized person completes the bank step the firm's procedure calls for and records the bank's reference.
Ledger entry. The bookkeeper enters it in the firm's accounting system, which stays the official record.
Each arrow between those steps is a handoff where something can sit unnoticed. The whiteboard also shows no written answer for "who owns a payment that matches no matter." Find that gap before building anything.
What each log entry records
The receipt log needs a few fields, and none asks software to judge anything:
Received: date and time, who received it, and the form it came in (mailed check, wire or ACH notice, card or online payment).
Payer and matter as recorded: the payer's name as it appears and the matter it appears to belong to, or "unmatched."
Current holder: the named person who has the item or task now.
Handling decision: stays "pending lawyer decision" until an authorized person fills it in. The system never infers it.
Bank reference: copied from the bank's own record by the authorized person after the bank step.
Ledger reference: the entry ID from the accounting system, added by the bookkeeper.
Scans of checks and notices stay in the storage your firm already approved; the log can point to them without copying them.
Handoffs, not edits
Every time an item moves, the log adds a line instead of overwriting the last one: from whom, to whom, when, and why. Corrections are new, named lines; originals stay visible. Access follows roles the firm sets: the front desk creates arrivals, designated people record decisions and bank steps, and the bookkeeper adds ledger references.
The working view is short: open items sorted by age, with the current holder and next step visible. The firm sets what "too long" means for each step; the software shows the age and alerts the named owner when that threshold passes. Unmatched payments go to an exceptions list with one named owner until a person resolves them. The system never matches or closes an item on its own.
Where AI helps, and where it stops
Logging, routing, and age alerts are ordinary business automation and do not need AI. AI can help on the staff side: drafting a weekly summary of open handoffs, suggesting a possible matter match for a person to confirm or reject, or preparing a first Spanish draft of an acknowledgment that a bilingual team member edits. It never records a handling decision, marks a bank step or ledger entry complete, closes an exception, or sends anything to a client.
Connect it to the systems you already run
Your accounting or trust accounting system stays the source of truth for ledgers, and your bank's records stay the source of truth for what the bank received. A receipt log can look up matters in your practice management system and receive ledger IDs from accounting, if those systems allow it. TwoQM calls this connected systems work, and whether your current software supports those connections is confirmed during scoping. Sometimes a shared, access-controlled log plus a written handoff map is enough, and scoping should say so.
Where to start this week
Have the people who touch incoming payments draw the path one payment takes, from arrival to ledger entry. Write a name next to every handoff and circle any step with no name, especially unmatched payments. Bring that map to the responsible lawyer, who decides the rules; the map becomes the brief for any tooling.
If you want those handoffs recorded in one place with a named owner at every step, TwoQM can scope the log, roles, and connections around your firm's existing systems. Pricing explains how business apps, systems, and custom software are scoped. TwoQM builds tooling; it does not give legal, ethics, or accounting advice, and no software makes a firm compliant on its own. Nothing here is legal advice.