Overtime Calculation

Your operations manager approved 12 hours of overtime for a crew of 8 workers last week. When the payroll register came back, three of them had overtime calculated differently from the others, because two states have daily overtime rules and one follows the federal weekly-only rule. Nobody had told the payroll system to apply state-specific rules to those employees. Overtime calculation is the process of working out which hours beyond a standard threshold earn a premium rate, and what that rate is. Under the federal Fair Labor Standards Act (FLSA), non-exempt employees must be paid at least 1.5 times their regular rate of pay for all hours worked over 40 in a single workweek. Federal law is the floor, not the ceiling. Several states, including California, Alaska, Nevada, Colorado, and others, impose daily overtime requirements that trigger at 8 hours per day, regardless of total hours worked in the week. When employees work in multiple states, or the payroll system isn't set to apply state rules by work location, overtime is miscalculated in the payroll run and the error isn't caught until an audit or a complaint.

How overtime is calculated

Under FLSA, overtime is calculated per workweek: a fixed, regularly recurring period of 168 hours (seven consecutive 24-hour days). The employer defines the workweek, and it does not have to match the calendar week or the pay period. Once an employee passes 40 hours in the workweek, every additional hour must be paid at no less than 1.5 times the regular rate of pay. The regular rate is not always the base hourly rate. It includes all pay for employment except specific FLSA exclusions: overtime pay itself, gifts, vacation pay, discretionary bonuses, and a short list of other items. Non-discretionary bonuses (tied to hours worked, productivity, or efficiency) must be included in the regular rate, which pushes the overtime rate above what the base wage alone would produce. California adds daily overtime: 1.5x for hours 9 to 12 in a workday, and 2x for hours beyond 12 in a single workday. California also requires double time for the seventh consecutive day of work in a workweek. Colorado has similar daily overtime rules. Nevada requires daily overtime for employees earning below a certain hourly threshold. For multi-state employers, the same hours can produce different overtime liability depending on the state, so payroll platforms must be configured with the correct state rules for each employee's work location to get the numbers right.

Where it gets complicated

Many operations and manufacturing employees work at different pay rates in the same workweek: a base rate for standard production work, and a higher rate for specialized tasks or a shift differential for overnight hours. When an employee works at two rates in a workweek and earns overtime, the FLSA requires a weighted average regular rate: total earnings across all hours and rates, divided by total hours worked, as the base for the overtime premium. The overtime due is then the weighted average rate multiplied by 0.5 for each overtime hour (the straight-time portion has already been paid). Employers often simplify this by paying the higher of the two rates on all overtime hours, which is always compliant but costs more than the weighted average method. Non-discretionary bonuses create a similar problem. If an employee earns a production bonus partway through the quarter, the bonus must be allocated back to the workweeks it covered, the regular rate for those weeks recalculated to include it, and any additional overtime computed and paid. This retroactive adjustment is called a regular rate true-up, and most payroll platforms don't do it automatically without configuration or manual work.

How platforms handle it

Enterprise payroll platforms like Workday, Ceridian Dayforce, and ADP Workforce Now have state-specific overtime rule libraries that can be assigned to employees by work state. Configured correctly, the system applies daily overtime thresholds to California employees and weekly-only thresholds to federal-rule employees automatically during the payroll calculation. The risk sits in that configuration: the system needs each employee's work location, each location must map to the correct state overtime rule, and the rules must be updated when state law changes. Platforms that update state rules automatically when the law changes take much less maintenance than those that need manual rule updates. Time-tracking integrations add another dependency. If the time-tracking system records daily hours but payroll imports only weekly totals, daily overtime can't be calculated no matter how the payroll rules are set up. State daily overtime rules only work when payroll receives daily hours by employee.

Questions to evaluate your overtime calculation process

• Is your payroll system configured with the correct state overtime rules for every state where you have hourly, non-exempt employees?
• Does your time-tracking system export daily hours to payroll, or only weekly totals? Does that affect your ability to calculate state daily overtime correctly?
• When employees work at multiple pay rates in the same workweek, does your payroll system calculate the weighted average regular rate, or does it default to the higher rate?
• Do you have a process for retroactive regular rate true-ups when non-discretionary bonuses are paid for periods that included overtime hours?
• Have you audited your exempt vs. non-exempt classification recently, particularly for employees whose roles have changed but whose classification hasn't been updated?
• Do any employees regularly work in more than one state in the same workweek? If so, how does your payroll system apportion hours for multi-state overtime calculation?

Where overtime calculation creates liability in practice

The most consistent source of overtime liability is assuming federal weekly rules apply in every state. Employers with California operations often underestimate California overtime costs because payroll was set up for weekly FLSA rules and nobody updated it when California employees were hired. Daily overtime liability builds on every paycheck, and the exposure grows quickly across a large hourly workforce. The second major failure is leaving bonuses out of the regular rate of pay. A non-discretionary production bonus paid quarterly but not applied back to the workweeks it covers creates an FLSA violation on every overtime paycheck in those weeks. It is a common audit finding because it doesn't show up in the payroll register: the base overtime rate looks right, but it is too low because the bonus wasn't included in the regular rate. The Department of Labor's Wage and Hour Division recovers hundreds of millions in back wages annually from regular rate miscalculations, and these cases often span multiple years of pay.

Regular rate against base rate

The multiplier applies to the regular rate, not the hourly base. Under the Fair Labor Standards Act the regular rate includes most non-discretionary bonuses, shift differentials and commissions, so an employee with a production bonus has a higher overtime rate than their quoted hourly figure. State law can also require daily overtime thresholds that the federal weekly test does not. Both are common sources of back-pay findings.

Comparing payroll platforms

Payroll platforms separate on filing coverage: which jurisdictions the vendor files in itself, and which ones it hands back to you. Once overtime calculation is settled as a requirement, read the Payroll Software category guide for how the market splits, then weigh the Gusto profile against the Rippling profile on that requirement rather than on the feature list. No head-to-head comparison is published in this category yet, so the profiles listed in the Payroll Software guide are the place to compare. Before you book demos, put your own numbers through the payroll savings calculator so the business case is written down before a vendor writes it for you.

Frequently asked questions

Related terms

Direct Deposit, Gross Pay vs Net Pay, and Pay Period come up in the same workflow as overtime calculation, and the rest of the payroll platforms cluster is indexed in the finance operations glossary.