New-hire reporting

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

New-hire reports support child-support administration

The federal-state new-hire system helps states locate parents, establish or enforce child-support orders, and detect some benefit overpayments. The employer sends specified data to the responsible state directory.

This report is separate from Form I-9, E-Verify when applicable, tax withholding forms, state employer registration, unemployment insurance, workers' compensation, payroll setup, background checks, licensure, payer enrollment, and credential verification. Completion of one never proves the others.

The work state usually drives the destination

The ACF new-hire reporting page routes employers to state requirements. Verify the employee's work state, employer entity and FEIN, payroll address, reportable hire date, and submission route.

Remote employees, employee moves, multistate assignments, and related entities can create routing questions. Use state guidance rather than the manager's office or employee mailing address alone.

Federal law supplies a general timing framework

The federal framework generally requires reporting within 20 days after the employee is hired. Employers transmitting electronically can generally submit twice monthly, with transmissions 12 to 16 days apart, under the applicable rules.

A state can require or allow a faster route, different trigger detail, or additional data. Build each state as a versioned rule with a source, effective date, due-date calculation, required fields, submission method, and acceptance artifact.

Hire and rehire dates need definitions

The reportable hire date is commonly tied to the first day an employee performs services for pay. Rehires after a break can trigger a new report under federal or state rules. States can define rehire and return-to-work treatment more specifically.

Do not use the offer date, background-check date, orientation invitation, payroll-entry date, or first scheduled session without confirming that it matches the governing definition. Paid training can be work and may occur before client service.

Required data is sensitive

Common fields include employee name, address, Social Security number, hire date, and employer name, address, and FEIN. States may request or require additional fields. The ACF state contact and program directory lists current state contacts, timeframes, data elements, methods, and contractor-reporting status.

Limit Social Security numbers and personal data to authorized roles and systems. Use the state's approved secure route. Avoid email, spreadsheets, and support tickets that expose full identifiers beyond the reporting need.

Multistate employers may select a consolidated route

A qualifying multistate employer can generally designate one state and report employees from multiple states electronically after completing the federal registration process. The election has conditions and does not automatically cover independent-contractor reporting or every state employer duty.

Compare consolidated reporting with state-by-state filing before choosing. Record the designated state, registration evidence, included entities, effective date, electronic method, update process, and state exceptions. A vendor setting marked “multistate” is not evidence of a valid designation.

Transmission and acceptance are separate states

Build a record from source HR data through report creation, approval, transmission, state acceptance, rejection, correction, and closure. A file leaving payroll has not necessarily reached the state.

Reconcile new hires from recruiting, HR, payroll, and accounts payable. This can surface late employee setup, rehires, people paid outside payroll, or a worker-classification question. Route classification to qualified review rather than submitting inconsistent labels across systems.

A fictional reporting cohort

Pinecrest ABA has 14 employee reports due during a month across three states. Twelve are accepted by the correct state within the applicable deadline. One was rejected for an FEIN mismatch; another was created late after paid orientation failed to trigger the HR event.

On-time accepted reporting is 12 of 14, or 85.7%. Both exceptions remain in the denominator. Pinecrest corrects and submits them, records actual completion dates, and reviews whether state penalties or other follow-up applies.

The percentage measures timely accepted reports. It does not establish correct classification, onboarding compliance, child-support withholding, or state tax registration.

Contractor reporting varies by state

Federal employee new-hire reporting does not produce one national independent-contractor rule. Some states require reports for specified contractors. Verify the state test, payment threshold, contract date, data fields, and due date.

A report does not decide whether the worker is legally an employee or contractor. Classification depends on applicable federal and state law and actual working facts.

Keep the workflow current

Test the trigger after payroll, HR, entity, FEIN, vendor, or state changes. Review state sources at a defined cadence. Preserve the due cohort, source data, transmission ID, acceptance, rejection, correction, and final status.

Give employees an accessible privacy notice about required uses of their information where applicable. Limit internal dashboards to the minimum data needed for completion and oversight.