Inputs you need for Overtime in Philippines

5 min read

Published April 15, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Inputs you will need

Run this scenario in DocketMath using the Overtime calculator.

To calculate overtime in the Philippines using DocketMath (jurisdiction: PH), you’ll need a complete set of time and pay inputs that let the tool apply the correct, jurisdiction-aware overtime rules. In practice, HR/payroll teams usually already have these values in timesheets, rosters, and payslips—but they may be spread across multiple systems.

Use this checklist to gather what DocketMath needs for the overtime calculator:

Note: If you don’t classify overtime as “regular day,” “rest day,” or “regular holiday,” your overtime pay output can be materially overstated or understated, because different work contexts trigger different overtime premium rules.

Where to find each input

Below is a practical “where to look” guide to pull these numbers quickly from documents you likely already have.

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

1) Pay rate inputs (hourly/daily)

From: latest payslip, payroll register, or HR compensation sheet
What to capture:
- Hourly rate, or daily rate plus the working-days basis
- Ensure it’s the rate actually used for overtime computation (some companies store a precomputed overtime hourly rate rather than deriving it on the fly)

Tip for accuracy: If your payslip shows “basic pay” but your payroll has a separate “computed overtime rate,” use the computed overtime rate so your result matches internal expectations.

2) Overtime dates

From: timesheet, attendance system, or daily log
What to capture:
- The exact calendar dates when overtime was worked
- If overtime spans midnight, record both date anchors—DocketMath typically relies on the date context to determine holiday/rest-day treatment

3) Overtime duration (per day)

You have two input paths:

Preferred path (clean input):
- From: timesheet overtime column, HR overtime approval form, or payroll extract
- Capture: total overtime hours per day
Fallback path (raw input):
- From: time-in/time-out punches
- Capture: start and end timestamps for the overtime portion you want included

Pitfall to watch: If your time punches include meal breaks or unscheduled idle time, confirm whether your payroll system already netted those out. DocketMath typically uses the hours you provide, not implied deductions—so align the input method with your payroll’s definition of “overtime hours.”

4) Regular working schedule

From: employment contract, roster/schedule memo, or HR handbook
What to capture:
- Regular hours per day (commonly 8)
- The roster’s regular workdays definition (the days the employee/team is normally expected to work)

Why it matters: Overtime logic often depends on distinguishing hours beyond the regular schedule vs. hours that occur during rest days or holidays.

5) Rest day vs. regular holiday classification

From: roster calendar, HR schedule master, or payroll holiday calendar
What to capture:
- Which days are designated as rest days for the employee/team
- Which dates are treated as regular holidays
- How your organization marks these days in attendance (so your inputs reflect the categories DocketMath expects)

Warning: Attendance systems may label “special non-working days” separately. If your team tests or compares outputs across categories, ensure you map those labels consistently to the rest-day/holiday flags you enter.

6) Special work arrangement flags (if applicable)

From: shift schedule, job rules, or payroll setup
Capture when relevant:
- Night shift designation
- Any internal rule that treats certain hours differently from standard overtime

Run it

Once you have the inputs, running overtime in DocketMath is quick.

Enter the inputs in DocketMath and run the Overtime calculation to generate a clean breakdown: Run the calculator.

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

Step 1: Open the overtime calculator

Go to: /tools/overtime

Step 2: Enter schedule and pay context

Start with the inputs that affect interpretation and classification:

Hourly rate (or daily rate basis)
Regular working schedule (hours/day and regular workdays)
Overtime date range
Rest day and holiday flags aligned to your roster/calendar

Step 3: Enter overtime hours

Choose one:

Total overtime hours per day (fastest), or
Time-in/time-out (if you’re inputting shift-level punches)

Step 4: Review outputs by day and totals

DocketMath should provide:

Overtime hours recognized per day (as you entered them)
Computed overtime pay by context (regular day vs rest day vs regular holiday, based on your flags)
A total overtime amount for the selected period

Step 5: Validate with quick sanity checks

Before relying on the result, run these checks:

Check	What to look for	What it suggests
Hours vs. timesheet	Does day-by-day overtime match your attendance/timesheet overtime column?	Confirms hours and date mapping
Rate consistency	Do premiums match the hourly rate basis you supplied?	Confirms correct pay basis
Context correctness	Do holiday/rest day entries produce higher premiums than normal days?	Confirms classification inputs

If you see results that look off:

Recheck the rest day/holiday labeling for the affected dates.
Confirm you entered overtime hours using the same method your payroll uses (e.g., whether break time is already excluded).

Gentle reminder: This tool helps with calculation and planning based on the inputs you provide. For payroll compliance decisions, coordinate with your internal HR/payroll policies or professional advisors.