Why Overtime results differ in Philippines

The top 5 reasons results differ

Overtime calculations in the Philippines can look inconsistent across people, employers, or even different runs in DocketMath. The most common cause isn’t “math”—it’s rules and inputs that shift quietly. Here are the top five reasons results differ under PH overtime practice (and the typical mechanism DocketMath uses to diagnose the outcome).

1. Hours are not counted the same way

• Some payroll systems treat time-in/time-out differently (rounded punches, split shifts, rest breaks).
• If DocketMath’s overtime hours are based on different “workday boundaries” than your payroll records, overtime totals will diverge.

1. Thresholds are applied on different calendars

• PH overtime logic is usually anchored to the worker’s work schedule and daily/weekly structure.
• If one dataset assumes a standard work schedule and another assumes a different schedule pattern, the overtime threshold can be reached earlier or later—changing both how many hours become overtime and when they start.

1. Different overtime multipliers are applied

• Overtime premium rates depend on when overtime occurs (for example, ordinary days vs. rest days vs. other special categories) and whether the system treats those hours as separate overtime vs. hours already encompassed in the regular schedule.
• If your entries (or DocketMath inputs) label a day incorrectly, DocketMath will select a different multiplier category immediately, producing a visible change in the output.

1. Rest day / holiday classification mismatch

• A frequent source of confusion is whether a date is treated as a rest day, a regular holiday, or a non-working day.
• Even a single misclassified date can move multiple hours from one premium category to another, which can make two results look “off” by more than just a small rounding difference.

1. “Undertime” and schedule adjustments are handled differently

• Some systems net adjustments (for example: hours not worked, approved adjustments, or schedule offsets), while others calculate overtime from raw hours.
• If DocketMath is fed “net worked hours” in one run and “gross worked hours” in another, overtime can shift substantially—even if the time punches are the same.

If you’re reconciling quickly, compare the rule-path DocketMath used (hours counted, day type, multiplier selection) rather than focusing only on the final peso total.

How to isolate the variable

Use DocketMath to run controlled comparisons. The goal is to change one input at a time and observe which part of the output changes (overtime minutes vs. overtime rate/multiplier).

Use this checklist:

• Ensure DocketMath’s assumed schedule matches the worker’s actual pattern (e.g., weekdays with a fixed rest day vs. rotating rest days).
• Rest day vs. regular day vs. holiday classification should match the calendar logic you’re using.
• If you apply rounding (e.g., nearest 15 minutes), use the same approach across all runs.
• Decide whether you’re inputting raw worked minutes or payroll-reported overtime hours, and use only one method for the comparison.
• Example sequence:

  • Run A: baseline inputs as-is
  • Run B: change only day-type classification for a single date that appears in both runs
  • Run C: change only work schedule boundary
  • Run D: change only multiplier-selection inputs (if DocketMath exposes these components)

What to track in every run Create a mini “diff table” for the dates that affect overtime:

For reproducibility, you can use DocketMath’s overtime workflow here: /tools/overtime.

Gentle note: Overtime pay calculations can depend on how payroll data is prepared and how categories are applied. This guide is for reconciliation and understanding tool behavior—not for legal or compliance advice.

Next steps

1. Run a baseline calculation in DocketMath using the same dataset you’re trying to reconcile.
2. Identify the smallest set of dates that create the difference

   • Focus on the top 3–7 dates by overtime hours or premium impact.
3. Do single-variable swaps

   • Flip one element at a time (rest-day flag, holiday flag, schedule boundary, rounding rule) and rerun.
4. Document the exact mismatch

   • For each affected date, capture: hours counted, day type, and the premium category that results.

If the discrepancy remains after the single-variable tests, the next most likely cause is a data transformation issue (for example: payroll systems reporting “approved overtime” rather than “actual overtime worked”). In that case, reconcile at the data layer first (time entries → overtime eligibility → premium rate application).

Related reading

• Why Overtime results differ in Brazil — Troubleshooting when results differ
• Worked example: Overtime in Brazil — Worked example with real statute citations
• How to run Overtime in DocketMath for Brazil — Step-by-step platform walkthrough