Almost everything a business tracks arrives on the calendar first. A license expires on a printed date. A return falls due at the end of a quarter. An inspection comes round each spring. You can look at any of them a year out and know exactly when they land. New hire reporting is the opposite kind of obligation: nothing about it is on next year's calendar, because it is created by a decision the business has not made yet. You hire someone, and a deadline exists that did not exist the previous afternoon.
The federal requirement itself is short. Under the personal responsibility and welfare reform legislation of 1996, now codified at 42 U.S.C. § 653a, every employer has to report basic details about each newly hired and rehired employee to a State Directory of New Hires, which passes them to the National Directory used to enforce child support orders and to detect improper benefit payments. Most summaries stop there, at “within 20 days,” and that is where the trouble starts — because the statute does not describe one deadline. It describes two quite different ones, and which of them applies to you depends on how you send your reports rather than on when you hired anybody.
Then there are the two details that decide whether an employer catches every report or quietly misses a handful a year. The first is what the clock actually runs from, which is not the date anybody would call the hire date. The second is the rehire rule, where the thing that makes a returning employee reportable all over again is not the fact that they came back but the length of the gap before they did — a measurement of a period in which nothing was happening at all, which no onboarding process has any reason to take.
Here is how the new hire reporting requirement works to track, what your state can change about it, and how to make sure that a routine Tuesday hire never turns into a report nobody made.
General information, not HR or legal advice — state timeframes and penalties vary and can be stricter than the federal position described here. Confirm what applies to you with your state directory and the official sources in section 11.
1. What is new hire reporting?
New hire reporting is the obligation on every employer to tell the state when it takes someone on. Federal law requires each state to run an automated State Directory of New Hires, and requires employers to furnish a short report on each newly hired employee to it: the person's name, address and social security number, the date they first performed services for pay, and the employer's own name, address and identification number. The state adds it to its directory and forwards it to the National Directory of New Hires, where it is matched against child support cases so that income withholding can begin promptly, and against benefit rolls so that payments to people who have returned to work can be stopped.
The word “employer” here is deliberately wide. It takes its meaning from the federal income tax withholding rules, and it expressly includes governmental entities and labor organizations, so public bodies, nonprofits and unions all report alongside private companies. A practical rule of thumb that reflects the same scope: if a person completes a Form W-4, they should be reported. There is no minimum headcount to escape it, no seasonal exemption, and no threshold to cross before the requirement starts — unlike almost every other employer filing, which is one of the reasons it is easy to overlook. It applies from the first employee.
Remindax helps you hold a reporting due date against each new hire and each rehire, in the state where that person works, and reminds you before it closes. It doesn't collect employee data, prepare or submit anything, or interface with any state directory — it tracks the deadline. Because that deadline lands on the same people already carrying employment records, workforce filings and onboarding paperwork, it belongs in the same register as the rest of them, which is what HR compliance tracking is for.
1.1 The date the deadline runs from is not the hire date
Read the reporting requirement closely and one of the required data elements is oddly specific. It is not the date of the offer, or the date the offer was accepted, or the date the contract says employment begins. It is the date services for remuneration were first performed by the employee — the first day the person actually did paid work for you. That is the fact the report describes, and in most states it is also the fact the clock runs from.
For a straightforward hire who signs on Monday and starts the following Monday, the distinction makes no difference. It makes a great deal of difference everywhere else:
- →A start date that moves takes the deadline with it. Someone accepts in March and starts in May because of a notice period, a visa, or a project that slipped. The record in the HR system may still show March. The reportable date — and therefore the deadline — is in May, and an employer working from the earlier date files on a person who has not begun, or states the wrong date for one who has.
- →The record that holds the right date usually isn't the one people check. Offer letters, contracts and applicant systems hold the agreed start. Payroll and timekeeping hold the day work actually began. When those two diverge, the second is the one that matters, and it is generally created later and by a different team.
- →A no-show is not a reportable hire. If somebody accepts and never appears, no services were ever performed for pay. What creates the obligation is work beginning, not paperwork being signed — which is why the reporting deadline can only be set once the start is a fact rather than a plan.
- →The state is the one where the employee works. Not where the company is registered, not where payroll is processed, and not where the person lives. For a distributed or multi-site employer that means the applicable directory — and therefore the applicable timeframe — is a property of the individual hire, unless the employer has registered to consolidate.
Timeframes, required data elements, and penalties are set by each state within the federal framework and change over time. Confirm what applies to your organization at the official sources in section 11. This is general information, not HR or legal advice.
It is worth being precise about what kind of thing this is, because it is unlike most items on an employer's compliance list. There is no certificate to keep current, no renewal to diary, and nothing that expires. There is an act — hiring — and a short period afterwards in which a report has to reach a particular state's directory. Nothing about it recurs on a schedule; it recurs on your hiring, which means an employer with a quiet year has almost no exposure and one that staffs up for a season has dozens of small deadlines inside a few weeks, all of them created by decisions the business made for entirely unrelated reasons.
2. How long do I have to report a new hire?
Federal law requires an employer to report a new hire within 20 days of the date of hire. That is an outer limit rather than a target: states may set shorter timeframes, and a number of them do.
An employer transmitting reports magnetically or electronically may instead report by two monthly transmissions, made not less than 12 nor more than 16 days apart. Same statute, entirely different shape of deadline.
A returning employee is newly hired for reporting purposes if they were separated from that employment for at least 60 consecutive days. Some states apply a shorter separation, and a few ask for every rehire.
To the State Directory of New Hires for the state where the employee works — unless you have registered with HHS as a multistate employer and designated a single state to receive all of them.
Federal law caps what a state may charge rather than imposing a fine itself: no more than $25 per failure, or $500 where state law finds a conspiracy between employer and employee not to report.
The second line of that box is the one almost nobody reads, and it is the most consequential thing on this page. Federal law does not give employers a single deadline with a bit of flexibility around it. It gives them a choice between two obligations that behave in completely different ways, and the choice is made by an operational decision about transmission format rather than by anything a compliance calendar would recognize as a decision at all.
On the first route, the deadline belongs to the individual. Each person you hire brings a date twenty days after they start, and that date is theirs; it has nothing to do with anyone else's, it does not coincide with anything, and the only way to be sure it is met is to know it exists. Hire eleven people across a quarter and you have eleven separate obligations falling due on eleven unrelated days.
On the second route, the deadline belongs to the calendar. There are two transmission dates in every month, a fortnight or so apart, and whoever starts between them is simply included in the next one. Eleven hires across a quarter produce no individual deadlines whatsoever; they produce six transmissions that would have happened regardless. What was a series of personal clocks becomes a fixed cadence, and the failure mode changes with it — you no longer risk missing one person's date, you risk a transmission not going out, or a person not being on it.
Most employers report through a payroll provider or a state web portal, which means they are on the electronic route whether or not anyone ever framed it that way — and they are therefore running a twice-monthly cadence while thinking about a twenty-day one. That mismatch is usually harmless and occasionally expensive. An employer who believes it has twenty days per person will treat a hire on the second of the month as comfortable and one on the twenty-eighth as urgent, when on a batch cadence the opposite may be true. Knowing which structure your reporting actually runs on is a five-minute question with a permanent answer, and it changes what you need to watch.
Two cautions before anyone redesigns a process around the electronic route. It is available to employers who transmit magnetically or electronically, and the practical detail of how a given state accepts and schedules those transmissions is a matter for that state's program — the federal provision sets the framework the states implement, and their published requirements are what govern the reports you actually send. And the twenty-day figure is a ceiling for state law, not a floor: a state is free to require reporting sooner, so an employer operating across several of them may have a twenty-day answer in one place and a shorter one next door. Section 11 links the official list of each state's contacts and program requirements, which is where the answer for any particular state actually lives.
This is also the point at which the new hire reporting requirement stops resembling the annual employer filings that sit beside it. EEO-1 reporting, ACA employer reporting and the OSHA 300A annual summary all describe a year that has finished, on a date the year itself determined. This one describes a single person, on a date that person's own start created, and it happens as many times a year as you hire.
3. Why tracking new hire reporting matters
A short report about a person you have just hired, due within a few weeks, sounds like one of the least demanding obligations an employer carries — and per report it is. Four properties make the set of them hard to hold:
The deadline has two possible shapes
A per-person clock of 20 days, or a twice-monthly transmission cadence 12 to 16 days apart. Which one you are on is decided by how you send reports, not by law you can look up.
It starts on a day nobody records as the hire date
The first day of paid work, which lives in payroll rather than in the offer letter — so a start that moves silently moves the deadline with it.
The rehire trigger is a gap, not an event
Sixty consecutive days of separation makes a returning employee newly hired again — a fact about a period when nothing happened, which nothing in onboarding measures.
Nothing tells you a report is missing
There is no acknowledgment you would notice the absence of, and the person concerned is at work either way. A gap is discovered, if at all, long afterwards.
The first two points are worth putting side by side, because between them they explain why an employer can have a functioning onboarding process and still not know when its reports are due. One of them determines the shape of the deadline and the other determines when it starts, and neither is written down anywhere in the hiring paperwork. An organization that has never asked either question is not being careless; it is doing what the summary told it to do, which is to remember twenty days, and the summary omitted both.
The third is the one that costs employers the most reports, and the reason is structural rather than sloppy. Consider what an onboarding process is designed to detect. It notices a person arriving. It generates a contract, a payroll record, an equipment request, a W-4. Every one of those triggers fires on the same event: someone new is here. The rehire rule fires on something else entirely — on the measurement of an absence. Whether a returning employee has to be reported again depends on how long they were gone, and no step in a normal joining process has any reason to establish that. The information exists, usually in a leaver record filed months earlier, but nothing in the flow reaches for it.
Federal law treats someone as newly hired if they were separated from that employer for at least 60 consecutive days — and the practical trap is that sixty days is long enough for the return to feel like a resumption rather than a hire. A seasonal worker back for the summer, a teacher returning in the autumn, a retiree coming back for a project, someone who left in March and reappeared in June: internally, none of them is treated as new. They keep their old employee number, they skip most of onboarding, and nobody restarts the paperwork. Externally, all of them are newly hired employees who have to be reported again. Some states apply a shorter separation than sixty days, or ask for every rehire regardless of the gap, so the state's own rule is the one to work to.
It is worth separating this from the more familiar version of a per-person deadline in onboarding. Where a role requires a credential — the way food handler certification gives each new worker a set number of days to get certified — the clock is imposed, identical for everybody, and starts on an event the whole business can see. New hire reporting differs on both counts. The employer chooses, through its transmission method, which of two clock structures it is subject to; and the event that starts it in the rehire case is a length of time rather than an arrival. That is why a team can run a genuinely disciplined onboarding checklist and still be missing reports: the checklist is triggered by people showing up, and one of these obligations is triggered by how long they were away.
The fourth property is what allows the first three to go unnoticed for years. Nothing about a missing new hire report is visible from inside the business. The employee is working, being paid, and appearing in every system they should appear in. No filing receipt fails to arrive, because for a single unreported person nothing was ever expected. The state's directory simply has no record of that employment, which matters enormously if the person has a child support order attached to their name and not at all in any way the employer will ever see. That silence is the ordinary condition of this obligation, and it is why an employer's own record of what was reported and when is the only thing that ever answers the question.
4. Who needs to track new hire reporting deadlines
Formally the answer is every employer, from the first person hired. In practice the risk concentrates where hiring is frequent, distributed, or handled by people whose main job is something else:
HR & payroll teams
Where the obligation actually lands, and where it competes with the visible parts of onboarding. The reporting deadline is the only item on the joining checklist that a person can complete their first month without anyone noticing was skipped.
Learn More
Seasonal & returning-workforce employers
Agriculture, hospitality, retail, education, tourism, events. The whole workforce model is people leaving and coming back, which is precisely the pattern the sixty-day rehire rule turns into a fresh reporting obligation every cycle.
Staffing & temp agencies
Placing dozens of people a month, often the same people repeatedly, across assignments in different states — the highest volume of reportable events per unit of administrative attention of any employer type.
Multistate employers
Facing either a different directory and timeframe per employee, or a single designated state — a genuine simplification, but only for employers who registered for it and who then report electronically on the required cadence.
Learn More
Franchises & multi-site operators
Hiring decided at a location and reported by an entity, with no single person seeing both. A store manager who takes someone on has created a legal deadline for a back office that may not learn of it for a fortnight.
Small employers & office admins
No headcount threshold applies, so a business hiring its second employee owes exactly what a national chain owes — handled by whoever also does payroll, invoicing and the filing cabinet, and hiring rarely enough that the process is rebuilt from memory each time.
Learn MoreThe multistate case deserves a note, because it is the one place where this obligation offers relief that most others do not. An employer with employees in two or more states that transmits its reports electronically may designate a single state to receive them all, instead of sending each one to the state where that employee works. The relief is real and the administrative saving is substantial — but it is not a default and it is not automatic. It requires registering with the Department of Health and Human Services and notifying it in writing which state you have designated, and it carries the twice-monthly transmission cadence with it. Employers who assume they can simply start sending everything to one state have not reduced anything; they have added a set of reports going to the wrong directory. For the wider view of every recurring obligation an employer carries, see compliance tracking software — tracking and reminders, not a GRC suite.
5. What happens when a new hire report is missed
The honest answer, in the short term, is usually nothing at all — and that is the whole problem. A missed new hire report produces no rejected filing, no notice, no lapse in anyone's status, and no interruption to the employee, who is working normally and being paid normally throughout. The state simply does not know about that employment. Nothing in the business changes to reflect it.
The financial exposure is deliberately small, and deliberately per person. Federal law does not impose a fine directly; it limits what a state may impose if that state chooses to penalize at all. The cap is $25 for each failure to report, rising to $500 where state law finds that the employer and employee conspired not to supply the report. Twenty-five dollars is not a number designed to deter a large company, and it is not meant to be — the structure is meant to make compliance cheaper than the alternative rather than to punish. But the unit matters. It is per unreported employee, not per year and not per lapse, so the number that ends up on a notice is a function of how many people went unreported and for how long the practice continued. An employer that has been missing rehires for three seasons is not looking at one penalty; it is looking at one for each of them, in a state that may also have non-monetary remedies of its own available.
How it actually surfaces. Because nothing announces it, gaps come to light through routes that have nothing to do with the reporting itself. A state child support agency reconciles its caseload against wage records and finds an employment it was never told about. An unemployment insurance audit compares reported hires against quarterly wage filings. An acquiring company's due diligence asks for the last three years of these records and receives an explanation instead of a file. A new HR manager, reading the requirement properly for the first time, works out that returning seasonal staff were never reported and has to decide what to do about the last four cycles. In each of those, the trigger is somebody else looking, and the employer's position is determined entirely by whether it can show what was reported and when.
What the reporting is actually for. It is worth holding on to, because it explains why the requirement is drawn so broadly and why states pursue it despite the modest amounts involved. The directories exist so that income withholding for child support can begin as soon as a parent starts a job rather than months later, and so that unemployment and workers' compensation payments to people who have returned to work can be stopped promptly. A report that arrives late, or not at all, delays money reaching a child or allows a benefit payment to continue after it should have ended. The penalty is small; the thing the penalty is attached to is not.
This is a different failure pattern from the annual employer filings that share the same desk. A missed EEO-1 report or a missed ACA filing is a discrete, dated, unmistakable omission — there is one thing you were supposed to do, one day it was supposed to happen, and either it did or it did not. A new hire reporting failure has no such edge. It is a scattering of individually trivial omissions, none of which is memorable, distributed across a year in proportion to how much hiring you did. Nobody ever decides to skip one. They simply accumulate in the places where a busy month met a process that had no way to notice.
6. How Remindax keeps every hire reported on time
Remindax treats each hire as a dated item with a status, so that the question “is everyone reported?” has an answer that does not depend on anyone's recollection of a busy month.
A reporting due date per hire
One item per new or rehired employee, dated from the day they first worked and carrying the timeframe that applies in the state where they work — so the deadline exists somewhere other than in one person's head.
Reminders before each one closes
Staged alerts by Email, SMS and WhatsApp, to HR and to payroll rather than to a single owner, timed well ahead of the date rather than on it.
A rehire prompt, on the gap
A recurring item for returning staff, so that the question the onboarding process never asks — how long were they gone, and does that make this a fresh obligation — gets asked by something other than memory.
Whichever cadence you are on
Per-person due dates for employers on the 20-day route, or a recurring twice-monthly transmission item for electronic filers — held per entity and per state, in one view.
A record of what was reported, and when
Dates and confirmations kept per hire — the file that answers an audit, a due diligence request, or a new manager's question about last season, without reconstructing anything.
Entities and states side by side
Reporting deadlines across locations, entities and states in one register, with the designated-state arrangement reflected where a multistate employer has registered for one.
Remindax tracks dates and status. It is not an HRIS, not a payroll system, not an applicant tracking or onboarding platform, and not a reporting service — it doesn't collect employee data, hold social security numbers, prepare or submit anything, or connect to any state directory. What it does is make sure a deadline exists for every person who starts, that rehires get questioned rather than assumed, and that you can say afterwards which reports were made and when. For the wider picture see HR compliance tracking or office admin tracking — tracking and reminders, not workforce administration.
7. Why spreadsheets fail for new hire reporting
The characteristic new hire reporting spreadsheet is a tab on the joiners list with a column headed reported? and a column of yeses. It fails in four specific ways, and they are worth naming individually because each one produces a different kind of gap.
It fails first because it has no future. A spreadsheet records what was done; it cannot raise its hand about what has not been done yet. The only way a pending report gets attention is if somebody opens the file and reads down it, and the months in which nobody opens it are precisely the months with the most rows — a spreadsheet's attention is lowest exactly when the hiring volume is highest. Every other item on this site is at least anchored to a date somebody has diarized. A per-hire deadline is invisible until it is late.
It fails second on the date it is built from. Joiner lists are populated when someone is hired, from the record that exists at that moment, which is the offer or the contract. The reportable date is the first day of paid work, and it frequently is not the same day. The spreadsheet therefore computes a deadline from a plan while the obligation runs from an outcome, and the two agree most of the time — which is worse than never agreeing, because it means the error surfaces only on the unusual hire, and only after the fact.
It fails third, and most reliably, on rehires. A joiners list is a list of arrivals; a returning employee usually does not generate one, because they already exist in every system and there is nothing to create. The row that would have carried their reporting deadline is never added, and the absence of a row is not something anyone reviews. Worse, the sixty-day question requires data from a different file entirely — the leaver record — and nothing joins them. This is where the missed reports actually live, and it is not a discipline problem: the structure of the file makes the case invisible.
And it fails fourth by inviting the wrong contents. Because the underlying report contains a name, an address and a social security number, a tracking spreadsheet tends to grow those columns — until a file created to remember deadlines is holding identifying data for every person hired in the last three years, in a shared drive, with whatever access controls that drive happens to have. Nothing in the tracking task requires any of it. The tracker needs to know that a report is due for a particular hire on a particular date and whether it has been made; the data itself belongs in payroll, and in the state's submission, and nowhere else.
An automated register turns each hire into a dated item that surfaces on its own, computes from the day work began, prompts on returning staff instead of waiting to be told about them, and keeps the record of what was sent without holding the contents of it — which is the only version of this that survives a seasonal intake, more than one state, or more than one person doing the hiring.
- ✗Nothing surfaces a pending report before its date passes
- ✗Built from the contract date, not the first day of paid work
- ✗Returning employees never generate a row at all
- ✗No way to hold different state timeframes side by side
- ✗Tempts a team to store social security numbers in a shared file
- ✓Each hire becomes a dated item that raises itself in advance
- ✓Dated from the day services were first performed for pay
- ✓A standing prompt on rehires and the separation gap behind them
- ✓Per-state timeframes and per-entity views held together
- ✓Dates and confirmations only — no employee data in the tracker
8. Key takeaways
- ✓Every employer, from its first employee, must report each newly hired and rehired employee to a State Directory of New Hires — there is no headcount threshold and no seasonal exemption, and the rule of thumb is that anyone completing a W-4 is reportable.
- ✓Federal law describes two deadline structures, not one: report a new hire within 20 days of hire, or — for employers transmitting magnetically or electronically — by two monthly transmissions made 12 to 16 days apart. Which applies to you follows from how you report.
- ✓The reportable date is the day the employee first performed services for pay, not the offer or contract date — so a start that moves takes the deadline with it, and a no-show creates no obligation at all.
- ✓Rehire reporting turns on the length of the absence: an employee separated for at least 60 consecutive days is newly hired again. It is the most-missed case, because nothing in an onboarding process measures how long somebody was gone.
- ✓Twenty days is a federal ceiling that states may shorten, reports go to the state where the employee works, and multistate employers can designate a single state only after registering with HHS in writing.
- ✓Penalties are capped at $25 per unreported employee, or $500 for a conspiracy not to report — small individually, assessed per person, and attached to an obligation nothing in the business will ever tell you that you missed.
Never let a hire go unreported
Track every new hire's reporting deadline — and every rehire's — automatically. Remindax holds the dates, prompts on returning staff, keeps the record of what was reported and when, and reminds the right people while there is still time.
GDPR-ready · AWS secure cloud · Encrypted storage · Setup in under 5 minutes
9. Frequently Asked Questions
Federal law sets an outer limit of 20 days from the date of hire, and states may require sooner - so your own state's timeframe is the one to work to. Employers who transmit reports magnetically or electronically may instead report by two monthly transmissions made not less than 12 nor more than 16 days apart.
The date the employee first performed services for pay - the first day of actual paid work, not the offer date or the start date written in the contract. If a start slips, the reportable date and the deadline move with it, and someone who never turns up creates no reporting obligation at all.
Yes. An employee who was separated from your employment for at least 60 consecutive days is treated as newly hired again and must be reported afresh. Some states apply a shorter separation, and a few require every rehire to be reported regardless of the gap.
Every employer, including governmental entities and labor organizations, from its first employee - there is no headcount threshold and no seasonal exemption. A common rule of thumb is that anyone who completes a Form W-4 should be reported.
The State Directory of New Hires for the state where the employee works - not where your company is registered, where payroll is processed, or where the person lives. A registered multistate employer may instead send all of its reports to one designated state.
An employer with employees in two or more states that transmits reports electronically may designate a single state to receive all of them. It is not automatic: you must register with the U.S. Department of Health and Human Services and notify it in writing which state you have designated.
Federal law caps what a state may charge rather than imposing a fine itself: no more than $25 for each failure to report, or up to $500 where state law finds the employer and employee conspired not to report. States may also have non-monetary remedies of their own.
It feeds the National Directory of New Hires, which is matched against child support cases so income withholding can begin as soon as a parent starts work, and against benefit rolls so unemployment and workers' compensation payments to people who have returned to work can be stopped.
No. Remindax tracks each hire's reporting deadline and reminds you before it closes. Collecting the information and submitting it to your state directory are handled by you or your payroll provider - Remindax holds no employee data and connects to no state system.
Yes - a reporting due date per hire and per rehire, across your entities and the states your people work in, each with its own reminders by Email, SMS and WhatsApp, plus a standing prompt so returning staff get questioned rather than assumed.
Timeframes, required data, and penalties are set by each state within the federal framework and change over time. Remindax tracks the deadlines and reminds you; it doesn't collect employee data, prepare or submit reports, or connect to any state directory. Confirm current requirements with your state directory and the official sources below; this is general information, not HR or legal advice.
11. Sources & references
This page summarizes public requirements and isn't HR or legal advice. State timeframes vary and can be shorter than 20 days, and states set their own penalties within the federal caps — confirm what applies to you with your state directory and the official sources below.
- •Office of Child Support Services (ACF/HHS) — New Hire Reporting — the federal requirement, who must report, the 20-day timeframe, and what the National Directory of New Hires is used for.
- •OCSS — New Hire Reporting: Answers to Employer Questions — the W-4 rule of thumb, rehires, state timeframes, and the reporting obligations of multistate employers.
- •OCSS — State New Hire Reporting Contacts and Program Requirements — where to find your own state's deadline, required data elements, penalties, and submission methods.
- •OCSS — Multistate Employer Registration Form & Instructions — how to designate a single state, and the twice-monthly transmission cadence that comes with it.
- •42 U.S.C. § 653a — State Directory of New Hires — the statute itself: the 20-day rule and the two-transmission alternative, the 60-day definition of a newly hired employee, and the $25 and $500 penalty caps.
- •OCSS policy guidance — Multistate employer requirements under section 453A — the designation mechanism, the written notice to the Secretary, and the electronic transmission requirement behind it.