Inputs you need for Wage Backpay in New York

7 min read

Published April 15, 2026 • By DocketMath Team

Inputs you will need

To calculate wage backpay in New York with DocketMath (jurisdiction US-NY), you’ll want a consistent set of time-and-money inputs. Wage backpay generally comes from comparing what you should have earned during the backpay period versus what you actually were paid, then using that difference to compute the backpay amount.

Because you asked for jurisdiction-aware rules, this walkthrough uses New York’s general/default 5-year lookback for the claim period. Based on the jurisdiction data you provided, no claim-type-specific sub-rule was found, so the guidance below applies the general period as the default. The general statute of limitations for bringing claims is 5 years under N.Y. Crim. Proc. Law § 30.10(2)(c).
Source: https://www.nysenate.gov/legislation/laws/CPL/30.10

Before you start, gather the following inputs:

  • Start date of backpay period

  • End date of backpay period

  • Date of last unpaid/underpaid paycheck (if different from your end date)

  • Your wage type

    • ☐ Hourly
    • ☐ Salary
    • ☐ Commission/bonus (if you’re treating it as part of “wages” for this worksheet)
  • Pay rate

    • For hourly: ☐ hourly rate (e.g., $22.50/hr)
    • For salary: ☐ annual salary (e.g., $65,000/yr) or a monthly figure
  • ☐ **Hours worked (if hourly)

    • ☐ weekly hours, or
    • ☐ actual hours per pay period
  • ☐ **Expected work schedule (if hours vary)

  • Pay frequency

    • ☐ weekly ☐ biweekly ☐ semimonthly ☐ monthly
  • Payments already made for the period

    • ☐ amounts actually paid (gross pay)
    • ☐ any replacement income you plan to net out if you’re handling it consistently in the worksheet/tool inputs
  • Any deductions you will treat consistently

    • ☐ none
    • ☐ retirement/health premiums (use a consistent gross-to-net approach if you choose to model it)
  • ☐ **Pre-judgment interest handling approach (if you want it)

    • ☐ include interest
    • ☐ exclude interest

Gentle reminder: Avoid mixing gross pay and net pay. If your paystub shows gross wages, keep your “expected” and “actual paid” wage figures in gross terms for a consistent backpay comparison.

Quick validation checklist (to reduce mistakes before you enter anything into DocketMath):

InputCommon sourceWhat it controls in the math
Start dateoffer letter, payroll records, case timelinelimits the backpay window
End datelast day worked / last underpayment datedefines total unpaid days/weeks
Pay rateoffer letter, contract, paystubssets expected wages
Hours / scheduletimesheets, time records, payroll historydetermines expected hourly earnings
Payments already madepaystubs, payroll portalreduces backpay to the unpaid difference

Where to find each input

Most wage-backpay inputs come from payroll and employment documents. Here’s where to source each one reliably:

  • **Pay stubs (or payroll portal)

    • Pay rate (hourly rate and/or salary breakdown)
    • Pay frequency
    • Gross amounts actually paid during each pay period
    • The dates covered by each paycheck
  • Time records / timesheets

    • Hours worked per week or per pay period
    • Days worked (helpful if you want a more day-specific mapping)
  • Offer letter / employment contract

    • Annual salary figure or written hourly rate
    • Commission/bonus structure, if applicable and if you’re including it as part of wages
  • Email timeline / HR correspondence

    • Dates when pay stopped, reduced, or was disputed
    • Evidence supporting your proposed start and end dates
  • Your calendar or case notes

    • Useful if you don’t have every timesheet
    • If you reconstruct hours, be consistent about the method you used (so the expected vs. actual comparison stays aligned)

Practical tip to keep things clean: build a simple timeline first.

  • List each pay period in your backpay range.
  • For each period, note:
    • Expected gross pay (based on rate × hours, or an allocation of salary)
    • Actual gross pay received
    • Difference (expected − received)

Even if DocketMath ultimately handles the calculations, this timeline makes it easier to spot gaps, missing pay periods, or mismatched dates before you run the tool.

Run it

Open DocketMath for the wage-backpay calculator here: /tools/wage-backpay .

Then use this workflow:

  1. Select jurisdiction: US-NY

    • This is what makes the calculator apply the New York default 5-year lookback described in your jurisdiction data.
  2. **Enter your backpay dates (start and end)

    • New York default lookback: the calculator should restrict the period to a 5-year general/default statute.
    • Your dataset specifies N.Y. Crim. Proc. Law § 30.10(2)(c) as the general period (5 years) and notes that no claim-type-specific sub-rule was found. So the “default” is the one that applies here.
    • Practically: if your proposed start date is earlier than the allowed 5-year window, DocketMath will compute only the portion that falls within the allowed capped time range.
  3. Add your wage inputs

    • For hourly:
      • enter hourly rate and hours (weekly or per pay period, depending on the tool’s structure)
    • For salary:
      • enter annual (or monthly) salary so the tool can allocate expected wages across the period
    • If you’re including commission/bonus, enter it in a consistent way (for example, an average monthly amount that matches the time window you’re modeling).
  4. Enter payments already made

    • This step typically drives the backpay result.
    • In most backpay models, the output reflects the difference between expected wages and actual wages for the relevant (capped) periods.
  5. Review assumptions before finalizing

    • Confirm whether the tool is treating your numbers as gross wages.
    • Make sure you didn’t accidentally mix pay schedules (weekly vs. biweekly) or mismatch pay-period date ranges.

How outputs change when you adjust inputs

Use these “knobs” to understand your results quickly:

  • Moving the start date forward

    • Usually reduces total backpay, because fewer unpaid weeks fall inside the allowed window.
  • Changing pay rate

    • Typically changes expected wages proportionally (rate × time).
  • Changing hours worked

    • For hourly calculations, this can swing results materially—especially if hours vary.
  • Adding amounts already paid

    • Usually reduces backpay dollar-for-dollar for the periods covered by those payments.

Illustrative mechanics (not legal advice, just math):

  • If expected hourly earnings for a two-week period were $1,800 and you received $600, the unpaid difference for that period would be $1,200.
  • Total backpay sums those differences across the periods that fall within the New York capped calculation window based on your inputs.

Common pitfall: If your start date is outside the 5-year default window, the calculator can only compute what falls within the allowed period. Your result may look “lower than expected” even if the wage inputs are accurate—because the extra time is capped out.

After you run the calculator, save the output. If DocketMath provides a breakdown, use it to verify:

  • the effective calculation date range,
  • pay frequency alignment,
  • and that the “paid” amounts you entered correspond to the same periods you’re modeling as “expected.”

Related reading