Growth does not send a notice when it changes what your company owes the government. Federal regulatory law does that instead, and it does it at fixed, citable points, some tied to headcount, some to dollar amounts, and at least one tied to nothing more than where a single employee happens to be sitting when they log in for work.
Most growth-stage companies find these thresholds the hard way: a filing deadline missed, a deposit made a day late, an agency letter nobody recognized. The alternative is knowing where the thresholds sit before a company crosses them, and asking a more useful question than "who runs our payroll today." The better question is whether that person, team, or platform can actually see a threshold coming and act on it before it becomes a penalty.
Below are seven thresholds worth tracking, organized by the operating-model capability each one demands.
Key Thresholds at a Glance
The dollar and headcount figures below reflect thresholds published as of September 15, 2026. The Compliance Content team at Asure reviews them each quarter against the underlying agency source and updates this page when a figure changes; check the linked primary source directly if you are reading this well after that review cycle.
- 50 full-time employees, including full-time equivalent employees (threshold current as of September 15, 2026) triggers Applicable Large Employer status under the Affordable Care Act's (ACA) employer shared responsibility provisions. IRS.gov, "Determining if an Employer is an Applicable Large Employer"
- 50 or more employees for each working day during each of 20 or more calendar workweeks in the current or preceding calendar year (threshold current as of September 15, 2026) triggers Family and Medical Leave Act (FMLA) employer coverage company-wide; a separate 75-mile-radius test then determines which individual employees at a covered employer are eligible to take leave. 29 CFR 825.104, eCFR
- 100 or more employees triggers annual EEO-1 reporting for private employers; federal contractors meeting certain criteria must file starting at 50 or more employees (both thresholds current as of September 15, 2026). EEOC.gov, "EEO-1 Data Collection"
- $100,000 in accumulated federal employment tax liability (income tax withholding plus FICA) on any single day (threshold current as of September 15, 2026) triggers the next-day deposit rule, regardless of a company's normal deposit schedule. IRS.gov, Publication 15 (Circular E)
- $50,000 in lookback-period tax liability (threshold current as of September 15, 2026) is the line between a monthly and a semiweekly federal deposit schedule. IRS.gov, Publication 15 (Circular E)
- Personal liability with no headcount floor. Under IRC Section 6672, a "responsible person" who willfully fails to remit withheld income and FICA tax can be assessed the Trust Fund Recovery Penalty personally, for 100% of the unpaid amount. IRS.gov, "Trust Fund Recovery Penalty"
- One remote employee in a new state can create payroll tax nexus there. This is not a headcount threshold at all; it is a jurisdictional trigger that can arrive at 12 employees as easily as at 300.
Headcount thresholds do not all measure the same thing
Two of the thresholds above use the number 50, and it is tempting to treat them as the same milestone. They are not.
The ACA's Applicable Large Employer test is a full-time-equivalent calculation rather than a simple body count. Part-time hours are aggregated into FTEs, which means a company with 40 full-time staff and a rotating group of part-time workers can cross the 50-FTE line well before it has 50 people on a single org chart. IRS.gov walks through the calculation, and it is easy to run that math once and never rerun it as a part-time-heavy team grows.
FMLA coverage, by contrast, is a company-wide count with no full-time-equivalent conversion: 50 or more employees for each working day during each of 20 or more calendar workweeks in the current or preceding calendar year, per 29 CFR 825.104. A separate rule then determines which individual employees at a covered company can actually take FMLA leave: an employee is eligible only if they work at a location with 50 or more company employees within a 75-mile radius. A 90-employee company spread thin across four small offices is still a covered employer company-wide, but an employee at a 12-person satellite office may not be individually eligible to take leave, even though the company itself is on the hook for FMLA compliance everywhere. Coverage and eligibility are two different questions, and conflating them is an easy way to misjudge exposure.
EEO-1 reporting sits at a higher, simpler bar for most employers: 100 or more employees for private employers, per the U.S. Equal Employment Opportunity Commission (EEOC). Federal contractors face a lower bar: the EEOC also requires EEO-1 filing by covered federal contractors with 50 or more employees who meet certain contract-related criteria, so a mid-sized contractor can owe this filing well before it reaches the 100-employee private-employer line. By the time a growth-stage company reaches the 100-employee private-employer threshold, it has typically already crossed both the ACA and FMLA coverage lines, which means EEO-1 rarely arrives as a surprise on its own. It arrives as confirmation that the earlier thresholds should already have been on someone's radar.
The operating-model implication is straightforward: whoever or whatever runs payroll needs to be tracking FTE hours and location-based headcount continuously, rather than recalculating them once a year when a filing deadline forces the question. A 60-employee professional services firm running payroll through a spreadsheet and a part-time bookkeeper can cross the ACA's 50-FTE threshold without anyone recalculating full-time-equivalent hours until a 1095-C deadline is already close. Inside AsureCentral, payroll and HR data live in the same connected system, so headcount, hours worked, and location stay visible together as they change instead of getting reconciled after the fact.
Deposit timing precision the IRS expects, not suggests
Federal payroll tax deposits are not judged on whether the check eventually clears. They are judged against fixed dollar thresholds and specific calendar windows, and the penalties scale with how far a deposit misses the mark.
Under the federal employment tax deposit rules described in IRS Publication 15, any employer that accumulates $100,000 or more (a threshold current as of September 15, 2026) in federal income tax withholding and FICA liability on a single day must deposit that amount by the next business day, regardless of its normal deposit schedule. This rule, and the $50,000 lookback threshold below, govern Form 941 deposits specifically; FUTA (Form 940) runs on its own, separate quarterly threshold and is not part of this next-day rule. That $100,000 next-day rule can hit a company that has always been a routine monthly depositor, if a bonus run, a large payroll cycle, or a one-time payout pushes a single day's liability over the line.
Separately, the $50,000 lookback threshold (also current as of September 15, 2026) determines which deposit schedule a company is on in the first place: $50,000 or less in lookback-period liability means monthly deposits, and anything above that means semiweekly deposits, with far less room for error between a payroll run and the deposit deadline. A company that grows from monthly to semiweekly deposit status has, in effect, had its margin for manual error cut down, at exactly the moment its payroll volume is making manual tracking harder to sustain.
The capability this demands from a payroll operating model is not sophistication. It is precision: automatic recognition of which deposit schedule applies, and automatic initiation of the deposit itself, rather than a calendar reminder that assumes nothing has changed since the last quarter. AsureCentral is built to track lookback liability and apply the correct deposit schedule automatically, and Luna AI acts on routine work and escalates unresolved exceptions for human review, so a payroll administrator is working from active oversight rather than a static calendar reminder. Clients on AsureWorks skip that monitoring step entirely; Asure specialists own deposit-schedule tracking and initiation directly.
Jurisdictional complexity does not wait for a headcount trigger
Every threshold discussed so far is at least partly a function of size. Multi-state tax nexus is not. A single remote employee working from a new state can obligate a company to register, withhold, and file there, independent of whether that company has 12 employees or 1,200, though the details vary by state and by obligation. Nine states impose no wage income tax at all, so a hire there may create no withholding obligation in the first place; reciprocity agreements between some neighboring states can shift withholding to the employee's home state instead of the work state; and "convenience of the employer" rules in effect in New York and a handful of other states can keep the original state's withholding claim alive even after an employee has relocated, so two states can end up with a claim at once. Withholding registration, unemployment insurance registration, and corporate income tax nexus are also three separate questions with three different triggers rather than one single event, so a new hire can create some obligations right away and leave others contingent on facts that take longer to resolve.
This is the threshold most likely to catch a growth-stage company off guard precisely because it does not follow the logic of the other six. A company can watch its ACA, FMLA, and EEO-1 exposure approach for months as it hires. A single remote offer letter, accepted in a state the company has never operated in, can create a new jurisdictional obligation within days of being signed, once the applicable rules are worked through. A payroll process built around a fixed set of states, whether that process lives with an accountant, a bookkeeper, or a piece of software configured for a narrower footprint, is not built to absorb that trigger without a manual reconfiguration each time it happens. AsureCentral supports payroll tax registration, withholding, and filing across states as a company adds them, so a new-state hire is a configuration step inside the same platform rather than a separate project. For companies that would rather not run that configuration themselves, AsureWorks specialists handle the new-state registration and filing directly.
Personal liability has no headcount floor at all
The Trust Fund Recovery Penalty is different in kind from every threshold above it. It is not a compliance obligation that phases in with size. It is a standing exposure that exists the moment a person, at a company of any size, has control over which creditors get paid and willfully chooses not to remit withheld payroll taxes to the government. That word "willfully" is doing less work than it sounds like it should: under the IRS's own internal guidance (Internal Revenue Manual 5.7.3), willfulness for Trust Fund Recovery Penalty purposes means an intentional, deliberate, or reckless failure to remit, and, in the IRS's own language, "no evil intent or bad motive is required" for the penalty to apply.
Under IRC Section 6672, the IRS can assess a penalty equal to 100% of the unpaid withheld income and FICA tax against that "responsible person" individually. This is not a corporate liability that stops at the business entity; it attaches to the individual who had the authority and the willfulness. At a growth-stage company, that person is very often the owner, the controller, or whoever signs off on which bills get paid when cash is tight, which is exactly the situation in which payroll tax deposits are most tempting to delay.
The operating-model implication here is about accountability, not automation. Someone in the organization needs to be able to say, at any point, that payroll tax liabilities were remitted on schedule and that the decision authority over "which bills get paid" was never allowed to touch that obligation. On AsureWorks, that accountability sits with Asure specialists, who initiate and confirm the deposit directly rather than routing it through the client's own accounts-payable decisions. Companies running AsureCentral in-house keep that authority internally, but get a documented deposit record they can point to if a "responsible person" question ever comes up.
How to know your current model can absorb these triggers as they hit
None of the seven thresholds above announce themselves. They accumulate quietly through hiring, growth, remote work, and cash flow decisions, and the way most companies discover them is retroactively, through a penalty notice or an agency letter.
The useful test for a payroll operating model is not whether it handled last quarter's payroll correctly. It is whether it would surface an approaching threshold, an FTE count creeping toward 50, a lookback liability crossing $50,000, a new remote hire in an unfamiliar state, before that threshold is already in the rearview mirror. An accountant working from last year's numbers, a bookkeeper managing payroll alongside a dozen other responsibilities, and software configured once at setup and rarely revisited can all fail this test in the same way: none of them are structured to watch these lines continuously.
Asure offers two ways to close that gap without asking a growing company to choose between control and capability. On AsureCentral, payroll, HR, tax, benefits, and time data live in one connected system, so headcount, hours, and location stay visible in the same place a payroll run happens rather than getting reconciled separately after the fact. For companies that want the compliance work handled directly, AsureWorks puts Asure specialists behind payroll processing and tax filing execution, with the client remaining the employer of record throughout, no co-employment involved.
For a broader look at which function inside a growing company should actually own payroll, see Who handles payroll: HR or finance answers for growth-stage companies. For the fuller framework on choosing between accountant-led, software-led, and managed models as a company scales, see How to choose the right payroll and HR service model as your company grows.
The thresholds themselves are fixed and public. Whether a company finds out about them from a government notice or from its own payroll operating model is the part still worth deciding in advance.
