A monthly trust accounting checklist for California law firms

Use this guide to organize the monthly work

A monthly trust accounting process needs more than a date on the calendar. Someone must obtain the records, prepare a supported comparison, resolve questions, arrange attorney review and preserve the completed package. This guide provides a suggested operating framework for those handoffs, with fictional examples and reusable checklists.

For California accounts, the underlying monthly reconciliation requirement appears in standard (1)(d) under Rule 1.15 (opens in a new tab or window) . The rule and standards govern the relevant obligations. The schedules, worksheet fields and role assignments below are Mako's suggested practices, not additional statutory requirements or a prescribed State Bar timetable.

Use the guide as a reference. Start with the checklist, then open the sections relevant to your current obstacle. A firm with missing historical records will need a different work plan from a firm with complete records and one outstanding check. The aim is to make that difference visible rather than force every situation through an identical sequence.

The examples assume California trust-account records and fictional transactions. They do not resolve ownership of funds, authorize a disbursement, establish whether fees are earned or determine how another state's rules apply. Those questions require the relevant facts and appropriate professional review. The responsible attorney's role should remain explicit throughout the process.

The monthly trust accounting checklist

Keep this checklist beside the monthly account inventory. Mark a step complete only when its evidence exists. Where a question prevents completion, name the issue and next owner instead of substituting a checkmark. A short exception note is more useful than a reassuring status that conceals missing work.

1. Confirm scope. Identify each account, statement period and preparer. Include accounts that need review even when activity appears limited.
2. Collect the records. Obtain the statement, journal, individual ledgers, summary and outstanding-item support through the approved channel.
3. Align dates and filters. Check that reports describe the same account and closing date. Identify the supported opening balance.
4. Compare the records. Prepare the three-way reconciliation and trace transaction questions to their evidence.
5. Investigate exceptions. Distinguish missing information, timing differences, recording errors and decisions requiring the attorney.
6. Document corrections. Record the cause, approval, affected entries and regenerated reports; preserve the review trail.
7. Assemble the review package. Present the three totals, schedules, outstanding questions and supporting records clearly.
8. Obtain attorney review. Make the reviewer’s questions and conclusions part of the record. Do not imply review occurred before it did.
9. Archive the completed version. Retain source records, explanations and review evidence under the firm's applicable retention process.
10. Carry forward specific actions. Track outstanding items and process improvements into the next period without creating duplicate transactions.

For practical use, add columns for account reference, closing date, person responsible, status, evidence location and next action. A firm with several accounts can then see which packages are waiting on statements, which are in preparation and which need a decision. The checklist coordinates work; the underlying reconciliation and records support the conclusion.

Do not make a missed internal target disappear by moving it to the following month. Record what is outstanding and how it will be addressed. Likewise, do not label an account reconciled because all files arrived. File receipt, preparation, resolution and review are different milestones.

At the end of a cycle, inspect whether the checklist helped people act. If a line repeatedly attracts the same question, clarify its wording or the supporting request. Avoid adding a new paragraph of instructions every time someone asks a question. Often a clearer label, example or assigned owner is enough.

Assign responsibilities before requesting documents

Start with the decisions the work requires. Who can obtain the bank statement? Who can explain a receipt? Who maintains matter information? Who may prepare a correction? Who resolves questions about entitlement or authorization? A job title alone does not answer all of these questions.

In a fictional small firm, an office manager gathers records, an accounting preparer builds the comparison, and the responsible attorney reviews the package and addresses substantive questions. Another firm may combine some roles. The important point is that each task has a named owner and that combining roles does not obscure the review responsibilities.

We recommend a simple responsibility map with four columns: task, preparer, decision-maker and evidence of completion. Use it for recurring activities such as supplying statements, confirming allocations, approving corrections and reviewing the final package. Keep it short enough to use during the actual handoff.

Distinguish access from authority. A person who can edit a record in software is not necessarily authorized to decide the underlying treatment. Similarly, someone who has received an invoice is not automatically authorized to move trust funds. The map should identify which questions the preparer can resolve from records and which require a decision from the attorney.

Plan for absence. If the usual contact is unavailable, identify an approved substitute before the closing period. Do not respond to a delay by forwarding sensitive records to an unapproved contact. The firm's owner or authorized decision-maker should confirm any change to responsibility or access.

For each handoff, agree what the recipient should receive. A preparer needs usable records and explanations, while a reviewer needs a coherent package and clearly identified decisions. Giving both people an undifferentiated folder of files can create repeated work without clarifying responsibility.

Record the agreed roles in the engagement or operating protocol. Revisit them when staff leave, services change or a new account is added. A once-accurate map can become misleading if it continues to name people who no longer perform the work.

Create an internal calendar with dependencies

Build the calendar around the information required for each task. A statement must be available before its ending balance can be confirmed. Missing transaction explanations may prevent a package from reaching review. Scheduling every task for the same day ignores those dependencies and makes delays difficult to diagnose.

As an illustrative workflow, the firm can first collect period-end records, then prepare the comparison, then resolve exceptions and arrange review. Set actual target dates according to the firm's responsibilities and available records. This guide does not prescribe a universal deadline measured in business days after month-end.

Use a status that explains the next action. “Waiting for statement” identifies a dependency. “Prepared with two allocation questions” identifies a review task. “Awaiting attorney review” identifies the handoff. These descriptions are more useful than a single progress percentage that combines unrelated work.

When a target is missed, record the cause and impact. If a statement is late, identify the affected account and ask for that record. If several packages are blocked by the same unresolved opening balance, treat that as a shared issue rather than sending separate generic reminders for each package.

Agree how reminders operate. A request should state what is needed, why it matters to the current task and when the sender needs a response. The frequency should reflect urgency and the firm's protocol. Repeated messages with no change in information can create noise without resolving the underlying obstacle.

Keep escalation deliberate. If the assigned person cannot answer, refer the question through the agreed chain rather than automatically broadening access or contacting another client representative. The accountant's need for information does not itself establish permission to share the surrounding records.

After the cycle, compare planned and actual handoffs. Use recurring delays to improve the process, not to invent a claim that the next cycle will always close faster. A realistic calendar makes constraints visible and gives the firm a basis for assigning work.

Maintain an account and period inventory

A reliable monthly process begins with knowing which accounts are in scope. Create an internal inventory that identifies each account by an appropriate reference, its relevant dates, the responsible people and where its records are obtained. Keep sensitive account details in the authorized system rather than in a widely distributed planning document.

Record account openings, closures and changes to service scope. An account closed during a period can still have a final statement and activity that need to be understood. An account newly added to the engagement may need opening records before the preparer can explain its balance.

The inventory should also identify the last supported reconciliation available to the preparer. If the firm believes an account was reconciled but cannot locate the package, record that limitation. Do not infer support from a filename or from an assurance that the work was probably completed.

For a fictional inventory, Account North may have complete August support and September records ready. Account South may have September statements but no reliable July opening balance. Those accounts are not at the same stage, even if their current file folders contain the same number of documents.

Track periods explicitly. A checklist for “this month” becomes ambiguous when staff review it several months later. Use the actual closing date and account reference. Where the statement period differs from the expected reporting period, identify the difference and obtain the necessary explanation rather than silently assuming they align.

Reconcile the inventory to the agreed scope periodically. Ask whether new accounts, inherited records or closed matters have changed what needs attention. This is a practical completeness check, not a conclusion that the inventory itself proves all legal obligations have been satisfied.

Use the inventory to plan workload as well. Several accounts with clean prior records may need different preparation effort from one account with years of unexplained carryforward items. Scope the work around the evidence and questions, not simply the number of bank accounts.

Send precise record requests

A good request names the record and the period. Instead of asking for “the trust information,” specify the statement for the identified account, the journal through the closing date and the individual-ledger summary using that same date. The recipient should be able to identify what is missing without guessing at the accountant's intention.

The State Bar's preparer instructions (opens in a new tab or window) identify the core record package used with its reconciliation form. The practical request can follow those record types while explaining the exact account and period relevant to the firm's work.

Separate recurring records from exception support. A monthly statement is predictable. A request for evidence about an unusual deposit is specific to a question. Combining both in one long paragraph can cause the recipient to supply the familiar item and overlook the unusual one.

For a fictional deposit question, ask for the remittance or other supporting record that identifies the client and purpose, together with confirmation of the recorded date. Do not ask the recipient to make the ledger match a number supplied without context. The purpose is to establish facts before deciding what correction, if any, is appropriate.

Define acceptable formats when they affect usability. A readable statement file differs from a screenshot that omits the period or account reference. A transaction export may help analysis but should not be mislabeled as the bank's original statement. Keep both records distinguishable when both are needed.

Ask the recipient to identify what cannot be supplied. An explicit response that check images are unavailable is actionable; silence is ambiguous. Record the gap and the person responsible for investigating it. Any alternative evidence should be evaluated for the specific question rather than assumed equivalent.

Use the approved secure exchange process. The public consultation form is for business contact information, not statements, ledgers, bank passwords or client records. During onboarding, agree how requests will be delivered, who can respond and how corrected or additional files should be identified.

Check incoming records before starting calculations

Receiving a file is the beginning of the intake check, not the end. Confirm that it opens, is readable and corresponds to the requested account and period. If the filename says September but the statement itself ends in August, resolve that mismatch before using its balance.

Look for missing pages or partial exports. A summary page may show an ending balance while omitting the activity needed to trace transactions. A ledger export may exclude inactive matters or particular transaction types. Identify the report settings and record what the export includes before treating it as complete.

Keep an intake note for replacements. If a contact sends a corrected export, identify which earlier file it replaces and why. Preserve the source and change history appropriate to the firm's process. Do not leave the reviewer to choose between similarly named files based solely on their upload order.

For a fictional intake, three files arrive: a complete statement, a current-date ledger summary and a journal ending at month-end. The preparer can accept the statement and journal for the requested purpose while asking for a ledger summary with the matching cutoff. The whole request need not be described as either entirely received or entirely missing.

Check whether a file contains more information than the recipient is authorized to use. Route access questions through the agreed process rather than redistributing an unexpectedly broad export. An accounting task should not become a reason to enlarge access without a decision by the authorized firm contact.

Do not treat automated extraction as unquestionable. If a scanned amount or date is unclear, compare it with the source and request clarification where necessary. A spreadsheet can repeat an extraction error with great consistency; consistency does not establish that the original value was read correctly.

Once the intake checks pass, mark which version is being used for preparation. This gives later review questions a stable reference and prevents an unnoticed file replacement from changing the apparent basis of work already completed.

Establish the cutoff and opening balance

A monthly package needs a common date. The bank statement period, account journal, individual ledgers and outstanding schedules should describe a comparable point in time. Later activity can be useful for investigating clearance, but it should not silently change the earlier period's closing balances.

Suppose a fictional review uses a September 30 statement. A ledger summary generated on October 7 may include later receipts and payments. The preparation task is to obtain the appropriate September 30 report, not to invent reconciling items for every October transaction that appears in the later summary.

Locate the supported opening balance. Compare the current journal's beginning amount with the prior package's closing amount and investigate any change. A difference may reflect a correction, a report setting or missing information. Its existence identifies a question; it does not establish which explanation is correct.

We recommend recording the basis for any opening-balance revision. Note the affected period, supporting record, authorization and reports that were regenerated. If an earlier package has been revised, the current preparer should know that a different closing figure now applies and why.

Do not make the opening balance a convenient balancing figure. Entering an amount that allows the current month to match can conceal a historical problem. Where the starting point cannot be supported, identify that limitation and scope the historical investigation separately from the current month's otherwise available work.

Keep subsequent evidence clearly labeled. An October bank entry may confirm that a September outstanding check cleared, but it remains October bank activity. The relationship between the original recorded transaction and later clearance should be visible so neither period receives a duplicate transaction.

This date discipline supports both arithmetic and communication. When everyone refers to the same account and cutoff, a question about a difference becomes much more specific. It also makes it easier to reproduce the comparison when someone reviews the package later.

Prepare the comparison without losing the allocation detail

The three-way comparison connects the adjusted bank balance, account journal and combined individual-ledger balances. Use a reconciliation worksheet that shows how each total was obtained. The worksheet should identify the account and date and point to the supporting schedules rather than require the reviewer to reconstruct its inputs from unrelated files.

The State Bar's reconciliation form (opens in a new tab or window) separates client-ledger balances and the bank-charges balance, and adjusts the statement amount for outstanding deposits and disbursements. Follow the applicable distinctions rather than combining every amount into an unexplained client total.

For the firm's working process, trace transactions as well as totals. A journal can balance mathematically while an individual transaction belongs to the wrong client. A summary can conceal an omitted ledger if another error offsets its effect. The comparison identifies agreement; supporting records help establish what that agreement represents.

Keep confirmed reconciling items separate from unresolved differences. A documented check recorded before cutoff but not cleared is a different category from an amount nobody can identify. Putting both on an “outstanding” list can make the worksheet appear complete without resolving the uncertainty.

Use the same identifiers across working schedules. If a payment has a transaction reference in the journal, include that reference in the outstanding-item list and the exception note. This reduces the risk of treating several references to one transaction as several separate transactions.

When balances disagree, retain the intermediate result and investigate. Do not overwrite it with an unsupported number. The amount of the difference can help locate an issue, but matching the difference to a familiar fee or payment is a hypothesis until the supporting records establish the connection.

Mako's trust accounting support can be discussed around this preparation and review process. The engagement should make clear who supplies records, who prepares the comparison and which questions remain with the responsible attorney.

Case study: a complete account with two timing items

The following scenario is fictional. Assume an account begins the month with a supported $40,000 journal balance. Recorded receipts total $12,500 and recorded disbursements total $17,750. The journal therefore ends at $34,750. The preparer has supporting records for the transactions and is now comparing that result with the bank and ledgers.

The bank statement ends at $36,250. A supported $3,000 deposit recorded by the cutoff is not reflected on the statement, and $4,500 of recorded disbursements have not cleared. Adding the deposit and subtracting the disbursements gives $34,750: $36,250 + $3,000 − $4,500.

The allocation schedule shows $20,000 for Client A, $10,000 for Client B and $4,500 for Client C, plus a separately identified $250 bank-charges balance. The combined total is $34,750. The bank-charges amount is an illustrative assumption, not a universal permissible reserve; its appropriateness requires the actual account facts and governing rule.

Now test the bank movement from the same facts. Of the $12,500 recorded receipts, $9,500 cleared. Of the $17,750 recorded disbursements, $13,250 cleared. The statement calculation is $40,000 + $9,500 − $13,250 = $36,250. That agrees with the fictional statement ending balance and supports the timing explanation.

The preparation package should identify the particular transactions making up the $3,000 and $4,500, not merely the aggregate amounts. A reviewer needs enough detail to distinguish those items from another deposit or payment of the same size. Supporting dates, references and later clearing evidence can make that distinction possible.

The preparer can then present the three matching totals with their schedules and any remaining non-arithmetic questions. A matching total does not settle whether a particular disbursement was authorized. This scenario assumes those questions are handled through the firm's separate review and approval process.

In the following month, the outstanding items should be traced to their actual outcomes. If they clear, update their status without entering the receipt or disbursement again. If they do not, carry forward a specific investigation task. The monthly package should make that next action easy to identify.

Route exceptions according to the decision needed

Not every difference belongs with the same person. Some questions can be resolved by obtaining a missing statement. Others require the timekeeper or attorney to explain a transaction's purpose. Still others involve a recording issue that the accounting preparer can investigate once the supporting facts are available.

Use a short exception register with a precise question, evidence examined, responsible person and current status. Suggested categories include missing document, cutoff mismatch, unmatched transaction, allocation question, potential duplicate, correction awaiting approval and historical opening-balance issue. Categories support routing; they do not establish the answer.

For example, “Confirm the client associated with deposit reference D-104” is a different request from “Provide the missing September statement.” The first needs supporting context for an allocation; the second needs a source record. Sending both to the bank contact merely because both concern money may delay resolution.

Write down what is known and what is inferred. If two entries have the same amount, record that observation. Do not label them duplicates until the transaction evidence supports that conclusion. A good exception note leaves room for the facts to show that two apparently similar entries are legitimate separate events.

Set a next action that can be completed. “Investigate further” is often too broad. “Compare payment reference P-212 with the check image and ask the responsible attorney to confirm the client allocation” tells the owner what would move the issue forward.

When a question is answered, record the evidence and its effect on the package. If no correction is needed, state why. If a correction is authorized, identify which records change and who will rerun the comparison. Closing the question should not depend on someone remembering an informal conversation.

Escalate material uncertainty through the agreed protocol. Do not allow pressure to finish a checklist to turn an unresolved difference into an assumed timing item. A transparent incomplete status is more useful than an unsupported conclusion that the account is reconciled.

Case study: distinguish duplicate and missing entries

Consider a separate fictional account whose adjusted bank balance and individual-ledger total are both $18,400. The account journal shows $18,125, a difference of $275. The amount is a useful search clue, but it does not prove the cause. Begin by comparing transaction references and source records.

In this scenario, a $275 payment appears twice in the journal and once in the relevant ledger. The payment support confirms one transaction. The preparer documents the duplicated entry and routes the proposed correction through the firm's authorization process. A supported correction restores the journal to $18,400 without creating another bank transaction.

After correction, regenerate the journal and verify the ledger summary. Some systems update connected records when an entry changes, while others require separate steps. Confirm the actual result instead of assuming that an edit has the desired effect everywhere. Retain the original reference and the correction explanation.

Now consider a different scenario with the same $275 difference. A genuine disbursement may be absent from a ledger rather than duplicated in the journal. Removing a journal entry simply because $275 equals the difference would be the wrong response. The arithmetic identifies a direction for investigation, not a permission to choose whichever adjustment makes the totals agree.

The evidence should determine the correction. Compare the bank record, account journal, client allocation and supporting purpose. If a record is missing, request it. If two sources conflict, identify that conflict and obtain a decision rather than choosing the more convenient version.

Maintain a correction note with the period, affected entries, cause, authorization and resulting reports. If the correction changes an earlier period, identify which later opening balances may be affected. A local fix can have consequences beyond the worksheet where the discrepancy was first noticed.

The process lesson is to separate discovery from disposition. Finding a likely duplicate is progress, but it is not the same as confirming the cause, approving the correction and verifying the revised comparison. Give each of those stages an understandable status.

Case study: the bank agrees but the client allocation is wrong

Imagine a fictional account with an adjusted bank balance and journal balance of $22,000. Its displayed ledgers total $22,000 as well: Client A has $12,000, Client B has $9,800 and the bank-charges ledger has $200. At the total level, the three-way comparison appears to agree.

Supporting records then show that a $750 payment was assigned to Client A when it belonged to Client B. Under that confirmed assumption, the supported allocation would restore $750 to A and reduce B by $750. The corrected balances become $12,750 for A, $9,050 for B and $200 for bank charges. The total remains $22,000.

No bank-balance change is needed to explain the corrected allocation in this scenario. The issue is which ledger should reflect the already recorded payment. That distinction matters because a person looking only at totals may not notice the problem at all.

Before making an allocation correction, confirm the evidence. A client's name in a message may be incomplete or ambiguous, and one client can have more than one matter. The responsible reviewer should resolve any uncertainty about the payment's purpose and attribution through the firm's agreed process.

Record both affected ledgers and the reason for the change. A note attached only to the ledger receiving the adjustment may leave the other side unexplained. Preserve enough detail for a later reviewer to understand that the total stayed constant while the allocation changed.

This is also a useful staff-training scenario. Ask a preparer what additional evidence they would request before deciding the allocation, and ask a reviewer how they would identify the two affected ledgers. The exercise tests understanding without using a real client's records or implying that an invented case actually occurred.

A similar caution applies to negative individual balances. A positive amount elsewhere can offset a negative amount in a combined total. The summary arithmetic does not make the negative ledger acceptable or resolve its cause. Preserve the records and bring the specific transactions and questions to the responsible attorney.

Give outstanding items a history and next action

An outstanding-item schedule should allow someone to follow a transaction from its original record to its eventual bank outcome. We recommend keeping the recorded date, amount, reference, client identifier, supporting record, current status and clearing date where known. Use the same references that appear in the working reconciliation.

Separate outstanding deposits from outstanding disbursements. Their effects on the bank adjustment differ, and the evidence needed to investigate them can differ as well. A deposit question may concern submission or bank processing, while a check question may require contact with the payee and bank through an authorized person.

Carry items forward deliberately. If a check remains outstanding, keep its original date rather than replacing it with the date of the newest worksheet. Resetting dates can make an old item appear recent and obscure how long the question has remained unresolved.

Do not remove an item merely because it is old or inconvenient. Age identifies a reason to investigate, not a conclusion about the underlying obligation. Establish what happened, what communication is required and who can authorize any action. A stop-payment request, a replacement check and the original obligation need to be considered as distinct facts.

For a fictional schedule, a $900 check may have been mailed but not received. The accounting task is to preserve the original entry and collect the facts needed for the authorized decision. It is not to decide unilaterally that the payment should be canceled, reissued or reassigned.

When an item clears, record the evidence and link it to the original transaction. This prevents a later preparer from mistaking the bank appearance for new activity. Review whether any replacement or correction record also needs to be connected so the history remains understandable.

At the next monthly handoff, highlight items whose status has not changed and state the action already taken. “Still outstanding; payee confirmation requested on the recorded date” is more useful than silently copying the same amount onto another worksheet.

Keep bank-charge questions separate from unexplained differences

The bank-charges balance deserves a clearly identified place in the records. Rule 1.15(c)(1) permits firm funds reasonably sufficient to pay bank charges; it does not establish a universal dollar allowance for every account. The amount and its treatment must be considered using the actual facts and applicable requirements.

As a suggested workflow, identify the source of a charge, its date and how it was recorded before proposing an adjustment. A number equal to an unexplained difference is not automatically a bank fee. Compare the statement detail and relevant records rather than assigning a familiar explanation to an unknown amount.

For a fictional example, the statement shows a $15 charge and the journal has no corresponding entry. The preparer can identify that difference and obtain the appropriate review of how it should be reflected. The example does not determine which person's balance should bear the charge or authorize a transfer to replenish the account.

Keep the bank-charges ledger distinguishable from individual client balances in the summary. The review should show how the separately identified amount contributes to the combined total. A label such as “miscellaneous” may be too vague to explain the source and purpose of that balance.

Review recurring charges as an operational matter. If a fee repeatedly causes questions, clarify who obtains the supporting information, who reviews the treatment and who communicates with the bank. Improving that handoff can reduce repeated uncertainty without changing the governing limits.

Do not let this ledger become a container for unresolved client allocations. An unidentified receipt needs investigation into its source and purpose. Relabeling it as a bank-charge reserve would replace a factual question with an unsupported conclusion.

When the account or bank arrangement changes, revisit the supporting assumptions. The firm's prior process may need adjustment, but any change should be documented and reviewed. A previously used amount or label is not evidence that it remains appropriate indefinitely.

Handle quiet months, new accounts and closing accounts deliberately

A month with little visible activity can still require careful comparison of the records. Start with the actual statement and the relevant journal and ledgers rather than assuming that no new client activity means nothing changed. A bank charge, an old check clearing or an adjustment can affect the package.

The monthly recordkeeping requirement cited at the beginning should not be replaced with an invented exemption for a quiet month. Confirm the applicable circumstances with the responsible attorney and preserve the evidence supporting the period's records. The practical workflow can be simple without becoming undocumented.

For a newly opened account, establish the opening information and the first period under review. Identify the initial transactions and their allocation support. A zero opening balance may be straightforward, but it should describe the actual account history rather than serve as a default assumption.

For a closing account, identify the final statement and any activity that remains unresolved. A closure date does not explain every prior balance or prove that all supporting records have been assembled. Keep the account in the inventory with a status that describes the remaining review work.

Consider a fictional closed account with a final statement available but a missing explanation for an earlier disbursement. The bank relationship may have ended while the documentation question remains. Assign the record request and review responsibility instead of removing the account from the work list altogether.

Preserve access to necessary historical exports before a system or account arrangement changes, using the firm's authorized process. Do not wait until the reviewer needs an old record to discover that nobody knows how to obtain it. Record the location of the retained package in the account inventory.

These situations benefit from explicit labels: new account awaiting opening support, quiet period prepared for review, closed account with historical exception. Each label tells the next person what action is needed and avoids treating very different circumstances as simply inactive.

Coordinate several accounts without combining their conclusions

A firm-level dashboard can coordinate several accounts, but each account's reconciliation needs its own supporting comparison. Do not offset a difference in one account with an opposite difference in another and describe the combined position as reconciled. The location and allocation of the funds remain relevant.

In a fictional two-account example, Account East has a $400 unexplained excess in its adjusted bank comparison and Account West has a $400 shortfall. The net difference across both accounts is zero. That arithmetic does not establish the cause or authorize moving money between the accounts.

The preparer should identify the transactions involved in each account and investigate whether there is a relationship. A transfer may be one possible explanation, but it remains a hypothesis until the evidence supports it. Confirm dates, references, source and destination records and the required authorization.

Use consistent account references in requests and reports. Similar bank names or abbreviated filenames can cause a statement to be attached to the wrong package. The reviewer should be able to distinguish each account without relying on memory of the folder order.

Where the same staff support several accounts, make the handoff list explicit. A person supplying complete records for one account may reasonably assume the request is finished unless the other accounts are identified separately. Group related requests for convenience while keeping their scope clear.

Review shared issues at the firm level. A change in software, staff responsibility or bank access can affect several accounts simultaneously. Record the common action and identify which account packages depend on it. This avoids solving the same administrative question repeatedly while preserving separate accounting conclusions.

At the end of the cycle, the dashboard should summarize actual statuses rather than average them. One reviewed account and one unresolved account do not become a half-reviewed firm. Name the remaining work and the person responsible for moving it forward.

Separate historical cleanup from the current cycle

A backlog changes the sequence of work. If several earlier periods lack reliable records, the current month's opening balance may not be a dependable starting point. Identify the earliest supported position available and map the periods between that point and the current review.

We recommend a period inventory with columns for statement availability, journal availability, ledger completeness, prior reconciliation support and unresolved questions. This helps the firm see whether the problem is missing source records, incomplete allocations, unexplained corrections or a combination of issues.

For a fictional backlog, January and February may have complete packages, March may be missing ledger support, and April through June may carry forward the same unsupported difference. Treating the later months as independent cleanups can create repeated effort. Investigating March's issue may be a dependency for all subsequent periods.

Do not imply that finding the earliest difference automatically resolves everything after it. Later periods may have their own errors or missing records. Use the dependency map to order the work, then review each affected period and confirm its results.

Keep current records organized while historical work proceeds. Otherwise, the cleanup can grow faster than it is resolved. Agree how new statements, transactions and questions will be captured, even if a final current-period conclusion depends on earlier investigation.

Scope the historical project separately from the ongoing monthly engagement. Identify the accounts and periods, evidence available, questions requiring the firm's input and the basis for deciding that a period is ready for review. Avoid a vague instruction to “clean everything up” without a shared definition of the work.

Mako's trust-accounting cleanup support is the appropriate service discussion for historical discrepancies and missing-record work. The initial conversation can establish scope without uploading confidential files to a public form or assuming a particular outcome before the records are examined.

Document corrections so another person can understand them

A correction record should explain the original issue, the evidence supporting the change, the authorization and the resulting records. Its purpose is to preserve the reasoning, not merely announce that a number changed. A later reviewer should be able to distinguish an actual correction from an unexplained adjustment.

Suggested fields include account reference, affected period, transaction identifiers, original amounts, corrected amounts, cause, supporting source, decision-maker and completion date. Use references to secure records when copying the underlying client details into the log would create unnecessary exposure.

Separate the decision from the entry. A person may approve a particular treatment, but someone still needs to apply it correctly in the relevant records. Conversely, an entry can be technically possible in software without the underlying decision having been authorized.

After the change, verify all affected outputs. A journal correction may require a revised ledger summary, a new reconciliation worksheet or an explanation of a changed opening balance in a later period. Record those dependencies rather than assuming the software updates every report in the same way.

For a fictional correction, a $120 duplicate is confirmed in a prior month. The log should identify the duplicate entry and the support for a single transaction, explain the authorized correction and identify the packages that were regenerated. “Adjusted $120” would omit the facts that make the change understandable.

Preserve version clarity. If an earlier package has been superseded, mark its status in the firm's record system and identify the replacement. Do not erase the relationship between versions merely to make the folder look tidy. The reviewer needs to know which conclusion is current and what changed.

Use the correction log to identify recurring process problems as well. Repeated import duplicates may suggest a handoff issue, while repeated wrong-matter allocations may suggest unclear source information. Address the recurring cause without treating a process hypothesis as proof about every individual transaction.

Plan software changes around evidence, not just imports

Changing accounting or practice-management software can affect report names, filters, transaction references and how staff obtain records. A successful import does not by itself establish that the new system preserves the evidence needed for a monthly review. Define the records and comparison outputs before the transition.

We recommend identifying the cutover date, the supported balances at that date, the exports to retain from the old system and the reports to check in the new one. Include individual allocations and outstanding items, not just an account-level opening amount.

For a fictional transition, an account moves with a total balance of $25,000. If the new system contains only that total and no supported client allocation, the three-way process still lacks a crucial part of its evidence. The migration task must account for the underlying ledgers and their relationship to the opening figure.

Test report dates and filters with synthetic or appropriately authorized records. Confirm what happens when a report is run as of the cutover date rather than today. Identify whether inactive matters, reversed transactions or outstanding items appear as expected. Vendor documentation can explain features, but the actual configured output needs verification.

Keep a transition exception list. Record missing references, unmatched totals and uncertain allocations, with owners and evidence requests. Do not relabel an unresolved difference as a migration adjustment without establishing the facts and obtaining the required review.

Plan how reviewers will access old records after the change. A link that works only inside an account scheduled for closure may not be a dependable archive reference. Confirm authorized export and retrieval arrangements before removing access to the previous system.

This guide does not claim that Mako's portal automatically connects to or reconciles any particular accounting platform. Discuss the firm's existing tools and the agreed record exchange process during scoping. Software capability, service scope and professional responsibility should remain separate statements.

Use attorney review time for decisions and evidence

A review meeting should begin with a clear account and period, the three totals and the status of any exceptions. The reviewer should not need to spend the first part of the meeting discovering which worksheet is current or why several files contain different closing balances.

We recommend an agenda with four questions: are the records complete for the stated purpose, do the comparisons agree, what questions remain, and what decisions are required? Attach or reference the evidence needed for those questions. Keep general process improvements separate from unresolved accounting issues.

For a fictional meeting, the preparer may present one account whose timing items are supported and another with an allocation question. The first discussion can focus on reviewing the evidence and outstanding-item follow-up. The second needs the specific transaction support and the attorney's resolution of the allocation issue.

Do not treat attendance as approval. Record what was actually reviewed and decided, and identify questions returned for additional work. If the package changes materially afterward, arrange the required further review rather than assuming that earlier discussion covers the revised version.

The State Bar reconciliation form includes attorney certification and recognizes responsibility even when another person prepares the reconciliation. The firm's review record should reflect genuine involvement, not a signature requested solely to make a checklist appear complete.

Keep meeting notes concise and actionable. An item should state the decision or question, its owner and the expected follow-up. If the reviewer asks for evidence about an outstanding deposit, record the specific deposit reference and the source to obtain rather than a broad instruction to revisit the account.

Close the meeting by confirming which packages are ready for the next step and which remain open. A shared understanding at that point reduces the risk that one participant believes work is complete while another expects a correction or additional explanation.

Archive a package that can be reconstructed later

Preserving a package means keeping the information needed to understand the conclusion, not just the final total. Organize the statement, journal, ledger summary, supporting schedules, correction explanations and review evidence so an authorized person can follow the work after the original preparer is unavailable.

California Rule 1.15(d)(5) sets a minimum preservation period for covered records measured from final appropriate distribution. That trigger is not the upload date or the date a folder was created. Confirm the relevant retention obligations and any circumstances affecting preservation before adopting a deletion rule.

As a suggested naming practice, use a stable account reference, the closing date and the record type. Avoid filenames that disclose unnecessary client or account details in ordinary messages. The internal record system can carry the access-controlled context needed by authorized reviewers.

Identify the final reviewed version and its relationship to any earlier drafts. If a package is later corrected, retain the correction history and indicate which version supersedes which. Several unlabeled files called final can be harder to use than a clear series of dated review versions.

Test retrieval periodically as part of the operating process. Ask an authorized person to locate a selected account and period, identify the source statement and find the explanation for a reconciling item. The exercise can reveal missing references or access problems before a time-sensitive request arrives.

Keep retention and access decisions coordinated. A record may need to be preserved without remaining available to every former participant. When roles change, review who still requires access while maintaining the firm's ability to retrieve the retained package through authorized people.

Do not describe a storage feature as a guarantee that every retention obligation is satisfied. The firm's policy, applicable rules, actual record completeness and ability to retrieve the files all matter. The accounting workflow should identify who owns those decisions and who verifies the operational steps.

Keep sensitive records inside the agreed workflow

Trust-account records can contain client identities, matter details and financial information. Agree how the firm and its accounting provider will exchange those records before requesting them. The process should identify authorized contacts, permitted access and the channel used for documents and clarifications.

Use the public inquiry form to discuss business needs, not to deliver statements or credentials. A prospective firm can explain the number of accounts, the periods involved and whether it needs ongoing preparation or historical cleanup without exposing confidential client information.

During the engagement, make requests specific and permission-aware. The person who can answer a transaction question may not need access to every account package. Conversely, a reviewer may need a complete package rather than disconnected screenshots. Match access to the task and the firm's authorization.

Prefer an agreed delegated-access arrangement where the relevant provider supports it, rather than assuming that ordinary messages should contain account passwords. If access credentials are needed, use the approved secure process and confirm who may request, provide and use them. Do not treat possession of a credential as evidence of payment authority.

For a fictional clarification, the preparer can reference a transaction already stored in the authorized workspace and ask for its supporting remittance. That is generally clearer than copying a full statement into a message chain. The exact method should follow the tools and controls actually agreed for the engagement.

When a file is sent to the wrong place or an unexpected person receives a request, follow the firm's incident and correction process. Do not resolve the issue by broadening distribution further. Identify what was shared, with whom and what authorized action is needed.

Keep security descriptions factual. The existence of encryption or a portal does not remove the need for correct permissions, careful requests and appropriate handling by the people involved. Describe the implemented process and its limits rather than promise that sensitive data can never be exposed.

Define what the accounting engagement will cover

An effective scoping discussion identifies the work to be done and the evidence available to support it. Start with the accounts, periods, current tools and recurring obstacles. Explain whether the main need is organizing records, preparing comparisons, investigating historical discrepancies or coordinating review.

Ask what responsibilities the firm will retain. The accounting provider may need the firm to identify a transaction's purpose, supply a missing record or resolve a matter-specific question. The responsible attorney's decisions should not be left implicit simply because someone else is preparing the worksheet.

Separate routine monthly work from historical investigation. A package with complete current records and a supported opening balance differs from an account with missing ledgers across several years. The engagement should explain how additional historical work is identified and agreed, rather than hiding it inside an undefined monthly task.

Define deliverables in terms a client can recognize: a prepared reconciliation package, an exception list, documented correction support or a review handoff. Avoid describing every output as an audit. Routine accounting assistance does not automatically constitute an assurance engagement or a certification of compliance.

Agree communication expectations, including where questions appear, who responds and how urgent matters are escalated. A client should not need to guess whether a routine missing receipt belongs in a phone call, a general email or a specific document request.

For a fictional engagement, the firm may initially request help with two accounts and three historical periods, followed by ongoing monthly preparation. The work plan should identify the transition between those phases and the evidence needed before an ongoing process can rely on the corrected starting point.

Mako's trust accounting and historical cleanup service pages provide starting points for that discussion. Actual scope, responsibilities and deliverables should be confirmed in the engagement rather than inferred from a general educational guide.

Coordinate billing questions without merging separate approvals

Trust accounting and billing can share supporting information, but they do not ask the same questions. A billing review may examine rates, recorded work and invoice accuracy. A trust-account review considers the relevant records, allocations and transactions. An invoice's existence does not by itself resolve whether funds may be moved.

Create a clear handoff for questions that touch both processes. If a proposed payment references an invoice, identify the invoice version and the supporting matter information. Refer questions about entitlement, authorization or disputed amounts to the responsible attorney instead of assuming the billing status answers them.

In a fictional example, a draft bill contains a rate question that has not been resolved. The billing team is still determining the supported invoice amount. The trust-account workflow should not treat that unfinished draft as an automatic instruction to transfer funds.

Keep payment records and invoice records distinguishable. A recorded receipt, an applied payment and a bank movement can represent related but different events. The firm's chosen systems and procedures should make their relationship understandable without duplicating the same event as new activity.

For retainer-related questions, identify the relevant client or matter and the records being compared. Avoid a firm-wide balance being used as an answer to an individual matter question. The specific allocation and supporting facts are central to deciding what needs review.

Use a shared exception reference where helpful. The billing reviewer and accounting preparer can then see that they are working on different aspects of the same underlying question, while the authorized decision-maker receives a coherent request.

Mako's billing and collections support can be scoped alongside trust accounting when a firm needs both. The engagement should identify the handoff and approval boundaries rather than imply that one service automatically authorizes actions performed in the other.

Measure the process without creating misleading scores

Operational measures can help a firm see where monthly work is getting delayed. Useful counts might include packages awaiting source records, unresolved allocation questions, corrections awaiting authorization and packages awaiting review. Each measure should have a definition that connects to a real next action.

Do not reduce the process to a single percentage without explaining what it measures. A package with every file uploaded may still have an unresolved balance. A package with one missing document may have most of its comparison prepared but cannot yet support a conclusion. Those states should not be made interchangeable by a progress bar.

Track elapsed time by stage only when the timestamps are meaningful. A request created long before its actual need date tells a different story from a response overdue after an agreed deadline. Use the data to improve planning, not to imply a person's performance from an incomplete timeline.

For a fictional quarterly review, the firm might find that most delays involve missing allocation support rather than bank statements. The useful response is to improve the intake question and identify who supplies that support. Increasing every reminder's frequency would not necessarily address the cause.

Keep any service claims grounded in actual records. Do not turn an illustrative scenario into a claim that Mako reduced a client's closing time or prevented a specific compliance outcome. Public examples should remain clearly fictional unless a real case has verified facts and appropriate publication authorization.

Review the measures with the people doing the work. A category that is consistently misunderstood should be revised before its count is used for decisions. Preserve prior definitions when comparing periods, or explain that a change in classification limits the comparison.

The goal is a process that helps the firm act on its records. Measures support that goal when they reveal a specific obstacle, clarify responsibility or identify recurring work. They become less useful when they reward closing a status instead of resolving the underlying question.

Review the process when rules, tools or responsibilities change

A documented workflow can become outdated even when the files still open and the links still work. Rules may change, software reports may behave differently, staff responsibilities may move and the engagement may cover new accounts. Treat those changes as reasons to reassess the affected process.

We recommend quarterly checks of the official sources and operating assumptions used by the firm, together with an annual full review of the workflow. Revisit an affected procedure sooner when a relevant change is identified. These are suggested maintenance practices, not a claim that a universal quarterly legal review deadline exists.

For a rule change, distinguish announcement, adoption and effective dates. Determine which periods and circumstances are affected before rewriting a checklist. A historical correction may require attention to the rule applicable to the earlier transaction as well as the current process.

For a software change, verify the actual output. A familiar report title may now have different filters or available fields. Compare the result with the records needed for the review and document any change to the preparation instructions. Vendor release notes can identify questions but do not replace checking the firm's configuration.

For a staffing change, confirm the new owner of record requests, corrections, review scheduling and archive access. Remove ambiguity before the next closing period. A procedure that names a departed employee can leave work unassigned even when everyone assumes someone else has taken it over.

Maintain a short change record: what changed, when it applies, which accounts or procedures are affected, who reviewed the impact and what was updated. If a material question remains unresolved, say so and identify the interim handling through the firm's authorized process.

Review educational materials alongside operating procedures. A service description or article should not continue to describe an old process as current after the engagement or tools change. Corrections should preserve the history of what was reviewed rather than refresh a date simply to create an appearance of currency.

Reusable worksheet prompts for the monthly package

The following prompts are suggested working aids. Adapt them to the firm's actual records and authorization process. They are not substitute State Bar forms, and completing them does not independently establish compliance. Their purpose is to make the work understandable and the next action specific.

Record request

Identify the account reference and closing date. Name each requested source record and the report cutoff needed. State who may supply it, where it should be provided and what to do if it is unavailable. Separate the routine monthly list from additional support requested for a particular exception.

Exception note

Record the exact question, the records compared, the amounts involved and the evidence already examined. Distinguish confirmed facts from a suspected cause. Identify the person who can resolve the next question and the supporting record or decision needed. Update the note when the answer changes the package.

Correction record

Identify the original transaction and period, the supported reason for change, the authorizing decision and the records affected. Record how the correction was applied and which reports were regenerated. Preserve enough history to distinguish the corrected version from an earlier draft without requiring access to someone's memory.

Reviewer cover sheet

Show the account, closing date, three comparison totals and status. Reference the statement, journal, ledger summary and outstanding schedules. List open questions separately from resolved corrections. Provide a place to record what the reviewer considered and any work returned for further preparation.

Carryforward action list

Identify each outstanding item or process action that continues beyond the current review. Preserve the original transaction date where relevant, state the latest evidence and name the next owner. Keep a process improvement, such as changing a request label, separate from an unresolved accounting difference.

When introducing these prompts, use a fictional account to test whether staff interpret them consistently. Ask one person to prepare a note and another to explain the next action without additional oral context. If the second person cannot identify the task, revise the prompt before relying on it with real records.

Keep templates proportionate. Requiring the same explanation in several places can encourage copying outdated text. Prefer one clear record with reliable references over multiple versions that must be maintained independently. The packet should make the evidence easier to follow, not add paperwork with no review purpose.

Introduce the process through a controlled first cycle

Choose a defined starting scope: the accounts, closing period and people involved. Confirm that the necessary records are available and identify historical limitations before assigning dates. A controlled first cycle is an opportunity to test the handoffs and language, not a reason to lower the standard for a supported conclusion.

Walk through the request and intake process before preparation begins. Ask the firm contact to identify which records they can supply and which need assistance. Resolve unclear account references or report names early, when doing so can prevent multiple incorrect exports.

During preparation, record the questions that require clarification. A first cycle often reveals assumptions that were never written down, such as who confirms client allocations or where a prior correction explanation is stored. Turn those discoveries into specific responsibilities rather than a growing list of informal exceptions.

Use the review meeting to test whether the package is understandable. Can the responsible attorney identify the three totals and follow an outstanding item to its support? Are unresolved questions clearly separated from completed work? Does the reviewer know which version is being considered?

After the cycle, collect feedback on the process as well as the accounting questions. Identify instructions that were unclear, files that were difficult to locate and reminders that did not explain the next action. Keep the improvements tied to observed difficulties instead of adding speculative features.

Do not describe one successfully prepared package as evidence that every future period will be trouble-free. New transactions, changing staff and historical discoveries can create different questions. The value of the first cycle is a clearer operating agreement and a demonstrated way to handle the evidence available in that period.

Then revise the calendar, responsibility map and templates as needed. Record the agreed changes and make sure the next cycle uses the revised version. A process improves when the people involved can see what changed and why, not simply when a new document replaces the old one.

A retrieval rehearsal before closing the first cycle

Use a short retrieval exercise to test whether the package works for someone other than its preparer. Choose one fictional or properly authorized transaction already included in the review. Ask the reviewer to find the bank evidence, journal entry, client allocation and any explanation without relying on the preparer's memory. This is a suggested process check, not an additional regulatory certification.

For example, imagine a payment identified as transaction P-041 in the exception register. The reviewer should be able to locate its date and amount in the journal, see the client ledger affected, and identify whether it cleared by the statement cutoff. If the register describes a correction, the evidence should distinguish the original entry from the approved correction and explain which report version reflects it.

Record where retrieval breaks down. An ambiguous filename calls for a clearer index. A missing source calls for an evidence request. A link that works only for the preparer calls for an access correction through the authorized administrator. These are different problems, and none is solved by marking the entire package reviewed.

Repeat the exercise with an outstanding item whose supporting evidence arrives after month-end. Preserve the original period's explanation and add the later evidence in a way that shows when it became available. Avoid silently replacing a historical report with a current export that changes the apparent facts at the earlier cutoff.

Finally, test the handoff during a planned absence. The backup person should know which requests remain open, who may answer them and which decisions require the responsible attorney. They should not need another person's password or an informal transfer of unrestricted access. Record a short list of improvements, assign owners and carry only unresolved work into the next cycle.

Questions to settle before the next month-end

Which account and date are we reviewing? A precise answer prevents mismatched reports and makes every record request more useful. If there are several accounts, identify them separately and state whether each has a supported opening balance.

Who can answer the questions the records do not resolve? Identify the people responsible for transaction context, corrections and attorney decisions. Avoid routing every question to the same person when different evidence or authority is needed.

What does completion mean? Agree how prepared, unresolved, awaiting review and reviewed states are used. Do not let a file receipt or a matched total imply more review than actually occurred.

Where will the evidence remain available? Confirm the archive location, permissions and retrieval process. Retained records should be understandable to an authorized reviewer who did not participate in the original preparation.

What belongs in a separate cleanup scope? Identify missing historical records and unsupported opening balances. Keeping those dependencies visible helps the firm understand why current work may require earlier investigation.

If your firm needs help organizing this process, start a conversation with Mako Financial. Describe the accounts, periods and type of assistance needed using business contact information only. Sensitive statements, ledgers and credentials should be shared later through the agreed secure workflow.

California-focused educational operating guide. Primary sources checked October 5, 2026. The cited Rule 1.15 version is effective January 1, 2023; its recordkeeping standards identify November 1, 2018. The State Bar preparer instructions carry a November 9, 2023 revision. Internal calendars, templates and scenarios here are suggested practices and fictional illustrations, not a certification of any firm's compliance or authorization for a transaction.