The first IRS notice most founders receive is a small one. A $150 penalty for a late federal deposit, three weeks after a payroll the founder doesn’t remember running differently than any other. The notice is the first signal that the company has crossed into the “semi-weekly deposit schedule” — and the founder didn’t know what that meant until the penalty arrived.
Payroll taxes are a category where modern payroll providers (Rippling, Gusto) do most of the work correctly. The remaining work — the part founders need to understand — is configuration, classification, and the handful of decisions the provider can’t make for you. Get those right and payroll taxes are a non-event. Get them wrong and the penalties compound silently for months before anyone notices.
This post is the operator’s overview of what you actually owe, what your payroll provider handles, and what you still need to watch.
What you actually owe (employer side)
Five buckets of payroll tax that the company pays as the employer. These are on top of employee wages and are not deducted from the employee’s paycheck.
Social Security (employer portion). 6.2% of wages up to the Social Security wage base ($168,600 for 2024; $176,100 for 2025; the 2026 base will be announced in late 2025). Matched by the employee 6.2%.
Medicare (employer portion). 1.45% of wages with no wage base. Matched by the employee 1.45%. (Note: there’s an additional 0.9% Medicare surtax that employees owe on wages over $200K, but the employer doesn’t match this portion.)
Federal Unemployment Tax (FUTA). 6.0% of the first $7,000 of wages per employee per year. Reduced by a credit of up to 5.4% for timely state unemployment payments, bringing the effective FUTA rate to 0.6% in most states ($42 per employee per year). Filed annually on Form 940.
State Unemployment Tax (SUTA). Rates vary by state and by company. New-employer rates typically range 1.0%-4.0% on a state-specific wage base. After 3 years of operating history, the state assigns an experience-rated rate based on the company’s unemployment claims history. SUTA is filed quarterly with each state.
State and local payroll taxes. Some states (California’s ETT, NJ’s various funds) levy small employer taxes alongside SUTA. Some cities (NYC, San Francisco, Seattle, others) have local payroll taxes that fall on the employer. Modern payroll providers identify and collect these automatically once you’re set up in the state.
For a typical Series A SaaS startup with 30 employees averaging $150K salary, the all-in employer payroll tax burden is roughly 8-10% of gross payroll — which on $4.5M in gross wages is $360K-450K per year. This is real money and it should be in your financial model as a clearly broken-out line.
What you withhold (employee side)
These come out of the employee’s paycheck and you remit them to the relevant agency. The company is the legal custodian — like 401(k) deferrals, employee withholdings are not company funds, and late deposits trigger trust-fund-recovery exposure (more on that below).
- Federal income tax. Per the employee’s Form W-4. Withheld at progressive rates.
- Social Security (employee portion). 6.2% up to the wage base.
- Medicare (employee portion). 1.45% plus 0.9% surtax on wages over $200K.
- State income tax. Where applicable. 41 states have state income tax.
- Local income tax. Where applicable. NYC, Philadelphia, several Ohio cities, Pittsburgh, others. Pennsylvania has the most complex local tax structure in the country — see multi-state employment compliance.
- State disability and paid family leave. Where applicable. California, New Jersey, New York, Hawaii, Rhode Island, and a growing number of paid-family-leave states.
- 401(k) and other voluntary deferrals. Per the employee’s election.
The federal deposit schedule that will trip you up
This is the part founders almost always miss the first time. The IRS doesn’t accept federal tax deposits whenever you happen to remit. There’s a schedule, the schedule is determined by your payroll size, and the schedule can change without notice.
The two schedules. Most employers are on one of two:
- Monthly depositors. Federal income tax + FICA (employer + employee) deposits are due by the 15th of the following month. Used by employers with a “lookback period” total of $50,000 or less.
- Semi-weekly depositors. Deposits are due within 3 banking days of payroll. Wednesday/Thursday/Friday payrolls deposit by the following Wednesday; Saturday/Sunday/Monday/Tuesday payrolls deposit by the following Friday. Used by employers with a lookback period total over $50,000.
The lookback period. The IRS looks at your aggregate Form 941 reported tax for the four-quarter period ending June 30 of the previous year to determine your deposit schedule for the current year. So your 2026 deposit schedule was set based on your taxes for the four quarters ending June 30, 2025. The IRS sends a notice if your schedule changes; the notice arrives in the fall for the following year.
The trip wire. A growing startup will cross from monthly to semi-weekly somewhere in Year 2 or Year 3, typically around the time the team grows past 20-25 employees with reasonable salaries. The IRS notice arrives. The founder reads it. The founder forwards it to the payroll provider. The payroll provider was supposed to update the schedule, but didn’t. Three months later, the deposits are late, the penalties have accrued, and the founder is opening notices in disbelief.
The mitigation. Confirm with your payroll provider — Rippling or Gusto — that they have your current deposit schedule loaded and that it matches the most recent IRS notice. This is a 10-minute check that’s worth doing every year in October/November when the next year’s schedule is announced.
The $100,000 next-day deposit rule. Separately, if your accumulated federal tax liability hits $100,000 on any day, you must deposit by the next banking day, regardless of your normal schedule. This catches startups that run a large bonus payroll, an equity-vesting payroll, or a leadership comp event without realizing the threshold has been hit. Payroll providers usually catch this if the payroll is run through them; manual payrolls or off-cycle wire payments may not.
FUTA and SUTA — the unemployment world
Unemployment insurance is administered by states with some federal oversight. The employer pays both federal (FUTA) and state (SUTA) unemployment taxes; the employee pays nothing.
FUTA mechanics. 6.0% on the first $7,000 of wages per employee per year. The 5.4% credit for timely SUTA payments reduces the effective rate to 0.6% — $42 per employee per year. Filed annually on Form 940, due January 31. Deposits are due quarterly when the accumulated tax liability exceeds $500.
SUTA mechanics. Varies wildly by state. Wage bases range from $7,000 (a few states) to $72,800 (Washington) or higher. Rates vary by industry, by company history, and by state economic conditions. New employers receive a “new-employer rate” that applies for the first 3 years; after that, the state calculates an “experience rate” based on the company’s unemployment claims history. Quarterly filings are required in every state where you have employees.
The credit reduction states. Most years, a handful of states have outstanding federal unemployment loan balances. The states that haven’t repaid get hit with a “credit reduction” — meaning employers in those states pay a higher effective FUTA rate. California, New York, Virgin Islands have been credit-reduction states in recent years. The reduction is announced annually in November; if you have employees in a credit-reduction state, your annual FUTA bill is higher than the standard $42/employee.
Multi-state SUTA — the SUTA dumping rule. When an employee moves from one state to another mid-year, the wage base in the new state generally resets — meaning the company pays SUTA on the new state’s wage base from scratch, even though the employee’s annual wages may have already exceeded that base in the original state. This is called the “SUTA cliff” and it’s an unavoidable cost of multi-state operations.
The trust fund recovery penalty
This is the only personal-liability exposure most founders carry from payroll taxes. The Internal Revenue Code Section 6672 imposes a “trust fund recovery penalty” on individuals who are responsible for collecting and remitting employee withholdings — and who willfully fail to do so.
The trust funds are: federal income tax withheld from employees, employee portion of Social Security, and employee portion of Medicare. These are legally not the company’s funds — they’re held in trust for remittance to the IRS. If a company fails to remit them, the IRS can assess the 100% trust fund recovery penalty personally against any “responsible person” — typically the CEO, CFO, controller, or anyone with check-signing authority.
This is rare in practice because modern payroll providers handle the withholding and remittance automatically. The risk pattern: a company in financial distress directs the payroll provider to delay remittance to preserve cash. The provider complies. The IRS eventually catches up. The founder owes the underlying tax personally, even after a company bankruptcy that wipes out everything else.
We mention this because founders should know it exists. Don’t ever, under any pressure, defer the deposit of trust funds. The cost is too high.
State income tax withholding — the multi-state cascade
Once you have an employee in any of the 41 states with income tax, you have a withholding registration to complete, a state-specific filing cadence, and quarterly returns to file.
Registration. Triggered by the first dollar of in-state wages. Some states have a brief grace period for new employers; most do not.
Withholding rates. Per the employee’s state-specific withholding form (the state equivalent of the W-4). The employee fills these out at onboarding through the HRIS.
Filing cadence. Varies by state. Most states require monthly or quarterly deposits plus quarterly returns. Larger employers in some states move to semi-monthly deposits — a separate threshold from the federal one.
Local income tax. NYC, Philadelphia, several Ohio cities, Pittsburgh, and the Pennsylvania local-EIT system (where every Pennsylvania resident owes Earned Income Tax to their municipality of residence). Pennsylvania is uniquely complex; we’ve seen multiple startups discover the local-EIT obligation only after they’ve had Pennsylvania residents on staff for a year.
The full multi-state cascade is covered in multi-state employment compliance — the payroll tax piece is one part of a broader compliance picture.
What a good payroll provider does for you
Rippling and Gusto handle the operational mechanics of payroll tax with high reliability:
- Calculate federal and state withholdings per the employee’s W-4 / state-specific forms
- Calculate employer FICA, FUTA, SUTA contributions
- Deposit federal taxes on the correct schedule (monthly or semi-weekly)
- Deposit state taxes on each state’s schedule
- File Form 941 quarterly (federal employment tax return)
- File Form 940 annually (federal unemployment)
- File state quarterly returns in every state where you have employees
- Issue W-2s and 1099s at year-end
- Handle ACA reporting (Form 1095-C) for Applicable Large Employers
- Process IRS and state notices (response, reconciliation, follow-up)
The key word is “operational.” Providers execute against the configuration you’ve set up. They don’t validate that the configuration is correct.
What you still need to watch
Five things the provider cannot do for you.
Confirm your deposit schedule annually. When the IRS sends the November notice for the upcoming year, confirm with your provider that the schedule matches. If you’ve grown into the semi-weekly schedule, make sure it’s loaded.
Validate exempt/non-exempt classification. Misclassifying an employee as exempt when they should be non-exempt creates back-wage liability under the FLSA — which the payroll provider can’t catch because they classify employees the way you tell them to.
Catch state moves. When an employee moves to a new state, the company must tell the payroll provider. The provider won’t know unless you do. We’ve seen 6-month delays between an employee’s move and the provider’s awareness, with retroactive registration and withholding cleanup the consequence.
Reconcile quarterly. Each quarter, reconcile the payroll provider’s reported wages and taxes to your general ledger. Material discrepancies are usually configuration errors that compound over the year. A 30-minute reconciliation at quarter-end catches problems that would otherwise surface in your year-end audit.
Track new-state registrations to completion. Payroll providers initiate state registrations, but the states themselves drive the timing. Some states issue an employer ID within days; some take 6-8 weeks. Until you have the ID, deposits and filings sit in a holding pattern. Track these to completion — your provider has a registration status dashboard but somebody needs to actually look at it.
When you’ll get a notice (and how to respond)
You’ll get notices. Even with a clean stack, some small percentage of filings produces a notice — usually a mismatch between what the agency expected and what was filed, or an updated rate that wasn’t loaded in time.
The right response process:
- Open every notice within 5 business days. Don’t accumulate them.
- Forward to your payroll provider with the original notice attached. Rippling and Gusto have notice intake processes that handle the response.
- Set a calendar reminder to follow up 30 days later. Confirm resolution.
- Track all notices in a single file so you can see patterns. Three notices from the same state in a year means something is wrong in the configuration.
The fail mode: a notice gets opened, forwarded vaguely, and forgotten. The state escalates. By the time you re-engage, the original $200 penalty has compounded into a $2,000 mess plus an escalation contact at the state.
When to bring in operator support
You probably don’t need outside help if you have a clean Rippling or Gusto setup, employees in 2-3 states, and no recent notices.
You likely want operator input if:
- You’ve received multiple notices in the last 12 months and don’t know if they indicate a real configuration problem
- You’re scaling into your 5th-10th state and want to make sure the registration cascade is being driven correctly
- You’re preparing for an audit and want payroll tax compliance documented and verified before fieldwork
- You’re inheriting a payroll setup from a prior administrator and need to validate that nothing’s been missed
- You’ve had a SUTA audit, withholding mismatch, or unemployment claim and need help responding
Pegacorn Group works with venture-backed Series A and B startups on the financial infrastructure that keeps payroll, accounting, and compliance aligned. If your payroll tax stack feels like it’s running by inertia and you want a second look, let’s talk.
This post pairs with: How to administer payroll and 401(k) plans at a startup, Multi-state employment compliance, The Series A/B benefits stack, and Equity compensation 101.