Inputs you need for Wage Backpay in Missouri

Inputs you will need

Run this scenario in DocketMath using the Wage Backpay calculator.

To calculate wage backpay in Missouri with DocketMath, you’ll need inputs that capture (1) the unpaid wages for specific periods and (2) how far back the calculation can go under the general/default Missouri statute of limitations.

Important: This article uses Missouri’s general/default 5-year SOL period. No claim-type-specific sub-rule was found in the provided materials, so the calculator approach described here should be treated as the default window only.

1) Your backpay start date (or first unpaid pay period)

What to enter: the first date you believe you were not paid correctly (often the first affected pay period).
Why it matters: DocketMath measures unpaid wage amounts across time, and the earliest included period depends on the applicable limitations window.

2) Your backpay end date (or last unpaid pay period)

What to enter: the last date you were not paid correctly (or the date correct pay resumed, settlement occurred, or payments were restored—whatever you’re using as your cutoff).
Why it matters: A later end date increases the number of periods included, which typically increases total backpay.

3) Pay rate type: hourly rate vs. salary (and the basis used)

Backpay depends on how you were compensated.

• If hourly: enter your hourly wage.
• If salary: enter your salary and the work schedule basis you want the tool to use to convert salary into an hourly/weekly-equivalent amount.

Typical outcomes in wage calculators:

• Hourly: hourly rate × hours for each pay period
• Salary: converted period wage × number of periods

4) Hours (and whether they are consistent)

If you’re paid hourly, you’ll generally need hours.

• What to enter: regular hours per pay period (or hours per week), and—if your scenario/tool approach calls for it—any overtime hours used in the model.
• Why it matters: Even small weekly differences (for example, 37 vs. 40 hours) can compound into a large backpay difference over months.

5) Pay frequency / pay period cadence

DocketMath needs to align wages to the correct time “grid.”

• What to enter: weekly, biweekly (every 2 weeks), semimonthly (twice per month), monthly, etc.
• Why it matters: The tool maps your dates into the appropriate wage periods so the math matches how you were actually paid.

6) Amounts already paid for the same period (to avoid double counting)

If you received partial pay, you’ll want to account for it.

• What to enter: any wages already paid that correspond to the periods you’re treating as “unpaid.”
• Why it matters: The goal is to estimate what remains unpaid, not what was originally owed before offsets/partial payments.

7) Statute of limitations (SOL) window (Missouri’s default rule)

Missouri’s general/default SOL period is used here as the default limitations window.

• General SOL period: 5 years
• General statute: Mo. Rev. Stat. § 556.037
• Source: https://law.justia.com/codes/missouri/title-xxxviii/chapter-556/section-556-037/

Clarity note: If your first unpaid wages start date is more than 5 years before your calculation as-of date, the earliest periods may be treated as outside the general/default SOL window, which can reduce the total included by DocketMath.

(Always keep in mind this is an estimate workflow—not legal advice.)

Where to find each input

Here’s a practical place to look for each item in your records. If you’re missing a value, you can sometimes approximate—just be consistent with the assumptions you use.

• Backpay start date

  • Pay stubs / payroll history
  • Timesheet history or schedules
  • Employer emails/letters about pay changes
  • Documentation showing when underpayment began
• Backpay end date

  • Pay stubs showing when correct pay resumed
  • Settlement paperwork / final agreement dates
  • Termination and final paycheck documentation (if using that as a cutoff)
• **Pay rate type (hourly vs. salary)

  • Offer letter / employment agreement
  • Most recent pay stubs (and earlier stubs if the rate changed)
• Hours

  • Timesheets
  • Shift/schedule logs
  • Calendar + known shifts (only if you must estimate)
• Pay frequency

  • Pay stubs (pay period dates)
  • HR/payroll communications
• **Already-paid amounts (for same periods)

  • Pay stubs for the periods being evaluated
  • Lump-sum or retroactive pay records (if applicable)
• **As-of date (if the tool uses one)

  • The date you want the calculation to “run through” (today, settlement date, filing-related cutoff, etc.)

Quick input worksheet (fill before you run DocketMath)

Run it

Go to DocketMath’s wage-backpay tool and enter your values, using the dates and pay details you collected.

Primary CTA: /tools/wage-backpay

Enter the inputs in DocketMath and run the Wage Backpay calculation to generate a clean breakdown: Run the calculator.

What you should expect during the calculation

While every tool UI is slightly different, a typical wage backpay workflow follows this structure:

1. Enter your time range

   • The tool totals unpaid wage amounts from your start date through your end date.
2. **Apply Missouri’s default SOL window (5 years)

   • Under Mo. Rev. Stat. § 556.037, the calculation window is effectively constrained to 5 years as the general/default period (based on this article’s default approach).
3. Compute gross backpay

   • Hourly: hourly rate × hours by pay period
   • Salary: converted equivalent wage basis × periods
4. **Subtract already-paid amounts (if you entered them)

   • Periods where you received partial pay should reduce the remaining backpay estimate.
5. Check the output and breakdown

   • Look for total backpay and, if provided, a period-by-period breakdown so you can validate the dates and math.

Gentle reminder (not legal advice): If your underpayment began more than 5 years before your cutoff, DocketMath may exclude older periods under the general/default SOL window described above.

How changing inputs changes the output (practical examples)

• Move the start date forward (for example, by 12 months): total backpay usually decreases because fewer unpaid periods are included.
• Increase hourly rate: total backpay increases proportionally because each period’s wage calculation scales with the rate.
• Increase hours per pay period: total backpay increases because more work is being valued in each period.
• Enter partial “already paid” amounts: final backpay decreases because the tool reduces unpaid balances for those same periods.
• Shift end date later: total backpay increases because more periods are included (unless those extra periods are excluded by the SOL window).

Related reading

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