Compare the three trust-reconciliation records read-only Get the source data and prepare the review Documentation-checked proposed route; source collection and human approval required WHAT WAS CHECKED Official documentation checked; all routes are proposed and have not been run in a product account. No client data, account access, installs or account writes used. Native column names are distinguished from editorial kit contracts. Missing source evidence blocks completeness claims. BEFORE YOU START - Bookkeeper/accountant supervision; one specified trust account, currency and cutoff. - Actual bank-issued statement, firm control/trust ledger, complete client subsidiary balances and approved outstanding-item adjustments. - Clio Manage report access. If the firm uses Clio Accounting, its distinct reporting route must be used and verified separately. - Firm-approved Excel; optional Copilot entitlement and tenant approval for the exact minimized data. Native Excel analysis can be done manually if Copilot is absent. - Keep raw exports and identifying source pointers in a separate restricted location. The AI workbook contains only approved alias-based tables and visible policy/scope text, never raw client records on another tab. DATA ACQUISITION LIMITS - This is a read-only arithmetic/evidence check, not a completed regulatory reconciliation or authorization to move funds. - A Clio report’s bank-balance field entered by staff is not an independent bank statement. Missing client ledgers, unlinked funds or unapproved adjustments prevent a clean result. DECLARED INPUT CONTRACT reconciliation.json STEP 1: Collect the independent bank and ledger evidence Tool: Local document viewer and Clio Manage Open: Actual bank-issued statement; Reports > Classic reports > Reports > Client > Bank account activity / Trust ledger Access needed: See prerequisites; actual subscription, tenant configuration and permissions are untested. Read the actual bank statement locally and confirm account/currency/cutoff. Generate the selected-account Bank account activity report for the firm control balance, with opening balance and required date filters. Generate the Trust ledger for the same account/cutoff with opening balance and bank-account summary as needed. Preserve all client/matter balances and unlinked/unknown amounts separately; the bookkeeper verifies the subsidiary population is complete. Expected output: Three separately identified evidence sources: bank statement, firm control ledger and client subsidiary detail, plus approved adjustment evidence. Use it next: Keep originals restricted. Do not upload bank account numbers or raw client ledgers to AI. Check: If the report filters cannot isolate the correct account or reconstruct cutoff balances, stop. Never substitute transaction-period net movement for closing balance. Documentation limit: Official sources support named product features. Workflow-specific prompts, alias fields, mappings and reviewer rules are editorial adaptations, not native export promises. Source documentation: https://help.clio.com/hc/en-us/articles/9290078155803-Clio-Manage-Reports-Presets-and-History https://help.clio.com/hc/en-us/articles/14344842681115-Clio-Manage-Client-Reports https://help.clio.com/hc/en-us/articles/9290138047899-Trust-Reconciliation-in-Clio STEP 2: Read the existing reconciliation history, if relevant Tool: Clio Manage Open: Accounts > trust account > Reconciliations > View report > Export Access needed: See prerequisites; actual subscription, tenant configuration and permissions are untested. Open only an already completed reconciliation for the relevant prior/current period. Check its summary, transaction details and client ledger details; Export downloads its PDF. Use it as supporting history, not as a replacement for the bank-issued statement or current ledger. Do not start, finish, void or alter a reconciliation. Expected output: Existing reconciliation PDF and period reference, if available. Use it next: Bookkeeper checks outstanding items against their actual approval/source records. Check: A previous zero difference does not prove the current period or every client balance is correct. Documentation limit: Official sources support named product features. Workflow-specific prompts, alias fields, mappings and reviewer rules are editorial adaptations, not native export promises. Source documentation: https://help.clio.com/hc/en-us/articles/54824841490075-View-Reconciliation-Reports STEP 3: Map the observed records to the starter input Tool: Excel and authorized staff Open: Separate analysis workbook > Home > Format as Table Access needed: See prerequisites; actual subscription, tenant configuration and permissions are untested. Populate reconciliation.template.json manually from verified evidence: account_id alias,currency,cutoff_date,bank_closing_cents,firm_ledger_closing_cents; approved_bank_adjustments with adjustment_id,signed_cents,source_ref,approved_by; client_balances with client_id,balance_cents,source_ref; transactions with transaction_id,client_id,signed_cents,bank_match_id,classification,source_ref. This kit uses integer cents and is limited to currencies with 2 decimal minor units. Copy the same minimized data into visible Control, Adjustments, ClientBalances and Transactions tables; put approved sign convention and coverage in Scope. Create named tables for Control, Adjustments, ClientBalances and Transactions. Put the policy and review scope in visible worksheets or paste them into the next prompt. Expected output: Completed editorial JSON plus corresponding Excel tables. No bank/ledger value is inferred or copied from another source just to balance. Use it next: Check the mapping against each original source before using AI. Check: Aliases and missing policy fields are staff-created; do not relabel a native export as the kit schema. Unknown stays blank/unknown, not false or zero. Documentation limit: Official sources support named product features. Workflow-specific prompts, alias fields, mappings and reviewer rules are editorial adaptations, not native export promises. Source documentation: https://support.microsoft.com/en-us/excel/tutorial-import-data-into-excel-and-create-a-data-model STEP 4: Review the bounded evidence with Copilot Tool: Excel Copilot, optional Open: Approved analysis workbook > Copilot icon at lower right > Chat only Access needed: See prerequisites; actual subscription, tenant configuration and permissions are untested. Use Chat only and submit the prompt. Without Copilot: use independent integer-cent sums for bank adjustments and client balances, then compare both with the separately sourced control balance. PASTE THIS PROMPT Check Control, Adjustments, ClientBalances, Transactions and Scope only. Validate one account/currency/cutoff and complete subsidiary coverage. Compute adjusted_bank_cents=bank_closing_cents+sum(approved signed adjustment cents); client_total_cents=sum(client balances); show both differences to firm_ledger_closing_cents. Flag missing sources, unapproved/duplicate adjustments, unmatched transactions, negative client balances and unlinked funds separately. Unknown inputs block a clean result. Do not create balancing entries, certify legal compliance or authorize any payment/transfer. Cite rows and reproduce arithmetic for independent checking. Expected output: Three-way arithmetic worksheet and unresolved-evidence list. Use it next: Copy the draft exception list to the reviewer; retain row references. Check: Check every flagged row and the scope. A fluent answer is not evidence of completeness; no automatic workbook or source-system edits. Documentation limit: Official sources support named product features. Workflow-specific prompts, alias fields, mappings and reviewer rules are editorial adaptations, not native export promises. Source documentation: https://support.microsoft.com/en-us/excel/copilot/get-started-with-copilot-in-excel https://support.microsoft.com/en-us/excel/copilot/frequently-asked-questions-about-copilot-in-excel STEP 5: Approve the review result Tool: Responsible staff reviewer Open: Reviewed local worksheet Access needed: See prerequisites; actual subscription, tenant configuration and permissions are untested. The bookkeeper/accountant independently recalculates totals and checks every outstanding item, client balance and source. The responsible lawyer reviews the trust-control result through the firm’s established process. Expected output: Reviewed arithmetic exceptions or a limited no-difference observation for the supplied complete evidence. Use it next: Any external message, source change, payment or deletion requires its own authorized process. Check: No live reconciliation, fund movement, balancing adjustment or compliance certification occurs in this workflow. Documentation limit: Editorial human-review gate; linked Excel documentation supports the worksheet used, not legal or accounting conclusions. Source documentation: https://support.microsoft.com/en-us/excel/tutorial-import-data-into-excel-and-create-a-data-model ACCOUNT AND SOURCE CHECKS STILL NEEDED - Actual account access, plan and source-data completeness have not been tested. USING THE FILES IN THIS KIT Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs. The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.