Why Wage Backpay results differ in Idaho

The top 5 reasons results differ

Run this scenario in DocketMath using the Wage Backpay calculator.

If you run DocketMath’s Wage Backpay calculator for Idaho (US-ID), you may get different numbers than a coworker, prior case summary, or another tool. In Idaho, the spread usually comes from timing and scope—even when people think they’re entering the same wage facts.

Below are the five most common causes of differing results for Idaho backpay-style calculations, anchored to the Idaho general statute of limitations rule you’ll see reflected in the calculator output.

1) The calculation start date is off by days (or months)

Idaho’s general SOL is 2 years (Idaho Code § 19-403). If one person selects a claim-related start date like termination date, while another uses date discriminatory act occurred or date wages stopped, they’re effectively changing which portion of pay falls inside the 2-year lookback window.

What changes in results:

• Backpay included = wages within the SOL lookback window
• A few weeks’ shift can materially change totals when pay is regular

2) End date differences (e.g., “today” vs. “trial/settlement month”)

Even with identical start dates, using different end dates (the date you stop accruing backpay) changes totals.

Typical scenario:

• One run stops at settlement approval date
• Another stops at last day employed
  Same SOL window, different accrual horizon.

3) Different assumptions about how wages are measured

Backpay calculations often depend on a wage model, for example:

• hourly rate × hours expected
• salary × days/periods
• included compensation components (base pay vs. commissions vs. shift differentials)

When two calculations use different wage components, you’re no longer comparing apples to apples—even if the SOL window is identical.

4) Missed offsets (earnings mitigation or comparable wages)

Some workflows subtract other wages the claimant earned during the backpay period (commonly discussed as mitigation/offset concepts). If you include offsets in one run and omit them in another, the net result can diverge sharply.

What changes in results:

• Gross backpay (before offsets) may look similar
• Net backpay (after offsets) can swing significantly depending on interim work during the period

5) Confusion about “eligible period” versus “entire employment gap”

The Idaho general SOL doesn’t usually justify “all missed wages from the earliest gap” by default. In practice, the 2-year lookback matters—so the calculator output often filters to a window defined by your selected date trigger and the 2-year SOL period.

Practical effect:
Two people can agree on the overall employment gap length (e.g., 18 months), yet still get different results if one applies a different trigger for the 2-year window.

How to isolate the variable

To pinpoint why two Wage Backpay runs differ for US-ID, use this checklist to make every input identical except one change at a time.

Confirm both runs are using Idaho’s general 2-year period under Idaho Code § 19-403 (no claim-type-specific sub-rule applied in this workflow). Pick one date basis (for example: date wages stopped) and use it in both runs. Use the same end cutoff (settlement month, last accrued month, or the same “as-of” date). Ensure the wage basis is the same (hourly vs. salary, same hours-per-week assumptions, same included compensation components). Either both runs subtract interim earnings or neither does—don’t mix approaches.

A quick diagnostic pattern:

1. Run with your best guess and note the total.
2. Change only one variable (start date first, then end date, then wage model, then offsets).
3. Compare the delta after each change.

Interpretation shortcut:

• If results swing after changing start/end date → timing/SOL window alignment is the driver.
• If results swing after changing wage structure → wage measurement/model is the driver.
• If net amounts vary while gross looks similar → offsets/earnings treatment is the driver.

For convenience, you can start from the calculator workflow here: /tools/wage-backpay.

Next steps

1. Re-run DocketMath and capture:

   • your start date
   • your end date
   • your wage basis (hourly/salary and structure)
   • whether offsets/earnings are included
2. Compare inputs side-by-side with the other person’s run.
3. Build a simple plain-language audit trail, for example:

   • “Start date = date wages stopped”
   • “End date = last date accrued for backpay”
   • “Offsets = included interim earnings by month”
4. If you’re reconciling with a third-party summary (pay statement, internal spreadsheet, or settlement worksheet), treat those documents as input sources and convert them into the same date framework and wage model used in DocketMath.

Gentle reminder: This is not legal advice—just a practical way to understand why calculator outputs differ. If you need case-specific guidance, consult a qualified professional.

Related reading

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