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.

Q01 - Reconcile filing submissions with acceptance or rejection receipts

Status: Proposed / not tested

WHAT THIS KIT CONTAINS
Exact input scaffolds and synthetic examples for an offline pilot. Header, JSON-shape and fixture-consistency checks validate these files only; they do not test an assistant, product integration, legal decision, PDF inspection or live workflow.

PREREQUISITES
1. Firm-approved portal/mail exports; court-specific status dictionary; explicit filing-to-envelope mapping (one envelope may contain multiple filings); staff-supplied follow-up times; spreadsheet join or approved script. An envelope-level acceptance cannot silently imply every component was accepted.

SETUP
1. Use the separate synthetic example inputs first. Fill a copy of the blank template or input checklist for your own preparation; do not mix fixture information with real records.
2. Keep the envelope-only R5 separate. In a negative-control copy, remove R4: F3 must then remain unresolved rather than accepted.
3. Preserve exact CSV headers. CSV templates contain only a header row. Import ID, hash, page-label and timestamp columns as text; inspect leading zeros and do not enable formulas from untrusted input.
4. Give only the selected synthetic input sections/files and the prompt below to an existing firm-approved private workspace, or perform the clerical comparison manually. Keep expected-result notes separate from the input. For planning checklists, leave unknown requirements explicit instead of inventing them.
5. Compare the draft output with the expected fixture result. A reviewer checks original evidence and all exceptions before any separately approved action. Retain the version, scope and source references with the review.

INPUT RULES
All timestamps require an ISO 8601 timezone. Preserve IDs as text. Join on court_id + envelope_id + filing_id; blank filing_id is envelope-only evidence. Status dictionary normalized_status is submitted, accepted, rejected or unknown. Do not discard prior or conflicting receipts.

FILES
- submissions.template.csv: One row per component filing with staff-provided follow-up time
- submissions.example.csv: One row per component filing with staff-provided follow-up time
- receipts.template.csv: All supplied filing and envelope receipts; blank filing ID must not become a component match
- receipts.example.csv: All supplied filing and envelope receipts; blank filing ID must not become a component match
- status_dictionary.template.csv: Court-specific exact raw-status mapping supplied by staff
- status_dictionary.example.csv: Court-specific exact raw-status mapping supplied by staff

COPYABLE OFFLINE PROMPT
Use only these synthetic input tables. Validate required IDs, then reconcile each submission with receipts using court_id + envelope_id + filing_id. Preserve every receipt and its timestamp. Do not treat submitted as accepted, or envelope-only evidence as component acceptance. Flag no receipt, rejected, conflicting terminal statuses, unrecognized status and unmapped receipt. List staff-supplied owner and next_check_at without inventing times. Return a CSV with court_id,envelope_id,filing_id,last_status,exception,receipt_ids,source_refs,owner_id,next_check_at and a short coverage statement. Do not access the court, file, refile, calculate deadlines, email or make legal judgments.

INPUTS
submissions.csv = court_id,envelope_id,filing_id,matter_id,submitted_at,owner_id,next_check_at. receipts.csv = receipt_id,court_id,envelope_id,filing_id,status,observed_at,source_ref. status_dictionary.csv = court_id,raw_status,normalized_status (submitted|accepted|rejected|unknown). All times ISO 8601 with timezone; empty filing_id means envelope-level evidence only.

OUTPUT
filing-receipt-review.csv with submission IDs, last observed status, source evidence, owner and staff-supplied next check. Review post-submission receipts without treating a submitted envelope as an accepted filing.

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.

EXPECTED SYNTHETIC FIXTURE RESULT
Submission C1/E1/F1 has receipt R1 status submitted and R2 rejected; C1/E2/F2 has only submitted; C1/E3/F3 has accepted. Expected F1=rejected exception citing R2; F2=pending acceptance (not complete); F3=accepted evidence recorded, still subject to staff verification. Add an E3 envelope-only receipt with no F3 ID: it must not establish F3 acceptance.

LIMITS
- Staff opens original court evidence; lawyer decides what rejection means and any response. No legal date arithmetic, credential sharing, portal setup or automatic refiling. Verify export coverage and late-arriving/conflicting messages.
- Synthetic data only in the delivered files. No credentials, real client records, live-action scripts, API connection or Make blueprint is included.
- Real use requires firm-approved access, confidentiality, processing terms, retention, product access and reviewer authority. Pseudonymous IDs alone do not anonymize real records.