How Do I Rehire an Employee in ADP Workforce? (w/Examples) + FAQs

Yes, you can rehire a former employee in ADP Workforce Now, usually by reopening that person's existing profile. You do not build a new one from scratch. An HR admin or manager typically switches the record's status from terminated to active, then runs a short wizard that resets job, pay, and start-date fields. The employee's original ID usually carries over.

The tricky part is not the click path. It is which legal clocks restart. A rehire can trigger a new I-9 requirement, reset a benefits waiting period, or reopen a state sick-leave balance, depending on how long the person was gone. ADP calls itself among the largest payroll platforms in the country, and a wrong rehire date is one of the more common reasons a transaction gets kicked back for correction.

What "Rehire" Means in ADP Workforce Now

This guide reflects ADP Workforce Now's general rehire workflow and federal rules in effect as of 2026. ADP's own screens change over time, and so does employment law. Confirm your company's current ADP setup and your state's rules before you rely on any single step here. This is educational information, not legal or tax advice, and an unusual rehire, like one after a leave dispute, is worth a quick check with HR or an attorney.

ADP Workforce Now treats a rehire as a status change on an existing employee record. It is not a brand-new file. When someone leaves, ADP does not delete their history. The profile is marked terminated, and the pay, tax, and job history stay attached to that same internal record.

This distinction matters because of what rides along with the record. The employee's original hire date, prior job history, and year-to-date payroll totals stay linked to that one ID. That is why admins are generally told to correct data in the existing profile, not create a second one.

A 2016 ADP Portal rehire guide instructs managers to select "File # Rehire" as the reason for the action. That single field tells the system this is a continuation, not a new tenure. Choosing a generic reason instead can misroute the transaction or strip the wage-history link entirely.

Duplicating the record instead of reopening it is the most common failure mode. If a manager creates a fresh file for someone already in the system, ADP now has two IDs tied to one person. That splits their tax withholding history and can misstate year-to-date wages on the W-2. Support teams typically have to merge or void one record by hand, which can delay the employee's first paycheck by days.

ADP treats rehiring as common enough to warrant its own workflow, not a workaround. The company publishes a Worker Rehire API Guide for integrators who build custom onboarding tools. A parallel guide covers the same use case for ADP Vantage HCM, ADP's platform for larger organizations. Two separate guides confirm the mechanics differ by product tier, so your screen depends on which platform your employer licenses.

Which Rehire Path Applies to You?

The right screen to open depends on your role and how your company configured ADP Workforce Now. A payroll or HR admin usually has full access to the profile and the rehire wizard. A line manager may only see a simplified self-service version of the same event. Company size, and whether HR pre-approves personnel actions, also changes who can start and approve it.

For a Payroll or HR Administrator

As the admin, you generally have direct access to the terminated employee's record. You do not need anyone's approval to start the change. You open the profile, find the status field, and switch it from terminated to active. That single click unlocks a new-hire-style wizard for job data, pay, and benefits.

Because you can usually both start and approve the transaction, double-check every field yourself. There is no second reviewer catching a mistake before it hits payroll. Pay close attention to the effective date, since ADP calculates the first pay period from that field. A date off by even one day can shift the employee onto the wrong pay cycle or push a benefits enrollment window open a day early or late, which is harder to unwind after the fact than to get right the first time.

For a Line Manager Using Self-Service

If your company routes rehires through manager self-service, you likely see a guided, wizard-style version of the event. A 2016 ADP Portal manager guide describes managers selecting a "Rehire Employee" option. From there, you work through required screens for personal data, job data, and pay, before submitting the event for HR approval. Every required field is marked, and you cannot advance until you finish it.

Your submission does not take effect right away. It routes to the next approver, typically HR, who can accept it or reject it. A rejected transaction restarts the whole event from the beginning. Because a rejected rehire has to be re-entered from scratch, verify the former employee's Social Security number and address before you submit, not after.

For a Remote or Multi-State HR Team

If the rehired employee returns to a different state than before, treat the state question as its own step. Do not leave it for later. Paid sick leave reinstatement, final-pay deadlines, and even unemployment tax rates vary by state. The same rehire date can trigger different obligations depending on the work location on file.

Update the employee's work state and locality in ADP before you finish the wizard, since tax withholding calculates from that field. A mismatched work state is one of the more common data errors on multi-state rehires. ADP does not re-detect a new location on its own. Someone has to enter it correctly, every time an employee's home base changes, and that same field also feeds the state unemployment tax calculation, so an error here can surface weeks later on a payroll tax report.

Step-by-Step: How to Rehire an Employee in ADP Workforce Now

Most ADP Workforce Now setups start a rehire from the terminated employee's own record. You open the profile, find the employment status field, and change it from terminated to active. That action opens a rehire-specific wizard. From there, you move through a short sequence of screens covering personal data, job data, and pay.

The exact screen names and step count vary by client setup, since ADP Workforce Now is heavily customized per company. A 2016 ADP Portal manager guide walks through nine numbered screens for a manager-started rehire. Newer setups described in third-party ADP integration documentation compress this into editing a terminated-status field. Both paths land in the same place: a reactivated record with a new rehire date and updated job and pay data.

The typical sequence looks like this in most setups:

1. Open the employee's profile and locate the current terminated status.
2. Change the status field to active and select the rehire action for your configuration.
3. Enter the rehire date, the specific reason for the action, and any notes for the approver.
4. Review personal data: address, phone number, and any legal-name changes since the person left.
5. Review job data: job code, work location, reporting manager, and full-time or part-time status.
6. Review pay data: pay rate, pay group, compensation frequency, and standard hours.
7. Submit the transaction for approval and track its status until it posts.

Two fields deserve extra attention, because they drive downstream calculations. The reason for the action tells ADP this is a rehire, not a fresh hire. That is what keeps the original employee ID and wage history attached to the record. The rehire date drives the new benefits eligibility clock and the first pay period, so a wrong date can push someone onto the wrong paycheck.

Worked Example: Rehiring a Retail Shift Lead

Emma Torres worked as a shift lead at a regional retail chain. She resigned on May 2, 2025, to relocate for family reasons. She reapplied in July 2026, and her old store manager wanted her back in the same role. Because Emma left less than three years earlier, the manager rehired her through Emma's existing profile instead of creating a new file.

The manager opened Emma's record and found her status set to terminated. He changed it to active with a rehire date of August 18, 2026, the Monday she was scheduled to start. For the reason code, he selected the rehire-specific option, not a generic new-hire reason. That single field tells ADP to reuse Emma's original ID and preserve her prior year-to-date pay history.

In the job data screens, the manager confirmed Emma's job code stayed the same: Shift Lead at Store 214. He updated her standard hours to 32 per week, down from the 38 she worked before. Her pay changed too.

Emma had earned $19.50 an hour when she resigned, and the store's new starting rate for shift leads had moved to $21.00 an hour. On a 32-hour week, that raise works out to about $48 more in gross pay each week, or roughly $2,500 more over a full year. A gap like that is common after a year away from a fast-moving hourly market.

The manager submitted the transaction with a short note asking payroll to confirm Emma's direct deposit details. It then routed to the store's HR partner for approval. Approval came back two business days later, and Emma's first paycheck processed on the store's next regular pay run. Because her reason code was set correctly, her W-2 for the year still shows one continuous record.

What Changes When You Rehire vs. Hire New

Rehiring resets some parts of the employment relationship and preserves others. Mixing the two up is where most compliance mistakes happen. Four areas cause the most confusion: I-9 verification, FMLA eligibility, health-plan waiting periods, and retirement-plan vesting credit. Each one has its own rule for how much of a break resets the clock.

I-9 Reverification

Every employer must keep a valid Form I-9 on file for each employee, a federal requirement enforced through USCIS's I-9 guidance. If you rehire someone within three years of the date their original I-9 was completed, you generally have a choice. You can complete a new I-9, or update the old one instead. Wait past that three-year mark, and the choice disappears; you must complete a brand-new form.

A common misconception is that a rehire never needs a new I-9, as long as the original is on file somewhere. That is only true inside the three-year window. Even then, the employee's work authorization document must not have expired in the meantime. Skipping this check exposes the employer to fines during an I-9 paperwork audit, since violations are assessed per form, not per company.

FMLA Eligibility After a Break

The federal Family and Medical Leave Act requires an employee to have worked at least 12 months and logged 1,250 hours in the prior year, under standards the Department of Labor enforces. Time from a prior stint generally counts toward that 12-month total, as long as the break was under seven years. The 1,250-hour test resets with the return date, though. A rehired employee still has to log those hours fresh.

This trips up employers who assume five years of combined service means automatic FMLA eligibility on day one. It does not, and approving leave for someone who has not yet hit 1,250 hours can create a paid-leave dispute later. The months of prior service can count toward the 12-month test, but the hours worked in the current stretch still have to reach 1,250. Track the rehire date carefully in ADP, since most systems calculate FMLA eligibility from that date forward.

ACA Health-Plan Waiting Periods

Employers with 50 or more full-time employees generally must offer coverage under the ACA's employer shared responsibility rules. Most plans also apply a waiting period, commonly 90 days, before new coverage starts. Whether a rehire sits through that period again depends on the plan document and how long they were gone. Some employers treat a same-year rehire as a continuation and skip the wait.

Check the specific plan rules before you promise a rehired employee anything about coverage. A plan is generally allowed to require the wait again, if that requirement is reasonable. Assuming "they already waited once" can leave the employee without coverage longer than expected. Confirm the answer with your benefits admin, not from memory, and put the confirmed start date in writing so payroll and the employee both work from the same number.

Retirement Plan Vesting Credit

As a rule of thumb, many 401(k) and pension plans keep the vesting credit an employee already earned, if they return within five years of leaving. The real rule is more technical than a flat cutoff, since it weighs the length of the gap against the employee's prior years of service. A rehire with three years of credit before leaving often picks up close to where they left off. This is one of the few spots where a rehire can come out ahead of a brand-new hire, though the plan document sets the real answer.

The exception is a plan with its own, stricter break-in-service rules. Do not assume the five-year figure applies everywhere. Pull the actual plan document, or ask the plan admin for the rehire's specific credit. Getting this wrong in conversation with the employee can create expectations the plan does not support, and correcting a promised vesting date after the fact is a harder conversation than confirming it up front.

Lessons From Three Rehire Situations

The mechanics of the ADP screen are only half the job. The other half is what happens around the rehire: the paperwork it triggers, the state rule it activates, or the data cleanup it exposes. Three situations show how those pieces play out differently, depending on timing, location, and what was left unfinished.

Marcus and the Three-Year I-9 Window

Marcus worked as a warehouse associate for 14 months before a seasonal layoff. His former supervisor rehired him nine months later, well inside the three-year window that lets an employer reuse a prior I-9. The HR coordinator pulled Marcus's original form, confirmed his work authorization document had not expired, and completed the reverification section instead of starting over.

Skipping this step is an easy mistake, because the ADP rehire wizard does not require an I-9 check the same as it requires a job code. HR still has to pull the I-9 file separately, since ADP tracks employment status, not immigration paperwork. Marcus's case worked out cleanly, because the coordinator caught it before his first day back.

Priya and the State Sick-Leave Deadline

Priya worked as a marketing coordinator in Washington state and resigned in March 2025. She reapplied to her old employer in June 2026, about 15 months later. Washington's paid sick leave law requires employers to reinstate an employee's unused, accrued balance, if they are rehired within 12 months of separation. Priya's gap ran three months past that window.

A common misconception is that sick-leave reinstatement rules are federal and apply identically everywhere. They are not. Several states and cities set their own reinstatement windows, and some set none at all. The same 15-month gap that cost Priya her balance in Washington might not matter in a state without a similar law.

David and the Data Cleanup Nobody Did

David's position had closed out when his location shut down 18 months earlier. When his old manager tried to rehire him at a different location, the wizard kept pulling in his old department code. That code pointed to a location no longer active in ADP. The transaction stalled, because the system could not resolve a department never properly closed out.

Third-party guidance on rehiring through ADP notes that any position or department change tied to the old record has to be effective-dated correctly first. HR fixed the closed department's end date, then restarted David's rehire from a clean record. The lesson generalizes past David's case. A rehire into a changed org structure needs a quick data check before you touch the wizard, not after it throws an error.

Federal Baseline, and Where Your State Differs

Federal law sets the floor for most of what a rehire touches. I-9 verification, FMLA eligibility, and the ACA mandate all come from federal statutes, and they apply identically in every state. Federal law does not set a single rule for paid sick leave reinstatement, final-pay timing, or benefits reinstatement speed. States are free to layer their own, often stricter, requirements on top of that federal floor, and a handful of cities add a third layer on top of the state rule.

Washington's 12-month sick-leave window, covered earlier, is one example of a state rule with no federal match. Other states set their own limits, and several, including California, use a similar rehire window near one year. The exact number and conditions vary by state, so check the current rule with your state labor agency, not Washington's number. Many states have no statewide paid sick leave law at all, leaving the question to local rules or company policy.

Final-pay timing is another area where the state, not ADP, sets the clock. Some states require a terminated worker's last paycheck right away or within a day or two, while others allow the employer to wait until the next regular payroll. That distinction matters for a rehire that follows a short gap, since an employer that mishandled the earlier final pay can face a separate penalty on top of any rehire paperwork issue.

Because ADP Workforce Now does not adjudicate these differences, the compliance call still sits with the employer, not the software. Frequent rehiring and re-terminating the same workers can also affect an employer's state unemployment tax rate over time. Most states calculate that rate partly from a company's history of layoffs and claims. This rarely matters for a single rehire, but it becomes relevant for employers who cycle seasonal staff in and out every year.

Mistakes to Avoid When Rehiring in ADP Workforce Now

Most rehire problems in ADP Workforce Now trace back to one of these avoidable mistakes:

• Creating a new employee record instead of reopening the old one. This splits the person's wage and tax history across two IDs, which can misstate their W-2 and force a manual merge.
• Choosing the wrong reason for the personnel action. Selecting a generic new-hire reason instead of the rehire-specific code breaks the link to the employee's prior service and payroll history.
• Entering the wrong effective date. An incorrect rehire date can push the employee onto the wrong pay cycle or open a benefits enrollment window on the wrong day.
• Skipping the I-9 recheck. ADP's status change does not automatically verify or update Form I-9, so employers who assume it does risk a paperwork violation.
• Assuming sick-leave or benefits rules are federal. Many of the rules that matter most for a rehire are set at the state or plan level, not by a single nationwide standard.
• Leaving stale position or department data uncorrected. An old, unclosed department or position tied to the employee's prior record can stall the rehire wizard or route pay to the wrong cost center.
• Not confirming direct deposit and tax withholding are current. Bank details and W-4 elections from years earlier are often outdated, and ADP does not always prompt a re-verification during a rehire.
• Rehiring without checking eligibility restrictions. Some companies have a policy against rehiring anyone terminated for cause, and skipping that check can create a difficult reversal later.

Do's and Don'ts for a Clean ADP Rehire

Do

• Confirm the employee's eligibility for rehire first, since some companies flag certain terminations as ineligible before you touch ADP at all.
• Reopen the existing employee profile rather than creating a new one, so wage and tax history stay attached to a single ID.
• Select the rehire-specific reason code, because that field is what tells ADP to treat this as a continuation of employment.
• Verify the work state and locality on the profile, especially if the employee is returning to a different location than before.
• Double-check the effective date against the employee's actual first day back, since it drives pay-cycle and benefits timing.
• Loop in HR or payroll before submitting if the gap since termination is close to a legal threshold, like the 3-year I-9 window or a state's sick-leave reinstatement period.

Don't

• Don't assume the old I-9 is automatically valid. Check the three-year window and the employee's document expiration before you skip a new form.
• Don't guess at benefits eligibility. Confirm the plan's own rehire rule with your benefits administrator instead of assuming coverage restarts as before.
• Don't leave stale job or department data in place. An unclosed position tied to the old record can stall the rehire transaction before it ever reaches approval.
• Don't submit a rehire with unverified personal data. An outdated address or an incorrect Social Security number is one of the most common reasons HR rejects a submitted transaction.
• Don't treat every state the same. Sick leave, final pay, and benefits reinstatement rules can differ sharply once the employee's work state changes.
• Don't forget to tell the employee what carries over. Miscommunicating whether seniority, vesting credit, or PTO survived the gap creates avoidable friction on their first week back.

Pros and Cons of Rehiring vs. Hiring Someone New

Pros

• Faster ramp-up time. A rehired employee already knows your systems, your team, and often the exact job, so training time drops compared with an external hire.
• Preserved vesting and service credit. Retirement plan vesting and, in many cases, seniority-based benefits often continue rather than resetting to zero.
• Lower recruiting cost. Skipping a full external search and interview cycle saves the direct cost of job postings, agency fees, and reviewer time.
• Known performance history. You already have a real record of how the person performed, rather than relying on interviews and references alone.
• Faster ADP data entry. Reopening an existing profile is typically quicker than building a completely new employee record from scratch.

Cons

• Old baggage can resurface. If the person left on bad terms with a specific manager or team, rehiring them can reopen friction that never fully resolved.
• Compliance clocks can work against you. A rehire close to a legal threshold, like the I-9 three-year window or a state sick-leave deadline, adds administrative work a new hire would not.
• Pay equity questions. Rehiring at a different rate than current employees in the same role can create internal pay-equity concerns if the gap is not well justified.
• Skills can be outdated. Someone gone for a year or more may need refresher training even in a job they held before, especially if tools or processes changed.
• Data cleanup risk. Stale department, position, or cost-center data tied to the old record can cause more friction than starting fresh.

What to Do Next

Follow this order to keep a rehire clean from the first click to the first paycheck:

1. Confirm the former employee is eligible for rehire under your company's policy before opening ADP.
2. Locate their existing profile in ADP Workforce Now and change the status from terminated to active.
3. Gather the documents you will need: identification for a possible new I-9, an updated address, and current bank details for direct deposit.
4. Work through the rehire wizard, entering the correct reason code, effective date, job data, and pay rate.
5. Check whether the gap since termination crosses a legal threshold, like the I-9 three-year mark or your state's sick-leave window.
6. Submit the transaction for approval and confirm it posted before the employee's first scheduled shift.
7. Loop in HR, an employment attorney, or an accountant if anything about the rehire is unusual, such as a leave dispute, a different job classification, or a multi-state move.

Frequently Asked Questions

Does rehiring an employee in ADP Workforce Now create a new employee ID?

No. In most setups, reopening the existing profile keeps the original employee ID. That is why choosing the correct rehire reason code matters. Creating a brand-new record instead can split wage and tax history across two IDs.

Do I need to complete a new Form I-9 to rehire someone?

It depends on timing. If you rehire within three years of the original I-9 date, and the work authorization document has not expired, you can update the existing form. Past three years, a new I-9 is required.

How long can an employee be gone before ADP treats the rehire like a brand-new hire?

There is no single ADP-set limit. ADP itself does not force a cutoff, but legal thresholds, like the I-9's three-year window, effectively function as one. Check those thresholds individually rather than guessing.

Will a rehired employee keep their original seniority date?

Usually not on its own. ADP records the new rehire date as the active employment start date. Whether the company also credits prior seniority for PTO or bonus eligibility depends on your written rehire policy, not ADP's default settings.

Does ADP Workforce Now automatically restore an employee's old PTO balance?

No. PTO balances are usually set by company policy rather than restored by the software. Some employers reinstate a rehired employee's prior balance as policy, while others start every rehire at zero.

Can a company rehire someone who was terminated for cause?

That depends on company policy, not ADP. ADP will still allow the status change on any terminated profile. Many companies have an internal policy marking certain termination reasons as ineligible for rehire, which HR should check first.

Do rehired employees have to wait through a new health-benefits waiting period?

Sometimes. Whether a rehire restarts a 90-day waiting period depends on the plan document and how long the person was away. A plan is generally allowed to require the wait again, so confirm with your benefits admin.

Who typically approves a rehire request in ADP Workforce Now?

Usually HR or a payroll admin. A manager can often start the rehire event through self-service, but it typically routes to HR or payroll for approval. A rejected submission has to be corrected and resubmitted from the start.

Can a manager rehire someone without going through HR at all?

Rarely, in most setups. Even manager-initiated rehires generally route through an approval workflow rather than posting right away. That gives HR a chance to catch missing I-9 paperwork or incorrect pay data first.

Does ADP charge extra to rehire an employee?

Not as a standalone fee in most cases. Rehiring uses the same employee-record features included in a standard ADP Workforce Now subscription. Specific pricing and add-ons vary, so confirm with your ADP account representative if unsure.

What is the difference between "rehire" and "reactivate" in ADP Workforce Now?

They generally describe the same action. Both terms refer to changing an employee's status from terminated back to active. The exact label shown on screen depends on your company's specific ADP setup.

Can a company use ADP's API instead of the manual screens to process a rehire?

Yes, for companies with the right setup. ADP publishes a Worker Rehire API Guide for integrators who build custom onboarding or HRIS tools. That lets a rehire post programmatically instead of through the manual wizard.