1---2name: compare-uscis-filing-receipt-against-original-petition-submi3task_id: immigration/compare-uscis-filing-receipt-against-original-petition-submission4description: Discrepancy review comparing a USCIS filing receipt against the original petition submission, focusing on field-by-field mismatches, their potential effect on case linkage and identity verification, and the appropriate correction path based on the source and materiality of each error.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/compare-uscis-filing-receipt-against-original-petition-submi8---910# Skill: Compare USCIS Filing Receipt Against Original Petition Submission1112## 1. Subject-matter triage1314- Treat the receipt notice as a processing record, not a merits decision.15- Compare the receipt against the petition packet field by field, then separately check the petition packet for internal inconsistencies that may explain the receipt-level error.16- Distinguish between:17 - data-entry or transcription errors introduced by the agency,18 - source-document errors originating in the petition submission,19 - formatting-only variations that do not change substance,20 - discrepancies that affect case linkage, identity verification, or downstream filings.21- Where multiple receipts, petitions, beneficiaries, or filing events are present, enumerate them first and analyze each one separately rather than merging them into a single comparison.2223## 2. Failure modes the skill is correcting2425- Agents list mismatches without separating material errors from minor formatting differences.26- Agents identify a discrepancy but do not say whether it likely arose in the submission or in agency processing.27- Agents fail to tie each issue to its operational consequence, especially where a case identifier or name mismatch can disrupt later filings or status tracking.28- Agents describe the problem without stating the proper correction path or escalation route.29- Agents overlook internal inconsistencies within the original petition package that may be the true source of the receipt error.30- Agents collapse distinct fields into a single narrative instead of producing a field-level comparison.3132## 3. Legal frameworks / domain conventions that apply3334- A USCIS receipt notice is a generated record; its contents are only as reliable as the source data and subsequent data entry.35- Identity fields matter differently from tracking fields: name variations typically implicate verification, while receipt/case-number errors primarily implicate linkage and correspondence.36- Priority-date and classification errors can affect downstream eligibility analysis and should be treated as legally consequential if later filings depend on them.37- Correction pathways differ by error type: some minor corrections may be handled through ordinary agency service channels, while substantive identifier or record corrections generally require a documented written request to the processing office.38- The controlling authority for a correction analysis is the relevant USCIS filing and correction procedure for the form/type at issue, together with the agency’s case-tracking conventions; cite the governing form instructions, USCIS policy guidance, or other identified source authority when the source set provides it.39- Do not state that an item is “correctable” or “non-correctable” without linking that conclusion to the relevant agency procedure or source authority.4041## 4. Analytical scaffolds42431. Build a field inventory: list every receipt field that can be compared to the petition submission, including identity, case-tracking, filing/classification, date, and address/contact fields if present.442. Match source to receipt: for each field, identify the exact submitted value and the exact receipt value.453. Classify the discrepancy: determine whether it is a substantive mismatch, a transcription error, a formatting variant, an omission, or an internal inconsistency.464. Attribute likely cause: assess whether the mismatch appears to stem from the petition package or from USCIS processing, using the source documents themselves.475. Assign severity: use a uniform ordinal scale, defined once at the top of the report, based on effect on case linkage, identity verification, downstream filing risk, or administrative clarity.486. Cross-check interactions: see whether the discrepancy interacts with any other source document, cover letter, supporting exhibit, prior filing, or later filing that references the same matter.497. State consequence and remedy: for each issue, identify the downstream effect and the most appropriate correction path, including what evidence should accompany the request.508. Review internal consistency: separately test whether the petition packet contains conflicting names, dates, numbers, or classifications that could explain the receipt error.5152## 5. Vertical / structural / temporal relationships5354- Track how a discrepancy propagates over time: an error on the receipt may be harmless at intake but become material when later filings, notices, or status checks rely on it.55- Evaluate linkage hierarchy:56 - case number and receipt number for tracking,57 - beneficiary and petitioner identity for record association,58 - classification and filing basis for matter categorization,59 - dates and priority dates for downstream eligibility analysis.60- If the source set contains multiple versions of the same field, identify the sequence of occurrence and note which version appears controlling.61- If one field depends on another, analyze the dependency explicitly; do not treat them as isolated entries.6263## 6. Output structure conventions6465- Use a categorized discrepancy report in a table with, at minimum, these columns:66 - Field67 - Submitted Value68 - Receipt Value69 - Discrepancy Type70 - Likely Cause71 - Severity72 - Downstream Effect73 - Corrective Action74 - Priority75- Define the severity scale once at the top of the report and apply it consistently to every entry.76- Group entries by category, such as identity, case tracking, filing/classification, dates, and other administrative fields.77- Include a short narrative summary that highlights the most material discrepancies first and explains why they matter.78- End with a Recommended Actions section that states:79 - the action to take,80 - the responsible role,81 - and the timing/urgency tied to the filing timeline or downstream use.82- Keep the report focused on discrepancies and consequences; do not add background unrelated to the comparison.