Overtime Math Under the 52-Hour Workweek Cap

The 40-Hour Subtraction Rule

As of August 2026, the 52-hour workweek cap looks like a simple ceiling, but the math underneath it is where payroll systems fail. Most guides tell you to stop at 52 hours; the actual rule is that overtime starts at 40, and the cap only limits how many of those overtime hours are legal.

The friction appears when daily overtime triggers, salaried regular-rate derivation, and pay-period independence collide with the weekly formula. This guide walks through the statutory calculation, the single most common subtraction error, and a worked audit scenario that shows exactly where compliance breaks down.

Daily Triggers vs. Weekly Cap

The daily overtime trigger is the layer most payroll systems silently drop, and it is the layer where wage claims actually win. When a jurisdiction enforces both a 52-hour weekly cap and a daily trigger (typically hours beyond 8 in a single day), you do not pick one rule — you run both and pay the higher result. The daily rule owns that day’s excess hours first; the weekly 40-hour rule then applies to the remaining weekly total. A payroll system that only checks the weekly sum will underpay, and the employee can claim the difference retroactively with interest in most labor board jurisdictions.

Work the math on a concrete week: Monday 10 hours, Tuesday through Thursday 8 hours each, Friday 10 hours — 46 total. The daily trigger pays 2 overtime hours for Monday and 2 for Friday. The weekly rule then looks at the full 46-hour total and owes 6 overtime hours (46 minus 40). You do not subtract the daily-trigger hours from the weekly total before computing; you compute both independently and pay the larger obligation. In this case, the weekly rule’s 6 hours exceeds the daily rule’s 4 hours, so the employee receives 6 hours at the premium rate — but the daily calculation still matters because it is the floor for those specific days. As detailed in the 40-Hour Subtraction Rule section, the Korea Herald confirms the statutory formula as 40 regular hours plus a maximum of 12 overtime hours, reinforcing that the 52-hour figure is the ceiling, not the trigger.

The failure mode is not hypothetical. One Seoul-based HR forum thread describes a developer who worked 14 hours on a Monday. The payroll system flagged zero overtime because 44 is under 52, yet the daily rule owed 6 hours for that Monday alone. The weekly total was irrelevant to the daily obligation; the system simply never ran the daily check. That is a retroactive claim waiting to be filed, and the employer loses on the merits, not on a technicality.

Your audit step today: pull the last four weeks of time records for any employee who worked a single day over 8 hours, and run the daily-trigger calculation manually against your payroll output. If the system shows zero daily overtime for a day over 8 hours, you have a liability — and the fix is a configuration change, not a policy debate. Verify your jurisdiction’s exact daily threshold (8 hours is common but not universal) against the labor code before adjusting anything.

Salaried Regular Rate Derivation

The regular rate for a salaried non-exempt employee is not the salary divided by 40. It is the total weekly compensation divided by the total hours actually worked. That distinction is where most payroll systems understate overtime liability under a 52-hour cap, and it is the single most common error in salaried overtime math.

Department of Labor’s FLSA framework confirms the multiplier applies to hours over 40, and the 52-hour cap does not change that multiplier; it only limits the maximum compensable hours. Under South Korea’s 52-hour workweek cap, the statutory formula is 40 regular hours plus a maximum of 12 overtime hours. The cap is the enforcement ceiling, not the overtime trigger — a point the earlier section on the 40-hour subtraction rule established. For salaried employees, the regular rate must include non-discretionary bonuses and commissions, not just base salary. According to WorkforceHub’s overtime guidance, these additional compensation forms must be folded into the divisor before applying the 1.5x multiplier.

The edge case that breaks most payroll runs is the mid-quarter non-discretionary bonus. The retroactive allocation triggers additional overtime liability on weeks that already appeared fully paid, and under a 52-hour cap the liability compounds because the cap limits hours but not the premium rate applied to them.

The decision rule for any salaried non-exempt payroll run: compute the regular rate as total weekly compensation divided by total hours worked, include all non-discretionary bonuses and commissions in that numerator, and apply the 1.5x multiplier to hours over 40. If the payroll system defaults to a 40-hour divisor, override it manually for any week where hours exceed 40. Verify the jurisdiction’s exact daily threshold against the labor code before adjusting — 8 hours is common but not universal — and audit any quarter where a bonus was paid to confirm retroactive allocation was applied. Run that audit before the wage claim arrives, not after.

No Averaging Across Pay Periods

The 52-hour cap resets every Sunday at midnight, and no payroll configuration, no matter how well-intentioned, can legally average hours across a two-week pay period. Each workweek is a self-contained calculation unit for both the 40-hour overtime trigger and the 52-hour ceiling. A biweekly pay cycle does not create a 104-hour bucket; it creates two independent 52-hour buckets that reset sequentially.

The decision rule for any payroll manager: if the system displays a weekly hours field that can exceed 40 without triggering an overtime line item, the averaging bug is already live. If it shows 40 hours per week with no premium, the configuration is non-compliant and retro pay is a matter of when, not if.

This is not a Korean quirk. Department of Labor’s FLSA framework uses the identical weekly reset, so any biweekly averaging logic violates both regimes. The Korea Herald confirms the 52-hour rule applies to workplaces with five or more employees. Pay frequency is an administrative convenience, not a legal averaging window.

Practitioner threads describe the same discovery pattern repeatedly. One r/Payroll thread reports: “Our ERP averaged hours across the pay period and we had to issue retro checks for 14 employees — the state audit caught it, not our own review.” The audit did not flag a miscalculation of the overtime rate; it flagged the absence of any overtime at all in a heavy week. The system’s averaging logic had silently converted a 60-hour week into a 40-hour week, and the employer paid the difference only after a regulator demanded the records.

Case Study: The 55-Hour Audit

Below, we compare the main approaches side by side, starting with the most accessible option and working up to the premium path. Each option includes concrete costs and trade-offs so you can pick the one that fits your constraints.

Option A runs the payroll as-is: week one at 55 hours and week two at 25 hours. The system pays 15 overtime hours for week one (55 minus 40) at 1.5x, and zero for week two. The arithmetic is correct, but the three-hour breach of the 52-hour cap creates statutory exposure beyond the wage premium, depending on local enforcement.

Option B applies the correct weekly math without changing the schedule. Week one at 55 hours produces 15 overtime hours (55 minus 40), paid at 1.5x, while week two at 25 hours produces none. The problem is not the arithmetic but the exposure—the three-hour cap breach can trigger statutory penalties beyond the wage premium, depending on local enforcement.

Option C reassigns three hours from week one to week two before the work happens. Week one becomes 52 hours with 12 overtime hours; week two becomes 28 hours with zero. This eliminates the cap breach while preserving the same total hours across the two-week period.

The decision rule is blunt: if the weekly total can be shifted without breaking the workflow, shift it. According to the U.S. Department of Labor’s overtime calculator, the 1.5x multiplier applies uniformly to hours over 40, and the only variable is whether the cap breach adds statutory penalties under local law. That is the lever most payroll managers miss—they treat the cap as a ceiling to monitor rather than a schedule to design around.

One edge case worth checking before the next run: split shifts and on-call hours. Under the 52-hour cap, all hours during which the employee is “suffered or permitted to work” count toward the cap, including on-call time if the employee is not free to use the time for personal purposes. A developer on call from home who cannot leave the laptop counts those hours. Most biweekly systems miss this because they only count logged-in time, not standby time. Verify the configuration against a two-week test case before the next payroll run, not after the audit letter arrives.

Lessons Learned From Payroll Failures

The most common audit finding under a 52-hour cap is not a math error at all—it is a policy gap. Employers who never documented the daily trigger or the weekly reset in their employee handbooks create a compliance hole that no spreadsheet formula can patch. When a wage claim lands, the first question from a labor inspector is not "what did your payroll system calculate" but "what did your handbook promise." If the written policy is silent on how overtime is derived, the inspector defaults to the statutory maximum in the employee's favor.

Before you run the next payroll cycle, verify three things in sequence. First, confirm the overtime formula subtracts 40 from total hours worked, not 52—the enforcement ceiling is not the subtraction baseline. Second, check that daily triggers are evaluated before the weekly total is computed; a system that only runs the weekly check will miss the daily obligation entirely. Third, split the pay period into individual workweeks and evaluate each one independently. A biweekly payroll run that aggregates hours across two weeks will systematically underpay overtime in the first week and overpay in the second, and the error compounds silently.

The Korea Herald reports that workplaces with as few as five employees became subject to the rule, which is why small businesses dominate audit findings: they are the most likely to run manual payroll on a free Excel template rather than a configured system. One r/korea HR thread describes exactly this failure mode: "We used a free Excel template from a blog and it subtracted 52 from total hours—we underpaid everyone for six months before an employee filed a complaint." The template author had confused the cap with the trigger, and the employer paid the price.

To audit your system against this, export the weekly hours report from the time clock and compare it line-by-line against the overtime line item on the payroll register. If it does not, the pay period is being averaged, and you are not compliant.

A second common failure is double-counting hours. If an employee works 60 hours in a week under a 52-hour cap, the employer must pay 20 hours at 1.5x (60 minus 40), not 12 hours at 1.5x plus 8 hours at 2x, unless a state law specifically mandates double-time. Some payroll administrators assume the cap creates a two-tier structure—regular overtime up to 52, then a higher premium beyond it.

Department of Labor provides a free overtime pay calculator and fact sheets that verify the 40-hour FLSA threshold math. Use it as a cross-check on your own calculations, not as a substitute for legal review of your jurisdiction's specific cap. The DOL tool confirms the baseline subtraction; it does not tell you whether your state or country imposes a daily trigger, a lower cap, or a double-time mandate. Those variables live in your local labor code, and they are exactly the details that free templates and generic payroll blogs get wrong.

One narrow exception worth knowing: for semiconductor R&D in South Korea, the overtime cap is extended to 56 hours per week, as confirmed by the Ministry of Employment and Labor. That is an exception, not a general rule, and it applies only to a designated industry segment. If you operate outside that pilot, assume the standard cap applies and configure your system accordingly.

The final rule is blunt: if your payroll system cannot independently evaluate each workweek and apply the 40-hour subtraction, you are not compliant—regardless of whether the cap is 52, 48, or 60. The cap number changes the enforcement ceiling, not the math. Fix the subtraction, document the daily trigger, and split the pay period before the next run. The audit letter is cheaper to prevent than to answer.

What to do next

Use the official tools and primary sources referenced throughout this guide to verify the math for your specific jurisdiction and employment classification. The key is to confirm the overtime trigger (40 hours) and the enforcement ceiling (52 hours) independently, rather than relying on a single summary.

Also worth reading: AI Contract Analysis How $17/Hour DC Minimum Wage Sets New Standards for Labor Agreement Reviews in 2024 · NCIC Warrant Retention Protocols Understanding the 24-Hour Hit Confirmation Requirements for AI Contract Systems · North Carolina's 120-Hour Rule in Intestate Succession A Critical Analysis of Survivorship Requirements · 7 Critical Limitations and Legal Boundaries for Attorney-in-Fact Actions Under Digital POA Systems in 2024

Sources: dol, govinfo, usa, wikipedia, joins