Handling Client Money and Retainers Without a Trust-Accounting Headache

The sharpest line in legal finance is between money a firm holds and money it has earned. A retainer sitting in an account is the client's until work is done and billed against it. Treating it as revenue the day it arrives is not just optimistic accounting — in many jurisdictions it breaches the rules on client money.

The practical failure is subtler than outright misuse. It is a system that shows a net balance which happens to reconcile, with no visible sequence of how it got there. When a regulator or a client asks how a balance moved, a net figure is not an answer.

Billing against a retainer should read like a ledger, not a subtraction. What was held, what was drawn, against which invoice, on what date, and what remains — each step visible and in order.

That sequence is what makes the position defensible. It lets the firm show, at any point, that a specific fee was drawn against specific funds under a specific authority, rather than asserting that the arithmetic works out.

Retainer billing goes wrong in two directions, and both are common in a busy practice. A cycle is missed, and a month's fee is never drawn. Or a cycle is billed twice, because two people were being helpful on the same afternoon and neither knew the other had run it.

The fix is that the system, not a person, knows what has already been billed in the current period — computed from the retainer's own cadence, so the answer does not depend on who is looking or when.

Client money reporting has to be separable from firm revenue at a glance. What is held on account, across which clients, is a different question from what the firm has earned, and a dashboard that blends them is answering neither cleanly.

This is the same discipline that keeps proformas out of revenue: a single, consistent classifier deciding what counts as what, used everywhere, so the client-money position and the revenue position never contradict each other.

Each client's retainer carries an amount and a frequency, and Mersal knows what has already been billed in the current cycle — so a cycle cannot be missed or billed twice, and rebilling is an explicit act rather than an accident. Generation is per client or as a firm-wide batch, with visibility of what is on the monthly book.

Drawdowns are recorded as a visible sequence against held funds rather than a net figure, and settlement is guarded by an idempotency key so a retry cannot double-record a payment. Every money figure derives from fiscal documents through one shared classifier, so held funds, revenue and outstanding never disagree — and receipts issue on their own sealed serial, into the append-only ledger.