New Hire Reporting Compliance

New hire reporting is a federally mandated process requiring employers to submit information about newly hired and, in most states, rehired employees to a state directory within a strict timeframe after the hire date. The requirement originates from the Personal Responsibility and Work Opportunity Reconciliation Act of 1996 (PRWORA, P.L. 104-193), which established the Federal Case Registry and the National Directory of New Hires as tools for enforcing child support obligations. Employers who miss deadlines or submit incomplete data face penalties that vary by state, and multi-state employers carry an additional layer of election obligations. This page covers the definition, operational mechanism, common compliance scenarios, and the key decision boundaries that determine how and where reporting must occur.


Definition and Scope

New hire reporting is the employer obligation to notify a designated state agency of each person who is hired or rehired after a period of separation, supplying specific identifying and wage data so that the state child support enforcement system can locate obligors and issue income withholding orders. The requirement applies to all employers subject to the Federal Unemployment Tax Act (FUTA, 26 U.S.C. § 3301), regardless of size. There is no minimum employee count that exempts a business from the obligation.

The statutory backbone sits in 42 U.S.C. § 653a, which mandates that each state operate a New Hire Reporting Program and that employers report to the state in which the new hire works — or, for multi-state employers, to a single elected state. The Office of Child Support Services (OCSS) within the U.S. Department of Health and Human Services (HHS) administers the federal overlay and provides guidance to state IV-D agencies that run the day-to-day programs.

For payroll compliance requirements generally, new hire reporting is a distinct obligation layered on top of tax registration and wage withholding, not a substitute for any of them.


How It Works

The reporting pipeline follows a structured sequence from the hire event to federal data matching:

  1. Trigger event — An employee is hired or, if state law extends coverage, rehired after a separation of at least 60 consecutive days (the federal rehire threshold; states may lower this floor).
  2. Data collection — The employer assembles the federally required data elements: employee name, address, Social Security Number, date of hire or rehire, and employer name, address, and Federal Employer Identification Number (FEIN). States may require additional fields such as date of birth or salary.
  3. Submission — The employer transmits the report to the appropriate State Directory of New Hires (SDNH) by the state deadline. The federal outer limit is 20 days from the date of hire (42 U.S.C. § 653a(b)(1)(A)); 17 states require submission within fewer than 20 days, and some require two reports per month for employers who report magnetically or electronically.
    4.
  4. Matching — The NDNH cross-references new hire records against child support case data. Matches trigger income withholding orders routed back to employers.

Accepted submission formats include paper forms (typically a W-4 or state equivalent), electronic file transfer, and online portals provided by each state agency. The method does not affect the deadline.


Common Scenarios

Standard single-state employer. A company with employees working exclusively in one state reports all new hires to that state's SDNH by the state deadline. This is the baseline scenario and carries no election complexity.

Multi-state employer election. An employer with employees in 2 or more states may either report each employee to the state where the employee works, or elect to report all employees to a single state in which the employer has a place of business. The election must be registered with HHS (Office of Child Support Services multi-state reporting portal). Failure to register the election and then filing in only one state may create deficiency findings in the non-elected states.

Independent contractors. Federal law does not require reporting independent contractors as new hires. However, 27 states have enacted statutes extending reporting obligations to independent contractors compensated above a state-set threshold (commonly $600 per year, mirroring 1099-NEC thresholds). Employers should confirm state law before treating a contractor classification as exempt from reporting. For the broader classification question, see employee classification compliance.

Rehired employees. A returning worker separated fewer than 60 consecutive days does not trigger a new federal reporting obligation. A worker separated 60 days or more does trigger a new report, even if the employee was previously reported. States may use a shorter separation window.

Employees working remotely in a different state. The governing rule is the state where the employee performs work, not the employer's primary location state. A Texas-based company that hires a remote worker residing and working in Oregon must report that worker to Oregon's SDNH unless the company has elected multi-state reporting to a different state that includes Oregon.


Decision Boundaries

Employers encounter several classification forks that determine exactly what obligation applies:

Condition Reporting Required? Governing Authority
New employee, single-state employer Yes — to employee's work state 42 U.S.C. § 653a
Rehire, gap < 60 days No (federal baseline) 42 U.S.C. § 653a(a)(2)
Rehire, gap ≥ 60 days Yes 42 U.S.C. § 653a(a)(2)
Independent contractor, no state statute No Federal baseline
Independent contractor, state extends coverage Yes, above state threshold State IV-D statute
Multi-state employee, no election filed Report to work state 42 U.S.C. § 653a(b)(1)(B)
Multi-state employee, election registered Report to elected state 42 U.S.C. § 653a(b)(1)(B)

Penalty structure. Penalties for failure to report are set by state law. The federal statute authorizes states to impose penalties up to $25 per unreported hire and up to $500 per hire when the failure results from a conspiracy between employer and employee to not supply the information (42 U.S.C. § 653a(d)(2)). Several states — including California, with a $24 penalty per violation under California Unemployment Insurance Code § 1088.5 — set their own schedules within the federal ceiling.

Intersection with I-9 and E-Verify. New hire reporting is legally distinct from employment eligibility verification. Completing an I-9 form or running an E-Verify query does not satisfy the new hire reporting requirement, and the reverse is equally true. Both obligations run in parallel from the same hire trigger event. Employers managing compliance recordkeeping requirements should maintain separate documentation trails for each obligation.

Timing conflicts. When a state deadline is fewer than 20 days and the employer's regular payroll cycle does not generate the FEIN confirmation until day 18 or 19, the employer must initiate a manual reporting process for that employee rather than relying on automated payroll integration. The payroll system's batch schedule does not override the statutory deadline.


References

📜 7 regulatory citations referenced  ·  🔍 Monitored by ANA Regulatory Watch  ·  View update log

Explore This Site