Why Wage Backpay results differ in Kansas

The top 5 reasons results differ

If you run a wage backpay calculation in DocketMath for Kansas (US-KS), you may still see different results across otherwise similar cases. That’s usually not a “math error”—it’s the effect of Kansas-specific inputs and a jurisdiction-aware time window.

Kansas uses a general/default statute of limitations (SOL) approach for this calculator: 0.5 years (6 months). The period is anchored to K.S.A. § 21-6701. No claim-type-specific sub-rule was found, so DocketMath applies the general SOL period as the default rather than a specialized one.

Here are the top 5 reasons wage backpay outputs differ in Kansas:

1. Different backpay start dates

   • Backpay commonly begins at the date of an adverse employment action, termination, or denial of benefits.
   • A small shift (for example, 30 vs. 60 days earlier) can change how much time falls inside the 6-month default SOL window, which affects the payable total.

2. Different “as-of” (through) dates used to price damages

   • DocketMath needs a calculation “through” date (often the filing date, hearing date, or a settlement cutoff, depending on your workflow).
   • Extending the “through” date can increase the number of payable periods until the SOL truncates the lookback.

3. SOL truncation based on the SOL anchor

   • DocketMath’s Kansas logic applies K.S.A. § 21-6701 using the general/default window of 0.5 years (6 months).
   • If two runs anchor the SOL lookback to different procedural dates, the payable portion of the timeline can change even when employment dates are otherwise identical.

4. Different pay frequency + partial-period handling

   • Weekly vs. biweekly vs. monthly pay can change proration and how many wage “chunks” get credited.
   • In payroll-heavy datasets, mapping the same job timeline to different wage calendars can change the totals.

5. Different mitigation / interim earnings inputs

   • Many wage backpay models net interim earnings against otherwise owed wages.
   • If one run includes wages from a new job and another run excludes them (or excludes a specific month), the final “net backpay” number can shift significantly.

How to isolate the variable

To diagnose why results differ, isolate one variable at a time inside DocketMath. Use this checklist workflow:

A practical method:

1. Run Baseline A using the most defensible timeline (cleanest start date + consistent through date).
2. Duplicate it into Variant B and change only one input category:

   • Date (backpay start or through/as-of)
   • Pay frequency / proration mapping
   • Interim earnings (amounts and months)
   • Wage rate
3. Interpret the delta:

   • If changes mostly track the timeline boundary, the difference is likely due to SOL truncation clipping a different portion.
   • If changes track interim-earnings months/amounts, the delta is likely due to netting.
   • If changes align with partial periods or pay-cadence boundaries, the delta is likely due to proration/pay frequency.

Also check for “silent” differences:

• If two runs effectively use different procedural dates as the anchor for the SOL lookback, you’ll see different payable time windows even with the same employment dates.

(Gentle note: this is a technical diagnostic guide, not legal advice. SOL application can depend on case-specific facts and how dates are selected in the model.)

Next steps

Once you identify the variable, tighten the run so it’s reproducible and easy to audit:

• Write down your assumptions in a short internal note:

  • What you used as the backpay start date
  • What you used as the through/as-of date
  • Whether you included interim earnings, and which months/amounts
• Re-run DocketMath with:

  • The corrected timeline
  • A consistent pay calendar
  • The same Kansas SOL configuration based on K.S.A. § 21-6701 (general/default 0.5 years (6 months))
• If you share results, standardize inputs rather than just comparing outputs:

  • Provide the exact dates and wage cadence used
  • Keep the SOL window consistent with the general/default 0.5-year approach

If you want to validate the numbers and reproduce the workflow quickly, start here: Wage Backpay Calculator.

Related reading

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