Form I-9 Section 2: The Mistakes ICE Now Treats as Substantive
Read the article
Someone terminates in Workday on Friday. The I-9 system still shows them active on Monday because nobody told it employment ended. The one-year retention clock never started, or a blanket auto-purge fired six months later and deleted the form while ICE still expected it on file.
Federal law requires you to keep each Form I-9 until the later of three years from hire or one year after employment ends. The rule is simple to quote and hard to operationalize. Most retention failures we see are not math errors on paper. They are missing termination dates in the system that actually holds the I-9.
You must retain a completed Form I-9 for every employee hired after Nov. 6, 1986, for the entire time they work for you. When employment ends, keep the form until the later of:
That conditional rule is in USCIS retention guidance and 8 CFR 274a.2(b)(2)(i)(A). It applies to paper and electronic records. You must produce requested I-9s within three business days of a Notice of Inspection.
USCIS publishes a retention calculator that resolves to the same later-of date. Use it to spot-check your logic before you trust a spreadsheet.
Never destroy a current employee's I-9. The one-year-after-termination branch does not run until employment actually ends.
For a former employee, calculate both dates and keep the form until the later one:
Long tenure. Hired Jan. 1, 2019; terminated Jan. 1, 2026. Date A = Jan. 1, 2022. Date B = Jan. 1, 2027. Keep until Jan. 1, 2027.
Short tenure. Hired March 1, 2024; terminated June 1, 2024. Date A = March 1, 2027. Date B = June 1, 2025. Keep until March 1, 2027. A three-month job still runs three years from hire if that date is later.
Try your own dates: I-9 retention calculator.
Payroll knows the separation date. Benefits knows it. The I-9 file often never gets the message.
Without a recorded termination date on the I-9 itself (or in the dedicated I-9 platform), three bad outcomes show up in audits:
The fix is operational: every separation event in the HRIS should update the I-9 system the same day, with the same termination date payroll used.
If your I-9 vendor offers an HRIS integration, the separation workflow belongs in the API layer, not a quarterly spreadsheet cleanup.
On i9 Intelligence, that means calling POST /api/NewHire/terminate when an employee leaves. Pass the HRIS employee ID, location unit number, and the official terminationDate (YYYY-MM-DD). The platform marks the I-9 status TERMINATED, stores the date for retention math, closes any open E-Verify case, and keeps the record available for audit. The destruction date is calculated from that term date using the later-of rule, not from when someone remembered to update a spreadsheet.
That terminate call is the retention hook. Create handles new hires; terminate closes the retention clock. If you only sync hires and never sync separations, you do not have a retention program. You have a filing cabinet with a broken clock.
What a connected stack looks like in practice:
Integration overview and field mapping: API integrations. Technical walkthrough: developer docs cover create, status, delete (pre-start cancel), and terminate as four core workflows.
Any serious I-9 provider should expose a termination path with a retention date. If yours does not, you are manually exporting term reports or hoping HR remembers to click a button. That gap is where under-retention happens.
Four parts, same logic for every employee and location:
Before ICE asks, confirm you can produce any in-window I-9 in three business days. Book a free compliance call if you want us to stress-test your dates against a sample term list.
Rehire within three years. You may complete a new I-9 or reverify with Supplement B. If you reverify the original, the original retention clock still governs.
Leave of absence. FMLA, sabbatical, unpaid leave: still employed. Do not record a termination date or purge the I-9.
M&A. Acquired I-9s keep their original hire and term dates. Retention obligations transfer with the records. See I-9 errors in M&A.
1099 to W-2 conversion. New I-9 at conversion. Retention clock starts at the W-2 hire date.
Electronic I-9 systems must meet 8 CFR 274a.2(e): integrity controls, audit trail, immediate retrieval index, quality-assurance checks, legible reproduction. ICE's March 2026 fact sheet treats failure to maintain compliant electronic records as substantive, not a paperwork typo.
Retention period is identical for paper and electronic. Split storage across HRIS and a dedicated I-9 platform adds retrieval risk. More: storing I-9s in more than one system.
Under-retention. Form destroyed before the later-of date. Cannot produce it in three business days. Substantive failure. Paperwork range: $288–$2,861 per form (2026 I-9 penalties). One misconfigured auto-purge multiplied across dozens of former employees gets expensive fast.
Over-retention. Keeping every I-9 forever expands what an auditor can pull into the sample. A ten-year-old form with a Section 2 typo becomes a scored violation you could legally have destroyed years ago.
Workday, UKG, ADP, and similar platforms usually apply one personnel-file retention policy to everything attached to the employee record. I-9s need different math.
Manual verification: pick three long-tenured terms and three short-tenured terms. Calculate later-of by hand. Compare to what your systems would destroy today.
"Payroll always knows the term date. The I-9 file often does not," says Patricia Duarte, Director of Compliance at i9 Intelligence. "If your HRIS fires a terminate event into payroll and benefits but not into the I-9 platform, you do not have a retention program. You have a hope. Wire the termination API call the same day, store the date, and let the system calculate later-of. That is how you purge on time instead of by accident."
For current employees, the entire period of employment. For former employees, the later of three years from hire or one year from the date employment ended.
Only after the later-of retention date passes. Calculate at termination, destroy on that date, document the purge.
Not advisable. Every retained I-9 is inspectable. Over-retention expands audit exposure without adding protection.
Yes, if the integration includes termination. Syncing hires without syncing separations leaves the I-9 system blind to when the one-year clock starts. A terminate endpoint with the official separation date is how automated retention stays accurate at scale.
Same time period. Additional storage requirements under 8 CFR 274a.2(e). Non-compliant electronic storage is a substantive violation under ICE's March 2026 guidance.
Three business days from the Notice of Inspection. Weekends and federal holidays do not count.
If terminations are not reaching your I-9 platform, fix that before the next purge cycle or inspection. We can map your HRIS events to create, status, and terminate calls and show you what later-of dates should look like on a live export.
Call us at (713) 668-6200 (Mon–Fri, 8 AM – 5 PM CT), email support@i-9intelligence.com, or submit a ticket.
Estimate exposure: I-9 Risk Calculator. See the terminate workflow: API integrations.