Inputs you need for Wage Backpay in Pennsylvania
6 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
Run this scenario in DocketMath using the Wage Backpay calculator.
If you’re calculating wage backpay in Pennsylvania with DocketMath (jurisdiction US-PA), you’ll get the most accurate estimate when you collect the same core facts a wage backpay claim typically turns on: what wages you were owed, the dates those wages relate to, and what—if anything—you were already paid for those hours.
This page is practical and action-focused: it helps you build correct calculation inputs for DocketMath. It’s not legal advice, and it can’t confirm whether you have a valid legal right, what defenses apply, or which specific claim/filing theory you should use.
Wage-backpay input checklist (US-PA)
Use the checklist below as your input checklist for DocketMath’s wage-backpay calculator.
This is the wage number you expect to apply to the owed work. Choose the basis you want DocketMath to use for the backpay math (for example, straight hourly wages versus another rate method if your records support it). Capture compensable/owed hours (not just “hours you worked” if your theory is that additional hours should have been paid). Enter what you were already paid for the same time periods (if different from what you allege you were owed). This should tie to when the underpayment began for the period you want to model. Often this is the last date you’re claiming underpayment for (commonly the last date covered by the pay stubs you’ll review). Match your records (weekly, biweekly, semimonthly, monthly). This reduces mapping errors when DocketMath groups values into pay periods. Only include overtime amounts when you have a consistent, record-supported method. Don’t guess. If you’re including offsets, you should be able to point to a consistent record basis (e.g., payroll adjustments you can document). This helps keep your output consistent with how you plan to report the estimated backpay.
Pennsylvania time window you should plan around (default baseline)
For this walkthrough, DocketMath guidance uses the general/default limitations period (because no claim-type-specific sub-rule was identified in the brief).
- General SOL Period: 2 years
- General Statute: 42 Pa. Cons. Stat. § 5552
Important: This is a general baseline for planning your modeled date range. Some wage-related timing rules can differ based on the specific theory and forum. DocketMath can calculate from your inputs, but it can’t determine which limitations rule applies to your exact situation.
Where to find each input
To keep things practical, gather inputs from records you already have and keep them internally consistent: one set of dates and hours, one set of wage rates, and one set of pay records.
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) Hourly rate (or effective rate)
Where to look:
- Pay stubs (look for wage rate / “regular rate” or similar language)
- Employment agreement / offer letter
- HR pay history or documentation of rate changes
If your pay rate changed during the period you’re modeling:
2) “Should have been paid” hours
Where to look:
- Timesheets / attendance logs
- Shift schedules
- Emails/texts confirming schedules
- Supervisor logs
- Calendars showing scheduled/required work times
Practical tip:
3) “Actually paid / compensation already received”
Where to look:
- Pay stubs
- Payroll exports
- Direct deposit records paired with pay stubs
Common workflow:
4) Start and end dates
Where to look:
- The pay stub coverage dates (the “from/to” date range on each pay stub)
- The date the alleged issue began (e.g., missed raises, schedule changes, policy changes)
- The last date you’re claiming underpayment for (often aligned to your last pay period included)
How to align with the 2-year general SOL baseline:
5) Pay schedule / aggregation method
Where to look:
- Pay stubs frequency (weekly/biweekly/etc.)
- Payroll system configuration (if you exported payroll history)
Why it matters:
6) Overtime component (if applicable)
Where to look:
- Timesheets showing overtime hours (e.g., over 40 in a week, depending on your wage/overtime framework)
- Pay stubs that separately list overtime wages/line items
If overtime is unclear:
7) Deductions or offsets (if you plan to include them)
Where to look:
- Documented garnishments/withholding adjustments (if relevant)
- Payroll adjustment records
- Written agreements that match what payroll actually did
Pitfall:
Run it
After you’ve collected inputs, run your estimate in DocketMath using the /tools/wage-backpay calculator for US-PA:
- Tool link: /tools/wage-backpay
Enter the inputs in DocketMath and run the Wage Backpay calculation to generate a clean breakdown: Run the calculator.
Quick run sequence
Set the date range
- Enter the start date and end date you want to model.
- Use the 2-year general baseline from 42 Pa. Cons. Stat. § 5552 as your planning guide for the window, unless you have a different documented basis for your own modeling.
**Enter wage rate(s)
- Input your hourly rate for each segment (or one effective rate if appropriate based on your records).
Enter “owed” hours
- Add the compensable/owed hours for each time period.
**Enter “already paid” amount(s)
- Add the wages you received for those same periods so the output reflects net unpaid backpay.
**Apply overtime inputs (if used)
- Include overtime only when you can support the hours/components with your records.
Review and iterate
- Look at the output total and then adjust inputs to test different scenarios (e.g., alternative start dates, different segments for rate changes, or revised hour totals).
How changing inputs affects the result (quick sanity checks)
- Move the start date forward: result typically decreases (fewer pay periods included).
- Increase owed hours: result typically increases (often roughly proportional to the hourly rate, plus any overtime components).
- Increase already-paid amounts/offsets: result typically decreases (net unpaid shrinks).
- Change the hourly rate: result shifts in the affected time period(s) roughly in line with the rate change.
- Add overtime hours (when applicable): result typically increases more than straight-time because overtime wage math differs from base hourly wages.