ADP Workforce Now calculates overtime according to the pay rules and earnings codes configured in the system. Configuration errors can therefore repeat across pay runs. If a setting doesn’t match federal or state law, the same mistake can continue until someone finds and fixes it.
This guide explains common reasons ADP Workforce Now overtime comes out wrong. It starts with the regular rate rules that trip up payroll teams. Then it covers the integration gaps SaaS admins tend to miss and the new 2026 reporting rules for qualified overtime. Each section ends with what to check in your own setup, so you can find problems before an auditor or an employee does.
TL;DR
- Configuration can cause overtime errors because the system applies the rules and codes it’s given.
- Nondiscretionary bonuses and shift differentials are generally included in the regular rate of pay under federal rules, and leaving eligible earnings out can understate overtime.
- Employees who work at 2 or more rates need weighted average overtime unless a valid prior agreement says otherwise.
- Integrations and time settings, such as pay class and rounding, can distort overtime without any visible error.
- From 2026, the W-2 must show qualified overtime compensation, and state-only overtime has to be moved to separate codes.
How ADP Workforce Now calculates overtime
ADP Workforce Now handles overtime in 2 places. Time and Attendance collects punches and applies rounding rules before it totals hours and flags overtime. Payroll then turns those hours into pay using each employee’s rate and the earnings codes attached to their hours. When the 2 modules agree with each other and with the law, overtime comes out right. When either one is set up wrong, the error flows straight into the paycheck.
The key setting in Time and Attendance is the pay class. It tells the system how punches are rounded and when overtime starts. Supervisors can open an employee’s Individual Timecard and click the Show Pay Class link to see exactly how that employee’s time is being calculated. That view is the fastest way to confirm what the system is actually doing, as opposed to what your team assumes it’s doing.
Payroll adds a second layer. Earnings codes decide how each payment is treated. Some codes feed the overtime calculation and some don’t. A bonus code set up years ago by an implementation consultant might never touch the overtime math, and nobody on the current team may know it.
This split matters for payroll and HR teams because it clarifies which part of the process each team needs to verify. ADP runs the calculation engine, but your organization owns the configuration. ADP’s own guidance on overtime laws by state makes clear that state rules can add daily thresholds and double time on top of the federal 40-hour standard. The software can support those rules, but it can’t know which ones apply to your workforce unless someone sets them up. Every section below traces a specific way that setup can drift away from what the law requires for ADP Workforce Now overtime.
Why overtime errors cost more than the missing pay
Small overtime errors add up fast because they repeat across every employee and every pay period. A premium that’s short by a few dollars a week turns into a large liability once you multiply it by a workforce and 2 or 3 years of history.
Federal enforcement is active. The Department of Labor’s Wage and Hour data shows the division recovered more than $259 million in back wages for 176,957 employees in fiscal year 2025, an average of $1,465 per worker. That was the highest recovery since 2019. Food service and healthcare were among the industries with the most resolved violations, and both rely heavily on hourly shift workers with overtime.
Many recent cases involve exactly the regular rate problems covered in this guide. In May 2025, the DOL announced that Cupertino Electric, one of California’s largest electrical contractors, paid more than $1.4 million in back wages to over 2,600 employees. Investigators found the company left nondiscretionary bonuses out of the rate used to calculate overtime. Another 2025 case against M.J. Electric recovered $207,470 in back wages and damages for the same issue, plus a $19,782 civil money penalty for a repeat violation.
Back wages are only part of the cost. Under the FLSA, employers can also owe an equal amount in liquidated damages, along with the employee’s legal fees. State laws can add their own penalties on top. For a SaaS-based payroll setup, there’s also the internal cost of rework. Correcting a past error means recalculating historical pay and issuing adjustments. It can also mean filing corrected tax forms. Finding the problem early is far cheaper than fixing it after a complaint.
Nondiscretionary bonuses missing from the regular rate
Leaving eligible nondiscretionary bonuses out of the regular rate can underpay ADP Workforce Now overtime. Federal law requires overtime at 1.5 times the regular rate of pay, and the regular rate often includes more than the base hourly wage. It’s total pay for the workweek, minus certain statutory exclusions, divided by total hours worked.
What counts as discretionary
The rules for bonuses come straight from federal guidance. The DOL’s Fact Sheet 56C says discretionary bonuses can be left out of the regular rate, while nondiscretionary bonuses must be included unless another statutory exclusion applies. The catch is that a bonus only counts as discretionary if it meets every statutory requirement. The employer must keep sole discretion over both the fact and the amount of the payment until at or near the end of the period it covers. If employees know about the bonus in advance and expect it for meeting a target, it’s nondiscretionary.
That rule pulls in far more bonuses than most teams expect. Attendance bonuses, production bonuses, quality and accuracy bonuses, safety bonuses and retention bonuses are all common examples of nondiscretionary bonuses. Bonuses promised in an offer letter or a written plan also count. A holiday gift that’s truly unannounced and not tied to hours or output can be excluded. A “holiday bonus” that employees get every year based on hours worked probably can’t.
In ADP Workforce Now, each bonus type should have its own earnings code with a clear decision about whether it feeds the regular rate of pay. If your team uses 1 generic “Bonus” code for everything, you can’t tell the 2 types apart in reporting, and the safer assumption is that some of those payments were handled wrong.
Bonuses that span several weeks
Bonuses paid quarterly or annually add another layer. When a nondiscretionary bonus covers more than 1 workweek, the employer has to allocate it back across the weeks it was earned. Then the regular rate for each of those weeks must be recalculated, and extra overtime premium paid for any overtime hours in them.
The DOL walked through this math in a 2026 opinion letter, FLSA2026-2. A law firm summary of the DOL opinion letter shows the adapted example. An employee earns $880 in straight-time pay, including a bonus, across 50 hours. The regular rate becomes $17.60 an hour, the half-time premium is $8.80, and 10 overtime hours add $88 in premium pay.
Most payroll platforms, including ADP Workforce Now, won’t run this look-back on their own unless you’ve set up a process for it. Someone has to identify the bonus period, pull the overtime hours in that period and calculate the true-up. If your company pays quarterly incentives to hourly staff and nobody runs that calculation, overtime has likely been short every quarter.
Shift differentials and other pay left out of the overtime base
Bonuses get the most attention, but they aren’t the only pay that belongs in the regular rate of pay. Shift differentials count too, and so do many other incentive payments. If an employee earns an extra $2 an hour for night shifts, that $2 is part of their pay for the week and has to be included before the overtime premium is figured.
A common ADP Workforce Now overtime setup error puts the differential on its own earnings code that doesn’t feed overtime. The employee then gets time and a half on the base rate only. For a worker who does a lot of night shifts and regular overtime, the shortfall builds every week without any visible sign on the pay stub.
The FLSA does allow some payments to be excluded. These include:
• Payments for time not worked, such as vacation or sick pay.
• Reimbursed business expenses that the employee paid on the employer’s behalf.
• Truly discretionary bonuses and gifts that aren’t tied to hours or performance.
• Contributions to certain retirement and health plans.
• Premium pay for overtime or special days that meets the legal conditions for exclusion.
Everything else generally goes into the overtime base. The practical test for your setup is simple. Pull a list of every active earnings code in ADP Workforce Now and mark whether each one should feed the regular rate. Then compare that list with how the codes are actually configured. Any code that pays for work performed but doesn’t feed overtime deserves a closer look.
State rules can be stricter. California, for example, has its own regular rate rules that sometimes include payments the FLSA would exclude. If you operate in several states, the earnings code review should be done with the strictest applicable rule in mind.
Weighted average overtime for employees with multiple rates
Employees who work at more than 1 rate in a week need a different overtime method. Federal regulation 29 CFR 778.115 says that when an employee works at 2 or more rates in a single workweek, the regular rate is the weighted average of those rates. Total earnings from all rates are added together and divided by total hours worked at all jobs.
Here’s how weighted average overtime works in practice. Say an employee works 30 hours as a cashier at $20 an hour and 15 hours as a shift lead at $26 an hour, for 45 hours total.
| Step | Calculation | Result |
| Straight-time earnings | (30 × $20) + (15 × $26) | $990.00 |
| Weighted regular rate | $990 ÷ 45 hours | $22.00 |
| Half-time premium rate | $22.00 × 0.5 | $11.00 |
| Overtime premium due | $11.00 × 5 overtime hours | $55.00 |
Now compare that with 2 common system shortcuts. If the setup pays overtime on the employee’s home rate of $20, the premium is $50 and the employee is short $5 that week. If it pays on whichever rate was active when the employee crossed 40 hours, the result could be higher or lower depending on the schedule. Neither shortcut matches the rule by default.
There is a legal alternative. Under the FLSA, an employer can pay overtime at 1.5 times the rate for the type of work performed during the overtime hours. This “rate in effect” method only works if the employer and employee agreed to it before the work was done. It can’t be applied after the fact to fix a missed calculation.
Check whether weighted average overtime is actually turned on for employees who work multiple positions in ADP Workforce Now overtime processing. Then test it. Pick a real employee with 2 rates and overtime in the same week, run the numbers by hand, and compare them with the pay statement. If they don’t match, the setup needs attention before the next payroll.
Integration gaps between time systems and payroll
Many companies don’t collect time inside ADP Workforce Now at all. They use a scheduling or time tracking app that sends hours into payroll through an integration. That handoff is a common place for ADP Workforce Now overtime to go wrong, because each system can assume the other one is handling part of the calculation.
Vendor documentation often spells out these limits. The help documentation for When I Work’s ADP integration shows how this can play out. Position-specific pay rates are sent into ADP as a Temporary Rate on the pay data grid. The same page notes that the integration doesn’t modify rates for overtime premiums, and that overtime premiums have to be configured in ADP Workforce Now itself. If your team assumed the scheduling tool handled the premium, and ADP was never set up to do it, nobody is calculating it correctly.
Other integrations have similar limits, so read the fine print for any tool you connect. ClockShark’s documentation, for example, says that if an employee tracks time against a task mapped to a special pay rate that isn’t assigned to them in ADP, the system falls back to their base pay rate. The employee’s hours arrive correctly, but the rate behind them doesn’t. Weighted average overtime then gets calculated on the wrong inputs.
Mapping errors cause a different kind of problem. Each integration asks you to map its hour types to ADP earnings codes, such as regular hours and overtime. If overtime hours are mapped to a regular code, or double time is mapped to a standard overtime code, the hours land in payroll with the wrong multiplier. These mistakes are easy to make during setup and hard to spot later, because the pay stub still shows the right total hours.
For SaaS admins, the fix is to document every integration as a data flow. Write down which system calculates overtime and which earnings code each hour type maps to. Review that document whenever either vendor releases an update or your team adds a new position. Integrations that worked at go-live can break quietly after a single configuration change on either side.
Pay class settings and state overtime rules
The pay class controls when ADP Workforce Now overtime starts, so a wrong assignment can underpay an employee on every shift. Two settings deserve close review: the workweek definition and the state rules built into the class.
Workweek versus pay period
Federal overtime is calculated by the workweek, which is 7 consecutive 24-hour periods. ADP’s guide on overtime compliance basics notes that employers must calculate overtime based on the defined workweek, not the pay period. An employer can change its workweek, but only if the change is permanent and isn’t meant to avoid overtime.
This matters most for biweekly and semimonthly payrolls. An employee who works 50 hours in week 1 and 30 in week 2 averages 40 hours across the pay period but is still owed 10 hours of overtime for week 1. If a pay class or custom rule averages hours across the period, the system will miss that overtime entirely. Semimonthly payrolls add another wrinkle, since pay periods don’t line up with workweeks and a workweek can split across 2 checks.
Daily overtime states
Several states require overtime based on daily hours as well as weekly hours. Alaska, California, Colorado and Nevada all have daily overtime rules. California’s are the strictest. Nonexempt employees earn time and a half for hours over 8 and up to 12 in a workday, plus the first 8 hours on the 7th consecutive day in a workweek. Double time applies to hours over 12 in a workday and hours over 8 on that 7th day.
A pay class built for weekly federal overtime won’t apply any of these rules. So if a California employee is assigned to a weekly-only class, every 10-hour shift underpays them by 2 hours of overtime, even in weeks where they stay under 40 hours. This often happens when an employee transfers from another state or when a new location opens and the default pay class gets copied over.
The check here is a simple report. Pull every employee’s work state and pay class, and flag any mismatch. Employees who work across state lines need extra care, since the rules that apply usually depend on where the work was performed.
Rounding rules in Time and Attendance
Rounding settings in Time and Attendance change the hours that feed ADP Workforce Now overtime, so they deserve their own review. ADP Workforce Now applies rounding rules automatically when it collects punches and totals hours. That’s convenient, but it can quietly shift paid time up or down.
Federal law allows rounding within limits. Under 29 CFR 785.48(b), employers may round start and stop times to the nearest 5 minutes, tenth of an hour or quarter hour. The practice is only accepted if it doesn’t, over time, fail to pay employees for all the time they actually worked. In other words, the rule has to be neutral in how it’s designed and in how it plays out for your workforce.
Problems show up in 2 ways. The first is a rule that only rounds in the employer’s favor, such as always rounding clock-outs down. The second is a rule that looks neutral on paper but underpays in practice because of how employees punch. If staff routinely clock in a few minutes early and start working, a quarter-hour rule can strip that time out week after week.
California has raised the bar further. In Camp v. Home Depot, a California Court of Appeal held that when a timekeeping system can capture exact minutes worked, the employer must pay for all of that time, even under a rounding policy that’s neutral on its face. A law firm analysis of the Camp v. Home Depot decision noted that 1 employee lost about 7 hours of pay over 5 years, even though the policy was a net positive across all employees. The California Supreme Court granted review in 2023. As of September 2026, Camp v. Home Depot, S277518, remains pending and fully briefed, with no decision issued. The court’s docket shows an August 20, 2026 filing concerning the setting of oral argument.
Since ADP Workforce Now records punches to the minute, many employers now ask whether rounding is needed at all. Turning it off removes a source of risk, and the hours feeding overtime then match the punches exactly. At a minimum, run a report that compares rounded hours with actual punched hours across a few months. If the gap consistently runs against employees, the rule isn’t neutral in practice.
The 2026 qualified overtime reporting problem
A new federal tax rule has added a reporting risk that didn’t exist before. The One Big Beautiful Bill Act created a deduction for qualified overtime compensation for tax years 2025 through 2028. Employees can deduct up to $12,500 a year, or $25,000 for joint filers, with a phase-out at higher incomes. Employers have to report the qualified amount on the W-2.
The definition is narrow. Qualified overtime is only the premium portion of overtime that’s required under Section 7 of the FLSA. For a worker paid time and a half, that’s generally the extra “half,” and the straight-time portion doesn’t count. A California employer guide on state-only overtime explains that overtime required by state law but not by federal law doesn’t qualify. Overtime paid only because of a union contract or company policy doesn’t qualify either.
How ADP handles it
For tax year 2026, the W-2 instructions require the qualified amount in Box 12 with the new code TT. ADP’s summary of the early H.R. 1 guidance covers the draft forms that introduced that code. The IRS gave employers penalty relief for incomplete reporting in 2025, but that relief was limited to the 2025 tax year.
Here’s the part that catches ADP Workforce Now overtime users. ADP’s 2026 tax season update says that for payrolls with a check date of January 1, 2026 or later, hours in the existing overtime and double time earnings codes will be used to calculate the premium portion and report it in Box 12. ADP also added new “NQ” (non-qualified) overtime codes for hours that don’t qualify for the federal deduction. A new Qualified Overtime Compensation Summary report shows the qualified premium per payroll.
The default only works if your codes reflect the law. If you pay California daily overtime or contractual overtime through the standard overtime codes, ADP will treat all of it as federally required. Your Box 12 TT figures will then be too high. ADP’s earnings quick reference lists the NQ overtime codes and notes that those amounts aren’t qualified overtime under the new law.
What to separate
Getting this right means splitting overtime by the reason it’s owed. Hours over 40 in a workweek for FLSA-covered, nonexempt employees go in the standard codes. Daily overtime that doesn’t also push the employee over 40 hours goes in NQ codes. The same applies to 7th-day premiums in California and overtime paid only under a contract. Double time needs care as well, since only the part that meets the FLSA minimum can count as qualified.
Correct coding during the year makes year-end reporting easier because the W-2 total depends on how qualified overtime is recorded. If an employer later finds that box 12 code TT is wrong, IRS guidance provides for correction using Form W-2c. Any ADP reprocessing needed to support that correction depends on the underlying records and coding issue. Review the Qualified Overtime Compensation Summary report during 2026 payroll processing and compare it with sample calculations.
How to audit ADP Workforce Now overtime step by step
A focused audit of ADP Workforce Now overtime can find most of these issues in a few weeks. The steps below are ordered so each one builds on the last, starting with the settings that affect the most employees.
1. Export every active earnings code and mark whether it should feed the regular rate of pay. Compare your list with the actual configuration and flag every mismatch.
2. List every bonus plan and incentive paid to hourly staff. Sort them into discretionary and nondiscretionary types using the DOL criteria, and confirm each one uses the right code.
3. Check whether any nondiscretionary bonuses covered more than 1 workweek. If so, confirm that a true-up process exists and that it has actually been run.
4. Pull every employee who worked at 2 or more rates in the same week. Recalculate weighted average overtime by hand for a sample and compare it with their pay statements.
5. Map every time system integration. Record which system calculates overtime and how each hour type maps to an earnings code.
6. Run a report of work state against pay class. Fix any employee in a daily overtime state who’s assigned to a weekly-only class.
7. Compare rounded hours with actual punches over at least 3 months. Look for a pattern that consistently runs against employees.
8. Review 2026 overtime coding for the W-2. Move non-qualifying hours, such as state-only daily overtime, to the NQ codes, and check the Qualified Overtime Compensation Summary report.
9. Calculate any back pay owed for past errors and decide how to correct it with legal counsel.
10. Document the final settings and set a schedule to review them after every major change.
The first 4 steps focus on earnings and rate issues. Steps 5 through 8 cover integrations, pay classes, rounding, and 2026 coding. The last 2 steps address corrections and ongoing controls so the review can be repeated after future changes.
Who owns overtime accuracy in a SaaS payroll setup
In a SaaS payroll model, the vendor runs the software and the customer stays legally responsible for paying employees correctly. ADP provides the software and the calculation engine. Your organization chooses how it’s set up and which rules apply to which employees. The FLSA holds the employer liable for unpaid overtime, whichever system produced the paycheck.
That makes ownership a governance question. Payroll work is often split across several teams, and overtime settings can fall between them. A pay class change made by HR and an integration update pushed by IT can each affect overtime without anyone reviewing the combined effect. Assign 1 named owner for overtime configuration, with sign-off rights on any change that touches pay rules or integrations.
Change management matters just as much. Treat any change to pay rules like a software release. Write down what’s changing and test it against sample employees before it goes live. Keep a record of who approved it as well. When the DOL or an employee’s lawyer asks why overtime was calculated a certain way, a clear change log is one of the strongest defenses you can have.
If an audit does uncover past underpayments, there’s a formal path to fix them. A DOL release on a 2026 overtime case involving bonuses left out of overtime pointed employers to the agency’s Payroll Audit Independent Determination (PAID) program. It lets employers self-report and resolve potential minimum wage and overtime violations under the FLSA. The same release highlighted the division’s recent opinion letters on what belongs in the regular rate. Talk with employment counsel before deciding whether PAID fits your situation, since state claims may work differently.
Final thoughts
ADP Workforce Now overtime errors can come from configuration, earnings-code choices, time data, or rule mismatches, and a focused audit can identify many of them. Regular-rate issues include bonuses and differentials that never reach the overtime math, while employees with multiple rates may need a weighted-average calculation. Integrations and time settings can add other risks that don’t show up clearly on a pay stub.
The 2026 reporting rules raise the stakes. Your earnings codes now affect wage and hour compliance and W-2 accuracy at the same time. Teams that review their ADP Workforce Now overtime settings now, split qualified from non-qualified hours and assign clear ownership for pay rule changes will be in a much stronger position when the next audit or year-end close arrives.
Frequently asked questions
Why is ADP Workforce Now overtime calculating wrong?
ADP Workforce Now overtime can be wrong when configuration, earnings codes, pay classes, integrations, or time rules don’t match the applicable pay requirements. Common causes include bonus and differential codes that don’t feed the regular rate, missing weighted-average setups, wrong pay class assignments, integration mapping errors, and rounding rules. The calculation engine applies the rules and codes configured for the employee.
Does ADP automatically include bonuses in overtime?
Only if the bonus earnings code is set up to feed the overtime calculation. Nondiscretionary bonuses must be included in the regular rate of pay under federal law. Bonuses that cover several weeks also need a look-back calculation, which may require a separate payroll process.
What is the regular rate of pay for overtime?
The regular rate is total pay for the workweek, minus certain statutory exclusions, divided by total hours worked. It often includes nondiscretionary bonuses and shift differentials on top of the base hourly wage. Overtime is owed at 1.5 times that rate.
What makes a bonus nondiscretionary?
A bonus is nondiscretionary if employees expect it for meeting set criteria, such as attendance, output, safety or staying employed until a certain date. It’s only discretionary if the employer keeps full control over whether to pay it and how much until near the end of the period it covers.
How does weighted average overtime work?
Add up the straight-time pay from all rates in the workweek and divide by total hours worked. That gives the regular rate. The overtime premium is half that rate for each overtime hour, since straight time has already been paid for every hour.
Can we pay overtime at the rate of the job being done instead?
Yes, if the employer and employee agreed to it before the work was performed. This method pays 1.5 times the rate for the type of work done during the overtime hours. It can’t be applied after the fact to correct a missed weighted average calculation.
Do shift differentials count toward overtime?
Yes. Shift differentials are pay for work performed, so they’re part of the regular rate. A night shift premium has to be included before the overtime premium is calculated, or the employee will be underpaid.
Why is overtime missing for biweekly payrolls?
Federal overtime is based on the workweek, not the pay period. If hours are averaged across 2 weeks, an employee who works 50 hours in 1 week and 30 in the next will miss 10 hours of overtime. Check that the pay class calculates overtime by workweek.
Which states require daily overtime?
Alaska, California, Colorado and Nevada have daily overtime rules. California also requires overtime and double time on the 7th consecutive workday. Employees in these states need a pay class that applies the daily rules.
Is time rounding legal in ADP Workforce Now?
Federal law allows rounding to the nearest 5 minutes, tenth or quarter hour if it doesn’t underpay employees over time. California’s treatment of rounding when systems capture exact minutes remains under review in Camp v. Home Depot, which is pending before the California Supreme Court as of September 2026. Compare rounded hours with actual punches and review current California authority before relying on a rounding rule.
What is qualified overtime compensation?
It’s the premium portion of overtime that’s required under Section 7 of the FLSA, generally the “half” in time and a half. Employees can deduct it on their federal returns for 2025 through 2028. Overtime required only by state law or a contract doesn’t qualify.
What are the NQ overtime codes in ADP?
NQ stands for non-qualified. ADP added these earnings codes for overtime and double time hours that don’t qualify for the federal deduction, such as state-only daily overtime. Hours in the standard overtime codes are treated as qualified for W-2 reporting.
Where does qualified overtime appear on the W-2?
Starting with tax year 2026, employers report qualified overtime compensation in Box 12 using code TT. ADP builds that figure from the overtime and double time earnings codes used during the year, so coding accuracy directly affects the W-2.
How far back should we look for overtime errors?
The FLSA generally allows claims going back 2 years, or 3 years for willful violations. Some states allow longer periods. Review at least that far back when you audit, and work with employment counsel on how to correct any errors you find.
Who is responsible for overtime errors in ADP Workforce Now?
The employer is. ADP provides the software and calculation engine, but the employer chooses the configuration and remains legally responsible for paying overtime correctly under federal and state law.
