How to run Overtime in DocketMath for Philippines

Step-by-step

Run this scenario in DocketMath using the Overtime calculator.

Below is a practical way to run an overtime calculation in DocketMath for Philippines (PH) using jurisdiction-aware rules, and then interpret the result you get from the Overtime calculator.

1) Open the Overtime tool

• Go directly to: /tools/overtime
• If you’re coming from the DocketMath site navigation, open the Overtime calculator under the payroll/time computation tools.

2) Select the PH jurisdiction context

In the tool UI, set:

• Jurisdiction: **Philippines (PH)

This matters because the tool applies Philippine-specific overtime computation logic and assumptions (for example, how it treats “regular” baselines and overtime premium categories).

3) Enter work schedule context (the baseline inputs)

Overtime calculations need a clear definition of what counts as the worker’s regular hours (the baseline) versus overtime hours. In DocketMath, look for inputs such as:

• Overtime basis / work arrangement

  • Common options may include daily hours, weekly hours, or scenario-specific baselines.
• Regular working hours per day

  • Example label: “Regular hours per day” (often 8 hours, depending on the scenario)
• Overtime hours worked
• Overtime day type (category)

  • Common choices include:

    • Regular working day
    • Rest day
    • Special/regular holiday (only if supported in the tool)

How to input:

• If the tool asks for both regular hours and overtime hours, fill in both.
• If it only asks for overtime hours, DocketMath may assume a default baseline—check the result/assumptions panel so you know what it assumed.

4) Provide wage inputs (so DocketMath can compute rates)

Overtime pay depends on the worker’s rate. In the Overtime tool, you’ll typically choose one of these wage input approaches:

• Monthly salary, or
• Daily rate / hourly rate

Use the input format you already have in your payroll records:

• If you have a monthly salary, enter it and let DocketMath convert to the rate basis it uses for the PH overtime scenario.
• If you have an hourly rate, enter it directly to reduce the chance of conversion or rounding surprises.

Also check whether the tool expects:

• Basic pay only vs. other pay components
  If you’re unsure what the tool’s rate basis includes, rely on your internal payroll configuration and use the assumptions summary in the tool to guide you.

5) Choose the overtime type / premium logic (regular vs rest vs holiday)

In Philippine overtime scenarios, the premium can change depending on when the overtime was worked. In the Overtime calculator, select:

• Overtime type / Day type

  • Regular day overtime
  • Rest day overtime
  • Holiday-related overtime (if available)

Then complete any additional prompts the tool requests (examples might include confirming whether the overtime is performed beyond normal working hours and whether it corresponds to a rest day or holiday category).

6) Review the assumptions panel before calculating

Many calculators include a short summary or assumptions panel. Before you click calculate, scan for things like:

• Regular baseline used

  • Example: confirms baseline is 8 hours/day (if that’s your scenario)
• Rate used

  • Confirms whether the tool is using hourly/daily logic derived from your wage input
• Overtime category selected

  • Confirms the tool matched your “regular vs rest/holiday” selection
• Multiplier/premium behavior

  • Confirms which premium rules apply for the chosen category

This step helps catch input mismatches early—especially for day type selection and baseline hours.

7) Run the calculation and capture the outputs

Click Calculate (or the tool’s equivalent action). DocketMath should return outputs such as:

• The overtime gross amount (the key figure you’d typically enter into payroll drafts)
• A breakdown (when available), which may show base overtime and any premium component(s)
• The overtime rate(s) or multiplier used

Practical tip: If you need payroll for multiple shifts or workers, run the tool per scenario (per wage basis and per day type) rather than trying to combine categories into one run.

8) Do a quick sanity check (inputs → outputs behavior)

Before exporting, recording, or using the result as a draft figure, do a fast check:

• Hours check: confirm the overtime hours you entered match timesheet data (not total worked hours).
• Rate check: confirm the daily/hourly rate aligns with what the tool derives from your wage input.
• Category check: confirm the day type in the tool matches the actual calendar day type.

Here’s a small checklist table to verify behavior:

9) Use the result as a payroll draft, not final authority

After the calculation:

• Record the overtime gross amount
• Save your scenario inputs (overtime hours, baseline, rate input type, and day type)
• Reconcile with your internal payroll components, rounding rules, and HR/pay policy

If the Overtime tool provides export or a copy breakdown option, use it to maintain a clear audit trail of what you entered and what the tool returned.

Common pitfalls

Below are common reasons overtime numbers can be off when using DocketMath for PH—usually due to input alignment rather than calculation mechanics.

• Using the wrong wage basis

  • Example: entering a monthly salary when you intended to use an hourly rate (or vice versa).
• Mismatch in day type / overtime category

  • If overtime was worked on a rest day or holiday, selecting “regular working day” can materially change the premium logic.
• Confusing “overtime hours” with “total hours worked”

  • DocketMath typically expects overtime hours separately. Entering total hours can inflate overtime dramatically.
• Incorrect regular baseline

  • If your setup uses a regular workday different from a common default (often 8 hours/day), update the baseline input if the tool allows it.
• Rounding surprises during conversion

  • Conversions (monthly → daily → hourly) may round. Check the tool’s displayed assumptions/rates where possible.
• Not matching the shift/timekeeping reality

  • If a shift includes different day categories (e.g., part regular day and part rest day), run separate scenarios rather than mixing categories.
• Overlooking scenario toggles

  • Some tools include toggles like “overtime on rest day” vs. “overtime beyond normal hours.” Ensure toggles match the scenario you’re modeling.

Try it

You can run the calculation immediately using DocketMath’s Overtime tool:

• /tools/overtime

For your first run, use this checklist:

To stress-test your setup, do two quick runs:

1. Same wage, same overtime hours, but flip the day type (regular vs rest/holiday).

   • Expected: overtime gross should change due to different premium logic.
2. Same category, but change overtime hours (for example, 2 hours → 4 hours).

   • Expected: overtime gross should generally scale with hours (subject to rate conversion/rounding).

If the outputs respond to those changes the way you expect, your inputs are likely aligned with how DocketMath expects the Philippine overtime scenario.

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