H-1B Cap Alert: Attorneys Urge Matching SOC Codes Between Lottery Registration and Petition
Key Takeaways
- The SOC code on an H-1B cap petition should match the SOC code listed in the H-1B lottery registration, according to the Murthy Law Firm.
- Limited exceptions may be possible if a different SOC code does not reduce the wage level, but approval is not guaranteed.
- Mismatched SOC codes can trigger RFEs (Requests for Evidence) or denials due to perceived inconsistencies or material changes.
- Employers should align the registration, LCA (Labor Condition Application), and Form I-129 to reflect the same occupation and wage level.
Why the SOC Code Now Matters Even More
The Standard Occupational Classification (SOC) code is the government’s label for a job’s occupational category. In the H-1B process, it ties directly to the LCA filed with the U.S. Department of Labor, which sets the prevailing wage and wage level (Levels I–IV). According to guidance from the Murthy Law Firm, the SOC code identified during H-1B cap registration should carry through to the H-1B cap petition filed with USCIS (U.S. Citizenship and Immigration Services). Deviating from the original SOC code can raise red flags about whether the offered role is the same one that secured a lottery selection.
What Murthy Says—and the Narrow Room for Change
Per Murthy’s analysis, a different SOC code may be acceptable only in limited scenarios, and typically where the change does not result in a lower wage level. Even then, there is no guarantee of approval. USCIS adjudicators scrutinize consistency across the registration, the LCA (ETA-9035), Form I-129, and the employer’s support letter. A mismatch can be read as a material change in the offered position, potentially leading to an RFE or denial. Employers considering a different SOC should be prepared to document why the role remains substantively the same and ensure the wage level is maintained or increased.
What This Means for Employers and Beneficiaries Now
For cap-subject employers and H-1B candidates, the practical takeaway is simple: lock in the job description, SOC code, and wage strategy early—and keep them aligned through filing. If responsibilities have evolved enough to warrant a different SOC, consult counsel before filing to assess risk, adjust the wage level if needed, and prepare robust evidence. With filing windows typically tight and processing delays common (even with premium processing, RFEs can slow outcomes), a preventable inconsistency could cost a cap number and months of planning.
Source: Original Article