START WITH THE PRODUCT STEPS Read START-HERE.txt first. It states the actual source acquisition, access/privacy limits, manual field mapping and exact next prompt. The original file templates and synthetic examples below are supporting review aids. Some paths need separately supplied documents or source text; a blank worksheet is not a native export or completed integration. S12: Reconcile recurring management reports Starter kit Status: Proposed / not tested PURPOSE Weekly/monthly reporting cutoff → load approved exports, enforce common periods/keys and reconcile totals → reproducible report plus data dictionary and exceptions tab. PREREQUISITES 1. Deidentified exports, report name/generation timestamp, applied filters, currency/timezone, agreed metric definitions, source row IDs and control totals; Excel/Power Query. No unsupported direct Clio connector implied. 2. Synthetic files first. Real use requires firm-approved access, privacy, processing terms, retention controls, export coverage and a named reviewer. 3. Prepare any required original files or rendered evidence separately. This kit does not configure accounts, connectors or live actions. FILES AND FORMATS report-rows.csv: source_report, source_row_id, record_id, metric, activity_date, invoice_date, collection_date, amount, currency source-controls.csv: source_report, generated_at, filters, period_start, period_end, date_basis, timezone, currency, control_row_count, control_total metric-definitions.csv: metric, approved_definition, date_basis, inclusion_rule, duplicate_key, approver_ref Files without .example are blank input worksheets; CSV templates contain headers only. .example files contain invented records for the dry run. Text input .txt files contain blank labeled fields. Use the original base filename when supplying an example to the prompt, or explicitly map the example filename to that input. CSV files are UTF-8 with comma delimiters, quoted fields where needed, and CRLF row endings. Preserve identifiers as text when importing into Excel. Blank means missing or unresolved, never a zero or a pass. Multi-value fields use a pipe only where the fixture scope says so. SETUP AND DRY RUN 1. Copy this kit to an approved working folder. Keep examples separate from any real exports. Do not upload client, privileged, personal, credential or financial-account data to an unapproved service. 2. Read the .example text policy/scope files and all .example.csv inputs together. They define this fixture only. For a real pilot, fill the blank templates from approved exports without changing headers and obtain approved policy values. 3. Use native read-only exports, exact joins and arithmetic for deterministic checks. This kit includes no executable automation, OAuth setup, live-action instructions or importable Make blueprint. 4. Give only the approved prepared inputs to a firm-approved text assistant and use the recipe prompt below. Keep source IDs, source row numbers and unresolved evidence visible. 5. Compare the proposed result with expected-fixture-result.txt. Verify every listed issue and that the prompt invents no missing evidence. The expected file describes assertions, not a performed workflow run. 6. Have the named reviewer check source evidence and record remaining questions before any separately authorized action. RECIPE PROMPT Build this management report from the supplied deidentified exports using only the metric definitions and reporting period provided. Preserve row IDs. State each source's filters and generation time. Reconcile counts and totals; explain unmatched rows, nulls and period differences without forcing them to balance. Do not mix billed, earned and collected figures, rank employees or change accounting entries. Mark incomplete inputs visibly. INPUTS report-rows.csv: source_report, source_row_id, record_id, metric, activity_date, invoice_date, collection_date, amount, currency source-controls.csv: source_report, generated_at, filters, period_start, period_end, date_basis, timezone, currency, control_row_count, control_total metric-definitions.csv: metric, approved_definition, date_basis, inclusion_rule, duplicate_key, approver_ref OUTPUT report-reconciliation.csv: report_alias, date_range, filter_scope, source_row, observed_amount, comparison_amount, difference, explanation_evidence, unresolved_question, reviewer. Never invent a balancing entry or alter financial records. Use only these synthetic or firm-approved inputs and preserve source row/page IDs. Keep missing or conflicting evidence unresolved. Return a draft for the named reviewer. Do not send messages, connect accounts, change records or permissions, move money, or make legal decisions. Keep source files unchanged. List missing prerequisites before continuing. REVIEW CHECKLIST [ ] Headers match the exact input schema and the export covers the stated scope [ ] Synthetic example files were used alone for the first dry run [ ] Every output finding retains its original source ID/row/page reference [ ] Missing keys, contradictions, unavailable originals and ambiguous dates remain unresolved [ ] Every expected fixture finding is present; no live action or unsupported result is claimed [ ] Responsible reviewer checks the original records before a real deployment RECIPE-SPECIFIC REVIEW Firm administrator/bookkeeper signs off definitions and totals. Plant a duplicate row and a next-month invoice for prior-month activity. Distinct from A20 flat-fee economics and growth attribution reports. VALIDATION Exact CSV header order, field counts, serialized round-trip values and fixture semantics were checked during kit preparation. This does not test OCR, a vendor integration, a model response or end-to-end reliability. All data and identifiers are synthetic. Dates are fixed fixture dates, not current monitoring results.