Why Wage Backpay results differ in New York

The top 5 reasons results differ

Run this scenario in DocketMath using the Wage Backpay calculator.

When you run wage backpay calculations in New York (US-NY) with DocketMath, it’s common to see different outputs—even when two runs are based on what seems like the “same” dispute. In practice, most mismatches come from input differences, date/timing choices, or New York–aware limitation logic that changes what portion of the backpay period is counted.

Below are the top 5 causes of different results, written as a diagnostic checklist so you can quickly identify the driver in your own worksheet.

1. **Which backpay window you allowed (lookback / limitation window)

   • DocketMath’s wage backpay calculator typically limits the accrual window using a limitations reference date you provide (or a date tied to your input workflow).
   • The New York data you provided points to a 5-year general statute of limitations. Specifically, N.Y. Crim. Proc. Law § 30.10(2)(c) states a 5-year general period in the cited subsection.
   • Important: your note says no claim-type-specific sub-rule was found. So, treat this as a general/default 5-year reference, not a specialized wage-backpay limitation rule tailored to a specific claim theory.

2. Different “start date” assumptions

   • Wage backpay calculations need a start point (for example: date employment ended, date discriminatory conduct began, or the modeled first wage loss date).
   • Even a small shift (e.g., one month) can change the number of pay periods included—especially if your model uses a pay frequency such as biweekly vs. weekly.

3. Pay rate inputs don’t match

   • Results diverge when the wage base differs, such as:

     • hourly rate vs. annualized salary
     • different wage rates before/after a raise
     • different hours per week (part-time vs full-time assumptions)
   • DocketMath will follow the pay structure you input, so two “similar” runs can produce materially different totals if the wage inputs are not identical.

4. Mitigation / earnings offsets

   • Many backpay models apply offsets for earnings from other work during the backpay period.
   • If one run includes an earnings offset schedule (and the other does not), the backpay total can swing dramatically.

5. Interest and discounting settings

   • Some workflows add interest to principal backpay (and some omit it).
   • If one result includes interest and the other does not—or if interest is calculated using different settings—your totals won’t reconcile even if the underlying principal backpay is the same.

Common pitfall: a date mismatch (lookback window or backpay start date) is the most frequent root cause. Once dates differ, later checks for “interest” or “offsets” often won’t fully explain the discrepancy.

How to isolate the variable

Use a one-change-at-a-time approach. The goal is to change one variable, re-run DocketMath, and compare outputs so you can attribute the difference to a specific input.

• Freeze the jurisdiction and tool settings so both runs use the same rule set.
• Compare one input at a time (dates, rates, amounts) and re-run after each change.
• Review the breakdown to see which segment or assumption drives the difference.

Practical step-by-step checklist

• Lock the limitation / lookback settings

  • Confirm the run uses the 5-year general/default period referenced by your provided New York source: N.Y. Crim. Proc. Law § 30.10(2)(c).
  • Since no claim-type-specific sub-rule was identified in your note, apply it as a general reference, not a bespoke wage rule.
• Lock the dates

  • Fix the:

    • backpay start date
    • backpay end date
    • filing/charge date or the limitations reference date used by the calculator
• Lock the pay structure

  • Match hourly vs salary, hours per period, and wage rate(s) across the two runs.
• Lock the offset logic

  • Ensure both runs either include or exclude the earnings/benefit offset treatment your workflow models.
• Lock interest settings

  • Verify whether interest is enabled/disabled and whether both runs use the same interest rate/method settings (if your workflow allows configuring those).

Quick reconciliation order (fastest path)

1. Dates first (lookback window + backpay start date)
2. Then wage rate
3. Then offsets
4. Finally interest

Next steps

1. Run a “locked inputs” comparison

   • Keep all inputs identical except the single suspected variable (commonly the limitations reference date or the backpay start date).
2. Save and compare

   • Store both outputs and note the exact input delta (e.g., “limitations reference date changed from X to Y”).
3. Anchor the limitation assumption

   • Document that your worksheet’s limitation window is based on the provided general reference:

     • N.Y. Crim. Proc. Law § 30.10(2)(c) = 5-year general period
   • Also document that this is treated as general/default, not claim-type-specific, based on your provided note.

Gentle note: This is general guidance to help you debug your modeling inputs; it’s not legal advice.

Related reading

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