Sam asked for a read-only accounting follow-up packet for three review flags in /Users/samaguiar/Documents/Projects/admin/scratch/accounting-recap-finance-control/runs/2026-06-11T200812-0400-manual-2026-06-11. Scope was local CSVs, extracted PDF text, and read-only live LITIFY_ORG SOQL only.
Read the run summary, reconciliation CSVs, PDF matter rollups, deposit-detail rows, unique recap summary, attachment manifest, and extracted text for MAT-25090465511, MAT-23110163266, and MAT-25112165858. Ran read-only SOQL against live LITIFY_ORG for the three matters and their Resolution rows. Also checked MAT-26011266051 after the June 2 PDF showed the same LaTisha Gray name with two different MAT IDs.
MAT-25090465511: April 14 PDF shows two GeneralStar escrow lines of $500,000 each and a $350,000 fee-income line. April 1 PDF also shows $200,000 Canal escrow, $70,000 fee income, and $1,681.64 costs. Live Resolution rows total $1,250,000 settlement, $437,500 gross fees, $218,750 net attorney fee, and $218,750 fees due to others. The PDF gross-fee movement appears explainable by co-counsel fee split payments to Minner Vines, but live Fees_Due_to_Others_Paid__c totals only $35,000, so accounting should verify whether Litify paid-to-others fields are incomplete.
MAT-23110163266: April 23 PDF shows Deanne Riddle fee income of $28,957.61 and costs of $2,217.59 in the operating deposit detail. Live Matter exists, is closed as of 2025-03-05, has null insurance settlement and fee totals, and has zero live Resolution rows. A duplicate-name check found only one Deanne Riddle matter, so this is a real data-completeness follow-up rather than an obvious duplicate matter match.
MAT-25112165858: June 2 PDF fee/cost rows use MAT-25112165858, but the State Farm escrow deposit line uses LaTisha Gray MAT-26011266051. Live Litify has two LaTisha Gray matters. The $6,000 settlement, $1,705 fee, and 2026-06-02 fee collected date align with MAT-26011266051, not MAT-25112165858. Accounting should verify whether the June 2 QuickBooks fee/cost rows were coded to the older LaTisha matter by mistake.
Run folder: /Users/samaguiar/Documents/Projects/admin/scratch/accounting-recap-finance-control/runs/2026-06-11T200812-0400-manual-2026-06-11.
Main evidence files: reports/litify-reconciliation-issues.csv, reports/litify-reconciliation-rows.csv, reports/pdf-matter-rollup.csv, reports/deposit-detail-matter-rows.csv, reports/unique-recap-summary.csv, and the four extracted text files for hashes 95f1d224..., 5e80ffae..., 3ca91aab..., and 05e1c37....
No local files were edited. No Litify or Salesforce records were modified. The only live-system actions were read-only SOQL queries.
Accounting should verify the Brown co-counsel split against closing statements and Litify paid-to-others fields, verify whether Deanne Riddle should have a Resolution row or documented exception, and confirm whether the June 2 LaTisha Gray QuickBooks fee/cost lines should be recoded from MAT-25112165858 to MAT-26011266051.
Continue the accounting recap finance-control review from the 2026-06-11 run. Use the local run folder above, inspect the same CSV and extracted-text evidence, and run read-only LITIFY_ORG SOQL only unless Sam separately approves data changes. Focus next on verifying Brown co-counsel paid fields, Deanne Riddle missing Resolution rows, and the LaTisha Gray MAT-25112165858 versus MAT-26011266051 coding mismatch.
Saved local memo: /Users/samaguiar/Documents/Projects/admin/scratch/accounting-recap-finance-control/runs/2026-06-11T200812-0400-manual-2026-06-11/reports/deep-dive-review-flags-2026-06-11.md.
Additional MAT-25090465511 finding: live litify_fin__lit_Transaction__c contains two standalone GenStar Credit rows for $1,000,000.00 each, both created April 1, 2026. The April 14 recap PDF shows two GeneralStar escrow deposit detail rows for $500,000.00 each, and the large Litify Resolution is $1,200,000.00. Accounting or Litify data hygiene should verify whether those GenStar financial transaction rows are duplicates, should have been $500,000.00 each, or represent a non-cash tracking value.