February 13, 2026 · Updated: February 13, 2026
Registration window: Mar 4–19, 2026 (12:00 ET)
Fee: $215 per registration
Rule effective: Feb 27, 2026
H-1B FY2027: Registration March 4–19, 2026, the $215 fee, and what changes under the Feb 27, 2026 rule
In February 2026, search intent spikes around “H-1B FY2027 registration dates,” “H-1B March 2026 registration,” “H-1B $215 registration fee,” and “how to create a USCIS organizational account.” People are not looking for generic explanations — they want a clear timeline, what must be ready before the window opens, what the Feb 27 rule changes, and the mistakes that cause registrations to be rejected or effectively “not filed.”
Why this matters now. The highest-impact tasks (creating a USCIS organizational account, preparing beneficiary data,
aligning SOC / work location / wage, and ensuring a clean payment flow for $215 per registration) are best completed
before March 4. During the window, the biggest failures happen at deadlines, drafts, duplicates, and payments submitted in the last hour.
How to use this guide (fast)
- Start with the day-by-day calendar and internal deadlines (to avoid draft/payment losses).
- Then read what the Feb 27, 2026 rule changes: wage-weighted selection and why OEWS wage levels matter.
- Next follow the organizational account and $215 payment checklist (roles, access, and payment controls).
- Finish with the top “registration-killer” mistakes and the FAQ + Schema FAQPage.
Contents (links jump to page blocks)
- 1) Day-by-day calendar: what to do before/during/after Mar 4–19deadlines, owners, risks
- 2) Feb 27 rule: wage-weighted selection + OEWS wage levels (I–IV)logic + readable chart
- 3) USCIS organizational account: setup + paying the $215 feeroles, access, status control
- 4) Mistakes that get registrations rejected or “lost”duplicates, IDs, deadlines
- 5) FAQ (7 questions) + Schema markupshort answers for search
1) Day-by-day calendar: FY2027 deadlines (ET) and what to finish early
The goal is simple: enter March 4 with accounts and data ready, then use the window only for batching, quality checks, and paying the $215 fee — without deadline chaos.
Time-zone reality (for teams outside the U.S.). USCIS uses Eastern Time (ET). If your HR/finance/legal team works from Europe,
March deadlines often land in the evening locally. That’s why the best control is not “submit late on the last day,” but “finish and pay a full day early.”
Operational best practice
Internal cutoff: March 18 — everything intended for submission should already be Submitted and paid.
| Date (ET) | What to do | Owner | Risk if delayed |
|---|---|---|---|
| Before Feb 27 prep |
Lock the internal beneficiary list and collect core identifiers (passport/travel document, date of birth, citizenship). Align the intended job offer: role, work location(s), SOC approach, and wage range. | HR + Legal | Data chaos, inconsistent spellings, last-minute changes without control. |
| Feb 27 rule |
Account for the Feb 27 rule: ensure the team understands the OEWS wage level ↔ SOC ↔ intended work area linkage and keeps it consistent with later petition documents. | Legal | Wage/location inconsistency now becomes a measurable risk later (petition stage). |
| Mar 1–3 account |
Create/verify the USCIS organizational account, assign the employer admin, set roles, link counsel (if applicable), and dry-run the workflow: draft → review → ready to pay. | Employer admin | Day-1 access issues; the right person cannot submit/pay on time. |
| Mar 4 (12:00) window opens |
Window opens. Work in controlled batches: small set of registrations → duplicate check → payment → status log. Do not turn the first hour into a high-error race. | HR + Admin | Rushed entries, duplicates, incomplete submissions, unpaid filings. |
| Mar 10–14 audit |
Mid-window is the best time for a clean audit: consistent passport data and spelling, one logic for the job offer, aligned SOC/location/wage, and no second registration for the same beneficiary by the same employer. | Legal + HR | You discover critical mismatches too late to fix them safely. |
| Mar 18 internal cutoff |
Internal cutoff: finalize all drafts that will be submitted and ensure successful payment (bank limits, corporate policies, compliance checks on repeated $215 charges). | Finance + Admin | Payments get blocked and registrations remain effectively unfiled. |
| Mar 19 (12:00) window closes |
Window closes. After 12:00 ET, new registrations cannot be filed. Confirm every intended registration is Submitted and paid. | Admin | A “perfect draft” does not count — only submitted and paid registrations exist. |
| By Mar 31 selection |
Monitor selection results in the account and record outcomes per beneficiary. For selected cases, immediately start petition prep rather than waiting until the filing window is already tight. | HR + Legal | Lost time — you rebuild documents from scratch under deadline pressure. |
Checklist: what should be done before March 4 (ideally March 1–3)
- Organizational account: created, login tested, roles assigned, clear submit/pay owner.
- Beneficiary data: passport/travel document, DOB, citizenship, consistent name spelling.
- Job offer logic: real role, agreed work location(s), SOC approach, wage level rationale.
- Payment readiness: bank limits/anti-fraud pre-checked; backup payment method available.
- Duplicate prevention: one master list + one final approver for submissions.
2) Feb 27, 2026 rule: how wage-weighted selection works — and why wage level is now critical
In FY2027, it helps to separate two layers: (a) the operational registration process (accounts, payment, status) and (b) the cap selection logic. The Feb 27, 2026 final rule changes the selection logic: when a random selection is required, USCIS uses wage-weighted selection based on OEWS wage levels (I–IV).
The core idea (one paragraph)
USCIS conducts selection among unique beneficiaries (beneficiary-centric selection remains). When selection is needed because demand exceeds the cap, each beneficiary is assigned an equivalent OEWS wage level using the linkage SOC code + area(s) of intended employment + proffered wage. Then the beneficiary enters the selection pool with different weights: Level IV = 4 entries, Level III = 3, Level II = 2, Level I = 1. If multiple registrations exist for the same beneficiary with different levels, the process ties the beneficiary to the lowest wage level among them.
Chart: wage level weight and illustrative selection probability
DHS regulatory analysis estimates; actual outcomes depend on the pool
OEWS Level I
1× · 15.29%
OEWS Level II
2× · 30.58%
OEWS Level III
3× · 45.87%
OEWS Level IV
4× · 61.16%
Benchmark: in an unweighted random model, probability was estimated as equal across levels (≈29.59%)
Multiple registrations do not “stack”; a low-level registration can pull the beneficiary’s level down
If wage is listed as a range, level is assessed using the lower end of the range
What this changes in real workflows
- Data precision becomes higher-stakes. SOC, location, and wage must match — wage level is no longer a “cosmetic” field.
- Hybrid/multi-location planning matters. Your intended work area drives the wage level (and must remain consistent with later filings).
- Multiple job options are not a free advantage. If you submit multiple registrations for one person and one is lower, the lowest can control the weighting.
- Consistency with the petition package. Registration data should align with LCA/offer and supporting documents to avoid downstream mismatch risk.
| Data area | What FY2027 registration needs | Common error + prevention |
|---|---|---|
| OEWS wage level | Select wage level (I–IV) supported by the offered wage for the relevant SOC and intended work area(s). | Error: “Looks like Level II.” Prevention: document your internal rationale and keep one approved parameter set before the window opens. |
| SOC code | Use a SOC code that reflects the real job duties (it drives the wage-level comparison). | Error: choosing an overly broad SOC for convenience. Prevention: ensure duties and SOC remain defensible at petition stage. |
| Work location | Intended employment area(s) consistent with the actual worksite model (onsite/hybrid/remote) and later documentation. | Error: “placeholder location” without real worksite alignment. Prevention: confirm worksite policy and reflect it consistently across documents. |
| Wage range | If wage is a range, wage level is assessed using the lower end of the range. | Error: assuming the upper end elevates the level. Prevention: validate wage level using the lower bound before submission. |
| Multiple registrations | Remember: the beneficiary is considered once; if levels differ across registrations, the lowest level controls. | Error: “Submit two versions, one strong and one backup.” Prevention: avoid “backup” registrations that lower the beneficiary’s effective level. |
Bottom line for FY2027
The winning approach is not volume — it’s discipline: one master list, one approved parameter set, and the ability to explain why this job, this location, and this wage are consistent.
3) USCIS organizational account + the $215 fee: setup without surprises
In FY2027, many “failed” seasons are not legal failures — they’re procedural: wrong account type, no one assigned to submit/pay, drafts left unfinished, or banks blocking a series of identical $215 charges.
A practical 60–90 minute plan before the window opens
-
1Assign the employer admin (and a backup).These must be people who can manage access, submit registrations, and coordinate payment approvals.
-
2Verify you’re using the correct organizational/employer account flow.Confirm login works, email is verified, and the employer profile data is accurate — before March 4.
-
3Make “duplicate prevention” a process, not a hope.One master beneficiary list, one approval channel, one final submitter.
-
4Prepare a registration data packet per beneficiary.Passport/travel document, DOB, citizenship, consistent name spelling + approved SOC/location/wage-level logic.
-
5Pre-check the payment route for repeated $215 charges.Bank limits, anti-fraud triggers, corporate compliance approvals, plus a backup payment method.
-
6After submission, maintain a live status log.Per beneficiary: submit timestamp, Submitted status, payment confirmation, and duplicate checks.
Roles and accountability: don’t let submit & pay depend on luck
The operational failure mode is predictable: drafts exist, but the wrong person has permissions; or payment is “someone else’s job.” A simple role map prevents the most expensive mistake: thinking you filed when you only prepared a draft.
| Role | What it does in practice | Common risk + prevention |
|---|---|---|
| Administrator | Manages roles/access, creates/edits registrations, submits, and pays. | Risk: single admin is unavailable. Prevention: at least two admins + a clear responsibility matrix. |
| Member | Helps assemble data and drafts, but should not be the only point of submission/payment. | Risk: drafts are ready but never submitted/paid. Prevention: daily status checks + “draft ≠ filed” discipline. |
| Representative (if applicable) | Supports registration/petition consistency and may assist with review and process management. | Risk: employer and counsel work off separate lists. Prevention: one master list and one “source of truth.” |
4) Mistakes that get registrations rejected or effectively “lost” (and how to prevent them)
These are not “scare stories.” They are the real-world reasons the outcome becomes binary: either the registration is submitted and paid, or it does not exist in the system in a meaningful way.
A
Payment didn’t go through (or only partially succeeded)
If the $215 payment is not confirmed, the registration is not complete.
Prevention
Set an internal payment cutoff (March 18), pre-check bank limits/anti-fraud, keep a backup payment method.
B
Duplicate registration for the same beneficiary by the same employer
This usually comes from parallel submissions across departments.
Prevention
One master list + one final submission channel + no “side submissions” without approval.
C
Passport/personal data mismatches
Inconsistent transliteration, swapped name order, wrong document number — common and avoidable.
Prevention
Use one standardized data intake form and a second-person review before submission.
D
Wrong account setup or submitter lacks permissions
During the window, there is little time to “fix access” calmly.
Prevention
Dry-run the workflow (draft → submit → pay) on March 1–3.
E
Betting on the last day / last hour
Late-stage failures are driven by external risks: payment delays, compliance checks, human error.
Prevention
Plan to finish by March 18 with daily status control.
F
Inconsistent job offer logic (SOC / location / wage)
In FY2027 this is also “selection math”: wage level depends on this linkage and must stay consistent later.
Prevention
Use one approved parameter set and prohibit ad-hoc changes without version control.
Final internal control before the window closes
By the evening of March 18 you should have: (1) a final beneficiary list, (2) Submitted status per intended filing, (3) payment confirmation per filing, and (4) a clean duplicate check across the employer.
5) What happens after March 19: selection and the next step
After the registration window closes, USCIS posts selection statuses in employer/representative accounts. Selected registrations then move to the petition filing stage.
Post-window workflow (simple and actionable)
-
Mar 19 (12:00 ET)
Window closes.
Lock the final registry: who was submitted, who was paid, and what statuses appear in the account.
-
Mar 20–31
Monitor selection.
Check account statuses and record outcomes per beneficiary in your master tracker.
-
After selection
Start petition preparation.
The selection notice defines the petition filing window and details. For selected cases, avoid starting from zero.
-
If not selected
Reassess options.
Consider cap-exempt options, alternative statuses, next season, and your job-offer data quality (especially under weighted selection).
FAQ: 7 common questions about H-1B FY2027
1) What are the FY2027 registration dates and which time zone applies?
The electronic registration period runs from March 4, 2026 (12:00 ET) to March 19, 2026 (12:00 ET).
USCIS uses Eastern Time (ET), so set internal deadlines with a safety buffer.
2) How much is the registration fee and when is it paid?
The registration fee is $215 per registration (per beneficiary). Operationally, a registration is not “real” unless it is Submitted
and the payment is confirmed.
3) What is a USCIS organizational account and why does an employer need it?
It’s the USCIS online account structure that enables employer-side workflows: building registrations, managing roles/access,
tracking statuses, and coordinating with a representative (if applicable) within one environment.
4) What exactly changes under the Feb 27, 2026 rule?
The cap selection logic changes: when selection is needed, USCIS uses wage-weighted selection. Unique beneficiaries receive different
weights based on OEWS wage level (I–IV): Level IV = 4×, Level III = 3×, Level II = 2×, Level I = 1×.
5) How do you choose a wage level (I–IV), and why can’t it be guessed?
Wage level follows the linkage SOC + intended work area(s) + offered wage. It affects selection weighting and should be consistent with petition documents.
If wage is listed as a range, the level is assessed using the lower end of the range.
6) What mistakes most often cause problems or effectively invalidate a registration?
The most common: payment fails; duplicate registrations for the same beneficiary by the same employer; mismatched passport data; wrong roles/permissions;
submitting at the last minute; and inconsistent job-offer logic (SOC/location/wage).
7) When should you expect selection results, and what happens next?
Selection statuses appear in the employer/representative account. For selected registrations, follow the dates and instructions in the selection notice —
it defines the petition filing period and technical requirements.
Official sources (dates, process, and the final rule)
- USCIS — FY2027 H-1B cap: initial registration period (Mar 4–19, 2026) USCIS announcement confirming the registration window and key operational details.
- USCIS — H-1B Electronic Registration Process Core USCIS page describing the electronic registration workflow and account usage.
- USCIS — Organizational Accounts FAQ How organizational accounts work, including role structure and setup considerations.
- Federal Register — Weighted Selection Process (Final Rule; effective Feb 27, 2026) The final rule implementing wage-weighted selection using OEWS wage levels.
Related services
Explore Our Employment-Based Immigration Pathways
Quick internal navigation to key EB categories and the L-1 track.
