Legal Services Offshore research · Access Governance
Trust request evidence: what a disbursement file shows
A bounded review of whether trust disbursement requests carry the ledger match, the authorization, the supporting document, and the posting confirmation.

Research context
This research brief is designed for legal operations planning. Use the findings to ask better workflow questions. Test any proposed process against the firm’s jurisdiction, professional duties, systems, and client commitments. Treat every local result as a starting point for review rather than a universal benchmark.
Question and decision use
This study asks which required elements are present in a trust disbursement request at the moment it reaches the authorized signer. The elements are the client and matter identity, the request type, the ledger match, the supporting document, the approval, and the posting confirmation. The decision it informs is whether the firm's preparation routine gives the signer enough evidence to approve or reject the request. The study does not decide whether a disbursement is proper under the applicable rules.
A useful question names the specific risk. If the concern is an unauthorized payment, the study should test the approval and the payee match. If the concern is an unexplained ledger difference, the study should test the balance and the supporting calculation. If the concern is a missing record after the fact, the study should test the posting confirmation. Each question requires a different sample, and the team should choose one before opening any file.
Population and unit
The population should be a frozen list of trust disbursement requests prepared during a defined window, with the request type, the matter, and the status recorded. Include requests that were approved, rejected, or returned for correction. Exclude requests that were withdrawn before preparation and record the reason. The unit is one request followed from its opening event to the final posting or the end of the observation window.
If a request covers several payments, treat it as one unit only if the approval covers the whole set. Otherwise split it into separate units and record the parent request. A request that is corrected should remain linked to the same unit, with the correction event recorded rather than replacing the original observation. Report the count of requests and the count of payment movements separately, because one request can produce several movements.
Evidence dictionary
Define each required element before reviewing any request. The client and matter identity should come from the approved matter system. The request type should come from a closed list. The ledger match should show the balance observed, the date, and the account. The supporting document should be identified by its document number and version. The approval should name the authorized signer, the date, and the scope approved. The posting confirmation should show the payment date and reference.
Distinguish a missing document from a document that does not support the request. An invoice that names a different entity is present but inconsistent, and that is a different failure from a missing invoice. Define how to treat a verbal approval that was later confirmed in writing, and how to treat an approval that covers a different amount. The dictionary should also define what counts as a ledger match when the request is for a partial payment or a payment from a different client ledger.
Sampling and reviewer calibration
Draw the sample from the frozen request list using a documented method. Stratify by request type, amount band, and status so the study does not overrepresent routine fee transfers or unusually large payments. Include returned and rejected requests, because those cases show whether the preparation routine catches problems. Record the selection method and any replacement. If the sample is small, report every request rather than a rate.
Two reviewers should classify a calibration set before the main review. Compare their decisions on each element and discuss the ambiguous cases. Revise the dictionary and repeat the calibration. During the main review, double-review a subset and preserve the first ratings. A disagreement about whether an approval covers a payment is exactly the kind of case the calibration should surface. Report the disagreement and the adjudication rule rather than hiding it in a final consensus.
Measures and reporting
Report the presence of each required element as a count and a rate, with the denominator visible. A single overall percentage can hide the difference between a missing approval and a missing posting confirmation. Report the requests that were returned and the reason for each return. Report the time from request opening to approval and from approval to posting, because a slow posting can create a reconciliation problem even when the approval is sound.
Include the count of requests with a ledger difference and the count with an unidentified payee. Those are high-risk exceptions and should be reported separately. Do not combine them with a missing attachment, because the remedies are different. Report the correction rate and the reviewer who approved each correction. A request that was corrected before payment is a control working, not necessarily a preparation failure, and the report should distinguish the two.
Analysis and interpretation
Compare the element rates across request types and matter groups only when the subgroup is large enough to support the comparison. Inspect the narratives behind the largest gaps. A cluster of missing supporting documents in one request type may indicate an unclear checklist, while a cluster of ledger differences may indicate a timing or posting problem. The remedy should match the stage where the gap entered.
Do not use the study to rank individual preparers. Assignment and request complexity may explain differences that look like performance. The more useful question is whether the preparation routine gives the signer a complete package. If the signer frequently has to ask for the same missing item, the checklist or the intake form is probably incomplete. That is a process finding the team can act on without blaming a person.
Limitations and sources of error
The study observes requests that reached the preparation frame and may miss payments made outside the routine. It cannot determine whether a disbursement was proper under the applicable trust rules, and it does not review the substantive legal basis for a fee. The result describes the sampled requests, not every trust movement the firm makes. Reviewer judgment is another limitation, especially for the sufficiency of a supporting document.
System changes can affect the result. A new accounting system, a revised approval workflow, or a change in the request form may alter what is recorded. Note the relevant dates and avoid comparing periods as if the instrument stayed constant. A small sample can reveal a missing control without supporting a precise estimate. The report should state that limitation plainly and avoid presenting a local observation as an industry benchmark.
Privacy and role boundaries
Use the minimum client and financial information needed for the study. Replace client names and account numbers with study keys, restrict access to the crosswalk, and follow the firm's retention rules. Do not copy bank details or identity documents into the analysis file when a reference to the approved system is enough. The offshore team may prepare the sample, classify administrative fields, and maintain the study log.
The authorized signer decides whether funds may be released and whether an exception is permitted. The study should not be used to make a client-facing statement about the firm's trust compliance or the propriety of a payment. If a request contains information from another client, stop and report it through the firm's incident path. The privacy rule applies to the study just as it applies to the underlying ledger.
Worked example
A fee transfer request arrives with a bill, a ledger showing sufficient funds, and an email approval that names the matter but not the amount. The preparer records the request as awaiting approval rather than treating the email as sufficient. The authorized signer confirms the amount in writing the next morning, and the preparer updates the request with the new message. The ledger and the bank record are reconciled after posting.
The example shows why the evidence standard separates the scope of an approval from the existence of one. An email that approves a transfer in principle is not the same as an approval of a specific amount and payee. If the preparer had accepted the first message, the request would have looked complete while leaving the signer's intent ambiguous. The extra day is a controlled delay, not a failure, and it gives the firm a record that can be reviewed if the client later asks about the payment.
From finding to controlled change
Choose one change based on the most common or most consequential gap. It might be a required approval field, a mandatory ledger match, a clearer supporting-document rule, or a posting check before the request closes. Name the owner, the due date, and the measure that will show whether the change helped. Recheck the same measure after the next review cycle.
Keep a decision log with the finding, the change, the owner, and the result. The log helps the firm see whether a change addressed the cause or only improved the paperwork. If the measure does not move, inspect the narratives and the workflow again. The goal is a request that gives the signer the evidence needed to decide and leaves a record that can be reviewed later without reconstructing the file from memory.
Sources and method
Open each source to confirm its scope, publication date, and applicability before relying on it for a legal workflow decision.