Legal Services Offshore blog
Triage trust account requests before any disbursement
A preparation routine that gathers the ledger, the approval, and the supporting document for every trust request while leaving the disbursement decision with the authorized signer.

Identify the request type first
Trust account requests are not all the same, and the first step is to classify the request before gathering documents. A client cost advance, a third-party payment, a fee transfer, and a refund each follow a different path. Record the request type, the matter, the client, and the amount requested. If the request does not fit a defined type, stop and route it to the authorized signer rather than choosing the closest category.
A clear classification prevents the team from applying the wrong approval rule. A fee transfer may need a bill and an engagement provision, while a third-party payment may need an invoice and a payee confirmation. A refund may need a closing statement and a client instruction. Write the required evidence for each type in the procedure so the preparer does not have to improvise. The classification is an administrative step, not a legal conclusion about whether the funds may be released.
Verify the client ledger and the matter
The request should be matched to the client ledger and the matter record before any document is prepared for signature. Confirm the client name, the matter number, the available balance, and any hold or lien noted in the file. A request that exceeds the available balance needs an explicit explanation, not an adjustment to the ledger. Record the ledger date and the balance observed.
If the ledger and the request disagree, preserve both observations and route the difference to the authorized signer or bookkeeper. Do not move funds between client ledgers to make a request work. Do not apply an unrelated credit without written approval. The preparer can organize the comparison and flag the discrepancy, but the decision to release funds belongs to the lawyer or firm role authorized under the firm's trust policy and jurisdiction.
Keep the approval with the authorized signer
Every trust movement needs an approval from a person authorized to give it. Record the approver's name, role, the date and time of approval, and the exact scope approved. An approval to pay a vendor is not an approval to pay a different amount or a different payee. If the approval arrives in an email, link the message rather than retyping it into a note. If the approval is verbal, record the details and ask the approver to confirm in writing.
The preparer should never sign as an approver or use a shared login to record approval. A shared credential destroys the evidence of who decided. If the authorized signer is unavailable, the procedure should name a backup rather than allowing the request to proceed informally. A payment held for approval is a controlled status, not a failure. The record should show who is expected to approve and when the request will be reviewed again.
Record the supporting document for each movement
Each request should point to the document that supports the amount and the payee. For a vendor payment, that may be an invoice and a statement of account. For a fee transfer, it may be a bill and the relevant engagement language. For a refund, it may be a closing statement and a client direction. Record the document identifier, the version, and the date reviewed. Do not rely on a description of the document when the document itself can be linked.
If the supporting document is missing or inconsistent, record the specific gap. A missing invoice is different from an invoice that names a different entity. The preparer can ask the client or the matter team for the missing item, but should not create a substitute document. When the amount is calculated, show the calculation and the source figures. A trust request that cannot be recalculated from its supporting documents is not ready for approval.
Flag shortages and unidentified funds
A shortage or an unidentified deposit is a serious signal, not a routine exception. If the ledger shows less than the request or contains funds that cannot be matched to a client, stop the request and escalate. Record what is known, what is missing, and who has been notified. Do not attempt to correct the ledger by reallocating funds or by delaying the entry. Those actions can make the record harder to reconstruct.
The firm's trust policy and the applicable jurisdiction govern how a shortage or unidentified fund is handled. The preparer's role is to preserve the evidence and follow the escalation path. Keep the request in a hold status with a clear reason and an owner. If the issue affects other clients, the authorized signer needs to know promptly. A calm, documented escalation protects the client and the firm far better than an improvised fix.
Separate fee transfers from third-party payments
A fee transfer moves earned funds to the firm, while a third-party payment moves client funds to someone else. The evidence and the approval path differ, and mixing them creates confusion. For a fee transfer, confirm the amount earned, the bill, and the client's consent where required. For a third-party payment, confirm the payee, the invoice, and the client's direction. Record the distinction in the request type so the reviewer sees it immediately.
Do not net a fee against a third-party payment without explicit approval. A netted transaction can obscure the gross amounts and make a later reconciliation difficult. If the client asks the firm to pay a vendor from trust and also transfer a fee, record two separate movements with separate approvals. The bank and the ledger should tell the same story. A clean separation also makes the monthly reconciliation easier and gives the firm a defensible record if the client asks for an accounting.
Close the request with a dated confirmation
The request is not complete when the payment is approved; it is complete when the movement is recorded and confirmed. Record the payment date, the method, the confirmation reference, and the ledger entry. Link the bank confirmation or the transaction record to the request. If the payment fails or is returned, keep the original request and add the exception with its resolution. Do not overwrite the first attempt.
Send the client a clear confirmation through the approved channel when the firm's procedure requires it. The message should state the amount, the payee, the date, and the remaining balance without offering legal advice. Before closing, compare the request, the approval, the ledger, and the bank record one last time. A monthly sample of closed requests can reveal recurring gaps in documentation or approval. Fix the procedure before the next cycle rather than relying on the same preparer to catch the same problem.