Across growth-stage payroll engagements, Asure has found that FUTA miscalculations almost never stem from applying the wrong rate. They stem from losing track of where each employee sits relative to the $7,000 federal wage base across pay periods. Fix that structural problem, and Form 940 accuracy follows.
The FUTA Rate Is the Easy Part
Start with how FUTA tax is calculated, because the arithmetic takes about ten seconds. Under IRS Publication 15 (2026 edition) (https://www.irs.gov/pub/irs-pdf/p15.pdf), the FUTA tax rate is 6.0%, and it applies to the first $7,000 you pay each employee in wages during the year. Employers who pay their state unemployment taxes in full and on time can take a credit of up to 5.4%, which brings the effective rate down to 0.6%.
So how much FUTA tax do you pay? At the full credit, the math caps out at $42 per employee per year. That is 0.6% of $7,000. Without the credit, the ceiling is $420 per employee. Small numbers. Simple percentages. Which is exactly why growth-stage teams trust the calculation more than they should.
Here’s where it breaks down. The $7,000 is a per-employee, per-year wage base, not a company-wide figure. Every employee crosses it at a different point in the calendar depending on pay level, hire date, and hours. The moment an employee’s cumulative wages pass $7,000, FUTA stops accruing on that person for the rest of the year. The calculation you ran in January is structurally different from the one you should be running in June, and different again in October.
In our work with growth-stage payroll teams, we consistently see the same miscalculation. The rate is right. The taxable wage pool is wrong. A team applies 0.6% uniformly to every payroll run all year, never resetting the per-employee clock, and ends up in one of two failure modes:
- Over-remit by continuing to apply FUTA to salaried employees whose wages exhausted the $7,000 base back in February.
- Under-remit by assuming everyone exhausted the base early, when part-time and mid-year hires are still accruing taxable wages in Q3.
A federal unemployment tax calculator will not catch either error. Calculators answer a single-period question, wages in, tax out, as if FUTA were one-step arithmetic. The IRS publishes the rules with precision but offers no view of where teams actually go wrong. The gap between those two resources is where growth-stage companies get hurt, because a proper FUTA tax calculation analysis starts with each employee’s cumulative position against the wage base, not with the rate.
This matters most at growth-stage companies with real payroll complexity but no dedicated tax specialist, where whoever runs payroll handles taxes alongside everything else. That person knows what FUTA is. What nobody has shown them is that the calculation logic changes mid-year, employee by employee, on every subsequent run. The rate is static. The taxable wage pool is a moving target.
Get that distinction wrong and the consequences arrive months later, as a reconciliation gap at filing time or an agency notice that turns into a fire drill. Get it right and everything downstream, the quarterly deposits, the Schedule A math, the Form 940 itself, becomes routine. The rest of this piece walks through the four places the wage-base problem shows up and the operational discipline that fixes it.
Per-Employee Tracking Is the Discipline FUTA Demands
The per-pay-period formula is simple to state in plain language. For each employee, each pay period, FUTA applies to the wages paid in that period, capped at whatever remains of that employee’s $7,000 annual base. Multiply that capped amount by the net rate. Once cumulative wages cross $7,000, the remaining balance is zero, and FUTA stops for that employee until January.
Watch how differently that plays out across three employees on the same payroll.
The $50,000 salaried employee. Paid semimonthly, this person earns roughly $2,083 per pay period. By the fourth check, cumulative wages pass $7,000, and only part of that fourth period is FUTA-taxable. The base exhausts before the end of February, deep inside Q1. Every payroll run from March through December should add zero FUTA for this employee. If your system keeps accruing, you are over-remitting on every run, 20 or more times in a year.
The $20,000 hourly employee. With fluctuating hours, this person may not cross $7,000 until the third quarter. FUTA-taxable wages show up in Q1, Q2, and part of Q3, then stop. The liability arrives in a different quarter than the salaried employee’s, which matters enormously once you see how deposit timing works.
The part-time employee earning under $7,000. This person never exhausts the base. Every dollar of wages is FUTA-taxable all year long. Teams that assume “everyone is done by summer” systematically under-remit on their part-time workforce.
Same company. Same rate. Three different exhaustion timelines. Now multiply by 40 or 80 employees with raises, terminations, mid-year hires, and rehires, and you can see why FUTA taxable wages per employee is a tracking problem, not a math problem.
The fix is a per-employee wage-base register, built on the first payroll run of January and maintained through every run after it. The register does four things:
- Record each employee’s cumulative FUTA-taxable wages against the $7,000 base.
- Update the running balance on every payroll run, including off-cycle runs and bonuses.
- Cap each period’s taxable wages at the remaining base balance, automatically zeroing out exhausted employees.
- Reconcile the register’s quarterly totals to your payroll system before each quarter closes.
Asure’s payroll compliance team builds per-employee wage-base registers as a standard practice, not because the IRS requires the artifact, but because it is the only reliable way to prevent over-remittance and under-remittance at the same time. Payroll leaders tell us their deepest fear is the spreadsheet workflow that breaks silently, the one nobody notices until a missed deadline or an agency notice surfaces it. The register is the control that catches the drift while it is still a rounding error instead of a penalty.
Maintained well, the register also becomes your audit trail. Every quarterly total, every deposit, and every Form 940 line traces back to a per-employee record you can produce on demand. That is what audit-ready actually means in practice.
Quarterly Liability and the Deposit Threshold Run on Two Different Clocks
Here is the piece of common wisdom that generates the most penalties. Form 940 is filed once a year, so practitioners treat FUTA as an annual tax, deferring all calculation and payment to year-end. The form is annual. The liability is not.
Per IRS Publication 15, Table 4 (https://www.irs.gov/pub/irs-pdf/p15.pdf), and the Instructions for Form 940 (https://www.irs.gov/instructions/i940), FUTA tax is figured quarterly for deposit purposes. The rule has two moving parts:
- Carry forward any quarter’s liability of $500 or less and add it to the next quarter’s liability.
- Deposit by electronic funds transfer (EFT) once cumulative undeposited liability for a quarter exceeds $500, by the last day of the first month after the quarter ends.
That means April 30 for the first quarter, July 31 for the second, October 31 for the third, and January 31 for the fourth. If your liability through Q4, including carryover, stays at $500 or less for the whole year, you may simply pay it with your Form 940 filing. Cross the threshold in any quarter and a deposit clock starts that has nothing to do with the annual filing date.
The $500 deposit threshold arrives faster than growth-stage teams expect. Run the arithmetic on a 30-person company where most employees cross the $7,000 base by late March. At the 0.6% net rate, that is up to $42 per employee, roughly $1,260 of liability landing in Q1 alone. That is more than double the threshold. A deposit is due April 30, nine months before the Form 940 is filed. Wait for year-end and you are three quarters late on the bulk of your annual liability.
Notice also how wage-base exhaustion timing, the problem from the last section, drives the deposit calendar. Salaried staff concentrate FUTA liability into Q1 and Q2. Part-time staff spread it across all four quarters. You cannot know which quarter trips the threshold without the per-employee register.
What Asure sees in pre-filing reviews is a consistent timing gap. The math is right. The annual total matches Form 940, Line 12, to the penny. But the quarterly deposits were late, because the team treated FUTA as a once-a-year reconciliation rather than a rolling quarterly liability. Correct calculation, wrong calendar, real penalties. It is the most frustrating failure mode in payroll tax, because the team did the hard part well.
It is also, in our field experience, the moment that sends growth-stage companies looking for help. Pain builds quietly for quarters, and then a notice arrives. The owners and finance leads we work with rarely call about software features. They call because an agency letter made the risk concrete, and they want this category of surprise off the table. CFOs put it plainly. The success metric is no surprise tax notices, ever. Hitting that metric takes both clocks running, the liability clock and the deposit clock, all year.
The SUTA Credit Is a FUTA Input, Not a Separate Calculation
Most teams treat FUTA and SUTA as two unrelated tax problems. In a FUTA SUTA tax calculation, they are one problem, because the SUTA side determines which FUTA rate you are allowed to use.
The 5.4% credit that turns the 6.0% gross rate into the 0.6% net rate is conditional, and IRS Publication 15 (2026) (https://www.irs.gov/pub/irs-pdf/p15.pdf) states the conditions precisely. You get the maximum credit only if your state unemployment taxes were paid in full, on time, and on the same wages that are subject to FUTA tax, and only if your state is not a credit reduction state. Miss any condition and your effective FUTA rate rises. Calculate at 0.6% anyway and you have quietly under-accrued all year.
The condition that blindsides growth-stage teams is the credit reduction state. When a state borrows federal funds to pay unemployment benefits and does not repay the loan on schedule, the IRS reduces the FUTA credit for every employer in that state. Per the IRS FUTA credit reduction page (https://www.irs.gov/businesses/small-businesses-self-employed/futa-credit-reduction), the reduction is 0.3% for the first year and grows by an additional 0.3% for each year the loan remains unpaid. The Department of Labor announces the affected states after the November 10 deadline each year, and the authoritative list lives on DOL’s FUTA Credit Reductions page at oui.doleta.gov.
For tax year 2025, the most recently completed Form 940 cycle, the only credit reduction jurisdictions were California at 1.2% and the U.S. Virgin Islands at 4.5%, per Schedule A (Form 940) (https://www.irs.gov/pub/irs-pdf/f940sa.pdf). For a California employer, that meant an effective rate of 1.8% instead of 0.6%, an extra $84 for every employee who hit the $7,000 base. On 60 capped employees, that is over $5,000 of liability a 0.6% assumption never accrued. The 2026 determinations will not exist until after November 10, 2026, so do not assume this year’s list matches last year’s. Check the DOL list (https://oui.doleta.gov/unemploy/futa_credit.asp) before you close the year.
The timing rule compounds the trap. Per Publication 15, credit reduction liability is treated as incurred in the fourth quarter and must be included with your Q4 deposit, due January 31. Teams that skip the check discover the shortfall at Schedule A time, after the deposit window has closed.
Asure flags SUTA credit reduction exposure as a first-pass check in every Q4 payroll review for clients operating in states with outstanding federal loans. In our reviews, it is the most common source of unexpected FUTA liability at year-end. This is also where multi-state growth changes the job. Hire in a second or third state and you now track separate SUTA accounts, separate timeliness conditions, and separate credit reduction exposure per state. Asure Payroll Tax Management was built for exactly this, multi-jurisdiction payroll tax filing infrastructure that handles federal, state, and local filings and tracks agency notices, the same infrastructure that runs alongside enterprise payroll systems like Workday, Oracle, and SAP. Statutory liability stays with you as the employer. What you hand off is execution, backed by a documented reconciliation trail.
Form 940 Is a Reporting Translation, Not a Calculation
The last structural failure is treating Form 940 as the place where FUTA gets calculated. Teams open the form in January, reconstruct a year of wages from memory and spreadsheets, and force the numbers to fit the lines. Those filings routinely fail to reconcile to payroll records, and filings that do not reconcile draw IRS correspondence.
Contrast that with teams that maintained the per-employee register all year. For them, Form 940 FUTA liability is already known before the form is opened. The form becomes a structured translation of the register into the IRS line format:
- Lines 3 through 8 take total payments to all employees, subtract exempt payments and the wages above each employee’s $7,000 cap, and arrive at total taxable FUTA wages. Your register already holds these numbers per employee.
- Line 11 carries the credit reduction amount calculated on Schedule A, if any of your states appear on the DOL list.
- Line 12 is total FUTA tax after adjustments. If your quarterly accruals were right, this line equals what your register predicted, and your deposits already cover it.
The filing deadline follows a standing rule. Per IRS Tax Topic 759 (https://www.irs.gov/taxtopics/tc759), Form 940 is due January 31 following the tax year, and employers who deposited all FUTA tax when it was due get until February 10 to file. Note what the extension rewards. Deposit discipline. The IRS gives the extra days to the teams that ran the two clocks correctly all year.
In Asure’s experience, the payroll teams that file clean Form 940s every year share one habit. They treat the form as the last step in a process that started on the first payroll run of January, not as the process itself. Their filing reconciles to their payroll records because both came from the same register, updated run by run for 12 months.
This is also where the register stops being a concept and becomes a system of record. Asure Payroll Tax Management keeps reporting records, deposit history, and agency notice tracking in one place, so when an auditor or an agency asks how Line 12 was built, the answer is a record you pull up, not a reconstruction. That is the audit-ready FUTA liability register made real.
The Bottom Line
FUTA accuracy is a structural tracking problem, not an arithmetic problem. The five patterns all point at the same root cause. Wage-base exhaustion varies per employee. Per-period discipline is what captures it. Deposit timing runs on its own quarterly clock. The SUTA credit is a conditional input that can change your rate. And Form 940 only reports what your records already calculated. Build a per-employee wage-base register on the first payroll run of the year, maintain it through every run, and filing reduces to a confirmation, not a scramble. Asure’s payroll compliance practice helps growth-stage teams build exactly that register and the quarterly review cadence that keeps it audit-ready.
Related Questions
What is the FUTA tax rate and taxable wage base? Per IRS Publication 15 (2026), the gross FUTA rate is 6.0% on the first $7,000 paid to each employee during the year, which is the federal wage base. Employers who pay state unemployment taxes in full and on time receive a credit of up to 5.4%, making the net rate 0.6% for most employers. The full credit is unavailable in credit reduction states.
How do I calculate FUTA tax per pay period for each employee? For each employee, multiply the net rate by the wages paid in that period, capped at the remaining balance of that employee’s $7,000 annual wage base. Once cumulative wages pass $7,000, FUTA stops accruing for that employee for the rest of the year. A per-employee wage-base register, updated every payroll run, is what keeps this calculation accurate as employees exhaust the base at different times.
When do I have to deposit FUTA taxes instead of waiting for Form 940? FUTA liability is figured quarterly, and quarters of $500 or less carry forward into the next quarter. Once cumulative undeposited liability exceeds $500 at the end of any quarter, an EFT deposit is due by the last day of the following month, meaning April 30, July 31, October 31, or January 31, per the IRS Instructions for Form 940. Only if liability stays at $500 or less all year can you pay it with the Form 940 filing.
How does the SUTA credit reduce FUTA tax, and what is a credit reduction state? Employers who pay state unemployment taxes in full, on time, and on the same wages subject to FUTA receive up to a 5.4% credit against the 6.0% gross rate. A credit reduction state is one with an outstanding federal unemployment loan, which shrinks the available credit by 0.3% per year the loan goes unrepaid and raises every in-state employer’s effective FUTA rate. For tax year 2025, the credit reduction jurisdictions were California at 1.2% and the U.S. Virgin Islands at 4.5%; the current-year list is published by DOL at oui.doleta.gov.
How do I map FUTA calculations to Form 940 lines? Lines 3 through 8 move from total payments through exempt payments and over-the-cap wages to arrive at taxable FUTA wages. Line 11 carries any credit reduction amount from Schedule A, and Line 12 is your total FUTA tax after adjustments. The form reports what your payroll register already calculated, which is why filings built from a maintained register reconcile cleanly.
If you would rather not carry that tracking burden alone, Asure Payroll Tax Management and AsureWorks put the calculations, deposit timing, and filings in the hands of specialists who help you stay compliant. AsureWorks is a managed service and a PEO alternative with no co-employment, so you always remain the employer of record. Statutory FUTA liability never transfers to any provider; what transfers is execution, with a documented division of responsibilities, a reconciliation trail, and a notice-resolution workflow handled by one accountable team. Talk to an expert.
