Inputs you need for Wage Backpay in Philippines

Inputs you will need

To estimate wage backpay in the Philippines with DocketMath (PH → wage-backpay), collect the inputs that let the calculator reconstruct (1) the covered period, (2) the wage rate for that period, and (3) the gap between what should have been paid vs. what you actually received.

If you’re missing an item, don’t stop—mark what you don’t have and use the closest alternative you can support. DocketMath can still generate a useful range, but your confidence improves as your inputs get more document-backed.

Core wage backpay inputs (recommended)

• Employer name (for recordkeeping)

  • Workplace location (city/province) (useful for organizing documents; not usually a direct wage-rate driver in the calculator)
  • Employee type: rank-and-file / managerial
  • Employment status during the backpay period (examples: “employed but illegally denied work,” “terminated then later found entitled,” etc.)
  • Start date (YYYY-MM-DD)
  • End date (YYYY-MM-DD)
  • If your documents are inconsistent, note whether they reflect daily coverage or only month-level coverage
  • Daily wage and/or monthly wage
  • Basis for computation in your records: daily rate, monthly rate, or a wage component schedule (if your payslips separate items clearly)
  • Working days per week (e.g., 5 or 6)
  • Work schedule type (typical weekday schedule vs. shift schedule)
  • Whether your period includes rest days that may affect premiums
  • Whether wage rates changed between the start and end dates
  • If you have wage-rate-by-date information, list it
  • If not, use a consolidated rate you believe is correct and keep a note of why

Amount you actually received (to find the missing wages)

Backpay calculations typically reflect the difference between “should have been paid” and “was actually paid.” So you’ll want inputs that let DocketMath subtract what you already received.

• Amounts already paid (lump sum or partial payments)
• Dates of payment (even approximate dates are helpful)
• Confirm whether received amounts were wage (earned for work) or other benefits (e.g., reimbursements)
• If unsure, set aside doubtful items for now and run wage-only first—then refine later if your records support it

Wage components to include (depends on your facts)

DocketMath’s accuracy depends on which wage components you choose to include. If you include a component, you should ideally have records that support it for the relevant dates.

• Overtime rate assumption
• Overtime hours (or a way to estimate them) per week or per relevant date range
• Rest day premium (if your evidence involves rest-day entitlements)
• Holiday pay (if your documents cover holiday occurrences and pay)
• Whether they are wage-like and earned for work performed
• Use payroll records to keep treatment consistent across the covered period

Practical pitfall to avoid: Don’t mix gross income with wage-only figures. DocketMath works best when you feed it wage components that belong in the wage base you’re modeling.

(Gentle reminder: This guide is for preparation and estimation, not legal advice.)

Where to find each input

Most wage backpay inputs come from a small set of documents. Use this map to quickly locate what you need.

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) Backpay period (start/end dates)

• ✅ Termination/denial documents

  • Notice of termination (if applicable)
  • Notice of suspension/refusal to deploy you
  • Any directive, decision, or order identifying the entitlement period
• ✅ Payroll cutoffs

  • Last paycheck date you received before the denial/withholding
  • First date you received wages again (if you returned)

How to confirm: Align your start/end dates with payroll cycles and the timing shown in your wage records.

2) Wage rate (daily or monthly) and pay schedule

• ✅ Employment contract / job offer

  • Monthly salary or daily wage rate
• ✅ Payslips

  • Best evidence of what was actually being paid
• ✅ Company pay policy or payroll structure

  • If payroll is built from daily wage plus specific line items, capture the base wage line clearly

How to confirm: Choose a “steady” month (in the middle of your backpay period) if possible, then verify it against other payslips to ensure the rate didn’t shift.

3) Working days and rest days (for premium-related computations)

• ✅ Timesheets / attendance logs
• ✅ Scheduling documents

  • Shift rosters, duty schedules, rotation schedules
• ✅ Company policy

  • Standard working week (5-day or 6-day schedule)

How to confirm: If your schedule changed during the period, split the backpay period into date ranges that match the schedule changes (when you model your inputs).

4) Actual payments received (to compute the gap)

• ✅ Payroll history

  • Identify partial releases or interim wage payments during the covered period
• ✅ Bank statements / remittance proofs

  • Useful when payslips don’t reflect the full payment picture
• ✅ Settlement documents

  • If there was a partial settlement, record the amount and date so you don’t double-count

5) Wage components (overtime, holiday pay, premiums)

• ✅ Payslips with breakdown

  • Overtime line items
  • Rest day/holiday premium line items
• ✅ Attendance/time records

  • Overtime hours
  • Work performed on rest-day/holiday occasions

Run it

After you gather your inputs, run the calculator in DocketMath.

1. Open /tools/wage-backpay
   **DocketMath Wage Backpay tool
2. Enter:

   • Backpay start date and end date
   • Wage rate basis (daily or monthly) and the wage amount
   • Working schedule assumptions

     • Working days per week
     • Include rest-day/holiday settings only when supported by your documents
   • Actual wages already paid (if any)
   • Select which wage components to include:

     • base wage
     • optionally overtime and/or premiums (only if supported by your records)
3. Review outputs:

   • Total backpay estimate
   • Component breakdown (base vs. any premium/extra components computed)
   • Net amount after subtracting already-paid wages

How outputs change when you adjust inputs

Use these expectations to sanity-check results:

If you want a cleaner approach, run in stages:

• Pass 1: Base wage only
• Pass 2: Add premiums (rest day/holiday) only if your records support them
• Pass 3: Add overtime only if you have overtime hours/rates consistent with your evidence

Related reading

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