New-Hire Reporting: Prove the State Received the Right Employment Event
The payroll roster shows six people added this week. The reporting service shows one file sent. Those two totals do not tell the employer which employment events were reportable, where each report went or what happened to individual records. A rejected row can sit behind a successful file upload.
New-hire reporting needs its own completion evidence. Build the process around the employer, employee event, reporting jurisdiction, due date and returned result. A first paycheck, an active employee profile and a new-hire report answer different questions. None should silently stand in for the others.
This guide addresses U.S. private-sector employers and ordinary state new-hire reporting. Federal employers and specialist arrangements need their applicable instructions. Official sources were checked November 10, 2026. The examples and register are original operating aids, not agency forms, legal determinations or evidence that a payroll product has been tested.
Contents
Identify the event the agency needs
Start with the real employment event. Under Social Security Act Section 453A, the federal definition includes an employee who has not worked for the employer before and a returning employee separated from that employer for at least 60 consecutive days. Verify applicable state requirements before using the federal definition as the whole rule.
Keep the first day services were performed for pay distinct from an offer date, a profile-creation date and the first payday. A person can begin work in one payroll period and receive the first payment later. Record the source of the start date so an operator does not substitute whichever date appears first in an export.
Reconcile the event list with HR and the responsible manager. Include starts recorded after the ordinary onboarding meeting, returns from seasonal shutdowns and employees who leave quickly. California EDD expressly requires reporting even when a new employee stops working before the reporting deadline, including someone who worked less than a full day. Removing that person from the active roster does not resolve the report.
Review a return from leave separately from a genuine separation and rehire. A payroll status code alone does not establish the legal event. Keep the prior employment end, return date, employer identity and reviewer conclusion together. Ask for a state-specific answer where the facts do not fit the ordinary rule, rather than inventing a reporting event to satisfy a software flag.
An acquisition or entity change deserves the same care. California distinguishes acquiring an ongoing business and employing the former owner's workers from changing entity type while workers continue with the business. The first situation requires new-hire reports under its instructions; the second does not. That is a California distinction, not a universal rule for every transaction. Send the actual facts to the applicable reporting owner.
If you are comparing payroll services, ask how each service identifies reportable starts and returns, determines the receiving state and exposes records that need attention. A free SelectSoftware Reviews advisor discussion can help you shortlist payroll options around those administration needs.
Put the receiving state beside the employer
The ordinary federal route is the State Directory of New Hires where the employee works. An employer with employees in two or more states can instead use the federal multistate option: designate one state in which it has employees, report electronically or magnetically, and notify the U.S. Department of Health and Human Services of that designation.
Do not choose a destination merely because it is the employer's headquarters, the employee's home address or the payroll provider's usual processing state. Establish the applicable route from the work facts and any valid multistate designation. Preserve the selected state, covered employer and supporting registration reference in the reporting instructions.
Check the arrangement at the employer level when a provider serves many customers. Maryland's employer FAQ explains that a provider cannot place every client's reports in one state unless each client's circumstances and registration support that route. The provider's own multistate presence is insufficient. Ask whose designation is being used and whether that employer actually has employees in the selected state.
For a remote hire, record the work location that supports the reporting decision and distinguish it from a mailing address. A later move may require a new review of payroll or reporting instructions, but it should not automatically create a duplicate new-hire event. Document whether the employer and employment relationship changed before sending another report.
Keep registration and reporting separate in the task list. Evidence that the employer enrolled in a portal or registered a multistate election does not show that an employee's report was submitted. Conversely, a portal accepting a file does not establish that the employer chose the correct reporting route. Both questions must have an accountable answer.
Keep the employment event, reporting destination, transmitted version and returned result connected. Use the register below to record the answer at each stage.
Schedule reporting from the governing rule
Federal law sets an outside ordinary reporting period of 20 days after hire and an electronic or magnetic alternative of two monthly transmissions, when necessary, 12 to 16 days apart. States may require earlier reporting. Confirm the current state-and-method instruction before designing the calendar.
Do not translate “twice monthly” into an arbitrary first-and-last-day schedule, or assume every report can wait until the next normal payroll. California's current instructions require two monthly electronic reports 12 to 16 days apart when there are new or rehired employees to report. Its ordinary start-of-work rule uses 20 calendar days. Apply the instructions for the actual method rather than blending parts of different schedules.
Build internal dates backward from the governing requirement. Identify when HR must supply the event, when missing information must be escalated, when the transmitter sends it and when the reviewer checks the result. Leave time for correction within the applicable deadline. An internal early target is a control choice; it does not change the legal deadline.
A fictional employer uses a reviewed electronic calendar with transmissions on November 5 and November 20, fifteen days apart. HR identifies three supported starts before the November 5 batch, but one record lacks a required field. Sending two records and moving the third into an exception queue does not make all three complete. The owner still needs a timely supported reporting route for the missing record.
Ask who watches the queue over holidays, absences and provider cutovers. If the state requires an earlier date than the calendar's next batch, resolve that conflict before release. Keep a separate due date for each affected event when one shared batch date would hide an earlier obligation. Do not mark a late report timely by changing the employee's actual start date.
Match the fields to the selected reporting method
The federal minimum covers employee identity, address, SSN and first paid-service date, plus employer identity, address and identifying number. A state can require additional fields. Confirm the current official specification for the reporting jurisdiction and method.
California, for example, also lists its EDD employer payroll tax account number and an assigned branch code among the required employer information. A file that meets one state's specification can therefore remain incomplete for another. Keep the applicable field list with the employer's approved reporting route.
Validate the actual outbound representation, not only the profile screen. Confirm employer identifiers, the complete employee identity, start or rehire date and address fields in the submission. Preserve leading zeros where the official format requires them. Compare a sample export against the specification when the provider can safely supply one.
A copy of Form W-4 sitting in the payroll system is not proof that a new-hire report was sent. California permits an augmented W-4 or DE 4 as a paper reporting option, but requires added start-of-work and employer-account information. That limited option does not make an ordinary stored withholding certificate a completed filing.
If a required SSN is missing or invalid, keep the case open and obtain the applicable agency instruction. Maryland warns against substituting an ITIN or a resident-alien number for the required SSN. Do not invent an identifier, borrow another person's number or treat the reporting exception as a payroll determination about work authorization.
Keep sensitive identifiers in the approved reporting system and restricted source records. The working register below uses references instead. A shared operational list can show that a record needs identity review without exposing the employee's full SSN or private family circumstances. Give the responsible specialist access to the actual evidence through the authorized route.
Follow the result beyond the send event
Use distinct operating statuses: Ready, Submitted, Confirmed, Needs correction and Outcome unknown. Define them for the actual channel. “Submitted” means the authorized report was transmitted; “Confirmed” means the retained agency or provider evidence supports the completion described. Do not imply that every agency supplies the same acknowledgment or a record-level acceptance file.
California's linked electronic filing guide describes confirmation numbers after successful online or bulk submissions. Save the confirmation and connect it to the relevant employer, report and included population. A screenshot showing only a success banner, without a report identity or retained scope, can be difficult to use when a later question concerns one employee.
Determine what the receipt establishes. It may confirm receipt of the file, completion of a portal submission or another stated outcome. Ask whether additional validation results or notices follow and how the transmitter retrieves them. If the channel offers only limited confirmation, record that limit and the agency's supported follow-up route.
For a bulk file, reconcile the source population with what was transmitted and any returned record outcomes. Distinguish a file rejected before processing from a submission containing an individual problem. Do not let a provider's file-level success clear every underlying employee event automatically.
Consider a fictional batch of six reportable events. The available evidence establishes four confirmed records, one rejected record and one record whose outcome is unknown. The control total is six: four plus one plus one. Only four have the stated confirmation evidence. Two need follow-up, and the rejected record and unknown outcome need different actions.
In this fictional batch, four confirmed events plus one rejected and one unknown reconcile to six. The two open events need different follow-through; a file-level success cannot resolve them.
For the rejected record, preserve the error, obtain the authorized correction and use the receiving agency's supported correction or resubmission method. For the unknown outcome, trace the original submission before sending another copy. Search the provider's retained record or obtain help from the reporting agency. A blind replay can add uncertainty about which version is authoritative.
Give every unresolved item an owner, deadline and next action. If the applicable reporting deadline has passed, record that fact and seek the supported response promptly. Keep the original date and failed attempt visible. A later successful submission can close the missing outcome while leaving a late-reporting issue that still requires review.
Make the provider's promise specific
Ask whether the service covers the actual employer, jurisdiction, employee event and chosen reporting route. Identify who turns reporting on, what data is required, when the service transmits and how someone learns that it could not finish. “New-hire reporting included” does not answer those operational questions.
Gusto's current help page illustrates why setup and evidence need separate questions. It describes an employee-level choice to request reporting, says reports are sent within a few days of the request, and tells employers not to request a duplicate when another party already handled it. Confirm the state deadline and account setting before relying on that timing.
The same help page has both a statement that the filed report is not visible and a later section describing filed documents with state-dependent availability. Ask Gusto which evidence is available for the specific state and account, and obtain support confirmation if the report is absent. Do not treat a missing document as proof of failure or guarantee that every state provides a downloadable copy.
Document how the employer learns of missing data or an unsupported case. Does the service send a usable exception notice, leave a task in a dashboard or require an employer query? Establish who receives that information during an administrator's absence. Ask the provider to demonstrate the notification route in a supported test environment or with its supplied examples. Do not transmit a fictitious employee report to a government agency to test an alert.
When switching providers, divide responsibility by real employment events and reporting outcomes. Importing an existing workforce should not automatically instruct the new provider to report every continuing employee as newly hired. Preserve the prior reporting evidence and identify unresolved events individually. Give the incoming service a dated list of what it must report and what was already handled.
Ask what happens when the start date changes after the reporting instruction is saved, or when the company corrects the legal employer. Obtain the supported process before an operator tries to undo a report. The employer should know whom to contact, what evidence to retain and how a correction is distinguished from a fresh hire.
Bring the unresolved reporting-state, exception-notice and receipt questions to a SelectSoftware Reviews advisor conversation. Use the shortlist to investigate each payroll provider's actual service scope, with the applicable agency confirming reporting requirements.
Handle the cases that fall outside a clean first hire
A seasonal return needs the prior employment facts, not just a reused employee ID. Establish whether there was a separation and whether the applicable reporting rule treats the return as reportable. Link the event to the earlier worker record while keeping the return's reporting date and outcome distinct. Reusing the profile does not establish that the agency received a rehire report.
For temporary staffing, establish which organization actually employs and pays the individual. Maryland's FAQ distinguishes an agency that only refers people from one paying their wages; the latter has reporting duties for its employees. A new client assignment and a new employment relationship can therefore be different events. Ask the responsible reviewer to resolve the actual arrangement instead of sending reports from both organizations by default.
Do not use an AP payment label to decide the reporting population. Maryland notes that some states impose independent-contractor reporting beyond the federal employee rule. Have the classification and reporting owners identify the applicable route and threshold. A year-end information return does not establish that any earlier state report was completed.
A payroll conversion can also leave an event in two queues. If the old provider says it sent the report and the new provider still shows it pending, compare the employer, employee event and retained transmission evidence. Resolve responsibility for the existing report before instructing the new service to send another. Preserve both providers' references in the handoff record.
Treat a reported start that never occurred as a correction question. Preserve what was authorized, what changed and whether anything was transmitted. Use the agency's current instructions to resolve a submitted error; do not assume that deleting an employee profile recalls information already delivered outside payroll.
A new-hire report can later lead to an income-withholding notice, but the report itself is not an instruction to create an employee deduction. Receive, validate and process an actual notice through the order-handling process. Keep the reporting receipt and the later withholding case linked without treating them as the same obligation.
Use the New-Hire Submission and Acceptance Register
Use one event record per employer and reportable employment event, with a batch reference where appropriate. Store it in an approved work location. The fields below are selectable text for copying into a controlled register. They are not an agency form and should contain evidence references rather than full SSNs or unnecessary personal information.
Event and destination
1. Employer identity: Legal employer and controlled FEIN/account reference: ______.
2. Employee event: Internal employee reference, first hire or return, and supporting employment event: ______.
3. Trigger date: Actual first paid-service or applicable return date, source and reviewer: ______.
4. Reporting route: Work state or approved multistate destination, with designation reference where applicable: ______.
5. Rule checked: Current official requirement, method, due date and review date: ______.
Keep an unresolved event or destination visibly open. A convenient portal default is not a substitute for the reporting owner's decision.
Preparation and submission
6. Required data: State-and-method field checklist, source version and unresolved missing item: ______.
7. Reporting responsibility: Employer preparer, provider/transmitter, reviewer and absence coverage: ______.
8. Planned send: Internal preparation deadline and scheduled transmission, checked against the governing requirement: ______.
9. Submitted version: File or report reference, included event list, transmission time and submitting party: ______.
10. Receipt: Agency or provider acknowledgment reference and exactly what it confirms: ______.
Record outcomes and correction
11. Event outcome: Confirmed, Needs correction or Outcome unknown, with supporting evidence: ______.
12. Returned issue: File or record error, affected field and responsible correction owner: ______.
13. Authorized response: Supported correction, resubmission or trace request and authorizing instruction: ______.
14. Follow-up date: Next action, responsible person and applicable reporting or escalation deadline: ______.
15. Final result: Retained confirmation, corrected version and disposition of the earlier submission: ______.
Record a late or uncertain outcome honestly. Closing the operational task must not erase the original deadline, rejected version or unanswered agency question.
Batch review and handoff
16. Population match: Events due, transmitted, confirmed, rejected and unknown, with reconciliation explanation: ______.
17. Duplicate prevention: Prior-provider or earlier-batch check and the authoritative report retained: ______.
18. Reviewer closure: Reviewed outcome, remaining issue owner and date of review: ______.
19. Downstream notice: Any later agency notice routed to its own responsible process: ______.
20. Evidence access: Restricted source location, access owner and retention/hold instruction: ______.
For the six-event example, field 16 reads six due and six transmitted, with four confirmed, one rejected and one unknown. Fields 12 through 15 carry the rejected record's correction. The unknown record receives its own trace action. Keep these statuses separate until each event has supported closure.
Carry one rejected event through the register
Suppose internal employee H62 begins work for employer E17 on November 3. The reporting owner has already verified the destination, method and due date against the applicable instructions. The transmitter includes H62 in the November 5 batch, but its returned result identifies an employer-account formatting error for that event. These are fictional operating facts, not a state's prescribed error message.
Fields 1 through 5 retain E17, H62, the supported start and the reviewed reporting route. Fields 6 through 10 identify the source version, responsible people, November 5 transmission and receipt reference. Keep the original submitted version even after someone finds the correct account format. Otherwise a reviewer cannot explain why the first attempt failed.
Set field 11 to Needs correction. Field 12 identifies the account-format issue and its owner; field 13 records the receiving channel's supported response. If the agency or provider requires an amended record rather than a fresh submission, retain that instruction. Field 14 carries the next action and the actual governing deadline, rather than simply borrowing the next payroll date.
The responsible party sends the authorized correction on November 6 and retains evidence that the corrected submission was received. Field 15 describes that limited result exactly. If the channel has a later validation stage, keep that stage open instead of translating receipt into final acceptance.
Update the batch reconciliation without counting H62 twice. There is still one employment event, with an original attempt and a corrected version beneath it. The reviewer records any remaining uncertainty, the evidence location and who will monitor later notices. Another operator should be able to continue the case from those references without asking the employee to repeat sensitive information.
Reconcile the queue when the people or service changes
Check the reporting queue when HR changes its onboarding process, an administrator leaves, a new work state is added or payroll moves to another provider. Confirm that someone can retrieve earlier evidence and monitor outstanding results after the change. Portal access disappearing is an operational problem even when the underlying report was properly submitted.
Compare the event list with the relevant HR changes at a frequency that supports the actual reporting deadlines. Include events discovered late and explain duplicates or excluded records. Do not wait for a quarterly wage filing to discover that no one reported an employee who started weeks earlier. Maryland's FAQ treats new-hire reporting as a separate, earlier information stream from quarterly wage data.
Keep the register focused on decisions and outcomes. A useful review can identify the event being reported, why the destination and timing apply, what was sent, what evidence came back and what still needs action. That is enough to distinguish a functioning reporting process from a growing collection of completed onboarding checkboxes.
If reporting exceptions repeatedly consume time your team cannot support, use the register to describe the service you need. A free SelectSoftware Reviews advisor conversation can help compare payroll options, while your employer reporting owner retains the rule, receipt and correction decisions.
Continue with payroll reporting guides and resources:
About the author
Ben Scott writes and maintains payroll decision guides for founders and operators. His work focuses on execution realities and how decisions hold up under growth, complexity, and controls and documentation pressure. He works hands-on in HR and leave-management roles that intersect with payroll-adjacent workflows such as benefits coordination, cutovers, and compliance-driven process controls.
