Build the H-2A backpay file before replacement AEWRs create exposure

The deadline is a records deadline

The date to mark is September 2, 2026, when DOL's notice set the potential H-2A backpay period running until replacement adverse effect wage rates, or AEWRs, issue under a new methodology. As of that notice, no employer currently owes H-2A back wages. The workaround is to build the exposure file while the wage baseline is still known, so the later calculation does not start from a reconstruction.

On August 26, 2026, the court ruled DOL's October 2025 AEWR methodology unlawful, while the existing AEWRs stayed in place. Wage-adjustment exposure is not automatic: employers could owe wage adjustments only if the later AEWRs are higher than the hourly pay already made to eligible H-2A staff and U.S. staff in comparable employment. DOL's compliance with the court's notice order is not an admission that a court can lawfully force DOL or employers into back wage adjustments. That keeps the immediate task on evidence, not payment.

The file is the defense

A backpay file is a record that lets you calculate, defend, or close the exposure. Keep it narrow enough to review quickly, but complete enough to survive an audit. Its value is in the controls that show what was paid, to whom, and why no payment is due today.

Start with the payroll extract, not the immigration file. The payroll extract shows the wage baseline; the immigration file shows who was in scope. Keep the two linked by worker, pay period, and rate, so an auditor can follow a single worker from hours to wage comparison.

Make the file readable by an auditor who has never seen the season. It should show who was paid, at what rate, for which hours, and how the rate would move if the replacement AEWRs are higher. The controls should make that reading possible without a season-by-season reconstruction.

Assign one owner. The owner can pull the file without asking payroll, immigration, and HR for separate versions. Version the file, because the wage baseline can move while the record is still open. Keep the two worker groups in separate columns, because the calculation will need both sides of the wage comparison.

Do not build a narrative that explains the season. Build a file that answers the audit questions. The season story can be long. The exposure file should be short. Split the paid workers from the unpaid workers, and the offered rates from the paid rates. Split the complete records from the records that need follow-up.

The five controls make the file defensible

Each control below is testable in a minute. If one fails, the file is not ready. Treat the list as a control, not a project.

• Confirm the in-window list. Cover every case in the notice's scope: H-2A certifications that remain valid, H-2A applications that are pending, and new H-2A applications filed before DOL publishes a new AEWR methodology.
• Confirm the payroll snapshot. Capture worker-level hours, pay periods, and hourly rates for the open backpay window.
• Confirm the contact sheet. Record the same data for each potentially backpay-eligible H-2A worker and each corresponding U.S. worker: name, permanent home address, Social Security Number if issued, I-94 Arrival/Departure Record Number where available, permanent email address, and phone number.
• Confirm the rate table. Put paid hourly rates beside current AEWRs, then test what replacement-AEWR levels would do for eligible H-2A staff and U.S. staff in comparable employment.
• Confirm the memo. Record the no-current-obligation position and note the non-admission about court-ordered back wage adjustments.

Keep the whole file small enough to review in a meeting. A missing pay period, a missing address, or an incomplete contact record can turn a clean file into a scramble before a future AEWR arrives.