Five configuration places Korean overtime premiums often drift

Overtime disputes rarely begin with a blank payroll application. They begin with a setting that almost matches the posted schedule—until a weekend, a holiday, or a night rotation arrives.

1. Weekend codes that inherit weekday rates

Some applications store Saturday and Sunday as separate calendar types but allow a fallback rate when the custom code is missing. Audits often find the fallback still pointing at weekday overtime.

2. Night differentials that stop at midnight

When a shift crosses midnight, premium windows can split across two calendar days. If only the first segment carries the night flag, the second segment silently drops.

3. Holiday premiums stacked incorrectly

Public holiday work may require both holiday and overtime treatment depending on hours. Configuration that applies one or the other—but not the combination your policy requires—shows up clearly in holiday-month samples.

4. Allowance codes excluded from the overtime base

Certain allowances belong in the base used to compute premiums. If those codes are marked “display only,” the payslip looks complete while the premium under-calculates.

5. Manual overrides without an expiry

Temporary rate overrides entered during a busy season sometimes remain active. Periodic reassessment is the practical way to catch them after the season ends.

If several of these sound familiar, a wage rule gap review can isolate the components without opening a full multi-module audit.