Overtime rule lens: Philippines

The rule in plain language

Run this scenario in DocketMath using the Overtime calculator.

In the Philippines, “overtime” is generally paid when an employee works beyond the applicable limit on hours of work in a day or week under the Labor Code of the Philippines and its implementing rules. The core statutory baseline is commonly anchored to Articles 87 and 88 of the Labor Code of the Philippines (Presidential Decree No. 442, as amended), with overtime premium mechanics further clarified through administrative issuances and implementing regulations.

A practical way to think about overtime pay for calculations is:

• Overtime pay applies when work exceeds the employee’s regular hours (for example, an 8-hour day / 40-hour week arrangement, or another recognized schedule under Philippine labor law and implementing regulations).
• Premium pay is required for overtime worked—typically a percentage increase over the employee’s regular wage. In practice, the premium may differ based on the time category (for example, ordinary workday overtime vs overtime on a rest day and/or holiday).
• “Work” and “hours” matter: the focus is on actual hours worked, not just the scheduled plan.

What to anchor in your calculation

When you build an overtime calculation in a tool like DocketMath, you typically need:

• Regular wage basis (e.g., daily or hourly equivalent)
• Overtime hours
• Overtime category (ordinary workday vs rest day/holiday)
• Whether the overtime falls on an ordinary workday under the statutory schedule or on a rest day/holiday category
• Any exemptions or special arrangements that may affect how overtime is treated for that employee

Because different categories often use different premium rates, the cleanest workflow is usually category-based: compute ordinary overtime pay separately, compute rest day/holiday overtime pay separately, then sum.

Why it matters for calculations

Overtime isn’t just “multiply hours by a rate.” In the Philippines, small input choices can shift results a lot—especially because you’re applying a premium on top of a regular wage basis and the premium can vary by category.

1) The wage base affects every overtime hour

Overtime premiums are calculated as an uplift over the employee’s regular wage (often derived from daily or hourly wages). If the wage base you enter doesn’t match how the calculator expects it, the computed overtime can be materially off.

Common wage-base pitfalls include:

• Using monthly pay as if it were daily (or vice versa)
• Confusing gross pay (which may include non-regular components) with the regular wage concept used for overtime computation
• Entering the wrong “regular wage” basis if your payroll uses allowances or components that may not be treated the same way in the statutory computation

2) The time category changes the premium percentage

Overtime rules in the Philippines often create different premium outcomes for:

• Overtime on ordinary workdays (commonly referenced as an additional premium over the regular wage for ordinary overtime)
• Overtime on rest days/holidays (often with a higher premium)

This is why you should label overtime hours by category before calculating. If you lump all overtime into one bucket, you can underpay or overpay depending on the mix.

3) Rounding and “time in hours” assumptions

Many payroll and timekeeping systems convert minutes into decimal hours. If the timestamps or time capture method doesn’t match what the tool expects (for example, rounding 1:05 differently across systems), outputs may drift.

4) You may need separate lines across different days/categories

If overtime spans multiple dates that belong to different categories (ordinary workday vs rest day/holiday), you’ll typically want separate line items per category to keep the computation auditable and easier to review.

Quick audit checklist

Use this checklist to sanity-check the inputs you’ll feed into DocketMath:

Use the calculator

DocketMath’s overtime tool is designed to compute overtime pay using jurisdiction-aware inputs for the Philippines (PH).

Run the Overtime calculation in DocketMath, then save the output so it can be audited later: Open the calculator.

Capture the source for each input so another team member can verify the same result quickly.

Step 1: Open the tool

Start here: /tools/overtime

Step 2: Enter the wage base

Provide the employee’s regular wage basis in the format the calculator expects (commonly a daily or hourly regular wage).

If your payroll uses a different structure (like a monthly salary), convert it carefully. A common practical approach is to derive an hourly equivalent from the wage basis your payroll uses for overtime computation. (Exact conversion may depend on the employer’s consistent computation method and how your payroll policy defines the divisor.)

Step 3: Split overtime into categories

Enter overtime hours by category where the calculator supports it, for example:

• Ordinary workday overtime hours (e.g., 2.0 hours)
• Rest day/holiday overtime hours (e.g., 5.5 hours)

If you only know a single total overtime number, you’ll generally need either:

• A reasonable estimate of the split by category (best if backed by time records), or
• To categorize the overtime as specifically as your timesheets support

Step 4: Review outputs and compare to your expected structure

After you run DocketMath, check that:

• The tool applies a higher premium to rest day/holiday overtime hours (if that’s what your inputs indicate)
• The output aligns with the sum of category line items if the tool shows a breakdown

Example workflow (category-based)

Here’s a sample setup you can mirror in DocketMath:

• Regular wage basis: ₱750/day
• Ordinary overtime hours: 2.0
• Rest day/holiday overtime hours: 5.5

Then the conceptual structure is:

• Ordinary overtime pay = (base rate × ordinary premium factor × ordinary hours)
• Rest day/holiday overtime pay = (base rate × rest/holiday premium factor × rest/holiday hours)
• Total overtime pay = ordinary + rest/holiday

You don’t have to manually compute the factors to validate the result—your main goal is to confirm the tool’s category logic matches your case inputs.

Step 5: Do “what-if” checks (inputs → outputs)

Use these quick checks to understand how the computed overtime changes:

• Increase ordinary overtime hours by 1.0 → total overtime should increase by a predictable amount based on the ordinary premium applied to your wage base.
• Move hours from ordinary to rest/holiday category → total overtime should jump if the rest/holiday premium is higher.
• Increase the regular wage basis by 10% → overtime should change roughly proportionally, since the premium is applied on top of the regular wage basis.

A practical controls layer for audit readiness

If your overtime comes from timestamped time entries:

• Convert timestamps into decimal hours consistently (e.g., 1:15 → 1.25 hours)
• Keep a log linking each time segment to its overtime category
• Store the mapping between your timesheet dates and the categories you input into DocketMath

This makes it much easier to explain how the computed overtime pay was derived.

Sources and references

Start with the primary authority for Philippines and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• Primary authority reference

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