How to calculate Overtime in Philippines
9 min read
Published April 15, 2026 • By DocketMath Team
Quick takeaways
Run this scenario in DocketMath using the Overtime calculator.
- In the Philippines, overtime (OT) pay is generally calculated using a multiplier of your regular hourly rate, with different rates depending on when the overtime is worked (e.g., rest day, special holiday, regular holiday, and other day-type categories).
- DocketMath’s overtime calculator (PH) helps you:
- convert your salary structure into the correct hourly base rate
- apply the right overtime multiplier based on the day type and whether night hours overlap your OT
- produce totals, including OT pay per classification (regular workday vs. rest day vs. holiday types).
- Your results are only as accurate as your inputs—especially:
- your OT base rate (the regular wage basis your employer uses)
- how you split OT by day type and night overlap (if applicable).
- Your time records drive the calculation. If OT hours are recorded incorrectly, the math will be wrong even if the multipliers are correct.
Warning: Don’t “estimate” OT hours. In practice, OT pay disputes often hinge on which hours were actually worked/authorized and how they were recorded. Use your timekeeping/DTR records as the starting point, then run the calculation with those exact hours.
Inputs you need
Before you open DocketMath’s overtime tool, gather the information needed to determine (1) your hourly base rate and (2) the overtime multiplier for each portion of time.
Use this intake checklist as your baseline for Overtime work in Philippines.
- jurisdiction selection
- key dates and triggering events
- amounts or rates
- any caps or overrides
If any of these inputs are uncertain, document the assumption before you run the tool.
1) Your wage and the OT computation basis
Choose the wage basis that matches how your payroll computes OT. Common options:
- ☐ Daily rate (if your payroll is based on days)
- ☐ Monthly salary (most common)
- ☐ Hourly rate (if provided in your arrangement)
- ☐ Other components that your employer includes/excludes in the OT base
What to have ready
- Your current rate (daily or monthly)
- Any relevant wage components that your employer uses as part of the OT computation base (if your payroll policy specifies them)
How your input affects the output
- If your OT base rate is higher, OT pay for every line rises proportionally.
- If you enter a figure that isn’t the OT “regular wage” base (for example, a gross amount that includes allowances not treated as regular wage for OT), the computed OT can be overstated.
2) Overtime hours by classification
You’ll typically enter multiple OT lines. For each line, prepare:
- ☐ Date or date range (optional, but helpful for sanity-checking totals)
- ☐ OT hours for that classification
- ☐ Day type:
- ☐ Regular workday
- ☐ Rest day
- ☐ Special holiday
- ☐ Regular holiday
- ☐ Time window details if your schedule crosses into night hours
3) Whether the overtime overlaps night hours
Night hours (often reflected through night differential rules) can affect how overtime should be treated.
To compute correctly, you need:
- ☐ Night overlap hours (hours worked during the night hours portion, as captured in your timekeeping policy/employer coding)
How to confirm
- Check your timekeeping system for how it codes night hours/night differential, or review how your DTR reflects those segments.
- DocketMath can be set up so your entered night overlap is reflected in the calculation, keeping the workflow transparent.
4) Your own recordkeeping notes (authorization/audit trail)
You usually don’t need this to “click calculate,” but it’s useful if you later reconcile with payroll or challenge/verify amounts:
- ☐ Whether OT was authorized or within company policy
- ☐ Whether OT was required vs. voluntary (for internal documentation)
Note: DocketMath focuses on computation of pay amounts based on inputs. It can’t confirm whether OT was authorized—your DTR/time records and payroll basis do.
How the calculation works
DocketMath’s overtime (PH) calculator follows a straightforward workflow. Understanding the steps helps you see why a small input change can alter your total.
DocketMath applies the Philippines rule set to the inputs, then runs the calculation in ordered steps. It validates the trigger date, applies rate or cap logic, and produces a breakdown you can audit. If you change any one variable, the tool recalculates the downstream outputs immediately.
Step A: Determine your regular hourly rate base
Most overtime calculations start by converting your regular wage into an hourly equivalent.
Common conversions include:
- Monthly salary → hourly rate
- Daily rate → hourly rate
In practice
- You provide the wage input type (e.g., monthly salary), and the tool converts it into an hourly base used for OT math.
Output impact
- A higher hourly base produces higher OT pay for each OT line.
- Entering the wrong “base rate” (for example, using a gross/total payslip number rather than the OT regular wage base) can inflate results.
Step B: Select the correct overtime multiplier
Philippine overtime pay is commonly expressed as a multiple of the hourly base, and the multiplier depends on when the OT was worked.
DocketMath’s PH overtime calculator is jurisdiction-aware, so the multiplier selection is driven by:
- your entered day type (regular workday, rest day, special holiday, regular holiday)
- your entered night overlap hours (when applicable)
Step C: Multiply by overtime hours and total everything
For each OT line:
- OT Pay (line) = (Hourly Base Rate) × (Overtime Multiplier) × (OT Hours)
Then DocketMath aggregates:
- Total OT pay
- Breakdown by day type/classification (helpful for payroll reporting and reconciliation)
- Subtotals if available
Mini example (illustrative)
- Hourly base rate (computed by the tool): PHP 100
- OT: 2 hours on a regular workday (multiplier chosen for that category)
Then:
- OT Pay = 100 × (regular workday OT multiplier) × 2
Repeat for rest day and holiday OT as separate entries so each category receives its correct multiplier.
Practical checklist (to mirror the calculator workflow)
Pitfall: Entering “total OT hours” without separating by day type is one of the fastest ways to get the wrong OT total, because rest day and holiday overtime multipliers are not the same as weekday overtime multipliers.
Common pitfalls
Even with the right calculator workflow, these issues commonly lead to incorrect overtime totals.
- missing a required input
- using a stale rate or rule
- ignoring calendar or holiday adjustments
- skipping documentation of assumptions
Capture the source for each input so another team member can verify the same result quickly.
1) Using the wrong wage basis (regular wage vs. gross payslip figures)
- If DocketMath requires the regular wage basis for OT computation but you input a different figure (e.g., a gross amount including components not treated as regular wage for OT), the OT output can drift.
Fix
- Use the wage basis your employer/payroll uses for OT computations and enter it consistently.
2) Mixing rest day and holiday hours in the same entry
- Rest day OT and holiday OT typically carry different multipliers.
Fix
- Enter separate lines for each classification:
- regular workday OT
- rest day OT
- regular holiday OT
- special holiday OT
3) Forgetting night overlap hours (when your OT crosses into night hours)
- If your overtime spans into night hours, the rate treatment may need adjustment.
Fix
- Use your DTR/timekeeping records to identify night overlap.
- Enter the night overlap explicitly (or split your OT segments) so the calculator can reflect it.
4) Estimating OT hours instead of using recorded hours
- OT disputes often focus on which hours were actually worked and recorded.
Fix
- Use the actual recorded OT hours from your DTR/timekeeping, then calculate.
5) Rounding differences
- Converting monthly → hourly and then multiplying by multipliers can create small discrepancies depending on rounding behavior.
Fix
- Use the same rounding approach your payroll uses.
- If the tool shows intermediate values, keep extra precision for intermediate steps and only round at the end if your policy requires it.
Warning: If your payroll rounds OT to the nearest 15 minutes (or similar), but you enter OT hours rounded differently, totals can differ even with correct multipliers.
Sources and references
This guide is for computation workflow planning and understanding. It does not replace advice from qualified legal or labor professionals about your specific circumstances.
For general Philippines overtime compensation rules (coverage may vary depending on the exact OT scenario), these are commonly referenced sources:
- Presidential Decree No. 442 (Labor Code of the Philippines) (as amended), including provisions on hours of work, overtime pay, and related wage rules.
- Department of Labor and Employment (DOLE) issuances and implementing rules that address overtime compensation, including guidance on day types (workdays/rest days/holidays) and night shift treatment as applied through payroll/timekeeping.
If you want to map your scenario to the most relevant rule set, focus on:
- the day type (regular workday vs. rest day vs. holiday)
- any night overlap
- the wage base used for OT computation in your payroll policy
Next steps
- Open the DocketMath overtime tool: /tools/overtime
- Select your wage input type:
- monthly salary or daily/hourly rate (depending on what you have)
- Enter OT lines by day type and hours.
- Include night overlap hours where applicable
- Review the computed totals:
- check line-by-line classification multipliers
- validate your hours and whether rest day/holiday splits are correct
- Save/export your calculation output for reconciliation against your payslip
If you need help validating payroll inputs before running OT math, you can also check:
- /tools/salary
- /tools/deductions
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
