Does ADP Report New Hires to the State? (w/Examples) + FAQs

Yes, ADP can report new hires to the state, but only when new-hire reporting is switched on inside the employer's account. It is not automatic on every plan. The legal duty to file stays with the employer even after ADP submits the paperwork. A setting nobody checked can quietly leave a company out of compliance for months.

Missing that switch has real consequences. Federal law pushes all 50 states to collect new-hire data within a tight window of the hire date, according to Kansas's labor department. State child-support agencies use the filing to track parents who owe support. A fast-growing company that assumes its payroll vendor handles this automatically can build up unreported hires for weeks before a state notice arrives.

This article reflects federal new-hire reporting law and general ADP product structure as of 2026. State deadlines, file formats, and ADP's own service names change over time. Confirm your state's current rule and your account's live settings before relying on anything here. It is educational, not a substitute for advice from your ADP representative, an employment attorney, or your state's labor agency.

What New-Hire Reporting Requires

New-hire reporting is a legal filing, not routine onboarding paperwork. It exists because of the Personal Responsibility and Work Opportunity Reconciliation Act (PRWORA) of 1996. That federal law built a national system for tracking new workers, so states can enforce child support orders faster. The filing is mandatory, not optional, regardless of how small the employer is.

Every employer must report each new or rehired worker to a state directory of new hires. This applies to a one-person LLC and a national retailer alike. It also applies whether the person works full time, part time, or quits after a single shift. Size and industry never exempt any single employer from this legal duty.

The report itself is short. It needs the employee's name, address, Social Security number, and hire date, plus the employer's name, address, and Federal Employer Identification Number. Many states accept a copy of the employee's W-4 as the report itself. That is why Kansas's labor department tells employers to include their FEIN on the W-4's employer block.

A missing field is the most common reason a state rejects a submission and asks for it again. States forward new-hire data to the National Directory of New Hires. That directory matches it against child-support cases, so an income-withholding order can start before a parent changes jobs again. That national matching step is what makes new-hire reporting different from most payroll paperwork, which usually stays inside one state.

The same data catches people drawing unemployment or workers' compensation benefits while secretly back on payroll. An employer that never reports is unknowingly shielding both problems at once. A common misconception is that this filing only matters when a support order already exists. States run every new hire through the match, so no employer knows in advance whose case will be affected.

How ADP Fits Into New-Hire Reporting

ADP already captures the data a new-hire report needs. The same W-4 and I-9 information that sets up a worker's pay and tax withholding also fills the report's required fields. What ADP does with that data next depends on the product the employer uses. It also depends on whether new-hire reporting has been turned on for the account.

ADP publishes guidance aimed specifically at employers trying to understand this filing on its own resource pages. That signals ADP treats new-hire reporting as its own compliance task, not something buried inside standard payroll setup. Automatic reporting is a service, not a default.

Employers who never enable it are still full ADP clients running complete payroll, yet nothing goes to the state. This is the most common misunderstanding among employers who switch to ADP mid-year. They assume that because ADP files taxes and W-2s automatically, new-hire reporting rides along the same rail. It is a distinct, separate box to check.

A free self-check confirms the setting in minutes. Log into the employer's ADP portal and open the compliance or reports section. Look for a "New Hire Reporting" status or a recent filing log. If nothing appears there, or ADP support cannot confirm an active service, treat the account as unreported until proven otherwise.

Running this check costs nothing and takes less time than a single payroll cycle. Repeat it whenever the company switches ADP packages or adds a new work state. A setting that worked in one state does not automatically extend to another. Building the check into a standing onboarding list removes the need to remember it case by case.

RUN Powered by ADP

RUN targets small businesses running their own payroll without a dedicated HR staff. New-hire reporting is typically offered as an add-on compliance service, not a feature baked into the base plan. A ten-person shop on RUN's standard tier may find that new hires are never reported unless someone specifically added the service during setup.

Cost is often the deciding factor for a small business weighing whether to add the module. Checking a plan's actual price tier first beats assuming the feature is bundled. ADP's small-business pricing explains what typically comes standard versus what carries an extra fee. A company that skips this check can run months of payroll believing it is compliant when it is not.

The owner who set up the RUN account is often the only person who remembers which add-ons were selected. That knowledge rarely transfers cleanly if HR duties change hands. Asking ADP support to confirm the account's active services in writing closes that gap for good. Save that written confirmation somewhere the next HR hire can find it.

ADP Workforce Now

Workforce Now serves mid-market employers, often with multiple locations or states. It generally includes a more built-out compliance module, with new-hire reporting sitting next to other statutory filings. The reporting still is not automatic by default.

A payroll manager has to confirm the service is turned on per state. A company that expands into a new state mid-year does not get new-hire filings there simply because its home state was already covered. That gap is easy to miss during a busy expansion, when HR staff focus on hiring speed rather than a settings menu.

A mid-market employer usually has one payroll or HR manager who owns this check. A small RUN client often lacks that, so the task falls to whoever logs in that day. Building a state-by-state check into the expansion plan, right next to lease signing and benefits setup, keeps reporting from becoming an afterthought. A quarterly review of every active state catches a gap before it turns into a state notice.

ADP SmartCompliance

SmartCompliance is ADP's dedicated employment-tax and compliance layer. It is built for employers juggling many states or a high hiring volume. New-hire reporting is one of its core modules, not an afterthought. Even here, data accuracy stays the employer's job.

SmartCompliance transmits whatever payroll gives it. A mistyped Social Security number entered at onboarding produces a bounced report, no matter how automated the pipeline looks from the outside. The tool cannot substitute for a basic data check at hire time. Nothing in the platform flags a wrong-but-valid-looking number before it reaches the state.

Employers at this scale often assume that paying for the most complete compliance product removes all manual oversight. That assumption is where the startup example later in this article goes wrong. A monthly spot-check of a handful of records catches the kind of error automation alone will miss. Ten minutes of review each month is a small price against a rejected filing nobody notices for half a year.

Federal Baseline vs. Your State's Rules

Federal law does not set one universal reporting deadline. PRWORA, codified at 42 U.S.C. § 653a, caps every state's deadline at 20 days from the hire date. A state running two scheduled reporting cycles a month may space them no more than 12 days apart instead.

States are free to choose anything at or under that ceiling. The actual number a given employer must hit depends entirely on where the employee works. Kansas shows how specific a state can get with its rule.

Kansas requires the report within 20 business days of hiring, rehiring, or the date the employee first receives pay, per Kansas's new-hire statute. It counts business days, not calendar days. That distinction matters for a multistate employer, because a deadline measured in business days behaves differently around a long holiday weekend. Never assume your state matches the federal ceiling exactly.

The only reliable method to confirm your real deadline is to check your own state's new-hire directory page directly. A quick search for "[your state] new hire reporting" usually surfaces the right agency page within a few clicks. Bookmark that page, since state agencies update deadlines and file formats without much advance notice.

Multistate employers may have one meaningful piece of relief available. Federal guidance lets an electronic filer with new-hire duties in several states apply to send every report to one chosen state instead. That state's own requirements generally need to be met first. Where it applies, this single change can turn a monthly filing chore across five states into one routine task.

That election is a simplified model of a more detailed enrollment process. A company still has to register the election with the federal Office of Child Support Enforcement before combining filings. Treat this as the idea to raise with a payroll manager, not a step to attempt without checking the paperwork first.

What Counts as a "New Hire" You Must Report

Not every payroll event triggers a fresh report, and getting this wrong in either direction causes real problems. An employee who works two hours and quits still counts and must be reported. The state cannot know in advance that a job will be short-lived. The address on file stays useful even after the person leaves.

A worker who returns after a gap of 60 consecutive days or more must be reported again as a "rehire." This applies whether the gap came from a layoff, unpaid leave, or a plain termination. It applies even if nothing else about their pay setup changed. Missing this rule is one of the most common gaps in an otherwise compliant reporting process.

Two situations do not require a new report. An employee already reported once does not need reporting again purely because a business changes ownership. That is true as long as the original report happened before the takeover. Only employees hired after the ownership change need fresh filings under the new employer.

Temporary staffing agency workers are reported once by the agency itself, when they sign a W-4 and start an assignment. They are not reported again every time that same worker moves to a new client company. The agency, not the client business, carries the reporting duty in that relationship.

A related misconception trips up employers who also file quarterly wage reports and assume those cover new-hire reporting too. They do not. Quarterly wage data can take two to six months to reach the state after a person is hired, according to Kansas's labor department. That is far too slow for a child-support agency trying to intercept wages from a parent who recently started a new job.

That delay is exactly why the separate, faster new-hire report exists in the first place. A parent could change jobs three or four times in the gap a quarterly report would leave open. The faster filing closes that window and keeps support payments flowing.

Worked Example: Calculating the Cost of a Missed Report

A 40-person distribution company hires 12 new warehouse workers over one quarter. It assumes ADP's standard payroll package is filing new-hire reports on its own, as automatically as it handles payroll taxes. That assumption is wrong. The company never activated the reporting service when it onboarded with ADP six months earlier.

The state agency eventually cross-references payroll tax filings against its new-hire directory. It flags all 12 workers as unreported roughly 90 days after their start dates. By then, the exposure has already stacked up across an entire quarter of hiring. Nobody at the company had any warning until the state's letter arrived.

Federal law caps a state's civil penalty at $25 per unreported employee for an ordinary failure to report. That figure rises to $500 per employee if the state determines the employer and employee conspired not to report. At the standard rate, 12 unreported hires works out to $300 in potential penalties. That number is only the fine itself, before any staff time or paperwork is counted.

That $300 is a modest number by itself, but the real cost runs deeper. The company still has to manually file all 12 reports late. It also has to verify the Social Security numbers and write up why the lapse happened, in case the state follows up. The compliance team spends roughly three hours confirming every report was accepted, on top of its normal payroll work.

That time would have been unnecessary had someone checked the ADP setting on day one. A business operating in five states multiplies the risk across every state where new-hire reporting was never turned on. A single missed setting during a payroll switch can build up across an entire year of hiring before anyone spots the gap. A five-minute check at onboarding is cheaper than any of these fixes.

Where Employers Get New-Hire Reporting Wrong

Three genuinely different failure points show up again and again once ADP is in the picture. Each one teaches something the others do not, from a missing setting to a data error that automation cannot catch on its own. None of them required a careless employer; each came from a reasonable-sounding assumption that turned out to be wrong.

The Solo HR Admin Who Assumed the Feature Was Included

Maria runs HR alone at a 15-person marketing agency that migrated to RUN Powered by ADP the prior year. She assumed new-hire reporting rode along automatically with payroll, much like tax withholding does. She never checked a settings menu to confirm it. Six months and four new hires later, the state's child-support office mailed a notice asking why none of the new employees showed up in its directory.

Maria discovered the reporting add-on had never been purchased. Fixing it took one phone call to ADP support and a same-day activation. Still, the four missed hires had to be filed manually and late. Now Maria checks the reporting status every time she onboards a new employee, instead of trusting it silently in the background.

The Multistate Retailer That Skipped the One-State Election

A retail chain hiring across three states used ADP Workforce Now. It filed new-hire reports separately with each state's directory every time a store opened. The company never registered the federal election that lets a multistate electronic filer send every report to one state. Its HR team spent hours each month formatting three different file layouts for three different agencies.

Once the company registered the election, its monthly reporting workload dropped from roughly six hours to under one. The lesson here is not about a missing setting inside ADP, but about a federal option most multistate employers never learn exists. Nobody at the retailer had reason to search for it, since Workforce Now filed every state correctly on its own. The process simply cost more time than it needed to.

The Startup Whose Data Bounced Silently

A 20-person startup on ADP SmartCompliance had reporting fully activated, so the founders assumed the system was foolproof. A new hire's Social Security number was transposed by one digit during onboarding. The state's directory rejected the filing outright, rather than flagging it for a manual fix. Nobody at the company knew the report had failed until an audit eight months later caught the gap.

The lesson is that even a fully active, correctly configured reporting service depends on accurate data going in. Automation moves the paperwork; it does not check whether a nine-digit number is right. A short manual review at hire time is the one step no ADP product replaces.

Which Situation Applies to You?

If your company is a small, single-state business on a basic ADP plan, first confirm whether new-hire reporting was ever added. It usually is not bundled by default at the entry tier. Checking costs nothing and prevents months of silent non-compliance. Ask your ADP representative directly, since sales pages rarely spell out the exact boundary between tiers.

If you operate in more than one state, your priority is registering the federal one-state election. That stops your team from juggling separate filings for each state. This fix pays for itself the first month you use it, based on the hours it saves an HR team formatting redundant files. It also lowers the odds of missing any single state's deadline.

If your company recently switched to ADP from another payroll provider, treat the transition itself as a risk window. Settings from the old provider do not carry over. New-hire reporting is exactly the kind of compliance task that quietly falls through the cracks during a system migration. Confirm the setting again within your first full payroll cycle on the new system, before a single new hire slips through unreported.

If you are opening a new location in a state where you have never had employees before, plan for this early. An existing new-hire reporting setup does not automatically extend there. Each state requires its own registration, and often its own proof that ADP is actively filing there. Build that check into your location-opening checklist rather than treating it as an afterthought.

Whichever situation applies, the fastest path to certainty is a direct question to ADP, not an assumption based on price or product name. A short email asking which states your account actively reports to creates a written record you can point to later. That record matters if a state ever questions your compliance history.

Mistakes to Avoid

• Assuming reporting is automatic on every ADP plan. Many accounts run full payroll for months with the new-hire service never turned on, leaving every hire unreported.
• Confusing new-hire reporting with Form I-9 or W-4 processing. Completing onboarding paperwork does not send anything to the state's new-hire directory on its own.
• Skipping the check after switching ADP products. Moving from RUN to Workforce Now, or adding a new state, does not automatically carry the reporting setting forward.
• Not verifying the SSN and hire date before submission. A single transposed digit can cause a silent rejection that nobody notices for months.
• Ignoring the 60-day rehire rule. Employees returning after a gap of 60 or more days need a fresh report, even if their pay setup barely changed.
• Filing separately in every state without registering the one-state election. Multistate employers waste hours on redundant filings they could combine into one.
• Treating the quarterly wage report as a substitute. That data arrives two to six months late, far too slow for the child-support matching this filing exists to speed up.
• Never assigning an owner for compliance checks. Without someone accountable, a bounced report or an expired setting can go unnoticed for an entire audit cycle.

Do's and Don'ts for New-Hire Reporting on ADP

Do

• Confirm your ADP plan includes an active new-hire reporting service before assuming it does, because the safest assumption is that it is off until verified.
• Register the federal one-state election if you hire across more than one state, since it collapses several filings into one.
• Recheck your reporting settings every time you add a new work state, because coverage does not extend automatically.
• Keep a simple log of new-hire report confirmations, so a bounced filing surfaces quickly instead of during an audit.
• Ask your ADP representative directly which product tier includes new-hire reporting, since marketing pages rarely spell out the exact plan boundary.

Don't

• Don't assume Form I-9 or W-4 completion means the state new-hire report went out; they are separate processes that happen to share source data.
• Don't skip verifying SSNs at onboarding, since a typo produces a silent rejection rather than a helpful error.
• Don't wait for a state notice to discover a gap; by then, weeks or months of hires may be unreported.
• Don't assume a platform migration preserves compliance settings automatically, since new-hire reporting is often left behind.
• Don't treat the 60-day rehire threshold as optional; missing a rehire report carries the same exposure as missing a new hire.

Pros and Cons of Letting ADP Handle New-Hire Reporting

Pros

• ADP already holds the required data from W-4 and I-9 intake, so no separate data entry is needed once the service is active.
• The one-state election, when registered, removes most of the manual work for multistate employers.
• SmartCompliance and Workforce Now bundle new-hire reporting with other statutory filings, reducing the number of separate compliance vendors.
• Automated filing reduces the odds of a late report compared with manual submission by a busy HR team.
• A documented, vendor-run process is easier to point to during a compliance audit than an ad hoc manual system.

Cons

• The service is not automatic on every plan, so employers can pay for ADP and still be non-compliant without realizing it.
• Legal responsibility for an accurate, timely report stays with the employer even when ADP handles the transmission.
• A data entry error, like a mistyped SSN, can cause a silent rejection that automation will not flag on its own.
• Enabling the service across a new state after expansion requires manual follow-up; it does not happen by itself.
• Employers on entry-level plans may face an added cost to unlock the reporting module in the first place.

What to Do Next

1. Log into your ADP portal and check the compliance or reports section for an active "New Hire Reporting" status.
2. If reporting is inactive, contact your ADP representative to confirm the exact plan tier or add-on that includes it.
3. Pull your state's specific reporting deadline and file format from its labor department's new-hire reporting page.
4. If you hire across multiple states, ask your ADP contact about registering the federal one-state election.
5. Spot-check a handful of recent new-hire records for accurate Social Security numbers and hire dates.
6. Set a recurring reminder to recheck reporting status whenever you add a new work state or switch ADP products.
7. If a report has already been missed, consult an employment attorney or your state's new-hire directory office about correcting it before a penalty is assessed.

Frequently Asked Questions

Does ADP report new hires automatically?

No. ADP only reports new hires to the state once the new-hire reporting service is active for the employer's account. It does not happen by default on every payroll plan.

Is new-hire reporting the same as filing a W-4?

No. A W-4 sets up tax withholding. Some states accept a copy of it as the new-hire report. Filing one with ADP does not, by itself, send anything to the state's directory.

How long do I have to report a new hire?

Federal law caps it at 20 days from the hire date. Many states set a shorter window, so check your specific state's labor agency page for the exact deadline that applies to you.

What happens if I never report a new hire?

A state can fine the employer. Federal law allows penalties up to $25 per unreported employee. That figure rises to $500 if the state finds the employer and employee agreed not to report.

Do I have to report an employee who quits after one day?

Yes. Any employee who completes a W-4 and works even a single shift must be reported, regardless of how briefly they stayed.

Does a rehired employee need to be reported again?

Yes, if they were away 60 or more consecutive days. A shorter break, like a brief unpaid leave, generally does not trigger a new report.

Can I report new hires to only one state if I operate in several?

Yes, in most cases. Federal guidance lets an electronic filer with duties in multiple states apply to combine filings into one state. Confirm the exact enrollment steps with your payroll provider.

Does ADP charge extra for new-hire reporting?

It depends on your plan. Some ADP packages bundle it with broader compliance services, while others require adding it separately, so confirm the cost with your ADP representative.

Is new-hire reporting only about child support?

Mostly, but not only. States also use the same data to catch unemployment and workers' compensation fraud by matching new hires against active benefit claims.

What information does a new-hire report include?

Name, address, and Social Security number for the employee, plus the hire date and the employer's name, address, and Federal Employer Identification Number.

Do temporary staffing agency workers get reported by the agency or the client company?

The staffing agency reports them, once when the worker signs a W-4 and starts an assignment. They are not reported again each time that worker moves to a new client site.

Does switching from another payroll provider to ADP carry over my new-hire reporting settings?

No. A payroll migration does not automatically transfer compliance settings, so reporting must be rechecked as part of the switch to ADP.