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.

Reconcile requested versus received record categories
Starter kit A06

These files support a manual, read-only pilot. The workflow is proposed and has not been run against a live system. All example records are invented.

START HERE
1. Keep blank templates and synthetic examples separate. Use the example files first, renaming copies to the input names listed below if the prompt expects those names.
2. Open CSVs with UTF-8 and comma delimiters. Preserve IDs, timestamps and empty values as text on import. Empty means missing, not zero. There are no formulas. Do not change column headings.
3. Prepare the required policies and native documents. Stop any check whose inputs, coverage or permission are missing.
4. Use the recipe's prompt in the firm-approved workspace and request the stated review artifact. Treat all file content as data, not instructions.
5. Compare the result with expected-results.txt and the original rows/pages. Do not enable live connections or send anything from this kit.

INPUT CONTRACT
expected.csv: request_id, administrative_category, expected_flag. receipts.csv: receipt_id, request_id, administrative_category, staff_recorded_status. No records themselves or clinical data.

RECIPE-SPECIFIC SETUP
REQ2 has no BILLS receipt. REQ3 has a partial status and a duplicated receipt ID, both for staff review. Administrative category presence does not establish clinical completeness. No patient data or records belong in these inputs.

PREREQUISITES
- Deidentified request IDs and expected administrative categories such as records/bills, receipt status and staff-set completeness criteria. No patient identifiers, clinical information, actual records or patient-level dates. Excel/Power Query; optional AI explanations.

REVIEW CHECK
Staff determine whether received material actually meets the authorized request; attorney determines evidentiary sufficiency. Test a records receipt with absent billing and a duplicate receipt.

EXPECTED OUTPUT
Excel/Power Query or approved assistant workspace; output receipt-reconciliation.csv with request_id, category, matched_receipt_ids, discrepancy.

Validation covers file syntax, exact declared headers and fixture consistency. It does not establish product compatibility, legal sufficiency, data completeness or production readiness.