Worked example: Wage Backpay in Philippines

Example inputs

Run this scenario in DocketMath using the Wage Backpay calculator.

This worked example shows how to estimate wage backpay in the Philippines (PH) using DocketMath: Wage Backpay—focusing on inputs you can actually measure and outputs you can explain.

Scenario (fictional but realistic)

• Worker: Mark (employed by a retail business)
• Work arrangement: Full-time employee
• Issue: Employer failed to pay the minimum wage (and corresponding wage differentials, where applicable) for a period
• Backpay period: March 1, 2023 to August 31, 2023
• Pay schedule: Monthly pay
• Days actually worked each month: Mark worked 26 days per month on average (you can also model by daily rates if your records support it)
• Current wage vs. required wage: The required minimum wage changed during the period due to wage-order timing and the applicable wage schedule in PH (jurisdiction-aware modeling)

Inputs you’ll enter in DocketMath (wage-backpay)

Use these kinds of inputs (field names may vary slightly depending on the tool UI):

1. Backpay start date: 2023-03-01
2. Backpay end date: 2023-08-31
3. Wage basis: Monthly
4. Worked days per month (or rate basis): 26 days
5. Region / locality: NCR (Metro Manila)
6. Wage standard used: Minimum wage compliance
7. Actual paid wage rate: PHP 550/day (the employer’s paid rate during the backpay period)
8. Required minimum wage schedule: DocketMath applies the jurisdiction-aware wage order minimums for the Philippines for each sub-period inside your date range.
9. Any allowances treated as wage: None (kept simple for this example)

If you don’t know all details, use the best-documented rate and the exact dates you can support. The tool’s outputs depend heavily on (1) the dates and (2) the rate you enter as “actual paid.”

Example run

Below is a sample run showing what the tool is doing conceptually. (The tool’s exact line items and rounding can differ slightly, but the structure should match.)

Run the Wage Backpay calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

1) Split the period into sub-periods with different required minimum wage levels

DocketMath accounts for changes in the applicable minimum wage during the requested date range.

• You provide region/locality (here, NCR)
• You provide start/end dates (here, Mar 1 to Aug 31, 2023)
• The tool then treats the timeline as a set of sub-periods where the required minimum wage level is the relevant one

So you don’t manually compute wage-order effective dates—DocketMath does that internally once the inputs are set.

2) Compute the shortfall per sub-period

For each sub-period, the tool compares:

• Required minimum wage rate (based on PH wage-order minimums mapped to your dates)
• Actual paid wage rate (what you enter)
• Then multiplies the difference by the workdays you entered

Example math structure (per sub-period/month)

• Daily shortfall = Required daily minimum − Actual paid daily wage
• Sub-period backpay = Daily shortfall × workdays

3) Add resulting backpay totals

For illustration, assume DocketMath uses a schedule like this for NCR over your dates:

Estimated wage backpay total (Mar–Aug 2023):
260 + 260 + 260 + 260 + 520 + 520 = PHP 2,080

4) Interpret the tool output (how to think about the number)

In practical terms, the output is measuring:

• If the employer paid below the required minimum wage, the tool quantifies the difference times the days worked.
• If the required minimum wage increases mid-period, the later months show a larger shortfall.
• If you change any key input (region, dates, actual wage rate, or worked days), the total updates immediately.

What to check before relying on the figure

Use this quick checklist:

Sensitivity check

Wage backpay estimates are usually sensitive to a few inputs. Here’s how the estimate changes when you adjust the most common variables in DocketMath: Wage Backpay.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

A) Change the actual paid wage rate

If Mark actually received PHP 540/day instead of PHP 550/day, the daily shortfall increases.

• For required min 560/day months: 560 − 540 = 20 (was 10)
• For required min 570/day months: 570 − 540 = 30 (was 20)

Rough impact vs. baseline (PHP 2,080):

• Mar–Jun (4 months): each month 20 × 26 = 520 → 4 × 520 = 2,080
• Jul–Aug (2 months): each month 30 × 26 = 780 → 2 × 780 = 1,560

New rough total: 2,080 + 1,560 = PHP 3,640
So the estimate increases by PHP 1,560 (about +75%) in this example.

B) Change worked days per month

If Mark worked 24 days per month on average (instead of 26):

• Every monthly figure scales by 24/26 ≈ 0.923
• Baseline total PHP 2,080 becomes about: 2,080 × 24/26 ≈ PHP 1,920

C) Move the end date by one month

Extending from August 31, 2023 to September 30, 2023 adds another sub-period.

• The added backpay is essentially:
  (Required min for September − Actual paid) × workdays in September
• If September’s required minimum is higher than August’s, the incremental amount is typically larger (but it depends on the schedule DocketMath applies for the dates you enter).

Why exact dates matter: DocketMath is performing “piecewise” calculations across changes in minimum wage levels.

D) Region mismatch can dominate the result

If you accidentally pick the wrong region/locality, DocketMath applies different minimum wage levels. Even a small difference like PHP 10/day becomes meaningful:

• 10 × 26 = PHP 260 per month impact
• Over multiple months, that quickly adds up

Related reading

• Wage & Backpay Calculator Guide for Alabama
• Wage & Backpay Calculator Guide for Arizona
• Wage & Backpay Calculator Guide for Colorado