Worked example: Wage Backpay in Pennsylvania

6 min read

Published April 15, 2026 • By DocketMath Team

Example inputs

This worked example shows how DocketMath calculates wage backpay using Pennsylvania (US-PA) jurisdiction-aware rules—specifically, the general statute of limitations (SOL).

Because no wage-backpay-specific sub-rule was identified for Pennsylvania within the provided jurisdiction data, DocketMath uses the general/default SOL period. The governing general statute is:

Quick disclaimer: This is a worked example for education and planning. It isn’t legal advice, and real cases can involve additional facts, different claim types, or procedural issues.

Scenario (facts you would enter)

Assume an employee claims wage backpay due to unpaid wages related to a work period that includes the following:

  • Backpay period start date: January 1, 2022
  • Backpay period end date (last unpaid wage date): January 15, 2024
  • Weekly wage rate: $1,200 per week
    • (In this example, we treat the figure as already expressed as a weekly amount, so we do not do separate hourly-to-week conversions.)
  • Filed date (date the claim/complaint was filed): January 20, 2024
  • Any partial week handling: DocketMath prorates coverage when your dates don’t align perfectly with whole weeks, based on its internal time calculation approach.

Why SOL matters in the calculation

Pennsylvania’s general SOL is 2 years. With a filed date of January 20, 2024, wages earned more than 2 years before filing would be outside the recoverable window under the general/default SOL rule used here.

So the “recoverable” window starts:

  • SOL lookback start: January 20, 2022
  • SOL lookback end: January 20, 2024

DocketMath then caps this SOL window to your requested backpay period end date.

Note: DocketMath’s treatment in this example follows the general/default SOL period because no claim-type-specific sub-rule was found in the provided jurisdiction data.

Primary CTA (try it yourself)

Use the tool here: /tools/wage-backpay

Example run

Below is what a wage-backpay run looks like conceptually using DocketMath for US-PA with the 2-year general SOL described above.

Step 1: Determine the recoverable date window

Your requested backpay period is:

  • January 1, 2022 → January 15, 2024

But the recoverable window under the 2-year general SOL (using the filed date) is:

  • January 20, 2022 → January 20, 2024

To find what DocketMath counts, intersect the two ranges:

  • Recoverable backpay window: January 20, 2022 → January 15, 2024

That is the time span DocketMath uses to calculate payable wage backpay in this run.

Step 2: Convert time coverage into payable wage amount

You entered:

  • Weekly wage rate: $1,200/week

DocketMath computes wage backpay by applying the weekly rate to the amount of time (weeks plus any prorated fraction) included in the recoverable window.

Practically, if dates don’t line up with week boundaries, your total usually isn’t a whole number of weeks—so the result reflects prorating.

Step 3: Backpay result (what DocketMath outputs)

Using:

  • the SOL-restricted recoverable window, and
  • the weekly wage rate,

DocketMath produces a wage-backpay total.

Because the exact number of recoverable “week equivalents” depends on the tool’s internal day/partial-week logic, the most useful way to think about the output is:

  • Estimated backpay ≈ (recoverable week-equivalents) × ($1,200/week)

From Jan 20, 2022 → Jan 15, 2024, the window is approximately 103–104 weeks worth of time, minus/adjusted for the specific endpoints.

That yields an illustrative total in the neighborhood of $124k+. For example (illustrative):

  • Estimated wage backpay (SOL-restricted): ~$124,300

The exact dollar figure will be DocketMath’s computed output for these specific dates and its prorating method.

Step 4: What DocketMath is doing under the hood (jurisdiction-aware rules)

In this Pennsylvania example, DocketMath applies:

And since no wage-backpay-specific sub-rule was identified in the provided jurisdiction data, it uses the general/default limitation period rather than switching to a different one.

Sensitivity check

Now let’s see how the output changes when you adjust key inputs. These are the main drivers of swing amounts in backpay estimates: (1) dates affecting the SOL window, (2) the backpay period boundaries, and (3) the wage rate.

1) Changing the filed date (large impact via the SOL window)

Keep the backpay period the same (Jan 1, 2022 → Jan 15, 2024) and keep weekly wage rate = $1,200/week, but change the filed date.

  • Run A (baseline): Filed Jan 20, 2024
    • SOL lookback starts Jan 20, 2022
  • Run B: Filed Feb 20, 2024
    • SOL lookback starts Feb 20, 2022

Expected effect:
A later filed date generally shrinks the SOL lookback window (fewer days fall within the last 2 years), so the recoverable time—and therefore the backpay—typically decreases.

☑ Checklist for your own runs:

  • Is your filed date entered correctly (day/month/year)?
  • Are you consistent about what you use as the backpay period end date (the “last unpaid wage date”)?
  • If your dates aren’t whole-week aligned, does DocketMath prorate as you expect?

Warning: Even modest date shifts (like 10–30 days) can change the dollar amount substantially when weekly wages are high, because the SOL window can cut off earnable time.

2) Changing the backpay period start date (affects what gets clipped by SOL)

If you move your backpay period start date forward, you may be removing time that the SOL would anyway exclude.

Example change:

  • Backpay period start becomes July 1, 2022 instead of Jan 1, 2022
  • Keep filed date Jan 20, 2024

Under this setup:

  • If your backpay start is earlier than the SOL lookback start (Jan 20, 2022), SOL will eliminate that early portion.
  • Once your backpay start is on/after the SOL lookback start, SOL no longer “binds” on the start side, and DocketMath can include the full requested period (subject to the backpay end date).

Expected effect:
Moving the start date forward usually increases or holds the recoverable amount (because less time is lost to SOL clipping).

3) Changing the weekly wage rate (roughly linear)

Backpay totals typically scale close to linearly with the wage rate because the other major variable is the length of the recoverable window.

If weekly wage increases by $200/week, then (approximately):

  • Increase in backpay ≈ $200 × (recoverable week-equivalents)

Expected effect:
Higher wage rate → proportionally higher backpay total.

Related reading